Step Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 7 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Step.
Step
Software Engineer
Entry Average Positive experience No offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Offer
Interview formats
Coding System Design Behavioral
Had an initial coding interview, then a virtual onsite with two more coding interviews and a system design interview. They sometimes add another round (coding or design) if they need more info. The experience was good overall, they let me postpone the interviews so I could prep, and gave feedback really fast (like within 2 hours of the initial coding screen). They even took time to give me actual feedback after rejecting me, which was nice. The recruiters and technical interviewers were all super friendly. If I'd gotten an offer, it would've been a tough decision because I had another offer I accepted. The interviews weren't super hard, but I got the vibe they have a high standard.
Confirmed questions5 questions
- Two of the three coding interviews (including the first) involved problems similar to what you'd encounter on the job, one with an OO and multithreading focus. The other was a DSA focused medium Leetcode problem.
- For coding prep, focus on writing quality code quickly. None of the problems required a lot of code, but you want it to be production-ready. The OO question was particularly dense and time-consuming.
- I don't suggest using verbose languages like Java or C++ unless you're very comfortable with them (I used Python).
Step
Software Engineer
Mid Easy Positive experience Decline offer 4 rounds
Interview process
Technical screen Technical screen Technical screen Onsite
Interview formats
Technical Coding System Design Behavioral
The interview process included one round of SQL (medium to hard difficulty), two rounds focused on coding with Data Structures and Algorithms (easy to medium difficulty), and one round with the hiring manager that covered data model design, a deep dive into past projects, and behavioral questions. Overall, it was a very positive experience. They really prioritized the candidate experience, which was great. Even though I was in a significantly different timezone, they were accommodating and split up the interviews to fit my schedule, unlike other companies where I had to do virtual onsites without sleep. Everyone I interacted with was very pleasant. The recruiter was genuine and didn't pressure me during offer negotiations. Honestly, it was the best interview experience I've ever had!
Confirmed questions1 question
- What at work makes you angry?
Step
Software Engineer
Mid Average Positive experience Accept offer 6 rounds
Interview process
Technical screen Onsite Offer
Interview formats
Coding System Design
The interview process included 6 technical rounds, consisting of 5 coding interviews and 1 system design interview. The coding interviews focused on general problem-solving using data structures and algorithms, while the system design interview was thorough, domain-related, and involved many follow-up questions. The interviewers were smart and kind, leading to deep discussions. The scheduling was flexible, allowing one onsite interview to be split into two time slots. Post-offer, there were over 4 follow-up meetings with the CTO and potential manager, indicating the company's value for candidates. The process seems geared towards hiring intelligent individuals via general coding tests, but might overlook suitability due to the absence of behavioral rounds or in-depth domain-specific questions during the interviews.
Confirmed questions1 question
- Can you tell me about your experience with general data structures and algorithms questions?
Step Software Engineer Interview Questions
Quoted word for word from Step interview reports.
“I don't suggest using verbose languages like Java or C++ unless you're very comfortable with them (I used Python).”
Read reports →“Solve medium LeetCode problems.”
Read reports →“Questions were Leetcode style, mostly medium difficulty with some hard ones.”
Read reports →“For coding prep, focus on writing quality code quickly. None of the problems required a lot of code, but you want it to be production-ready. The OO question was particularly dense and time-consuming.”
Read reports →“The interviewer scoped the system design problem at a small/medium scale and didn't ask about scaling up. I received feedback that they were looking for a design that scaled better. I think this is ultimately what led to my rejection, so I recommend discussing or designing for scale unprompted.”
Read report →“Data structure and algorithms questions were asked.”
Read report →“Design a system, possibly related to financial applications.”
Read report →“For the system design round, I was asked to design a specific feature for a well-known app.”
Read report →“What at work makes you angry?”
Read report →Formats, difficulty and experience
Across all 7 Step interview reports.