Real Interview Experiences
Learn what to expect directly from candidates and interviewers who've been through it.
Interviewed recently? Share your experience to try it free, or become a member for full access.
“Interviewer were all really nice. Technical portion requires to be thorough in explaining thought process”
“Very thorough and difficult process. End to end you're doing a recruiter call, IQ/competency assessment, hiring manager interview (which was a mini case question), a combined 1.5 hour product sense + product execution interview, an engineering working session and a final in person presentation round. I only made it to the product sense. Did not like my two interviewers and the recruiter as they were not aligned with what I should expect. The recruiter had me prepare completely differently. Overall, they try to force fit the product interview frameworks and styles you'll find in big tech. ”
“The recruiter was exceptionally transparent and provided an accurate roadmap of what to expect. Their preparation tips were spot-on, which is a rare find in high-stakes tech recruiting. What didnt go well? The process was significantly more demanding than other major tech companies, leading to a bit of "interview fatigue" by the final stage.”
“It was smooth and well-coordinated. Emphasis on your life story and how you got to where you are now, and why you are seeking out this role. Execution/product sense interview went well - it was specific to Shopify's business line, so I had to understand their user segments. ”
“It was quite a lengthy process. The TAT was quite long and slow as well. Didn't receive a lot of feedback to prepare better for the next rounds, but overall was a great learning experience.”
“Too much bureaucratic process. Be prepared for ghosting. They expedite after onsites. Negotiation can take few rounds. Be patient, they do not throw away strong candidates.”
“This was my first interview ever, and I was nervous. However, the introduction went really well and caught the interviewer’s attention. At the start, I mentioned that my areas of interest were "geopolitics" and "music production". Since many people these days enjoy discussing geopolitics, he followed up by saying he was interested in it too and asked me about recent events I knew about. For the first 10 minutes, we talked about geopolitics, and It was a memorable first 10 minutes in my very first interview. Then we got back to him asking me technical questions. I think i had a good first impression. He first stated with asking general programming questions, about Object oriented programming, Polymorphism. I was good here. Then we got on topic of Database. Here i fumbled big time. First question "what is database?" My nerves answer: a place where we store data. I felt it me fumbling, i was nerves and never practice about database, SQL for this interview. Then here we go another fumble, He asked "What are operators in SQL?" I brain-fogged and said am not aware of this answer, i knew but in moment i did not understand the meaning of "operators", they he clarifies saying addition, subtraction. And it clicked in my mind, but still my answer was in 2 lines: "Plus, minus, subtraction, division, Arithmetic, Logical, Comparison" thats it. I should have expanded on it and explained in little more detail. I think i did this because it was my first interview and in my mind going through was i fumbled very bad and am not gonna be selected i lost my all hopes in between the interview. till now its been in total 20-25 minutes, we switched to last part which was coding part. He said he asked this question to last guy and he did not able to answer this question. I was confident on my problem solving and coding skills, but yeh as you could tell by now i suck at communication. The coding question was: "Given a array on integers return a frequency of each element". I though this is pretty easy and first explain him my first approach to problem, start implementing, code ran and passed on first run. Explain him what approach i used and why everything in detail, with time and space complexities. So the two best parts were long intro and last coding problem. I also asked him at the end what I could improve on, and he mentioned my theoretical knowledge. He explained that interviewers don’t expect you to recite textbook definitions word‑for‑word, but they do expect you to understand and be able to talk about the main ideas or high‑level concepts behind each topic. I somewhere knew that am not getting selected, and i was right.”
“The process was straightforward. It is a technical interview along with experimentation trade-offs. ”
“Started off with recruiter screening with light technical questions, and walked me through all the rounds. Next, I had several rounds. Very light coding, mostly case studies and stats knowledge. Very theory/application focused.”
Preview full access of other recent interview experiences
“The weirdest Anthropic round was the company values interview. It was almost like a therapy session, and honestly if you went to a therapist at some point, you will pass that round much more easily.”
“What was very unusual is they didn’t give me any tooling to draw the system design, so I just sketched it on a piece of paper and talked them through it, then we got into this oddly deep debate about whether hover-over history should count as a recommendation signal.”
