My interview journey for a different engineering role started with an online coding test used as part of screening. The environment they gave me was extremely bare—more like a simple text editor than a developer-friendly setup, with no real tooling support. When a closing tag issue came up, it was hard to notice without syntax highlighting or editor help, and I ended up missing the deadline by only about two minutes.
I reached out to ask for a second chance and explained what happened, but the HR response felt cold and dismissive. They told me they couldn’t send another assessment, which made the whole thing feel unfair given how limited the tool was.
> 1 year
Difficult Negative Bengaluru
My experience turned into a frustrating interview mainly because the flow felt chaotic. In my case, the session lasted a long stretch and the interviewer seemed unprepared about what to ask. After I managed to solve two coding problems successfully, the interview shifted into giving me additional problems to handle, and then the conversation abruptly turned into general commentary about needing to work on many things.
The other side of the same kind of bad experience was that the interviewers didn’t appear to have done the basic upfront review—one interviewer didn’t read my background properly and didn’t seem to have a plan for the assessment. Even when the format included an online assessment plus a technical interview, the questions didn’t feel connected to my resume or job description. The interviewer’s attitude also swung during the call, which made the whole thing even harder to stay focused through.
> 1 year
Average Neutral Algeria
My technical interview was very JavaScript- and front-end heavy. I got asked about the event loop, async and await, promises, callbacks, and even Reac…
Unlock every Frontend Engineer interview experience