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

GoogleBusiness Analyst
Reported Jul 2026

Google Business Analyst interview: technical screening and product communication

The interview loop felt fairly standard for Google, but I needed confidence at every stage. After speaking with a recruiter, I had a technical screen. The interviewer asked me to introduce myself, explain what I knew about the company and say why I wanted the role. We then moved to coding questions. The interviewer stayed relaxed as I worked. My impression was that they wanted me to keep steady a…

RejectedTechnical Screen0
Amazon Kuiper Commercial ServicesSoftware Engineer
Reported Jul 2026

Amazon Kuiper Commercial Services Software Engineer interview: debugging a full-stack repository

Much of my process involved coding and debugging at home. I started with a HackerRank/LeetCode-style question with about 40 minutes to work on it, followed by a debugging assignment that took around an hour. The repository was a full-stack application, and one API call wasn't behaving as expected. I had to trace the problem and fix it so all the tests passed. Understanding how the existing pieces…

0
Amazon DSPSoftware Engineer
Reported Jul 2026

Amazon DSP Software Engineer Interview Experience: DSA and rate limiter

The loop had no bar raiser, which made it look simpler on paper. Most rounds were DSA with a smaller set of low-level, product-style questions. The OA involved simulation-like grouping and sorting. In the live rounds, I found a median in an integer stream and identified the K most frequent elements in a stream. The low-level portion included implementing a sliding-window rate limiter. It felt str…

0
Amazon DSPSoftware Engineer
Reported Jul 2026

Amazon DSP Software Engineer Interview Experience: Full-stack debugging home test

I had an intense take-home stage. A home test split time between a HackerRank/LeetCode-style coding problem and a separate debugging task in what looked like a full-stack repository. In the debugging portion, an API call behaved unexpectedly. I had to find the bug and make every test pass, where small mismatches could break the result. The coding prompt was also time-boxed and seemed designed to…

0
Amazon AdvertisingSoftware Engineer
Reported Jul 2026

Amazon Advertising Software Engineer Interview Experience: Streams and rate limiting

My process focused on data structures and low-level reasoning, with leadership and workplace questions alongside them. There was no bar raiser, so it felt less like a large gauntlet and more like direct technical checks plus LP questions. The OA included simulation-style grouping and sorting. In live interviews, I worked on finding the median of an integer stream and the K most frequent elements…

0
Amazon AdvertisingSoftware Engineer
Reported Jul 2026

Amazon Advertising Software Engineer Interview Experience: Time-boxed debugging

The memorable part of my process was a take-home-style coding and debugging assignment. It began with HackerRank-like tasks in about 40 minutes, followed by a debugging section. In one version, I spent about an hour fixing an unexpected API-call behavior in a repository-style project so every test would pass. It was difficult because it resembled real work: I had to find why a larger codebase did…

Rejected0
Andela ProductsSoftware Engineer
Reported Jul 2026

Andela Products Software Engineer Interview Experience: Python, React, and live coding

I began with an online Python-and-React assessment that felt like a mini project. It started with debugging, then two Python functions using real data structures rather than LeetCode-style tasks. The logic was straightforward, but I spent most of my time writing tests. The final part was a React layout, and AI use was allowed there. After passing, I had a Python-focused interview covering Python,…

0
Infosys FinacleSoftware Engineer
Reported Jul 2026

Infosys Finacle Software Engineer Interview Experience: Hackwithinfy coding rounds

The process was framed as a Hackwithinfy hackathon, although it did not feel like a typical hackathon. I completed six coding questions across two rounds on two separate days, with MCQs mixed in. Clearing those rounds led to an in-person interview. That interview returned to coding, added a moderate SQL segment, and included system design discussion. The process stayed coding-heavy until the in-p…

0
LutronSoftware Engineer
Reported Jul 2026

Lutron Software Engineer Interview Experience: Technical barrage and app design

The first round was intense, more a barrage of technical questions than a calm conversation. I had to reason out loud as I went, which kept it stressful even when I felt confident. The next stage shifted to personality and professionalism, and that felt easier because it involved less technical problem solving. A later scheduling-app design session asked me to build the frontend and backend end t…

0
L3HarrisSoftware Engineer
Reported Jul 2026

L3Harris Software Engineer Interview Experience: HR and manager conversations

I started with an HR phone screen about my resume, past projects, and why I wanted the role. Next came a Zoom-style conversation with managers on the team. It was mostly behavioral, though a few lightly technical questions came up through how I described my experience and how I work. It was a typical multi-round process focused on my background and how I would operate in the role. Location: Camde…

