Taro Logo

Software Engineer Interview Experience - Bellevue, Washington

August 1, 2023
Negative ExperienceNo Offer

Process

You are contacted by a person that has been at the company for a long time. They will be coordinating most of the logistics until the front desk is tasked with scheduling your flight and hotel.

The first interview is a technical phone screen where they probably ask you to do atoi. You should expect to do this basically perfectly. They'll also ask you some questions about your experience before the question to assess your technical depth. That's about an hour of time, including questions for you to ask at the end.

If you do well, you'll be flown out within the next couple of weeks to interview on site, or you can interview remotely (the jobs are onsite).

The onsite loop is as described in the majority of the reviews here. The questions are boring and they expect you to answer them in the way they usually see them. As I answered them in a different way, however optimal (up to debate), they were visibly/audibly frustrated.

Each interview is a pair of employees, one pretty senior and one not as senior, typically from teams you'd be matched into. I'd say about 10% of them were personable and cared about me being there that day.

The onsite loop day starts with two coding questions on a whiteboard (it's a very big whiteboard). I think I did okay and was able to solve the problems while accepting criticism and working with the interviewers (not sure they liked that, though).

Then there's a lunch interview, which was awkward. I'd rather them have just let me eat alone and then asked me the same questions.

At that point, I thought I was going to be kicked out because I was waiting a while and they were probably deliberating as a halfway point. I believe anyone can veto you during the process.

I then had a non-technical interview as my 4/5th question, which I believe I did well on, but the interviewers were unenthused.

Five minutes after that interview ended, two people that interviewed me came back and ended the loop early with the following feedback:

  • Not enough evidence of technical depth
  • Not enough evidence of customer requirements gathering

They advised me to interview again in the future when I have more experience. This was confusing feedback given my background in startups, but maybe they asked poor questions or I didn't answer their questions in a way that was satisfactory to them.

I would have hoped for actual specific feedback. I'm pretty sure they just did not like me from a culture fit perspective, which is okay!

The office is super cool and if you get invited onsite, you might as well go just to check it out.

My take on Valve at this point is that as a small company, they have little incentive to recruit new people that can disrupt their structure and bonus incentives. They have a lot of money and cool tech at their disposal, so I hope they do good with it.

I will not be recommending any of my friends interview there.

Questions

atoi, min rect dist, simple calculator using string/number builtin funcs to make it easy, lunch interview to assess customer thinking, game scoring system

Was this helpful?

Interview Statistics

The following metrics were computed from 10 interview experiences for the Valve Software Engineer role in Bellevue, Washington.

Success Rate

10%
Pass Rate

Valve's interview process for their Software Engineer roles in Bellevue, Washington is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive60%
Neutral20%
Negative20%

Candidates reported having very good feelings for Valve's Software Engineer interview process in Bellevue, Washington.

Valve Work Experiences