My process started with a coding interview that took a few hours to complete and then I spent time cleaning it up so it was ready to submit. There wasn’t any recruiter call or proper briefing about the hiring steps—so I uploaded my code and waited.
It was easily one of the slowest parts: I submitted within a few days and then didn’t hear back for almost three weeks. When they finally reached out, it turned out they “couldn’t find” the submission, so they asked me to send it again. After that, I received a generic rejection and then I got ghosted when I asked for feedback.
> 1 year
Easy Neutral United States
My first step was a search algorithm assessment, and I finished it over a few days. After that, I moved into a technical interview that felt easy overall, and I was asked a programming problem involving binary trees. The question sounded approachable, and I actually misstepped on it, which was a frustrating moment because the problem itself felt straightforward.
The conversation didn’t stop at that coding-focused area. The interviewer also asked me software engineering questions touching multi-threading and a core-dump style concept, and we even got into a more conceptual differentiation question about something like double differentiation when finding maxima.
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