Offer0
Kiewit CorporationSoftware Engineer
Reported Jul 2026

Kiewit Corporation Software Engineer Interview Experience: Fit and relocation

I began with a quick recruiter pre-screen that took under 15 minutes. It covered my past experience, what I wanted next, behavioral and situational questions, and logistics such as relocation. They said an in-person meeting could depend on where I lived, but my next step stayed virtual. The virtual interview was relaxed and light on technical depth. I explained my resume, how my work connected to…

0
ADCI - KarnatakaSoftware Engineer
Reported Jul 2026

ADCI - Karnataka Software Engineer interview: timed code and debugging home test

I received a home test with two hands-on parts. First, I had a HackerRank or LeetCode-style question in a fixed 40-minute window. Then I had 60 minutes to debug a full-stack-app repository where one API call was not behaving as expected. The task was to find the bug and make changes until every test passed. It felt hard because a real-project workflow contains moving context, and I needed to trac…

Take-home Project0
Accenture in IndiaSoftware Engineer
Reported Jul 2026

Accenture in India Software Engineer interview: assessment, communication, and HR

After a recruiter interaction, I went through three Accenture in India phases. The online assessment covered basic reasoning and aptitude, computer-science fundamentals, and coding. The coding included HTML/CSS, JavaScript, and a problem-solving task. The communication round asked me to mirror what was on screen, repeat audio, and give a roughly two-minute introduction. The final interview was HR…

OfferOnline Assessment0
Honeywell TechnologiesSoftware Engineer
Reported Jul 2026

Honeywell Technologies Software Engineer interview: interruptions and laughter

The Honeywell Technologies process started with HR, with the recruiter calling candidates one by one. I then met two interviewers in the interview room. Their tone threw me off. They seemed mean, laughed while I answered, and repeatedly interrupted me before I could finish. The format itself was ordinary, but I experienced the interaction as disrespectful and unreceptive. I did not receive an off…

HR Screen0
MBDASoftware Engineer
Reported Jul 2026

MBDA Software Engineer interview: values and CV Teams conversation

I had a friendly MBDA Teams call centered on whether my values aligned with the company. They asked what I could bring to the team and to MBDA, and they also asked about my CV. The tone was more probing than I expected because values and motivation drove the conversation. I left feeling that they took fit seriously, so the call felt more focused than a generic screening. Location: United Kingdom.…

Other0
MBDASoftware Engineer
Reported Jul 2026

MBDA Software Engineer interview: month between HR and recruiter meeting

I started with an HR phone call. About a month later, I met the recruiter on site at the Plessis-Robinson location. Every exchange I had with the people involved was positive. The meeting was structured but did not feel hostile or overly pressuring. They seemed to be trying to get a clear read on my fit. The month-long gap made the process feel slower than the interactions themselves. Location: L…

Other0
Texas InstrumentsSoftware Engineer
Reported Jul 2026

Texas Instruments Software Engineer interview: Webex HR and technical screen

I interviewed with Texas Instruments online over Webex. It was a compact two-step process: an HR screen followed by a technical interview with staff. Before we started, I had to share my screen with my resume and introduce myself from it. The screening and follow-up covered personality-style and technical questions. The whole process lasted about 30 minutes. It was my first real job interview, an…

HR Screen0
Super Micro ComputerSoftware Engineer
Reported Jul 2026

Super Micro Computer Software Engineer interview: pleasant but uncertain pacing

The people I spoke with at Super Micro Computer were nice, and once the process started, communication moved toward decisions quickly. The overall path was not laid out efficiently, though, and I still felt that the company took its time advancing me. The final stage had multiple interviews on engineering fundamentals related to the role. The questions were not unfair, but different interviewers…

Technical Screen0
U.S. Bank National AssociationFinancial Analyst
Reported Jul 2026

U.S. Bank National Association Financial Analyst interview: behavioral rounds and a superday

After the recruiter stage, the process felt relaxed and well paced. I was kept informed and had enough time to prepare between conversations. Most questions were behavioral scenarios about how I'd handle different situations. When I needed a moment to think, the interviewers were calm and patient. I never felt rushed. The process moved quickly through several conversations. Apart from the superda…

Other0
TeslaSoftware Engineer
Reported Jul 2026

Tesla Software Engineer interview: algorithms, behavior, and system design

After a phone recruiter screen, I had two Tesla rounds. The first was LeetCode-style and focused on algorithms and problem solving. The interviewer cared about whether I could reason through the problem end to end, not simply arrive at an answer. The second round mixed behavioral questions and system design. We discussed how I work, how I would architect a scalable solution, and how I think about…

OfferTechnical Screen0

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