Strava Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 19 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Strava.
Strava
Software Engineer
Senior Easy Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen
Interview formats
Behavioral Technical
The interview process felt like a typical Bay Area experience, starting with a positive, altruistic vibe from the recruiter that quickly shifted to a negative, judgmental, and dismissive tone during the hiring manager interview. The recruiter was very friendly, and we had a great rapport, leading to scheduling an interview with the hiring manager. However, the hiring manager interview seemed rushed, possibly because he thought we only had 30 minutes instead of the scheduled 45. He asked two questions, and it felt like he was annoyed that the interview wasn't over yet. The only question that felt meaningful implied that without a specific experience, I would be incapable of performing the job.
Confirmed questions0 questions
No confirmed questions were included in this interview report.
Strava
Software Engineer
Intern Average Positive experience No offer 2 rounds
Interview process
Technical screen Recruiter call
Interview formats
Coding Behavioral
The interview process was fast and quite good, with two rounds. The first was a live coding session where I had to develop a small part of a feature using Java or Kotlin, and since I interviewed for the Android team, most questions were related to that. The second round was a managerial interview, which was much easier.
Confirmed questions1 question
- What are the architectural standards for an Android app, such as MVVM?
Strava
Software Engineer
Entry Easy Positive experience No offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Coding Technical System Design Behavioral
It started with a recruiter screen, then a hiring manager screen. After that, there was a coding challenge involving a DSA-style question related to Strava's business, similar to LC easy-medium problems. The process concluded with a virtual onsite that included a coding design, a systems design (focused more on reasoning than a traditional approach), and a final chat with the hiring manager.
Confirmed questions0 questions
No confirmed questions were included in this interview report.
Strava Software Engineer Interview Questions
Quoted word for word from Strava interview reports.
“What is the output of this Java string operation?”
Read reports →“Write a program to find the local maximum and minimum in an array.”
Read reports →“Could you find the largest climb, which is the largest contiguous group of altitudes that get sequentially larger, given an array of altitudes?”
Read reports →“What valuable data points can be derived from Strava user activity logs related to elevation changes?”
Read reports →“What are the architectural standards for an Android app, such as MVVM?”
Read report →“Can you print custom descriptions for the sorted objects?”
Read report →“Can you create a data structure to represent a deck of cards, including a shuffle operation?”
Read report →“How would you add shoe type to a Strava activity, and what are the use cases for this?”
Read report →“What is your reason for wanting to join Strava?”
Read report →Formats, difficulty and experience
Across all 19 Strava interview reports.