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

TSMCSoftware Engineer
Reported Jul 2026

TSMC Software Engineer interview: waiting after the interview invitation

At the time of my update, I was only at the early stage. I had just received the interview invitation and was waiting to see how the experience would go. I was looking for guidance from people who had already been through the process because I did not yet have firsthand details. I could not judge the difficulty because I had not interviewed yet. I felt anticipatory and cautious, trying to get som…

0
Tata CommunicationsSoftware Engineer
Reported Jul 2026

Tata Communications Software Engineer interview: networking fundamentals and project discussion

After speaking with a recruiter, I had a fairly relaxed technical conversation about core electronics and networking fundamentals. We covered basic electronic concepts, then the OSI and TCP/IP models, common networking protocols, and usual networking tools. A substantial part of the discussion was my project: how I implemented it, what problems came up, and what I personally contributed. They wan…

Technical Screen0
Prime VideoSoftware Engineer
Reported Jul 2026

Prime Video Software Engineer interview: DSA, design, and leadership principles

My process began with an online assessment on data structures and algorithms. Soon after that, I had a technical phone screen, followed by a final loop of multiple consecutive rounds. What I remember most is how much the later interviews emphasized Amazon leadership principles alongside system design. The technical and behavioral sides were not separate in the loop. System design was a major them…

Online Assessment0
Prime VideoSoftware Engineer
Reported Jul 2026

Prime Video Software Engineer interview: two practical programming problems

My assessment was practical and a little different from standard LeetCode. I got two programming questions that increased in difficulty. The first was fairly trivial math, while the second was more interactive and open ended about what they wanted. For the second problem, I had to work out the intended requirements and then implement several functions to make the solution work. It felt as though…

0
QualcommSoftware Engineer
Reported Jul 2026

Qualcomm Software Engineer interview: 30-question screen and DSA threshold

My process began with a multiple-choice screen of 30 questions. I needed at least 50% correct to move on, so the threshold was clear from the start. The next step was a technical screen on algorithms and data structures. I worked through classic sorting-style material, including moving all zeros to the end of an array, along with other DSA questions based on common algorithm patterns. It felt str…

Technical Screen0
SpeechifySoftware Engineer
Reported Jul 2026

Speechify Software Engineer interview: proctored timed assessment and screencast

The early technical step felt unusually uncomfortable because it was heavily proctored and camera-driven. I had to keep my camera on during a timed assessment, and the recording requirements made it feel more like surveillance than collaboration. It was an independent test, with no live interviewer helping while I worked. The assessment required a screencast. There were rules against AI tools and…

0
RevolutOperations Manager
Reported Jul 2026

Revolut Operations Manager interview: 30-minute screen and aptitude-test cutoff

I began with a 30-minute screening call about introductory context and my background. Right after that, I took a UCAT-style criteria aptitude test. The threshold for moving forward was very high. I scored below it and was rejected immediately, so I did not get to later steps. It ended quickly, with no extended follow-up or extra rounds. The test was the whole gatekeeping moment, and it felt unfor…

Rejected0
RoktSoftware Engineer
Reported Jul 2026

Rokt Software Engineer interview: CCAT, personality test, and one-way video

After applying, I was put through an automated sequence. First came the Criteria Cognitive Aptitude Test and the Employee Personality Profile. The CCAT was a timed, IQ-style block with pattern-recognition and math-style items. The personality portion took about 10 to 12 minutes and had no time limit. Some prompts were straightforward enough that it did not feel like a serious gatekeeping exercise…

No response0
SlalomConsultant
Reported Jul 2026

Slalom Consultant interview: friend referral and quick conversational process

My first conversation with Slalom came through a friend connection, so it started informally and felt friendly. They were flexible about my availability, and that tone carried into scheduling. It took less than a week to move from outreach to a real meeting, and the recruiter followed up at the exact time we had agreed on. The interviews were conversational rather than interrogation-style. They m…

Offer0
UiPathSoftware Engineer
Reported Jul 2026

UiPath Software Engineer interview: positive live feedback followed by rejection

After a recruiter resume screen, I had about an hour for a medium LeetCode-style technical round. The interviewer first asked questions tied directly to my resume, then moved into coding. It felt like a straightforward session about how I think, not a puzzle-only test. I got positive feedback during the live problem-solving portion. A week later, I received a canned rejection saying I lacked the…

