Interview Experiences

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

Share yours, earn XP

4433 stories

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

Amazon Web ServicesSolutions Architect
Reported Jul 2026

Solutions Architect interview at Amazon Web Services: withdrew after technical round

I entered through a referral and passed an initial assessment. That led to a recruiter phone screen and then a technical interview, so the process moved forward quickly once I cleared the test. I withdrew after the technical round and did not experience the full multi-round loop. The early funnel felt normal: assessment, recruiter call, then technical screen. Since I chose to step away, I cannot…

Withdrew0
AmazonSoftware Engineer
Reported Jul 2026

Software Engineer interview at Amazon: networking follow-ups

A phone screen began with my current experience and projects, then each response drew deeper questions. I used STAR structure for behavioral answers as the interviewer pressed past surface-level descriptions. Technical discussion covered TCP/IP and routing topics, including OSPF and BGP. It was an engaging but difficult conversation because of the depth expected in both storytelling and networkin…

0
AmazonSoftware Engineer
Reported Jul 2026

Software Engineer interview at Amazon: leadership narrative challenge

My three-round loop had two DSA rounds and a Leadership Principles round. The first DSA round included two medium LeetCode questions. The second had one medium and one hard question involving DP and graphs. The Leadership Principles interview was harder for me than DSA because it required a convincing narrative about how I would operate under Amazon's values. I did not receive an offer. The proce…

0
Zensar TechnologiesSoftware Engineer
Reported Jul 2026

Software Engineer interview at Zensar Technologies: unexpected technical round

The first technical interview was professional and covered .NET fundamentals and cloud basics. A later round was described as casual and HR-like but arrived as an unannounced technical-heavy interview. The interviewer felt rude and impatient, and the questions seemed limited to that person's own expertise rather than a fair view of what I could contribute. HR later ended communication by saying t…

0
ServiceNowSolutions Consultant
Reported Jul 2026

Solutions Consultant interview at ServiceNow: positive interviews and silence

After a recruiter screen, I had a quick hiring-manager call and two peer interviews back to back. They were personable conversations about my experience, motivation, understanding of the role, and basic experience-based questions. Both peers spoke positively and pointed me toward the next stage. Then communication stopped. I followed up after about a week and again later, but received only a feed…

No response0
SalesforceSoftware Engineer
Reported Jul 2026

Software Engineer interview at Salesforce: Futureforce offer

I applied to the Futureforce tech accelerator and received a HackerRank OA with two or three LeetCode questions. After about a month, I advanced and attended an online preparation presentation with engineers for the system-design discussions ahead. The interview combined behavioral discussion of projects and AI use with a LeetCode question and follow-ups. A week later, I received and accepted an…

Offer0
IBMSoftware Engineer
Reported Jul 2026

Software Engineer interview at IBM: automated rejection and silence

I completed a HackerRank online assessment under a tight timeline, but much of the rest of the process lacked human contact. I later received an automated-looking rejection notice without having heard from an actual person. In another similar timeline, I completed a HireVue-style interview with standard prompts and then waited more than a month and a half without an update. That long silence felt…

Rejected0
Burns & McDonnellSoftware Engineer
Reported Jul 2026

Software Engineer interview at Burns & McDonnell: full-day onsite

I attended a full-day interview beginning with a short presentation on my background and experience. I then met in panels and individual conversations with engineers and managers, covering several perspectives on my fit. There was also a recruiter touchpoint and time to see the workplace and culture. The day was long but organized, with each part connected to how I thought and would work with the…

Offer0
BrillioSoftware Engineer
Reported Jul 2026

Software Engineer interview at Brillio: HR then technical fit

The process had two stages. First, I had a telephone discussion with HR about my background, experience, and expectations for the role. The next interview assessed problem solving, technical knowledge, past projects, and overall fit. It was a standard, straightforward sequence of context-setting followed by technical evaluation. Location: India. Overall feedback: positive. Offer status: no offer.

0
GoogleSoftware Engineer
Reported Jul 2026

Software Engineer interview at Google: long formal loop

