My interview started with a recruiter/HR-style connect where I was evaluated on fit and basic alignment, and that short stage set up the rest of the process. After that I went into a sequence that felt fairly well defined: a technical interview, then a managerial discussion, and finally an HR conversation centered on fit and next steps.
What I noticed most was the structure of the questioning. The technical portion pulled in role-relevant areas and wasn’t presented like a random collection of trivia. By the time I reached the managerial conversation, it felt less about throwing coding problems back at me and more about understanding how I approached work and how I’d collaborate.
7 months ago
Average Positive Lehi, UT
After a recruiter screen, my technical process started with a live coding exercise online that lasted about 45 minutes. What stood out was that the coding portion felt interactive—I wasn’t just reciting memorized patterns, and the interviewer leaned into dialogue where I could demonstrate how I actually thought.
Next came the onsite stage, split into multiple sessions, each around 90 minutes. The focus was still technical, but the overall style stayed conversational, and I wasn’t hit with an especially harsh LeetCode-like gauntlet. Before that, I’d also done a phone intro and then moved through a coding assessment step, followed by additional interviews that I didn’t get to fully complete.
9 months ago
Average Neutral Utahn, UT
My first step was a phone screen focused on confirming my background, interest, and fit. After that, I went into technical interviews that leaned on t…
9 months ago
Difficult Positive United States
I went through a longer loop that required multiple referrals—there were five interviews total, and I needed at least four referrals to be considered.…
10 months ago
Average Positive Provo, UT
My process started normally—HR and recruiters were in touch early, and after I cleared the technical parts I kept moving into later rounds. For me, th…
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
Interview Structure
The interview process typically begins with a recruiter screen followed by a sequence of technical and HR interviews, often including managerial discussions. Candidates appreciated the clear purpose and organization of each round, which helped them understand what to expect.
Recruiter screenTechnical interviewHR discussion
Technical Evaluation Style
Technical interviews focus on core software engineering concepts and practical problem-solving rather than purely theoretical or trick questions. Many candidates noted that the interviews felt collaborative, allowing them to demonstrate their thought processes and coding skills interactively.
HR and managerial interviews emphasize assessing cultural fit and collaboration style, with a focus on how candidates communicate and work with others. This aspect is often less formal and more conversational, allowing candidates to express their personality.
Cultural fitCommunicationBehavioral assessment
Process Length and Communication
Candidates experienced varying lengths of the interview process, with some reporting delays and a lack of communication during the decision-making phase. Clear and timely updates were highlighted as crucial for a positive experience.
Process lengthCommunicationDecision delays
Difficulty of Technical Rounds
The difficulty of technical interviews varied, with some candidates facing challenging questions while others felt the assessments were manageable. Candidates noted that the technical bar was taken seriously, particularly in areas relevant to the role.
Many candidates expressed frustration with the final decision-making process, citing instances of ghosting or vague feedback after completing multiple rounds. This aspect significantly impacted their overall impression of the interview experience.