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

HexawareSoftware Engineer
Reported Jul 2026

Hexaware Software Engineer interview: crowded multi-round process

I found the Hexaware process extremely long and crowded. Around 300+ people arrived for interviews, and it felt built for a large batch rather than careful one-on-one assessment. There were about two or three technical rounds, roughly an hour each, plus a managerial round. The main challenge was patience. Without the ability to sit through delays and wait for my turn, the process itself would hav…

Technical Screen0
Hays TechnologyConsultant
Reported Jul 2026

Hays Technology Consultant interview: consulting role and group assessment

My first in-person interaction focused on what the role meant day to day. They explained the position, the research and selection area, the team, and the kind of consulting work involved. We also discussed contract types, hybrid work, the selection process, and relationships with clients. The later conversations focused on recruitment and culture rather than heavy testing. I met people connected…

Onsite0
ASMSoftware Engineer
Reported Jul 2026

ASM Software Engineer interview: resume presentation and CS fundamentals

After a quick recruiter touchpoint, I had a 60-minute Teams interview with two senior software engineers. We began with my resume and projects, including questions about what I had built and how I approached it. Then we covered several straightforward CS fundamentals and finished with a manageable coding challenge. Later rounds followed a similar pattern: a short presentation about my work, follo…

HR Screen0
GHDSoftware Engineer
Reported Jul 2026

GHD Software Engineer interview: technical and STAR questions

After applying, I had an organized and professional early process. I began with a recruiter conversation about my background and role fit. My final conversation was with two interviewers, who started with a brief overview of the company and what they wanted. The interview mixed technical and competency questions but felt welcoming rather than combative. I explained my experience and problem-solvi…

RejectedHR Screen0
ADCI - KarnatakaSoftware Engineer
Reported Jul 2026

ADCI - Karnataka Software Engineer interview: HackerRank and AI assistance

I was given a HackerRank take-home exam and did not do well on it. I did not fully solve everything. After that, I faced another problem involving "AI assistance," but the help felt intentionally unhelpful. My impression was that I was better off ignoring it and solving the task directly. I still reached the next interview stage, where I answered LeetCode-style questions and explained my experien…

RejectedTake-home Project0
Abercrombie & FitchAccount Executive
Reported Jul 2026

Abercrombie & Fitch Account Executive interview: casual group setting

I had a casual, low-pressure group interview in a store setting. I sat with other applicants while the interviewer asked a small set of questions. It seemed intended to gauge how I carried myself, particularly around customer service, interacting in the moment, style, outfit presentation, and the energy I would bring to the brand. The questions covered my past experience, time management and orga…

OfferOther0
GlobalFoundriesSoftware Engineer
Reported Jul 2026

GlobalFoundries Software Engineer interview: conversational department panel

My interview began with a behavioral conversation with two people from the department. The focus was on day-to-day fit and how I would work, and it never became a technical grilling. What I liked was having time at the end for many questions. I planned ahead to ask about things that mattered to me, including employee resource groups. That exchange made the interview feel more like a conversation…

Technical Screen0
ADCI - KarnatakaSoftware Engineer
Reported Jul 2026

ADCI - Karnataka Software Engineer interview: AI-usage and top-k prompt

After the OA, I had two one-hour interviews. Both contained technical questions and leadership-principles discussion, and both included a question about using AI. In one hiring-manager-style round, I was given a prompt without an API that was framed as a variation on top-k elements. Another technical round used a more story-driven setting, including a restaurant-manager scenario involving groups…

Technical Screen0
ADCI - KarnatakaSoftware Engineer
Reported Jul 2026

ADCI - Karnataka Software Engineer interview: leadership principles and design

I began with an online assessment that combined Amazon leadership-principles behavioral questions with coding. After I passed it, I went to in-person interviews. The first was with the hiring manager and was mostly behavioral, with many leadership-principles questions plus discussion of my past experience and projects. Near the end of that sequence, I had a system-design coding problem. Then I me…

Online Assessment0
Prime VideoSoftware Engineer
Reported Jul 2026

Prime Video Software Engineer interview: sliding window and debugging

The interviews started simply enough with a behavioral component and a LeetCode-style coding problem. I found the behavioral part harder than expected because it was situation based and open ended. They cared about how I would approach a scenario and what my thinking looked like. In the phone-style flow, I also had a medium-difficulty coding question that used something like a sliding-window appr…

Technical Screen0
Prime VideoSoftware Engineer
Reported Jul 2026

