My process started with an HR conversation focused on questions tied to my CV. After that, I moved into a take-home exercise in JavaScript/TypeScript centered on async behavior and functions. The expectation felt like it was meant to test real-world correctness rather than memorized patterns.
Once I submitted, I had a code-view session with an engineer where we went through what I turned in and talked through the choices in my implementation. After that, there was another HR chat, and then I met with the hiring manager for what was mainly behavioral-focused questions about how I work and how I think about past experiences.
> 1 year
Difficult Negative Chile
I started with a screening interview where the questions were pretty standard—background, where I was coming from, and the usual context-setting. After that, they sent me a take-home assignment focused on concurrency and parallelism. They framed it as something that should take about 3–5 days, and I managed to finish it in roughly 2 days.
The assignment itself was challenging in the right way, but what ended up deciding it felt extremely sensitive to details. When the code was reviewed, the reviewer nitpicked something they said was a mismatch with the instructions. The tricky part was that the instructions were worded in a way that felt like it left room for interpretation, like a recommendation not to use Promise.all. I used Promise.allSettled because it was what I felt comfortable with, and that’s what got me rejected.
Reported
I ended up asking questions about what the front-end rounds looked like for what was described to me as a full-stack role at Facebook. The conversatio…
Unlock every Full Stack Engineer interview experience
