Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

4514 stories

Likes earn the author +10 XP for the first 3 likes each day

ALTEN BelgiumSoftware Engineer
Reported Jul 2026

ALTEN Belgium Software Engineer Interview Experience: A friendly start that drifted from cyber to DevOps

My experience was quick and simple at first. I had a straightforward conversation about my skills, and I got the impression that they were trying to place me on a project that matched them. The tone was friendly and positive, without feeling overly formal. Later, though, the process felt misleading. I was invited to talk about cyber, but I ended up in a conversation that felt more related to DevO…

Offer0
ALTEN BelgiumSoftware Engineer
Reported Jul 2026

ALTEN Belgium Software Engineer Interview Experience: A technical meeting where no one joined

My process started badly. The first HR interaction was not really an interview to assess my skills. It felt like a briefing for what would come next. Then I showed up on time for the second technical meeting, waited about an hour, and nobody joined. I reported it immediately, but I received no apology, explanation, or clear reason for the time I lost. Even after following up, I heard nothing. The…

No responseHR Screen0
Amazon Kuiper Commercial ServicesSoftware Engineer
Reported Jul 2026

Amazon Kuiper Commercial Services Software Engineer Interview Experience: Four different formats in an online assessment

After the recruiter screen, I took an online assessment that felt structured and timed. It started with coding on two LeetCode-medium questions, then shifted to workplace and behavioral situations where I had to choose how I would respond. It also had a short personality-style section asking how different skill statements matched me. The second time through the process, the online stage had four…

Online Assessment0
Amazon AdvertisingSoftware Engineer
Reported Jul 2026

Amazon Advertising Software Engineer Interview Experience: Medium coding under a compressed but supportive schedule

My process began with a thorough, tightly paced phone interview. Segments ran back to back. I first worked through two medium LeetCode questions, each followed by probing about how I approached the problem end to end. Then I did workplace-style behavioral questions and a quick personality-type check about how I work and where I see my strengths. What stood out was the interviewers' tone. Even wit…

Technical Screen0
Amazon AdvertisingSoftware Engineer
Reported Jul 2026

Amazon Advertising Software Engineer Interview Experience: A four-part OA with AI-assisted debugging

I started with an online assessment in four parts. First was a 40-minute HackerRank coding test with standard DSA questions. Second was 60 minutes of AI-assisted coding in a project-repository environment, where I had to trace a simple bug, such as why a request was not committing to the database. The available options included Node.js, Springboot, C++, and Django. Third came 30 minutes of workpl…

Online Assessment0
Automatic Data ProcessingAccount Executive
Reported Jul 2026

Automatic Data Processing Account Executive Interview Experience: Behavioral structure, sales scenarios, and STAR reflection

My recruiter conversation set the tone for a straightforward process. We discussed expectations and my past experience, and after the call went well I moved to a one-on-one interview with higher-ups. That part felt strong, and I left feeling that it had clicked, though I was then waiting for next steps. The format varied, but each stage relied on prepared questions. In a roughly half-hour Zoom in…

HR Screen0
AndurilSoftware Engineer
Reported Jul 2026

Anduril Software Engineer Interview Experience: Mock application work and a project presentation

My experience began with easy coordination. Reaching the recruiter and scheduling interviews was smooth. From there, the questions were tightly connected to the actual job and how effective I could be in it. I expected a typical interview structure, but it had a stronger performance element than I was used to. I had to demonstrate my abilities through mock application-style work, not just theory.…

HR Screen0
AMD Construction GroupSoftware Engineer
Reported Jul 2026

AMD Construction Group Software Engineer Interview Experience: Medium LeetCode, RTL, and CUDA optimization questions

My process started with an HR-style phone pre-screen about my background and basic logistics. Then it became very technical. In a manager-style round, I walked through my resume and projects, which led into coding on a couple of medium LeetCode problems, mostly strings and arrays where edge cases mattered. The next technical discussion stayed in that problem-solving lane, with emphasis on RTL kno…

HR Screen0
ALTEN Technology USASoftware Engineer
Reported Jul 2026

ALTEN Technology USA Software Engineer Interview Experience: A missed technical meeting after an HR briefing

My process began with an HR call that did not really feel like an interview. There were no questions to verify my skills, only a briefing about what would come next. For the second technical meeting, I joined on time and waited about an hour, but nobody showed up. I flagged it immediately and never received an apology or explanation for the lost time or the preparation I had done. After two follo…

No responseHR Screen0
Alten SpainSoftware Engineer
Reported Jul 2026

Alten Spain Software Engineer Interview Experience: One hour waiting for a technical interview that never happened

