The process was frustrating. In one early call, the hiring manager seemed to have reviewed my resume around the time of the interview. They asked roughly seven or eight questions, with follow-ups when an answer prompted more curiosity, but the process still felt uneven and ended with a quick rejection signal.
Another stage was a video phone screen with Leadership-Principles behavioral questions and distributed-systems jargon. I explained a solution using a particular tech stack and architecture, but it seemed the interviewer wanted specific terminology. Then I was asked to implement a calculator in a text editor without a description. When I asked for requirements and input details, I was pushed to code anyway. I used a typical DSA-style approach, which was not what they wanted, and was later questioned about OOP principles and why my structure did not reflect them.
It felt less like a fair evaluation and more like guessing the mental model they wanted. I regretted the effort because the interaction left confusing rather than actionable signals.
Location: Seattle, WA. Overall feedback: neutral. Offer status: no offer.
Discussion
Loading comments…