My interview journey had a pretty specific shape: first I took an online assessment, and then I went into a series of technical interviews centered on data structures and algorithms. Along the way, there was also a managerial or HR conversation.
The most distinctive part was a craft demo, basically a project presentation where I showcased work from my past. It wasn’t just describing it—I had to walk through it in a way that connected to the engineering craft part of the role.
> 1 year
Difficult Positive Israel, TX
My biggest technical hurdle was a very specific coding task: I had to implement a class that replicated the exact behavior of JavaScript’s Promise and then, including edge cases and the tricky details that make it behave like a real Promise. The expectation included correct handling of asynchronous execution, error handling, and state transitions, not just a simplified version.
It was difficult, but it was also focused—the whole point was to see if I could match real Promise semantics closely rather than approximate the idea. I ultimately received an offer, and that result made the effort feel worth it, even though the task itself was undeniably hard.
> 1 year
Average Negative India
I went through a fairly structured process: a screening round, then four technical-style conversations that included an introduction and craft discuss…
> 1 year
Difficult Negative United States
My process started like it was going to be normal, with recruiter and tech phone screens. Then the wheels fell off once I hit the onsite. The biggest …
Unlock every Frontend Engineer interview experience
