I started with a take-home where they’d share a GitHub link and the task was to build an API in the language and framework of my choice. There wasn’t much of a deadline, but the expectation was that it was usually solvable in about an hour or two, so I focused on getting a clean, complete submission rather than trying to over-engineer it.
After I turned it in, I ran into the same dead end: I either didn’t hear back at all or I only received silence after submitting something that was ready. One time I sent what I thought was a good submission, but even when I offered to give the reviewers access, I still ended up with an email that effectively closed the loop—automated and unhelpful. The process felt like it moved on without feedback, and I didn’t make it to any further rounds.
12 months ago
Average Positive Madison, WI
My process started like clockwork with a take-home assessment, and if I passed it, the next step was a technical call where I walked through what I’d built and explained my thinking. That call felt pretty focused on the take-home—almost like they wanted to see whether I truly understood the decisions I made—then I was pulled into an all-day interview.
At the super day, I went through several technical rounds in a single stretch. I started with a coding interview that landed in the LeetCode “easy” lane, then moved into object-oriented design, and later into system design. A behavioral interview rounded it out, followed by a wrap-up with the hiring manager. The pace was intense, but the structure was clear: short, timed segments and lots of discussion anchored to technical fundamentals.
12 months ago
Average Neutral United States
After applying, my first real step was a take-home project that felt more scrutinized than the usual “send code and wait” style. I submitted it, and i…
> 1 year
Average Negative United States
I went through a take-home first, then expected a structured review of what I built, but what I got felt more like a blend of a quick screen and a tec…
> 1 year
Average Negative United States
My first step was always a take-home that they described as a short effort, sometimes “a few hours,” and it included deployment and integration with t…
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
Take-home Assignment
Candidates start with a take-home project that typically involves building an API or application, with expectations for production-level quality and thorough documentation. The time commitment can be significant, often requiring several days to complete.
APIProduction-readyDocumentation
Technical Review & Walkthrough
After submitting the take-home, candidates participate in a technical review where they explain their work and decisions to engineers, focusing on understanding rather than just correctness. This stage is crucial for demonstrating comprehension of the project.
Technical reviewCode walkthroughUnderstanding
Structured Interview Loop
Successful candidates move into a structured interview loop that includes multiple technical rounds, such as coding, object-oriented design, and system design, often conducted in a single day. The pace is intense, with short, timed segments.
CodingSystem designObject-oriented design
Behavioral & Communication Assessment
Interviews also include behavioral components, assessing candidates on communication skills and how they articulate their thought processes during technical discussions. This aspect is emphasized as much as technical ability.
BehavioralCommunicationCollaboration
Feedback & Communication Issues
Many candidates report a lack of meaningful feedback throughout the process, often receiving generic rejections without constructive criticism. This can lead to frustration and a feeling of wasted effort.
FeedbackCommunicationFrustration
Overall Experience & Expectations
Candidates express mixed feelings about the overall experience, noting that while the process is structured, it can feel disorganized at times, particularly regarding scheduling and clarity of expectations. Some feel the difficulty of the interviews does not align with the role level.