My process started with a friendly recruiter screen about my background and previous work. I could tell the recruiter was listening for specifics, and we went past the scheduled time because I kept adding context. A couple of weeks later, I still hadn’t heard back, and I eventually received an automated rejection.
The technical rounds focused more on practical engineering ideas than on algorithms. In the technical screening experience, I saw an OOP-style coding challenge and a system design interview that didn’t follow the typical hard-LeetCode format. One system design prompt involved designing an email system, and some follow-up questions used business and analytics vocabulary more than classic system constraints. Another coding experience ended early because of how I was working through Python in the moment. I felt nervous and messy at the start, and the interviewer wasn’t convinced after the first few minutes.
Even though the difficulty was described as easy or straightforward, the process still felt inconsistent in where it landed. I didn’t get an offer. My main reflection was that I could do the technical work, but the evaluation seemed sensitive to presentation and the interviewer’s expectations as much as to the underlying problem.
Location: United States. Overall feedback: Neutral. Offer status: No offer.
Discussion
Loading comments…