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
- Cleared the Full Onsite, Then Rejected After a Messy Reference-Check SagaDatabricks · Software Engineer · Onsite · Jul 2026Rejected
Phone screen: system design — design a music playlist. The recruiter told me it would be a full-stack SD round with front-end code and everything, so I spent a long time brushing up on React, but it turned out to just be a normal SD round with no front-end content at all. My answer was pretty average. The interviewer seemed nice but looked exhausted the whole time — not sure if he was just overwo…
- Codespace-Based, No LeetCode, AI-Assisted Design TaskBilt Rewards · Software Engineer · Technical Screen · Jul 2026
A recruiter reached out and went straight to scheduling a technical interview. Their interview process was pretty confusing — they used a GitHub Codespace, zero LeetCode, and it was split into two main parts. Part one: fix failing unit tests. The project was structured similarly to a Spring MVC app, and it also tested SQL. I had to fix a few SQL queries and write the logic for determining reward…
- Coding Round with a 3-Milestone Pipeline ProblemPlaid · Software Engineer · Technical Screen · Jul 2026
There were two rounds total: the first was coding, and the second was a project deep-dive where I had to put together my own PPT slides presenting a project. Plaid coding interview experience. The question was about an automation pipeline, with 3 milestones that added conditions progressively. Milestone 1: single worker — calculate how many jobs get completed within the time limit. The pipeline i…
- Coding, Technical and Culture Rounds After a Long Search, One OfferMicrosoft · Site Reliability Engineer · Senior+ · Onsite · Jul 2026Offer
I got laid off from Amazon as a new grad SDE 1 a few years back, and the two jobs I took afterward gave me neither the growth nor the total comp I wanted. My current job is very relaxed and a solid long-term place for my peace of mind. So I only went after FANG+ roles that looked interesting to me and would roughly double my TC. I've been interviewing for 30 months now, although I was only out of…
- Conflicting Spreadsheet Instructions and a Stressful OnsiteGoogle · Software Engineer · Senior+ · Onsite · Jul 2026Rejected
I interviewed for Applied AI. I don't know why a senior-level interview had only two coding rounds and one system-design round. Questions: Coding 1: Spreadsheet, implementing set_cell / get_cell. Coding 2: Google Shop System design: A customer-service system where users talk to a virtual agent and can escalate to a human. The recruiter's feedback was that, of the three rounds, Coding 1 and system…
- Consultant interview at Accenture EspañaAccenture España · Consultant · Jul 2026
Scheduling became frustrating almost immediately. I was arranged through WhatsApp, then left waiting by the assigned recruiter without notice. I later learned that I had effectively been dropped because I could not join an unplanned surprise call. It happened in other forms too: I was invited to an interview where nobody appeared, and follow-up email brought no clear explanation. In one case an A…
- Consultant interview at Flight Centre Travel Group: interview experienceFlight Centre Travel Group · Consultant · Jul 2026Offer
The process was light-touch and felt more like a quick check than a large recruitment campaign. After applying, I had a short recruiter phone call about whether I had the confidence and energy they wanted. The questions stayed high level. I then joined a Zoom call with a few role-related questions about whether I could do the job day to day. There were not many hurdles, and the tone was calming r…
- Consultant interview at Infosys Finacle: fast technical and HR processInfosys Finacle · Consultant · Jul 2026Offer
I went through a structured process with screening, virtual technical interviews, and then in-person managerial and HR rounds. The second-round scheduling took some time, but once the process started it moved with momentum. I discussed previous work and projects, including async/await, microservices, and challenges from my prior role. The later conversations focused on experience and teamwork. I…
- Consultant interview at McKinsey &: interview experienceMcKinsey & · Consultant · Jul 2026Offer
Overall, I had a positive experience, although one part bothered me: I had to take an online numerical test. I understood it as a screening tool, but in 2026 it felt somewhat outdated. Apart from that, the process went well and I kept a good impression through the stages. I received an offer in the end, despite the friction of that numerical assessment. My reflection is simple. I could see the va…
- Consultant interview at McKinsey &: six-month case processMcKinsey & · Consultant · Jul 2026
My process lasted about six months, beginning with LinkedIn outreach and ending in rejection. The sequence was a game assessment, two interviews with engagement managers, and a final round of three partner interviews. I reached the end feeling confident, but was eliminated in the first interview of that final group after a simple math error. My result differed from the expected one, which led me…
- Consultant interview at Migso-Pcubed: interview experienceMigso-Pcubed · Consultant · Jul 2026
The process opened with a presentation I prepared in advance from a slide deck they asked me to bring. While I presented, we discussed it and they asked questions, so it stayed interactive rather than becoming a monologue. After the deck, they introduced the company and we continued with Q&A. The session ended with feedback from each person and information about whether I would be invited to the…
- Data Engineer interview at Facebook: unclear bookstore scenarioFacebook · Data Engineer · Jul 2026
After a recruiter screen, I went into a technical conversation that felt tougher than the preparation materials. The difficulty was not only coding or SQL. A scenario resembling a bookstore checkout system was described too vaguely for me to know the intended behavior, and the interviewer did not help clarify it. Once I understood what to build, I worked through it, but the experience still felt…
- Data Engineer interview at Meta Logistics: ambiguous technical promptMeta Logistics · Data Engineer · Jul 2026
After a standard screen, I had a technical conversation with a TA that felt harder than the preparation material. The concepts themselves were not impossibly advanced, but the problem statement was so vague that I struggled to understand what was expected. It resembled a bookstore checkout flow, yet the intended behavior and outputs were unclear and the interviewer did not help resolve that ambig…
- Data Engineer interview at Meta Platforms: timed Python and SQL screenMeta Platforms · Data Engineer · Jul 2026
I started with a recruiter-style conversation and moved quickly to a one-hour technical screen split between Python and SQL. I had to complete several Python questions before switching to SQL tasks involving window functions and other query patterns. The pace mattered as much as getting the answers right. It felt less like a search for a novel algorithm than a test of speed and complete execution…
- Data Engineer interview at TredenceTredence · Data Engineer · Jul 2026Offer
For this Data Engineer role, the process ran about 4 to 5 rounds. It started with a HackerEarth assessment mixing aptitude, SQL, and coding, then a communication round. Two technical rounds followed, with strong emphasis on SQL and PySpark plus basic DSA. The questions required precision and speed, and the interviewers pushed on how I approached data-engineering work, not only the tools I had use…
- Datadog Account Executive interview: clear recruiter guidance with an uneven panelDatadog · Account Executive · Jul 2026
The recruiter reached out and was helpful and transparent throughout. Before I spoke with a hiring team, I received a PDF explaining each stage and what I needed to prepare. That made the process predictable, and I did not feel as though I was guessing what would happen next. After the recruiter call, the process followed a standard pattern: an early phone or screening stage and then video interv…
- Datadog Account Executive interview: sales process and a mock cold callDatadog · Account Executive · Jul 2026
The process felt organized from the beginning. I started with a recruiter conversation and then met hiring leaders. In those calls, it seemed they were comparing my experience with what they needed in an Account Executive: my approach to sales, how I described my impact and how well that experience would translate to their environment. The hiring-manager questions were more pointed. I explained m…
- Datadog Software Engineer HackerRank and final technical interviewDatadog · Software Engineer · Online Assessment · Jul 2026Rejected
The process felt smooth and standard. It began with a HackerRank-style online test containing two LeetCode-like questions. Next came a roughly half-hour recruiter call focused on fit and the usual recruiter topics. The final technical stage lasted about an hour. It included more medium-hard LeetCode-style questions and a separate behavioral and HR block within the overall stage. The recruiter and…
- Datadog Solutions Engineer interview: presentation cancelled after the role was filledDatadog · Solutions Engineer · Online Assessment · Jul 2026Rejected
I reached the presentation stage after initial screens and a HackerRank assessment. It was due to be in person, and I put considerable effort into preparing something I felt confident presenting. Late the day before, a message said the role had already been filled and I didn't need to come in. The timing felt awful after all the preparation I'd done that week. Later, HR said they appreciated my p…
- Dayforce Software Engineer interview: SQL, JavaScript, and behavioral manager roundDayforce · Software Engineer · Technical Screen · Jul 2026
After recruiter outreach, I had a structured set of interviews. The first technical step used screen sharing: I discussed my background and answered questions about SQL and JavaScript. Soon afterward, I had a longer technical interview lasting about two hours in total, including a separate manager-focused section. I explained my experience concretely, while the manager asked behavioral questions…
- Delivery Hero Software Engineer Interview Experience: Three quick and kind roundsDelivery Hero · Software Engineer · Technical Screen · Jul 2026
After the recruiter call, I went through three rounds: a technical interview, a hiring-manager round, and a bar raiser. The process moved quickly and matched what I expected going in. Everyone I spoke with was kind and understanding, which made the pace easier to handle. I did not get an offer, but the process did not feel hostile or chaotic. It was a straightforward, quick evaluation path. Locat…
- Delivery Hero Software Engineer interview: backend-heavy technical roundsDelivery Hero · Software Engineer · HR Screen · Jul 2026
The process began with an HR screen, moved through technical interviews, and ended with a hiring-manager discussion. I was not offered the role. The technical rounds were the hardest part. They covered Python fundamentals, backend development, system design, APIs, databases, concurrency, and general problem solving. The questions were practical and tied to engineering scenarios rather than stayin…
- Dell Tech Laboratories Software Engineer interviewDell Tech Laboratories · Software Engineer · Online Assessment · Jul 2026Offer
After an online assessment, I went through four rounds: two technical discussions, a managerial or technical discussion, and HR. Clearing each stage felt necessary to stay in the process. The technical interviews assessed my engineering approach and fit. The managerial or technical conversation added how I would think with broader ownership and cross-functional responsibilities. I received an off…
- Dell Tech Laboratories Software Engineer interview experience: home assignment and onsiteDell Tech Laboratories · Software Engineer · Take-home Project · Jul 2026
My hiring loop began with a home assignment, before I reached the onsite. After submitting it, I attended an onsite that lasted about 1.5 hours and included three questions. The first onsite interview was strongly LeetCode-oriented, with time-pressured problem-solving. The second stayed entirely technical, without personal or background questions. Across those two technical questions, the bar fel…
- Dell Tech Laboratories Software Engineer interview: broad CS fundamentalsDell Tech Laboratories · Software Engineer · Online Assessment · Jul 2026
For the Software Engineering Student role, my process had three main stages and ended on July 27, 2026. It began with a HackerRank assessment on general software development, followed by an in-person interview at the Be'er Sheva office that went hard on core computer science fundamentals. That in-person round and the later advanced technical interview, held on July 12, both asked me to demonstrat…
- Dell Tech Laboratories Software Engineer interview: reasoning over memorizationDell Tech Laboratories · Software Engineer · Other · Jul 2026Offer
The Dell Tech Laboratories interview was positive and professional from the start. It focused on how I approached a problem, not only how quickly I could state an answer. I was asked to explain my reasoning and walk through my thought process step by step. The interviewer was friendly and encouraged discussion of different approaches. It felt less like a memorization test than a check on whether…
- Delta Air Lines Software Engineer interview: dismissive manager led to withdrawalDelta Air Lines · Software Engineer · Technical Screen · Jul 2026Withdrew
The first conversation was uncomfortable from the start. The hiring manager felt condescending, told me to "slow down" while I explained my background, and when I asked for feedback, criticized only my attire as too casual even though he was dressed much more casually. Very little of the discussion concerned technical skills or performance. He pointed to internal communications for the formality…
- Disney+HotStar Software Engineer interview: AI fluency and high-level designDisney+HotStar · Software Engineer · Technical Screen · Jul 2026
Recruiter coordination was a little difficult, but I thought the interviewers were good once the interviews began. I went through two rounds: AI fluency, then high-level design. I didn't receive an offer. In the AI fluency round, I had a system-design problem about where AI could be useful. It felt much broader than a typical high-level design question. I had to decide how the proposed system wou…
- DoorDash Data Scientist Interview Experience: SQL, cases, and virtual onsiteDoorDash · Data Scientist · Jul 2026
An HR-style call covered the role, compensation and benefits, and the hiring flow. The technical screen began with four medium SQL questions in a HackerRank-style format. I barely had time for the last one and got the impression they did not expect a full solution. A case study followed, where I explained how I would approach an open-ended business problem. After passing, I had a virtual onsite w…
- DoorDash Data Scientist interview: SQL and ambiguous casesDoorDash · Data Scientist · Technical Screen · Jul 2026
The first round combined a 30-minute SQL assessment and a case study. SQL felt very easy, while the case portion was more difficult: two prompts were straightforward and one was genuinely ambiguous. The next round included three case studies and an interview with a cross-functional partner. The interviewers were kind, but I still had to keep structure and clarity across the scenarios. I did not r…
