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

Accenture TechnologySoftware Engineer
Reported Jul 2026

Accenture Technology Software Engineer interview: Java, Spring Boot, and role mismatch

The interview focused heavily on Core Java and Spring Boot. I discussed Java OOP and concurrency, including multithreading, executor services, volatile, race conditions, and deadlocks. We also covered controller and rest controller annotations, the N+1 query problem, and eager versus lazy loading. There was a stream-related coding question as well. The experience was not smooth throughout. In one…

OfferTechnical Screen0
Honeywell TechnologiesSoftware Engineer
Reported Jul 2026

Honeywell Technologies Software Engineer interview: role fit and communication

I was first contacted for an introductory conversation and then moved to a technical interview. The technical discussion centered on the role itself, what I would be doing, and how well I understood the requirements. They also asked about my English language skills and my studies. It felt more like a screen for fit and communication than a hard technical challenge. I did not receive an offer, but…

Technical Screen0
Accenture in IndiaSoftware Engineer
Reported Jul 2026

Accenture in India Software Engineer interview: Core Java and Spring Boot

I expected a normal technical conversation, and that was what I got: focused, direct, and largely about Core Java and Spring Boot. The questions covered object-oriented programming and concurrency, including multithreading, executors, volatile behavior, race conditions, and deadlocks. On the Spring Boot side, I was asked about annotations such as @Controller and @RestController. They also tested…

OfferTechnical Screen0
Prime VideoSoftware Engineer
Reported Jul 2026

Prime Video Software Engineer interview: prior Python services and module ownership

A recruiter brought me into what felt like a screen focused on experience. Rather than starting with deep technical questions, the conversation was about my previous company and what I had been doing day to day. I described my work on Python services and a module system I built, stressing how critical it was to the broader setup. That focus on my actual work history shaped the interview and did n…

0
PerficientSoftware Engineer
Reported Jul 2026

Perficient Software Engineer interview: agentic AI and continuous feedback

I applied through the careers site and heard from a recruiter within about a week. The first phone screen covered my background and why I was interested in the role, and the process felt organized from the beginning. I then had a technical round with a senior developer that discussed technical agentic AI patterns and included some hands-on evaluation. What stood out was how smoothly the process r…

Technical Screen0
PalantirSoftware Engineer
Reported Jul 2026

Palantir Software Engineer interview: algorithms, REST API, and learning loop

After a recruiter call about my background and interests, I took a coding assessment with two medium-style algorithm questions and a REST API task. About a day later, I had a 45-minute technical interview that stayed focused on practical problem solving instead of theory alone. The process then moved into an onsite-style loop about learning and decomposition. In one round, I broke down an ambiguo…

Technical Screen0
Palantir technologiesSoftware Engineer
Reported Jul 2026

Palantir technologies Software Engineer interview: coding, REST API, and decomposition

I began with a short recruiter call that felt like a fit and motivation check rather than a technical grilling. I discussed my background and past work, and I got the sense they wanted to know whether I cared about the mission and the real-world impact of the software, not just the title. About a week later, I had a technical screen with a small set of coding questions: a couple of LeetCode-style…

Technical Screen0
Silicon LabsSoftware Engineer
Reported Jul 2026

Silicon Labs Software Engineer interview: unstable connection and scheduling breakdowns

My experience started with a scheduling mess and became an uncomfortable call. I told HR in advance that I would be overseas and might have an unstable connection because I would need a VPN. The first part of the interview was choppy, although it eventually stabilized. I could not shake how the hiring manager reacted. They seemed visibly impatient and annoyed throughout, and when I asked question…

Technical Screen0
SafranSoftware Engineer
Reported Jul 2026

Safran Software Engineer interview: written aptitude and technical test

I remember a fairly structured process. After an initial recruiter discussion, I later completed a short written test with aptitude and technical questions. I had only 45 minutes to finish the whole test. That was followed by two interviews. The first covered basic questions related to the field. The second was more application oriented and lasted about 30 to 45 minutes. The whole process felt me…

Online Assessment0
SamsaraAccount Executive
Reported Jul 2026

Samsara Account Executive interview: recruiter, hiring manager, and panel final

After a quick recruiter conversation, I spoke with the hiring manager. Those early calls were information focused rather than overly formal. The recruiter set context, and the hiring manager asked about my past experience, what I wanted in a company, and whether my background matched the role. The process was organized and not overly complicated. I moved through a small number of rounds, but the…

