Taro Logo

Software Engineer Interview Experience - San Francisco, California

February 1, 2013
Negative ExperienceNo Offer

Process

The interview process took a ridiculously long time from start to finish, for starters. I was actually an internal referral and from initial contact through the 2 screens all the way to the onsite took over 2 months. Then it took them almost 3 weeks to get back to me to tell me they didn't want me. I've been in this space for a while and that seemed odd to me. The rather large unnamed company I work for typically has about 2 week turn-around for remote applicants.

They did the typical 2 phone screens and flew me out to San Francisco to interview on site. Most of the guys on my loop seemed to not know each other at all and the transitions were rather awkward. There was no real pattern to the questions except for the fact that they covered your typical Computer Science fundamentals.

Actually, I expected more questions about scale and design. The only person who touched on that sort of thing was a senior software engineer but it was really round about how he got to it.

Overall, not a really bad experience, but based on the feedback, I have to believe they could have made up their mind more quickly.

Questions

None of their coding questions was unexpected. They all were all fairly straightforward questions about Hash Tables, finding palindromes, etc. However, the one which really threw me was when one of the Senior engineers asked me to describe a "cool" project I worked on. This in itself wasn't unexpected but his aggressive attitude was. A very short time into my explanation he got kind of aggressive and started bashing the project for its perceived faults, despite the fact that he hadn't touched on the actual requirements.

To my personal discredit, rather than point out that fact, and lay out the requirements and the technical merits of what I did, I got defensive and it all went down hill. Note to other interviewees... don't do that :). Just stand your ground and seek clarification or state clearly why you think their viewpoint isn't valid. In retrospect, this was probably a test of my disposition which, I don't mind saying, I failed!

Was this helpful?

Interview Statistics

The following metrics were computed from 75 interview experiences for the X Software Engineer role in San Francisco, California.

Success Rate

29%
Pass Rate

X's interview process for their Software Engineer roles in San Francisco, California is very selective, failing most engineers who go through it.

Experience Rating

Positive52%
Neutral21%
Negative27%

Candidates reported having very good feelings for X's Software Engineer interview process in San Francisco, California.