Step Software Engineer interview typically runs 4 rounds: recruiter screen, technical coding rounds, behavioral/Googleyness, and team match. It usually takes weeks to months and is notably DSA-heavy with live reasoning and follow-ups.
$106K
Avg. Base Comp
$203K
Avg. Total Comp
4-6
Typical Rounds
2-6 weeks
Process Length
We’ve seen a very consistent pattern across Step’s software engineer interviews: the bar is not just whether you land on the right algorithm, but whether you can narrate your reasoning cleanly under pressure. Multiple candidates mentioned live coding in shared docs or screen shares, with interviewers pushing on follow-ups, edge cases, and complexity as the solution unfolded. That shows up in everything from graph and interval problems to backtracking, heaps, and dynamic programming. Even when the question itself was familiar, candidates who stayed calm and explained their approach step by step tended to describe the experience more positively.
A recurring theme is that Step likes problems that expose how you think when the prompt is a little underspecified. We saw candidates get topological sort, caching for a blob store, rule-based simulation, and even oddball logic prompts like the bottle riddle or the coin-sized escape question. Those aren’t there to reward memorization; they’re there to see whether you can ask the right clarifying questions and adapt quickly. The strongest signal is structured problem decomposition, especially when the interviewer keeps the conversation moving with follow-ups rather than giving much feedback.
Another thing we’ve noticed is that Step doesn’t treat fundamentals as “easy” just because the question sounds basic. Candidates were asked about quicksort, merge sort, BFS, HTML5, Python methods, and time complexity in a way that still required precision. In other words, they seem to value engineers who can move comfortably between coding, CS basics, and practical tradeoffs. If there’s one non-obvious takeaway from the candidate pool, it’s that Step rewards breadth plus composure: people who can switch from a classic DSA problem to a design-style discussion without losing clarity.
Synthetized from 20 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Step process.
The toughest part of my Step interview was that it wasn’t just about getting to a correct answer — it was about how I reasoned through the problem out loud. My first round was a remote video interview, and the interviewer gave me a challenging algorithmic question and expected me to break it down step by step while talking through my approach in real time. That set the tone for the rest of the process: they cared a lot about problem-solving and communication, not just whether I could code quickly.
I also had an onscreen technical round that was more specific: a graph problem involving topological sort. It sounded simple at first, but I had to ask a lot of clarifying questions to understand exactly what the interviewer wanted before I could move forward. That was a good reminder that they were testing how I think through ambiguity. In addition to the coding rounds, there were behavioral and background-style questions, including questions about my resume, interests, and preferred roles or locations. One of the more unusual prompts was a logic-style question about how to get out of a bottle if you were the size of a coin, which felt like it was meant to test reasoning from different angles rather than pure technical depth. Overall, the process felt structured and fairly rigorous, with multiple rounds covering coding, design, and behavioral topics. I didn’t make it through, but the main takeaway was to be very comfortable explaining your thought process clearly and to ask clarifying questions early when the problem statement is underspecified.
Prep tip from this candidate
Practice explaining algorithmic solutions out loud, especially graph problems like topological sort, and get comfortable asking clarifying questions before you start coding. Be ready for at least one round that mixes resume/background discussion with a reasoning-style puzzle rather than pure coding.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Step
Write a query to get the percentage of search queries where all ratings are less than 3 rounded to two decimals
| Question | |
|---|---|
| Client Solution Pushback | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Rolling Bank Transactions | |
| String Shift | |
| Employee Salaries | |
| Raining in Seattle | |
| P-value to a Layman | |
| Closest SAT Scores | |
| Top 3 Users | |
| Weighted Keys | |
| Prime to N | |
| Maximum Profit | |
| Hurdles In Data Projects | |
| Over-Budget Projects | |
| Sum to N | |
| Find the Missing Number | |
| Over 100 Dollars | |
| Find the First Non-Repeating Character in a String | |
| Scrambled Tickets | |
| Minimum Change | |
| Payments Received | |
| Last Transaction | |
| Rectangle Overlap | |
| Size of Joins | |
| Download Facts |
Synthesized from candidate reports. Individual experiences may vary.
The process often began with recruiter outreach or an initial resume screen. Candidates were asked about their background, coding experience, interest in the role, preferred level, and sometimes location fit before moving on.
Many candidates completed an online assessment before live interviews, usually with one or two coding problems. In some cases it was a true algorithm screen with medium-difficulty questions, while in others it was more of a personality or behavioral-style assessment.
The first live round was typically a phone or video interview with shared coding, often in Python or a Google Doc. Interviewers expected candidates to talk through their reasoning step by step, ask clarifying questions, and solve a mix of easy-to-hard DSA problems.
Candidates then went through several technical rounds covering data structures and algorithms, with difficulty often increasing across the loop. Common topics included arrays, strings, graphs, trees, stacks, heaps, linked lists, intervals, dynamic programming, and rule-based simulation, plus follow-ups on complexity and edge cases.
At least one round focused on behavioral and background questions. Candidates were asked about motivation, resume details, teamwork, difficult coworkers, career goals, and why they wanted to work at Step, alongside broader judgment or logic-style prompts.
Some candidates reached a design-focused round that was either classic system design or ML/system design. Examples included designing a simplified Google Maps, a delayed task scheduler, or an end-to-end ML system, with emphasis on tradeoffs, scale, consistency, and error handling.