I first did an initial screening, which then led into a technical screen that was clearly divided into three parts: a discussion of my project, domain questions, and then LeetCode-style coding. I went in expecting the domain portion to be aligned with the project I’d talked about, but the vibe ended up feeling a bit cold.
During the domain section, the interviewer seemed to jump around and grab questions on the spot, and I got hit with a lot of basic, exam-like topics that I genuinely didn’t anticipate. It threw off my rhythm because the coding and project discussion were things I could prepare with more confidence, while the domain questions felt random.
6 months ago
Difficult Negative London, England
My process barely got off the ground. I had an initial interview where I could already tell it wasn’t going well for me—the recruiter’s demeanor felt disinterested and even moody, like they were tired. The conversation did include the usual logistics-style questions like salary and other standard screens.
Even with those familiar questions, the interaction felt off in a way that made me doubt my chances right from the start. I didn’t feel like I was being treated as a serious conversation partner, and I walked in expecting I would fail.
Reported
Remote
The onsite was the most intense stretch for me. I went into it expecting multiple technical rounds, and I ended up with a four-round sequence that mix…
Unlock every Backend Engineer interview experience
