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.

“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.”

“The interview process was well structured and covered a good mix of DSA, ML theory, and ML system design. The problem-solving and technical discussions went well, and the questions were relevant to the role. I felt I could have prepared more thoroughly for some of the system design and deeper ML theory questions. ”

“The interview process was fast-paced and heavily practical. It consisted of an initial recruiter screening, a past project deep dive, a live technical case study focusing on customer scenarios, and a leadership/behavioral session. What went well was the technical depth—the interviewers gave constructive feedback in real time and let me talk through complex architectural trade-offs without unnecessary micromanagement. What didn't go as well was the time management during the open-ended case study; having to balance high-level client communication with granular technical scoping in a short time frame felt rushed.”

“The recruiter was very accurate on the whole process. The interviews are very structured. learn the frameworks for the questions and cases.”

“I interviewed for an Amazon Software Development Engineer internship in February 2025. The process was three rounds over about three weeks: a recruiter screen, a HackerRank assessment, and a final technical conversation that also included behavioral questions. The recruiter screen was straightforward and helpful for setting expectations. The HackerRank portion was the most time-sensitive part, so it rewarded being comfortable turning an approach into working code without spending too long on setup. The final interviewer was genuinely nice and the conversation felt collaborative. The coding problem was to reverse a linked list. I started by explaining the iterative solution and the pointer changes before coding, then walked through edge cases such as an empty list and a single-node list. The behavioral questions were folded into the same conversation, so I tried to make my answers concise and connect them to how I approach problem-solving and teamwork. Overall, it felt like a fair intern process: not designed to be tricky, but it did require clear communication and clean implementation under time pressure.”

“A lot of focus spent in every round on LP questions. Make sure to have sufficient stories, sometimes they plan to ask two, but end up asking a third one.”

“The process wasn't too difficult. DSA/Leetcode wasn't heavily emphasized. It was a general programming type interview where you go through a code block and show your understanding of data structures”
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.”
