My process started with a Karat technical screening that surprised me with how much it emphasized conceptual basics before it ever got into coding. I was able to pick two topics to go deeper on, and I chose HTML/CSS and REST APIs. The kinds of questions felt pretty grounded—like identifying what a specific HTML tag corresponds to visually, and walking through how I’d create an endpoint for a new inventory item.
Then the interview pivoted abruptly into a live coding segment. The difficulty jump was the main thing that threw me: I had to solve LeetCode-style problems under time pressure and I ended up spending the full hour on the first greedy-algorithm question. I couldn’t find a similar example online, which made it feel less like a standard practice set and more like something unique. I didn’t pass all the test cases, and the whole experience left me thinking the transition between the conceptual part and the coding part wasn’t as smooth as I expected.
7 months ago
Average Neutral Mexico
I went through a sequence that took roughly a few weeks from start to finish, and although the people I spoke with were generally good, I ended up feeling like the process respected my time less than I expected. Early on, I had a recruiter screen and then a longer technical screen, followed by an onsite-style set of interviews that included programming, whiteboard work, a resume deep dive, and a code review, plus a final conversation with the hiring manager.
The technical side itself didn’t feel miserable; I felt like I did reasonably well across most parts. What hurt my experience was what happened after. I got no meaningful feedback from the recruiter and never really knew when I had been eliminated. When I tried to get clarity, I didn’t get responses back, and by the time more time had passed after the final round, it was clear there wasn’t going to be an offer.
7 months ago
Easy Positive Lahore
My first contact was a recruiter-level intake that set clear expectations about the role, the next steps, and what the process would look like. From t…
10 months ago
Average Neutral Austin, TX
After the recruiter call, I moved into a Karat technical screen where the focus was mostly practical coding. If I made it through, the process then sh…
> 1 year
Average Neutral Austin, TX
My interview sequence felt compact compared to the longer loops I’d heard about elsewhere. I ended up with five interviews total, where three were mor…
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
Recruiter & Initial Screening
The interview process typically begins with a recruiter call that sets expectations and outlines the steps ahead, followed by a technical screening, often conducted through a third-party platform like Karat. Candidates appreciated clear communication during this stage, but some reported issues with follow-up and responsiveness afterward.
Recruiter callKarat screeningExpectations
Technical Coding Assessment
Candidates face a mix of coding challenges during the Karat assessment, which often includes both conceptual questions and LeetCode-style problems under time pressure. The transition from conceptual discussions to live coding can be abrupt, and some candidates experienced technical issues during this phase, affecting their performance.
Coding assessmentLeetCodeTechnical issues
Onsite Interview Structure
The onsite interviews generally consist of multiple back-to-back rounds, including coding, system design, code reviews, and behavioral discussions. While the structure is thorough, candidates noted that the intensity and length of these sessions can be exhausting, and the pacing varies significantly between experiences.
Onsite interviewsSystem designCode review
Behavioral and Cultural Fit
Behavioral interviews are a key component, focusing on cultural fit and past experiences, often involving discussions about the candidate's background and expectations. Some candidates felt these conversations were constructive, while others noted a lack of clarity in feedback regarding their fit for the role.
Behavioral interviewCultural fitFeedback
Communication and Feedback
Candidates frequently expressed frustration over a lack of timely feedback and communication throughout the process, particularly after the final rounds. Many felt that the absence of clear follow-up left them uncertain about their status and the reasons behind their rejections.
CommunicationFeedbackClosure
Overall Experience and Difficulty
The overall difficulty of the interview process varies, with some candidates finding it reasonable and well-structured, while others felt it was overly challenging or chaotic. The perception of fairness and respect for candidates' time is a recurring theme, influencing their overall impression of the company.