Prime Video Software Engineer interview: four in-person rounds

After I finished the online assessment, I eventually heard back and was invited to an in-person set of interviews. The process was smooth, professional, and friendly. I had four rounds with a lunch break in the middle. One was purely behavioral, while the other three blended behavioral discussion with technical evaluation. The technical topics I remember were topological graph sorting, cycle dete…

Online Assessment0
Raytheon Technologies Corporate HeadquartersSoftware Engineer
Reported Jul 2026

Raytheon Technologies Corporate Headquarters Software Engineer interview: C++ resume deep dive

After speaking with a recruiter, I had two back-to-back rounds. The first was easygoing and focused on how I thought about code, core OOP ideas, and software-engineering fundamentals. I walked through what I had built and how those concepts appeared in practice. The second conversation was tougher. I met the hiring manager and several engineers, and they went deeply into my resume. Surface-level…

RejectedHR Screen0
RaytheonSoftware Engineer
Reported Jul 2026

Raytheon Software Engineer interview: resume-depth second round

The first interview was surprisingly laid-back. We spent a lot of time on OOP, including the classic four pillars, and broader software-engineering fundamentals. I explained how I thought about code, and it did not feel like they were trying to catch me out. The second round was a real step up. Several engineers and the hiring manager joined, and they examined the details behind what I had put on…

RejectedTechnical Screen0
PhonepeSoftware Engineer
Reported Jul 2026

Phonepe Software Engineer interview: DSA and order-feed design

After a recruiter-style touchpoint, the process became technical quickly. I had a machine-coding round on a hackathon platform with a live panel and several candidates on the call. The interviewer gave the problem, I worked alone in a tight window of about 90 minutes in one phase, and I sent my working solution to the recruiter in a zip file. Soon afterward, an interviewer reviewed my work in a r…

Technical Screen0
PhilipsSoftware Engineer
Reported Jul 2026

Philips Software Engineer interview: rushed panel logistics

My process had three rounds and felt like a quick sprint. I began with a phone screen, then had a virtual one-on-one with a manager, and finally a panel with several interviewers. The panel was not smooth: one person was on time, another arrived late, and one never appeared. I was also pushed to begin the next round immediately, so the flow felt rushed and poorly planned. The questions themselves…

Technical Screen0
PaychexSoftware Engineer
Reported Jul 2026

Paychex Software Engineer interview: take-home and load testing

After speaking with the recruiter, the process moved quickly into structured technical work. I had a technical screen with clear questions about my experience, then a longer coding take-home. Afterward, we reviewed my solution and covered more basic technical questions about fundamentals and how I approached the problem. Next came a longer manager discussion with behavioral questions and addition…

HR Screen0
SprinklrSoftware Engineer
Reported Jul 2026

Sprinklr Software Engineer interview: running median and LRU

I started with an online coding assessment, then moved into interviews that leaned heavily on classic DSA and competitive-programming-style problems. In the first interview, I was asked about finding the median in a running stream and about an LRU cache. It felt practical, as though they were testing whether I understood the data structures underneath the ideas. That round also included a horses…

Online Assessment0
Scientific ResearchSoftware Engineer
Reported Jul 2026

Scientific Research Software Engineer interview: CAPA panel

After applying online, I first spoke with a recruiter about the role and my background. That conversation was focused on fit and helped set expectations for what the hiring team cared about. Soon after, I had a panel-style interview that combined technical and situational discussion. Even when the topics became specific, the tone was conversational. The technical discussion centered on my CAPA-st…

RejectedHR Screen0
RevolutOperations Manager
Reported Jul 2026

Revolut Operations Manager interview: take-home and logic quiz

My interview path had several steps and felt more like a consulting-company funnel than a role-specific evaluation. After the early stages, I completed a take-home project and then faced a timed logic-question quiz that immediately changed how the process felt. The next major step was an interview with someone in the role I was applying for. What threw me off was how little the questions seemed r…

Take-home Project0
Samsung Austin SemiconductorSoftware Engineer
Reported Jul 2026

Samsung Austin Semiconductor Software Engineer interview: three-engineer panel

The process was very light and almost conversational. After a recruiter touchpoint, I had one panel interview with three engineers. There was no HR step attached to that day, no technical questions, and the atmosphere stayed relaxed. They asked behavioral questions about teamwork and my past projects. What stood out was that I was not being assessed for one narrowly defined opening. Instead, they…

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