My first step for the Staff Engineer role was a coding test on Coderbyte, and it felt a bit unfriendly from the start. The test had exactly two questions and gave me 75 minutes to complete them.
The first problem was an LRU cache implementation, and the second was a binary search question at a medium level. I focused on getting the logic right and finishing within the time window, and I ended up passing the test.
6 months ago
Average Positive Dublin, Dublin
The process I went through started with a recruiter call, and then I was pulled into a multi-round interview day. I had three rounds scheduled back-to-back: first a technical discussion, then a behavioral round with multiple interviewers, and then another behavioral-plus-technical conversation with my future manager.
Across the technical parts, the focus leaned heavily on core engineering skills like data structures and algorithms, with additional general technical questions mixed in. One of the conversations also included a DSA problem. On the more difficult end, there were signals that they were probing beyond surface-level coding—things like low-level and high-level design thinking, database design topics, and class modeling came up, along with a hiring-manager-style discussion of both behavior and technical skill.
> 1 year
Easy Negative Czech Republic
I went through a fairly typical, multi-round Groupon software engineer interview flow, but the details around timing and communication ended up making…
> 1 year
Average Positive Poland
After the recruiter call, I ended up going through a rapid sequence of online interviews with different people—directors, VPs, and engineers—scheduled…
> 1 year
Average Negative Ireland
I interviewed for a senior role connected to a team doing migration work to AWS. Right before the interviews, I asked directly whether the focus would…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Initial Screening & Recruiter Call
The interview process typically begins with a recruiter call to discuss background and fit, followed by a technical phone screen that often includes a coding problem. Candidates noted that the recruiter was generally friendly and provided useful preparation materials.
Candidates undergo a coding assessment, often using platforms like Coderbyte or HackerRank, focusing on algorithmic problems and data structures. The assessments can be narrow in scope, typically consisting of one or two main problems to solve within a set time limit.
The main interview day usually consists of multiple back-to-back technical rounds that cover a range of topics, including data structures, algorithms, system design, and sometimes database design. The interviews may blend technical and behavioral questions, with a focus on how candidates think and approach problem-solving.
Behavioral interviews often utilize structured formats like STAR to assess candidates' soft skills, teamwork, and leadership experiences. Interviewers tend to revisit similar themes across different conversations to triangulate candidates' responses.
Behavioral interviewSTAR methodTeamwork
Communication & Follow-Up
Candidates reported mixed experiences regarding communication and follow-up after interviews, with some experiencing long delays and lack of clarity on next steps. While some found the process organized, others felt it was chaotic and unprofessional, leading to frustration.
CommunicationFollow-upCandidate experience
Overall Experience & Outcome
The overall interview experience varied significantly among candidates, with some describing it as structured and positive, while others felt it was disorganized and disrespectful to their time. Many candidates noted the unpredictability of outcomes despite performing well in technical assessments.