The process took roughly one to two months, then extended further through team matching. It began with CV screening and a technical coding phone interview, followed by an onsite loop with several 45-minute coding interviews, architecture discussions, and Googliness questions. After the interviews came a formal hiring-committee stage and team matching, with a proposal only if a team aligned. The m…

0
MicrosoftSoftware Engineer
Reported Jul 2026

Software Engineer interview at Microsoft: respectful recruiter screen

The recruiter screen was prompt and professional. The recruiter explained the role, asked about my background, and clarified expectations, so the conversation did what an early fit check should do. I did not advance or receive an offer. The process felt clear and respectful, but the experience reminded me that an early screen can still be decisive even when the conversation goes well. Location: U…

0
Accenture EspañaSoftware Engineer
Reported Jul 2026

Software Engineer interview at Accenture España: smooth early rounds

I had an HR round and a business round, and the process wrapped up in about two weeks. It was straightforward, and I left feeling I had performed well. I was not selected, though the rejection communication was professional. Elsewhere in the process, delays and logistics problems showed how inconsistent the candidate experience could be. I came away feeling that confidence in the interviews did n…

Rejected0
Act DigitalFull Stack Engineer
Reported Jul 2026

Full Stack Engineer interview at Act Digital: quick start and no closure

The process began with a relaxed HR conversation about my background and resume. Since the role was tied to a client through a third party, the early focus was fit and logistics rather than deep technical questions. The technical stage covered a framework and my experience. Scheduling from recruiter to client moved quickly, but after the client interview I received no meaningful feedback despite…

No response0
Arch Global Services PhilippinesSoftware Engineer
Reported Jul 2026

Software Engineer interview at Arch Global Services Philippines: prolonged silence

The hardest part was the disorganized communication after I invested time. In one assessment flow I did not advance but at least received a rejection email. In others, I completed interviews or assessments and then heard nothing when I expected scheduling or status updates. Gaps between rounds reached three to four weeks, and after a final round the silence lasted months without feedback or an of…

0
AltimetrikSoftware Engineer
Reported Jul 2026

Software Engineer interview at Altimetrik: relevant frontend discussion

After recruiter conversations, I had a practical technical discussion on JavaScript, React, TypeScript, system design, performance optimization, and general problem solving. It felt connected to actual frontend work rather than random trivia. The HR round was transparent about role expectations and the hiring process, and the interviewer was approachable. Background verification and later communi…

Offer0
Amazon DSPSoftware Engineer
Reported Jul 2026

Software Engineer interview at Amazon DSP: principle-driven loop

My interview flow started with a recruiter screen, then an online assessment and technical interviews. Coding and behavioral evaluation were tied closely to Amazon Leadership Principles, particularly how I described ownership, impact, and decisions. GenAI concepts also appeared. The process was organized and serious, but I did not receive an offer. I understood the material, yet I could not turn…

0
Amazon DSPSoftware Engineer
Reported Jul 2026

Software Engineer interview at Amazon DSP: four DSA rounds

I went through four rounds that mixed DSA and behavioral evaluation. The first included two medium-hard questions with DP and graph themes, plus project discussion. The second had two easier-medium DP and string questions with more behavioral material. The third included one easy sliding-window-style problem. Although I felt some answers were reasonable, I did not make it past the earlier cutoff.…

0
Amazon AdvertisingSoftware Engineer
Reported Jul 2026

Software Engineer interview at Amazon Advertising: Leadership Principles

The process covered several technical levels, bar-raiser-style evaluation, and a program-manager round. Expectations were communicated clearly, and Amazon Leadership Principles were central even during technical discussions, where impact and ownership still mattered. The full process took nearly a week in business-day terms. I did not receive an offer, but the structure stayed consistent enough t…

0
Infosys FinacleConsultant
Reported Jul 2026

Consultant interview at Infosys Finacle: fast technical and HR process

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…

Offer0
HylandSoftware Engineer
Reported Jul 2026

Software Engineer interview at Hyland: technically prepared but not selected

After a pre-placement talk, I moved into a technical interview that felt normal for the role. I completed most of the work I was given, and the difficulty did not seem unusually high. The process was more competitive than I expected. I had not read the presentation as an immediate rejection, yet I was ultimately rejected. My preparation seemed adequate for the technical portion, which made the ou…

Rejected0

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