Rejected0
The SleepAccount Executive
Reported Jul 2026

The Sleep Account Executive interview: sales objections and manager scenarios

After applying, I had a recruiter phone screen about my background and how my sales experience would translate to the role. The questions were standard: why I wanted the job, how I would help customers, and how I handled objections or difficult situations. There was strong emphasis on confidence, being self-starting, and giving a detailed example of pushing past a customer objection and how the s…

0
VerkadaAccount Executive
Reported Jul 2026

Verkada Account Executive interview: sales sequence with recruiter ghosting

I went through what looked like a standard sales-track process: an internal recruiter round, a sales-manager round, a data-and-sales-figures review, and then a peer from the sales team I would have joined. On paper it sounded straightforward, but the coordination was a mess. I received requests for times I had already said I was unavailable. The recruiter asked again for availability for the foll…

No response0
TargetAccount Executive
Reported Jul 2026

Target Account Executive interview: virtual team conversations ended by scheduling

My process began with an HR call about my experience and what I was looking for. Then I had a virtual round and a few more Zoom meet-and-greet conversations with team leads and store managers. It felt organized and friendly, and people seemed genuinely interested in getting to know me. The process stopped because of scheduling conflicts on my side, not because of anything in the interviews. I lef…

Withdrew0
SyntesSoftware Engineer
Reported Jul 2026

Syntes Software Engineer interview: relaxed half-day panel session

Recruiter outreach came first, and they connected me with the team. The atmosphere was easygoing, and everyone felt friendlier than the people I had met at other European pharma companies. The process moved quickly into two rounds: a short call with the hiring manager, then, about a week later, a half-day in-person session. That session consisted of several panel-style conversations. Most intervi…

0
AMDSoftware Engineer
Reported Jul 2026

AMD Software Engineer interview: RTL verification and debugging fundamentals

My interviews were hardware-centric from the start, with a strong focus on verification and digital-design fundamentals. I had a digital and RTL round covering Verilog/SystemVerilog, UVM, and the practical work of verification. A second round brought together projects and real scenarios. The first technical section asked for solid fundamentals rather than broad buzzwords. The project round asked…

Rejected0
Amazon Web ServicesSoftware Engineer
Reported Jul 2026

Amazon Web Services Software Engineer interview: timed OA and leadership-principles discussion

After a recruiter call, I completed an online assessment that took a few hours. It included DSA, Leadership Principles, and a work-style simulation about what I would do in a typical workday. I had to manage time tightly and optimize as I went. It felt fair but not forgiving. Soon after, I had a technical and behavioral interview. I worked through a medium-to-hard DSA problem and then answered Le…

Offer0
ADPAccount Executive
Reported Jul 2026

ADP Account Executive interview: behavioral sales questions and missing follow-up

After a recruiter conversation about the role, I met sales leadership over Zoom. The flow felt organized and reasonable on timing, with each round checking a different part of my background and fit. I got standard why-sales and why-ADP questions, but the focus stayed on my work, how I handle situations, and whether I had the drive to close. The process was behavior-focused. My answers needed stru…

0
AmazonSoftware Engineer
Reported Jul 2026

Amazon Software Engineer interview: behavioral bar-raiser, DSA, and low-level design

My process started with an online assessment, then a loop of about three back-to-back interviews. It felt difficult. After the assessment, I had a fully behavioral session with a bar-raiser-style focus. The next two interviews were technical. One leaned on classic DSA, and the other moved toward lower-level system design. Each had a walk-me-through-your-reasoning feel: reaching the right answer w…

0
AmazonSoftware Engineer
Reported Jul 2026

Amazon Software Engineer interview: math prompt and interactive implementation

I began with two practical programming questions that felt more like testing how I translate an idea into working code than trick problems. The first was straightforward math. The second was interactive: I had to work out what the interviewer wanted and implement several functions to reach the final behavior. The second question made the process difficult because it required more back-and-forth t…

0
AmazonSoftware Engineer
Reported Jul 2026

Amazon Software Engineer interview: AI debugging and design rounds

The online assessment felt more demanding than a coding-only test. Along with two medium-to-hard DSA questions, it had an AI project-debug section and a working-style questionnaire. The follow-up sequence had three rounds on DSA, high-level design, and low-level design. The overall difficulty felt difficult. The tightly packed assessment and later rounds made the design portions feel especially h…

0

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