My first technical round ended up being heavily focused on a React-specific framework question, and it didn’t feel very friendly if React wasn’t already in my muscle memory. There weren’t any algorithm or data-structure problems attached to it, which actually caught me off guard a bit—mentally I was expecting something more broadly “CS interview” flavored.
Overall it landed as an okay experience. The interviewer was helpful and communicative, and I could tell they were trying to move things along, but I still walked away thinking it should’ve been more of a general technical screen rather than so framework-specific.
> 1 year
Difficult Positive São Paulo, São Paulo
My process started with a phone screen focused on a React problem in HackerRank. From there, the onsite shifted into multiple rounds: one more React interview, then systems design, then domain knowledge, and finally a discussion with the hiring manager.
The overall feel was difficult because it wasn’t purely algorithms or purely system design—it mixed framework-level work with broader design and then a manager conversation. I had to be ready to switch contexts quickly.
Reported
I tried to get clarity on the DoorDash interview process because I didn’t want to walk in blind. I was specifically looking for insights on what types…
Reported
I asked about what the very first step was for the front-end interview process at DoorDash, mostly because I wanted to map out the path before committ…
Reported
I was trying to get ready for a front-end technical interview where I’d be expected to build UI components. The key detail I had was that the focus wa…
Unlock every Frontend Engineer interview experience