HR Screen0
Southern California EdisonSoftware Engineer
Reported Jul 2026

Southern California Edison Software Engineer interview: STAR panel and electrical concepts

I started with a talent-acquisition recruiter call. Because I matched the role requirements, I moved to a four-person panel interview. They took turns asking questions, so the conversation was structured but moved quickly as each interviewer joined in. Most questions were behavioral and expected STAR-style answers. I was pressed about past experience and how I handled particular situations, with…

Technical Screen0
SwiggySoftware Engineer
Reported Jul 2026

Swiggy Software Engineer interview: DSA, LLD, and system design

I went through a straightforward Swiggy loop that flowed smoothly. After the recruiter touchpoint, I had two rounds: a coding interview on DSA and LLD-style patterns, then a system design round with an engineering manager. The difficulty felt average. The DSA and LLD portion was standard enough that I was not completely thrown off, and the system design discussion felt manageable but thoughtful r…

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

U.S. Bank National Association Business Analyst interview: organized behavioral rounds

I began with an HR screen about my background, experience, and behavioral questions. Everything felt organized, and the communication about scheduling and next steps was clear enough that I never felt lost. Later rounds remained formal but friendly. The interviewers asked many behavioral questions and created a comfortable rhythm, which made it easier to discuss my experiences without overthinkin…

HR Screen0
TELUS Digital -Account Executive
Reported Jul 2026

TELUS Digital - Account Executive interview: concerns about fairness

I did not find the process fair, and I left discouraged. I felt I was not given the same opportunity to show my skills and experience as other candidates, which made the experience feel uneven. As the interview progressed, I got the impression that I was being treated differently. That changed how I felt during it. Instead of feeling able to present my strengths clearly, I kept wondering whether…

0
Oracle HealthSoftware Engineer
Reported Jul 2026

Oracle Health Software Engineer interview: five-hour loop and existing Java codebase

A recruiter contacted me about two weeks after I applied. The recruiter call was basic, and a technical screener was scheduled for the following week. That first technical conversation was friendly and straightforward, almost a check on basics such as if-else control flow. The final loop was much harder to arrange: five separate one-hour interviews spread across a week, and I took PTO to make it…

Technical Screen0
Tata Consultancy Services (North America)Software Engineer
Reported Jul 2026

Tata Consultancy Services (North America) Software Engineer interview: long venue wait

My experience at the venue was disappointing because the day felt poorly managed. I arrived early but waited a long time before my name was called for the first round, late in the evening after most of the day had gone by. There were many other candidates, and I could not tell how the calling order was decided. The invitation gave a smaller time window, but the process ran until around the evenin…

Online Assessment0
JPMorganChaseBusiness Analyst
Reported Jul 2026

JPMorganChase Business Analyst interview: managing-director conversation

After I applied, HR emailed to schedule an interview with the managing directors for the group I was targeting. The meeting lasted about 45 minutes and stayed focused on my experience and fit for the role. I left feeling that they had real context for what I brought to the conversation. It did not feel like generic small talk. The meeting itself was not long, but the seniority of the people invol…

HR Screen0
JPMorganChaseSoftware Engineer
Reported Jul 2026

JPMorganChase Software Engineer interview: internet search and notes-based coding

My interviews leaned on software engineering fundamentals, not only coding. I was asked what happens when someone makes an internet search, including the behavior under the hood and what the system does end to end rather than just definitions. There were also a couple of LeetCode-style questions, but I answered them in a notes-style environment instead of compiling code. The difficulty felt tough…

0
MercorSoftware Engineer
Reported Jul 2026

Mercor Software Engineer interview: AI-generated resume-tailored questions

My interview was conducted entirely through an AI platform. It generated questions tailored to my resume, and I found the process efficient and positive. Even though it used AI, it did not feel like a cold or mechanical interaction. The questions sounded natural, and the exchange felt more human than I expected. It was comprehensive for the time it took but still moved smoothly. I felt the AI pac…

Offer0
LTMSoftware Engineer
Reported Jul 2026

LTM Software Engineer interview: cancelled offer after document checks

I completed every technical face-to-face round and felt confident I had cleared the hardest part. The process then moved to employment documents. I was asked for material from my previous employers, but I could not provide a bank statement from my first employer because that job was from several years ago. I submitted everything else I could, including PF records and bank statements from later em…

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