My experience started with a recruiter screen, then I met a dev for a follow-up. After that, I was given a small aptitude-style test and a short development assignment that I completed on my own. The work itself wasn’t the issue—it was the lack of follow-through. After about two weeks, I was rejected with no meaningful feedback or explanation, just silence where I expected at least a summary of how the assignment went.
What lingered with me was the feeling that I’d spent time on something substantial and never got closure, especially since the process had moved far enough that I expected at least a minimal debrief. I didn’t end up talking again beyond that point, and there wasn’t any clear next step.
> 1 year
Difficult Positive United States
I went through a pretty long, structured process that didn’t feel like a quick screening-to-offer path. It started with a cognitive pre-assessment, followed by a 30-minute meeting with a hiring manager. Then came a take-home assignment that took at least a full day of dedicated time, which was easily the most time-consuming part.
After that, I had a “power day” packed with three segments: one hour of algorithms, one hour focused on front-end system design, and then a 45-minute behavioral conversation with the CTO. Overall, it was a lot to keep switching gears, but the interviewers felt down to earth throughout, and the package seemed highly competitive.
> 1 year
Average Neutral United States
My process started with an online IQ test, then moved quickly into a recruiter phone call where I talked through my experience and what I was looking …
Unlock every Frontend Engineer interview experience