My experience was extremely unprofessional. The early steps already showed little seriousness. The first HR meeting was not a real interview: there was no skills assessment and no technical or substantive question, only a briefing about the next phase. For the second technical meeting, I was on time but waited an hour without anyone appearing. I raised it immediately and expected an apology or at…

No responseHR Screen0
Alten NederlandSoftware Engineer
Reported Jul 2026

Alten Nederland Software Engineer Interview Experience: An HR briefing and an unattended technical stage

My first impression of the process was terrible because of how unprofessionally it was handled. HR was supposed to conduct the first interview, but it was not really an interview. There was no skills assessment and no questions, only a briefing about what would follow. Then came the second technical stage. I arrived on time and waited for more than an hour, but nobody showed up. I reported it as…

No responseHR Screen0
Alten Delivery Centre SpainSoftware Engineer
Reported Jul 2026

Alten Delivery Centre Spain Software Engineer Interview Experience: A missed appointment and no technical feedback

My process began frustratingly. Even while arranging it, I noticed misalignment and little care around timing. I had appointments where the other person seemed more focused on their own CV than on what was actually needed for the technical interview. In one instance, I arrived on time and waited without anyone coming. I flagged it immediately, but got neither an explanation nor an apology for the…

No responseTechnical Screen0
AltenSoftware Engineer
Reported Jul 2026

Alten Software Engineer Interview Experience: A cyber invitation that became DevOps paperwork

My path with Alten was long, despite my initial impression. After several steps, I had to complete a skills dossier that, in substance, looked almost like a copy of my CV. I was also struck by the gap between what I was told and what actually happened: I had been invited to talk about cyber, but the focus ended up being DevOps. Overall, it was not a technical experience or a process that added re…

Offer0
AltenSoftware Engineer
Reported Jul 2026

Alten Software Engineer Interview Experience: An HR briefing, a missed technical meeting, and silence

I had a very unprofessional process. The first HR meeting did not resemble a real interview: there was no check of my skills and no questions, only a briefing about how the selection process would continue. For the second technical meeting, I arrived on time but waited about an hour without anyone showing up. I raised it immediately, but I received no apology or explanation for the time and prepa…

No responseHR Screen0
First Quality LaboratoryAccount Executive
Reported Jul 2026

First Quality Laboratory Account Executive Interview Experience: A fast offer with clear hustle-culture expectations

I had an easy, low-friction start. I spoke with someone by phone, answered a couple of questions, and they set up a more detailed interview within about a week. The process was smooth and welcoming, and the recruiter treated it as a real two-way conversation instead of a checklist. In the interviews, the role and expectations were explained clearly. The team seemed intentional about making sure I…

OfferHR Screen0
ZF GroupSoftware Engineer
Reported Jul 2026

ZF Group Software Engineer Interview Experience: An easy Teams round followed by deeper resume questions

My process had two structured rounds. The first was a Teams interview that felt relatively easy and stayed close to C programming fundamentals and Autosar concepts. I remember answering everything correctly, which helped me relax into the conversation. The second round went deeper into the skills on my resume. The questions were no longer surface-level; they asked about the reasoning behind what…

OfferTechnical Screen0
ValeoSoftware Engineer
Reported Jul 2026

Valeo Software Engineer Interview Experience: Academic projects, C fundamentals, and ECE questions

My first round was a written test that felt easier. Then we discussed projects I had completed during my academics, with a strong focus on C basics. The interviewers cared most about my project, so I had to explain every block and why I chose each component. They followed up with "why" and "what if" questions. They also tested C fundamentals directly: pointers, arrays, strings, functions, structu…

Online Assessment0
Delivery HeroSoftware Engineer
Reported Jul 2026

Delivery Hero Software Engineer Interview Experience: Three quick and kind rounds

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…

Technical Screen0
ValeoSoftware Engineer
Reported Jul 2026

Valeo Software Engineer Interview Experience: HackerRank, an online-store task, and a project walkthrough

The process began after I sent my CV. I completed a HackerRank assessment covering backend, frontend, HTTP, and cloud-related knowledge. Then they sent a task to build a simple online store or marketplace. The next step was an interview where I walked through the task and my experience, including what I did and how I approached it. The process felt structured and work-like because the conversatio…

Online Assessment0
TSMCSoftware Engineer
Reported Jul 2026

TSMC Software Engineer Interview Experience: A same-week invitation for a different role

After applying to multiple positions, I received an interview invitation for a role different from the one I had originally targeted. Scheduling was fast: once I accepted, the interview was set for that same week. When I wrote my update, the interview had not happened yet. My experience was mostly about the quick turnaround. I did not yet know the difficulty or the specific questions, but the pro…

In progress0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP