Taro Logo

Software Engineering Interview Experience - San Francisco, California

November 1, 2016
Negative ExperienceNo Offer

Process

Applied online, was contacted by recruiter and had an interview set up. The interviewer was about 45 minutes late to the interview, and I had emailed the recruiter that he was running late (before he connected later). Despite the lateness and me making it clear that the reservation for the private room I used to interview was about to end, I was still asked to continue the interview. Overall, it was still an interesting and productive conversation with the interviewer, as I had read the Strava engineering blog and was familiar a bit of their work in software infrastructure.

We then moved on to the coding portion of the interview, which is when things started to go south. The question was supposed to relate to extracting some useful information from a Strava user, but in my opinion it was posed in a very convoluted and unclear manner. Despite me asking several questions about what to implement, I wasn't even sure of what my function should return (he said it's up to me to return something useful, I gave a few suggestions and he didn't seem to like any of them). I finally just told him I was going to implement a method that returns the number of climbs a user did. I coded this up quickly (it was easy), and he just said okay and we moved on to questions for him. I could tell at this point by the quick change in demeanor that I wouldn't be moving on in the process.

Overall, a somewhat unprofessional experience with the late arrival and not being able to reschedule (I understand that stuff happens and people are late, but if this is the case I shouldn't be expected to continue the interview, especially if my room's time is about to be up), as well as a weird technical question. From what I've read though, Strava is a great place to work so I will be applying again next year.

Questions

Some question on detecting elevation changes in a user's run/bike. The interviewer wanted me to discuss what possible things we could return and I gave some ideas. Overall it was unclear what exactly I had to implement. So I just implemented a method that returns the number of elevation climbs the user did.

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Strava Software Engineering role in San Francisco, California.

Success Rate

0%
Pass Rate

Strava's interview process for their Software Engineering roles in San Francisco, California is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral0%
Negative100%

Candidates reported having very negative feelings for Strava's Software Engineering interview process in San Francisco, California.

Strava Work Experiences