I applied online. The process took 3 days. I interviewed at Veeva Systems (Pleasanton, CA) in Oct 2017
Interview
The interview process was, as a whole, fine. I talked with the hiring manager on the phone, nailed it, gave my salary desires. They said they couldn't match them exactly, but would do what they can.
Came in for an in-person interview. Interviewed with several people. It went well.
Came in for ANOTHER in-person interview with a development manager. It went well, as well.
Then they hit me with an offer that was only 2/3rds what I was asking (the offer -- base + stock -- was less than I was making 10 years earlier, base only). When I refused immediately, the hiring manager acted extremely agitated that I would refuse such a great offer, and said that this area doesn't pay as well as San Jose (which isn't true, since I'm currently working in Pleasanton at a different company, making as much as I was asking them for).
I didn't so much mind that they couldn't offer what I wanted. What I minded is that they had me waste my time interviewing 3 times KNOWING they couldn't even come close (it was a literal 33% drop from what I was asking). It was a waste of my time, and indirectly led to some extremely bad personal situations.
Interview questions [1]
Question 1
Given an infinite amount of resources, how can you determine which build of software caused a problem?
I applied online. I interviewed at Veeva Systems (Pleasanton, CA) in Oct 2017
Interview
Had a phone screen with the hiring manager. It went well. Then I came in, and interviewed with several other people in test, and a developer. That went well.
They told me at the time they couldn't _quite_ meet what I was asking, but made it sound like they would do their best to come close.
So they asked me to come in a third time, to speak with a more senior developer. That was the only moderately challenging interview I had.
The next day, they called me. With the most ridiculously lowball offer I ever heard in my life (including stock, it was less than I'd been making base 10 years earlier, and about 30% less than I was asking, which was already lower than I'd been making at my old job).
They said that this was the best they could offer in the East Bay. Which is wrong, given I have the same role now less than 5 minutes from their office and am making way more.
I wouldn't care about the low offer, if they didn't call me back in and waste my time when they knew they had no intention of coming close to what I was asking. (Seriously, the offer was so low as to be insulting)
Interview questions [1]
Question 1
If you have a range of builds where a bug might have occurred, what's the most efficient way to determine where it did occur?
