real interview stories, told over a cup of tea ♡
Interview Experiences
3935 interview stories from candidates at 857 companies: how each round went, what was asked and how it ended. Every company page links to practice questions in the same style.
- 3935
- Experiences
- 857
- Companies
- 532
- Offers
3935 results
- Amazon Development Center U.S. Software Engineer four-round coding and leadership loopAmazon Development Center U.S. · Software Engineer · Online Assessment · Jun 2026
After an online assessment, I entered a deliberate loop meant to assess both coding and engineering judgment, with leadership principles throughout. The loop had four rounds: two coding interviews, a behavioral conversation built around Amazon Leadership Principles, and a hiring-manager round with another coding problem plus a high-level design discussion. One coding round started with a medium p…
- Amazon Development Center U.S. Software Engineer interview experienceAmazon Development Center U.S. · Software Engineer · Technical Screen · Jun 2026
Recruiter outreach turned into a marathon. After the initial steps, I was scheduled for an onsite-style block of back-to-back interviews. I did four rounds in one day with senior engineers, followed by additional conversations about leadership and design. The day opened with coding and problem solving. For DSA questions, the interviewer cared about how I explained edge cases aloud. In one interva…
- Amazon Development Center U.S. Software Engineer Interview Experience: coding, design, and Leadership PrinciplesAmazon Development Center U.S. · Software Engineer · Technical Screen · Jun 2026Rejected
This Amazon process felt like a full technical deep dive rather than a quick screen. After applying, I had multiple live rounds combining coding, system design, and detailed behavioral questions about Leadership Principles. The coding work required more than an optimal LeetCode style solution. I had to explain my thought process, edge cases, time and space complexity, alternative approaches, and…
- Amazon Development Center U.S. Software Engineer Java Spring Boot debugging loopAmazon Development Center U.S. · Software Engineer · Technical Screen · Jun 2026
After a recruiter call, I had a technical phone screen of about an hour with practical engineering questions. Once I cleared it, I entered the loop. The loop combined coding, systems thinking, and Amazon Leadership Principles. I solved LeetCode-style problems, discussed system design, and completed a STAR-format behavioral round. In one round, I used an AI-enabled setup to debug code in a Java/Sp…
- Amazon DSP Software Engineer interview: OA coding and leadership assessmentAmazon DSP · Software Engineer · Online Assessment · Jun 2026
I received the online assessment about a week after applying, before any loop interviews. It took longer than I expected because it packed in a lot, including video material explaining the kind of reasoning and approach they wanted. The OA had standard coding challenges focused on algorithms and data structures, along with a leadership-assessment component. I had heard that leadership principles…
- Amazon DSP Software Engineer technical loop with leadership-principle bar raiserAmazon DSP · Software Engineer · Technical Screen · Jun 2026
After a recruiter conversation, I had a roughly hour-long technical phone screen. Once I cleared it, the process moved into scheduled loop interviews. It was structured, but intense. The loop combined coding with Amazon-style leadership discussions. I had two coding-heavy sessions: one began at medium LeetCode difficulty and another went into harder territory. There was also a system-design discu…
- Amazon Kuiper Commercial Services Software Engineer Interview Experience: a one day loopAmazon Kuiper Commercial Services · Software Engineer · Online Assessment · Jun 2026
After an online assessment, I entered a full loop packed into one intense day. It had the kind of Amazon structure I expected: multiple coding rounds, design, and a deep behavioral bar raiser. The first coding round began with a warm-up before moving to a practical meeting-intervals DSA problem. I used a heap, then had to think through reassignment and idle time in a follow-up. A later round pair…
- Amazon Kuiper Commercial Services Software Engineer Interview Experience: DSA, OOP, and DBMSAmazon Kuiper Commercial Services · Software Engineer · Online Assessment · Jun 2026
I started with an online assessment and then moved into a short, dense interview sequence. There was no HR phone screen for me. After applying, the assessment came first and scheduling moved directly into the loop. The loop had three rounds focused on data structures and algorithms, basic OOP, and DBMS concepts. Leadership Principles also appeared, and I had an HR interview mixed into the process…
- Amazon Kuiper Commercial Services Software Engineer Interview Experience: Two same-day technical roundsAmazon Kuiper Commercial Services · Software Engineer · Online Assessment · Jun 2026
I started with an online assessment, then completed two technical rounds over Zoom on the same day. Each technical round lasted about an hour. The pace was intense because I had to code in an online editor without predefined test cases while explaining my reasoning. After my introduction, the first round included two tasks on data structures and algorithms and behavioral questions about tight dea…
- Amazon Kuiper Commercial Services Software Engineer interview: long OA waitAmazon Kuiper Commercial Services · Software Engineer · Online Assessment · Jun 2026No response
My process began with an online assessment that took a long time before interviews started. After I submitted it, I moved into interviews built around coding patterns and Leadership Principles. The technical side leaned on LeetCode-style questions, while leadership themes stayed prominent. Based on what I had heard about common topics, I prepared stories around Customer Obsession, Ownership, and…
- Amazon Kuiper Commercial Services Software Engineer online assessment and four-round loopAmazon Kuiper Commercial Services · Software Engineer · Online Assessment · Jun 2026In progress
After an online assessment, I had a recruiter touchpoint and entered the loop roughly a week later. The loop had four rounds: two coding-focused interviews, a bar raiser round, and a separate discussion about fit with another team. The coding work combined algorithms and design. One round was LeetCode style, and the other was system design. Leadership Principles were a repeated theme, so I discus…
- Amazon Software Engineer interview experience: LRU cache implementation detailsAmazon · Software Engineer · Technical Screen · Jun 2026
After I cleared the initial steps, I had a phone-screen-style discussion that ran longer than expected and went deeply into implementation. The interviewer pressed me on an LRU cache: how I would combine a hashmap and doubly linked list, and how eviction would work. System-design examples on eviction policies had helped me prepare, so I could explain the reasoning instead of reciting a solution.…
- Amazon Software Engineer interview experience: maximal square and good nodesAmazon · Software Engineer · Technical Screen · Jun 2026
I interviewed for an SDE1 role at Amazon. The early process centered on DSA and, after applying, I went through two technical rounds with different coding challenges. The first included maximal square and merge intervals, which called for DP or matrix reasoning and careful interval manipulation. In the second, the questions shifted to something like counting good nodes in a binary tree, so I was…
- Amazon Software Engineer interview: AI coding assessmentAmazon · Software Engineer · Online Assessment · Jun 2026
My Amazon process began with online tasks before the more traditional interviews. The DSA portion used something like a house-robber II problem, so it felt more focused on dynamic-programming trade-offs than a simple brute-force solution. The assessment also had an AI-based coding round. I was given a code repository and an AI model with guardrails, then had to work from failing test cases to und…
- Amazon Software Engineer interview: brain teasers and OA rejectionAmazon · Software Engineer · Online Assessment · Jun 2026Rejected
The process began with online recruitment quizzes or an OA, and those early steps set the tone. One path was packed with brain-teaser-style questions that did not match the job I was applying for. It made the process feel disrespectful of my time. In another attempt at the same general funnel stage, I submitted OA solutions and received a rejection a few days later. That assessment was more typic…
- AMD Software Engineer interview on timing and DFTAMD · Software Engineer · Jun 2026Offer
My interview centered on my project experience, beginning with how I handled both my master's and undergraduate work. The technical conversation moved into more specific areas, including timing and static timing analysis, where the questions became fairly in-depth. I also discussed architectural topics and some DFT basics. The interviewers wanted me to speak concretely about what I had done and c…
- AMD Software Engineer interview with two weeks between HR and technical roundsAMD · Software Engineer · HR Screen · Jun 2026Offer
The HR screening covered the usual setup, and the technical process followed about two weeks later. The technical questions seemed straightforward at first, but they didn’t stay shallow. The interviewers kept digging into who I was as a person and how I worked, using my answers as the thread. The interviews felt more like an examination of how I function than a pure test of puzzle-solving. Even w…
- AMD Software Engineer interview: two in-person technical rounds and delayed feedbackAMD · Software Engineer · Technical Screen · Jun 2026
I had a couple of in-person technical rounds, and the interviewers gave me a positive signal because the sessions went smoothly. The process felt normal at the time, so I expected that I was moving forward. Afterward, the recruiter didn't update me for about two weeks. I followed up repeatedly, asking several times, and the response eventually became negative. The communication felt unprofessiona…
- Applied Materials Software Engineer interview experienceApplied Materials · Software Engineer · HR Screen · Jun 2026
The stages were fairly clear, but waiting between them felt heavy. I started with a recruiter call, then had an HR conversation about motivation, followed by an onsite interview. During the onsite, I completed a technical portion and met the person responsible for maintenance. HR returned with a final decision and feedback afterward. What I remember most is how long the time after the interviews…
- Applied Materials Software Engineer interview: unexpected technical onsiteApplied Materials · Software Engineer · Technical Screen · Jun 2026In progress
I did this interview partly for the experience, and it turned strange quickly. The first round was on Zoom. The interviewer had the wrong resume and accused me of lying about my experience before realizing the mix-up. He corrected it professionally, but the moment was tense. For the final onsite, I was told it would not be technical, which was fine because I was comfortable with LeetCode. When I…
- Arch Global Services Philippines Software Engineer Python, SQL, and flatten-list technical roundsArch Global Services Philippines · Software Engineer · Technical Screen · Jun 2026Rejected
The interviews were heavily technical and coding-focused. In one technical round, I discussed my project experience and then answered questions about Python and APIs, including Django, FastAPI, Pandas, and OOP. I also completed multiple Python coding exercises that tested how I broke down and reasoned through problems. Another technical session covered Python decorators and generators, the differ…
- Arista Networks Software Engineer interview: relocation conflict after a 15-minute callArista Networks · Software Engineer · Jun 2026Rejected
I had a very short conversation with a recruiting coordinator, about 15 minutes. She said right away, after going through my resume, that she did not think I was a fit and would not move me forward. Since the meeting was still on the calendar, it felt pointless. She explained that the issue was a mix of logistics and preference. Because I did not want to relocate immediately, they said an intervi…
- Artefact Consultant Interview Experience: group cases under time pressureArtefact · Consultant · Other · Jun 2026
The process was in depth and moved quickly once it started. There were about five rounds, and the people involved were responsive and easy to reach. They wanted me to begin right away, and the structure matched that pace. There were a few cases. At the more interactive stage, I presented a case and also completed a group case assignment that we had to present. That round was crowded. I was invite…
- Asana Account Executive interview with six stages and a final presentationAsana · Account Executive · Other · Jun 2026Rejected
I went through an intense, multi-step process that felt excessive for the role. After speaking with a recruiter, I had several interview rounds with detailed technical questions. The process stretched across six stages, ending with a 45-minute presentation that required a lot of preparation on top of everything else. I passed every stage with positive feedback and felt that the conversations were…
- Asana Software Engineer coding interview with no feedback before rejectionAsana · Software Engineer · Technical Screen · Jun 2026Rejected
I started with an initial screening that left me genuinely excited about the opportunity. The technical part didn’t match what I expected from the preparation materials. Instead of feeling like a collaborative back-and-forth, the interaction was noticeably less engaging, and the interviewer’s involvement felt minimal. I didn’t receive feedback after the coding interview, so the uncertainty dragge…
- Asana Software Engineer interview with a referralAsana · Software Engineer · HR Screen · Jun 2026
My process was short and ended quickly. It started with an HR introduction call focused on standard resume and experience questions, along with how my background fit the role. It didn't feel like much of an exploration of my strengths or working style. The call felt more like someone moving through a checklist. Because I had a referral, the conversation also felt somewhat ceremonial. After the HR…
- ASML Software Engineer interview, transactional recruiter screeningASML · Software Engineer · Jun 2026Rejected
My biggest frustration came before I reached any technical depth. The recruiter interactions were my first real signal, and they didn't feel aligned with what the role actually required. In our conversations, the recruiters seemed more focused on ticking boxes and pushing me to name a salary than on understanding my background or motivation. One screening call felt especially transactional. It se…
- AT&T Account Executive interview: objections, cold calling, and customer recruitingAT&T · Account Executive · Jun 2026
The process opened with a straightforward recruiter-style conversation, but the questions quickly turned to how I had handled work situations. One main prompt asked about my best and worst scenarios. I had to explain what happened, how I got there, and what I did to work through the challenge. I then had a short, structured set of interviews centered on sales fundamentals. We discussed overcoming…
- Axon Software Engineer Interview Experience: a take home system design presentationAxon · Software Engineer · Take-home Project · Jun 2026
The process began with a recruiter conversation about logistics and my background. That was followed by a hiring manager discussion focused on my previous work experience, and that part went very well. I then completed a take home system design deliverable. I submitted a written document and presented the design to two team members. Their follow ups went into deeper detail, so it was not simply a…
- Backend EngineerStripe · Backend Engineer · Technical Screen · Jun 2026
It was a multipart question. The question was based on string split, slicing, matching and basic checks. Attempting the question in python will really give us the edge instead of using any verbose language like Java. Given multiple strings separated by commas mapped as individual merchant information. First part was to retrieve merchant info from each string and then further parts was to perform…
