The interview process was a typical one for any engineering type role. Initial call is to talk with a recruiter and find what area you would like to work in (unless you applied to a specific role) and a follow up call with an engineer going over a simple data structures and algorithm question.
Once you have passed these you are asked for an onsite which is from 9:00am - 2:30pm or so. The interviews consisted of some infrastructure design questions, systems trouble shooting (SRE specific), and some SQL / data model questions.
Receiving replies from companies on why they decided to pass on you as a candidate is few far and between. I received a follow up e-mail and call explaining where why I was not a good fit for the position. This in itself really helps with the job search going forward and it is great to have Stava be this forward and open with candidates.
Not going to share their questions. Just study your typical systems engineering / dev-ops and you will do fine.
The following metrics were computed from 1 interview experience for the Strava Site Reliability Engineer role in San Francisco, California.
Strava's interview process for their Site Reliability Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Strava's Site Reliability Engineer interview process in San Francisco, California.