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
- DoorDash Data Scientist interview: SQL and case rounds with one missed conceptDoorDash · Data Scientist · HR Screen · Jul 2026
After a recruiter screen, I had two screening rounds involving SQL and a case study, followed by more case-study rounds. The onsite-style loop also included a meeting with a cross-functional partner, and I later spoke with a hiring manager. The setup was professional and moved quickly. The data-science questions were not easy. I had done well on the early screens and one case, but a later case br…
- DoorDash Data Scientist interview: SQL round and case study before a quick rejectionDoorDash · Data Scientist · Technical Screen · Jul 2026Rejected
The loop felt almost entirely about training the interviewers. There was no separate recruiter screening call. It began with a SQL round, then a case study. The recruiter mostly gave a brief introduction, while the two technical sessions carried the process. I finished the SQL questions and explained my thinking to the recruiter as things moved along. The case study also went well, and it felt li…
- DoorDash Data Scientist interview: take-home after manager screenDoorDash · Data Scientist · HR Screen · Jul 2026Rejected
I had a quick phone screen and then a Zoom meeting with the hiring manager that lasted about 30 minutes. After that, I completed a take-home assignment and submitted it within 72 hours. That was the end of the process for me. My submission did not move forward, and I did not get another live round. The path looked straightforward on paper, but it was still frustrating because all of my momentum r…
- DoorDash Software Engineer interview: bilingual 30-minute recruiter callDoorDash · Software Engineer · HR Screen · Jul 2026
After the recruiter contacted me, I had an initial conversation of about 30 minutes. The call began in Portuguese and then continued in English. It stayed general: we discussed my previous experience and what I was seeking in compensation, including salary and benefits. It did not advance to the technical part at that stage, so this was the only impression I had of the process. Location: São Paul…
- DoorDash Software Engineer interview: durable refund DAG system designDoorDash · Software Engineer · Technical Screen · Jul 2026Offer
The process was demanding from the start. After several rounds, I handled behavioral questions that, interestingly, matched my real experiences well. The technical work carried the most weight, especially a system-design challenge about building a durable DAG flow for order refunds. I was overwhelmed at first, but my earlier system-design interview study helped me organize the approach and unlock…
- DoorDash Software Engineer interview: internal electric-motor design screeningDoorDash · Software Engineer · HR Screen · Jul 2026
It began with a phone call with the recruiter. She was specific about the kind of person she was looking for, then asked technical questions focused on internal electric-motor design knowledge. The material was more targeted than I expected, and it was clear that the screen was trying to establish an exact fit with that technical background. Location: San Francisco, CA. Overall feedback: neutral.…
- DTCC Business Analyst interview: hiring-manager conversation followed by silenceDTCC · Business Analyst · Other · Jul 2026No response
After a recruiter call, I interviewed with the hiring manager. The conversation was straightforward, but I never really heard back after it. More than a month passed, and the recruiter stopped responding to update requests. The prolonged silence made what should have been a final stage feel flat and unprofessional. I received no clear next step or even a simple status message, only a waiting game…
- DXC Technology Software Engineer interview: .NET, APIs and frontend fundamentalsDXC Technology · Software Engineer · Technical Screen · Jul 2026Offer
After introductions, we discussed my previous projects and work experience. The technical conversation went deeply into the Microsoft stack: .NET, C#, ASP.NET Core and SQL. We also covered REST APIs and frontend work in JavaScript and Angular. There were questions about object-oriented programming, dependency injection and debugging scenarios too. The interviewer was professional and gave me time…
- DXC Technology Software Engineer interview: operations-focused discussionDXC Technology · Software Engineer · HR Screen · Jul 2026Offer
I first spoke with HR about my background, skills, and reasons for considering a change. Then I met the team lead for a technical conversation on building software and operational concerns, including application and infrastructure monitoring and incident management. We discussed the technologies I had used and how my prior work translated to their delivery needs. I returned to HR to cover organiz…
- E2open Software Engineer interview on Java and meeting-room designE2open · Software Engineer · Technical Screen · Jul 2026Offer
After speaking with the recruiter, I had two focused technical rounds. The first was an online technical discussion on Java fundamentals, including OOP, multithreading, and DSA-style problem-solving. Later I had a face-to-face system design round. The scenario was a meeting-room booking system, and we discussed how its database could scale. The progression from core concepts to system-level reaso…
- Eightfold.Ai Software Engineer interview: AI coding and take-homeEightfold.Ai · Software Engineer · Technical Screen · Jul 2026In progress
I came through campus recruiting, starting with a CGPA eligibility check and resume shortlisting. That led to a 60-minute coding interview with an AI. There were two questions, so I had to keep an eye on both the approach and correctness while the clock ran. Clearing that screen put me in consideration for a take-home assignment, although the hiring process was still underway when I last heard. T…
- Electronic Arts (Ea) Software Engineer interview: mismatched technical expectationsElectronic Arts (Ea) · Software Engineer · HR Screen · Jul 2026
After a recruiter call, I had five interviews: recruiter contact, a hiring manager, and three final-round interviews. I depended on the recruiter for preparation guidance, but the details were too vague to tell me what to study. The system-design round was framed first as technical architecture and then as mostly frontend React, but React barely mattered. Instead I faced OOP, performance optimiza…
- EPAM India QA Automation Engineer interview: technical breadth and delaysEPAM India · QA Automation Engineer · Technical Screen · Jul 2026In progress
The recruiter call went well. After that, though, the process became a long wait. I heard nothing for about two weeks, followed up by email and LinkedIn, then waited another week for a reply saying the recruiter was waiting on the hiring team. I followed up again about a week later, and the technical interview was finally scheduled almost a month after the first call. That interview covered Java…
- EPAM India QA Engineer interview: Python automation and practical codingEPAM India · QA Engineer · Technical Screen · Jul 2026
After the recruiter call, I had a technical screen focused heavily on Python and automation thinking. I discussed lists, decorators, generators, and the difference between iterators and generators in real code. They asked about PyTest fixtures, then moved into automation framework design and how I would structure it end to end, including CI/CD pipeline considerations. The coding portion was pract…
- EPAM India Software Engineer conflicting-rounds interview experienceEPAM India · Software Engineer · Technical Screen · Jul 2026Rejected
The process felt drawn out and wasteful. I had cleared two technical rounds, and HR scheduled a project interview. After that, HR told me I had cleared it and only needed a final managerial round. The managerial round felt disorganized. The manager did not seem to understand the project I was being considered for and asked questions that did not fit what I expected from the earlier stage. HR late…
- EPAM India Software Engineer interview with Python deep dives and an unaccommodated emergencyEPAM India · Software Engineer · Jul 2026Rejected
My process stretched across many rounds and felt heavy from the start. I had several technical and client-facing sessions with professional interviewers, including positive feedback from one client discussion. I was surprised by how long the process took and how many people I spoke with. The difficulty came from deep-dive topics rather than basic problem solving. I got Python questions on slices,…
- EPAM India Software Engineer interview with Python, SQL, cloud, and system design roundsEPAM India · Software Engineer · Online Assessment · Jul 2026Rejected
The process started with a timed online assessment covering coding, programming, logic, and problem solving. After I cleared it, the recruiter moved me forward. The next stages were straightforward and reasonable. I first had an HR-style conversation where the interviewer was helpful and explained what the company wanted. The technical interviews matched my stack rather than relying on obscure Le…
- EPAM India Software Engineer interview: LRU cache, technical rounds, and canceled follow-upEPAM India · Software Engineer · Jul 2026No response
My EPAM process was assessment-heavy. It started with an OA covering aptitude, OS, computer networks, and coding. Next came a pen-and-paper coding test in an auditorium, where I worked on an LRU cache problem. Then there was a group discussion where the evaluator let us choose the topic. After that came technical interviews on DSA, DBMS, OS, CN, and more coding, followed by HR. It was not one con…
- EPAM India Software Engineer interview: Spring Security, tracing and Python internalsEPAM India · Software Engineer · Technical Screen · Jul 2026
After the recruiter stage, I had a technical interview of about ninety minutes that went deeply into Spring and distributed systems. I discussed Spring Data JPA, Kafka, Java 8 functional interfaces and Spring Boot. For microservices, I explained the architecture, how services communicate and how security works. JWT questions went into detail: what a token is, how a service validates it, what happ…
- EPAM India Software Engineer interview: technical assignment, stack questions, and project availabilityEPAM India · Software Engineer · Online Assessment · Jul 2026
My EPAM process began with a technical assignment rather than an immediate interview. I spent a lot of time on it, and after submitting successfully, an interview was scheduled. The process then became more typical: recruiter contact, a technical session, and a manager conversation. The technical content was mostly stack-aligned instead of unusual puzzles. I had linked-list questions, including b…
- Epic Just Switched OA Question Banks, Old One Is UselessEpic Systems · Software Engineer · New Grad · Online Assessment · Jul 2026
Epic's official guide has been updated — first a phone call with a colleague introducing the role, then an online technical assessment. It's completely different from the old question bank. I'm a new grad currently job hunting, sharing this in good faith. True/False/Cannot Determine — 5 min Each question gives 4-5 facts, and you judge 5 statements as true, false, or cannot be determined. Roughly…
- Ernst & Young Consultant first interview nerves despite easy questionsErnst & Young · Consultant · Jul 2026Rejected
In my first interview, panic took over. The questions were easy, but I blanked in the moment and could not respond the way I knew I could. The difficulty was not the problem. The pressure of being in the room was. I did not move forward. The experience showed me how quickly nerves can erase familiar knowledge, and the miss felt more about nerves than capability. Location: India. Overall feedback:…
- Ernst & Young Consultant interview: basic questions and brain teasersErnst & Young · Consultant · Other · Jul 2026
The interviewers were kind, but the process felt a little unprepared. Most questions were the basic kind I expected early on. A few brain teasers appeared near the end, making the round less predictable and testing how I thought under light pressure. It was manageable rather than brutal, though somewhat scattered. I left wishing I had done a bit more live practice so the brain-teaser section woul…
- Ernst & Young Consultant interview: creative in-person stageErnst & Young · Consultant · Onsite · Jul 2026Rejected
The process took a while, but the in-person stage was engaging and mentally stimulating rather than merely formal. I felt encouraged to think outside the box, with a strong emphasis on logic and creativity. It was demanding, but also fun in that sense. The manager interview afterward felt more tense. Some questions did not seem clearly framed, which made it hard to answer confidently because I wa…
- Ernst & Young Consultant interview: two rounds and an SAP implementation caseErnst & Young · Consultant · Onsite · Jul 2026Offer
The process was short, with two distinct rounds: one online and the next in person. Both felt focused on fit, without much pressure from coding. In the first conversation, I walked through my resume and explained how my experience matched what they wanted. The second involved a case study about SAP implementations. My impression was that they wanted clear explanations of the fundamentals rather t…
- Ernst & Young U.S. LLP Consultant first-interview nerves and blankingErnst & Young U.S. LLP · Consultant · Jul 2026
My first interview was easy on paper, but I let nerves get the better of me. I panicked and blanked out even though the interviewer asked basic, straightforward questions. I could not answer them properly in the moment. The difficulty did not seem high, but my performance did not show what I knew. I left with the uncomfortable feeling that nerves, not a lack of understanding, had caused the probl…
- Eurofins scientific Software Engineer four interviews and unanswered follow-upsEurofins scientific · Software Engineer · Jul 2026No response
The recruitment process began with urgency, and I committed a lot of time because the timeline was presented as critical. I completed four interviews. After the last one, I received no response: no positive feedback and no rejection. Over the next several weeks, I followed up repeatedly by email, phone, and voice message, about a week apart. Nothing was answered. I eventually contacted an enginee…
- Eurofins scientific Software Engineer two-round interview experienceEurofins scientific · Software Engineer · Technical Screen · Jul 2026
I had two scheduled rounds for the Software Engineer role. The process was short, friendly, and straightforward. The questions felt easy to medium and mostly covered Java, Spring Boot, and material from my resume. The interviewer was easy to speak with, so it never felt like an interrogation. Hiring later slowed because of a freeze, and I did not receive an offer letter. Technically, I felt the i…
- Exl Business Analyst interview: shifting final stagesExl · Business Analyst · Senior+ · Technical Screen · Jul 2026Rejected
The process began with a hiring-team interview that went well, followed by a VP round. I was told an AVP-style final interview would come next, and the technical and leadership discussions seemed positive. I expected the process to reach a decision. Instead, I was pulled into another client-related conversation after the interviews appeared finished. I was then rejected for a basic hands-on skill…
- EXL Service Business Analyst interview: long and disorganized roundsEXL Service · Business Analyst · HR Screen · Jul 2026Rejected
After the initial HR contact, the process became a long sequence of interviews with gaps between them. There were so many stages that one day felt as though it would never end. I spoke with several people, including senior leadership, and repeatedly had to restate my background and the basics tied to the role. Coordination was the hardest part. I was asked to attend extra rounds that were not cle…
