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

LutronSoftware Engineer
Reported Jul 2026

Lutron Software Engineer interview: duplicate-removal problem

After the recruiter step, I had a short two-part interview. The technical part lasted about an hour and asked me to remove duplicates from an array without using a HashSet. I could choose the language, which made it feel more like demonstrating my reasoning than being put under unnecessary pressure. The behavioral discussion took about half an hour. The interviewers were nice, and both sections l…

OfferTechnical Screen0
Delivery HeroSoftware Engineer
Reported Jul 2026

Delivery Hero Software Engineer interview: backend-heavy technical rounds

The process began with an HR screen, moved through technical interviews, and ended with a hiring-manager discussion. I was not offered the role. The technical rounds were the hardest part. They covered Python fundamentals, backend development, system design, APIs, databases, concurrency, and general problem solving. The questions were practical and tied to engineering scenarios rather than stayin…

HR Screen0
FacebookSoftware Engineer
Reported Jul 2026

Facebook Software Engineer interview: two coding questions and onsite loop

After a recruiter call, I had a technical screen that began immediately with coding. I answered two LeetCode-style questions and had to communicate clearly as I worked. The questions were heavily Meta-tagged, so targeted preparation mattered more than generic DSA practice. The onsite loop added behavioral, two more coding questions, and system design. The recruiter was accommodating and the proce…

Technical Screen0
FragomenConsultant
Reported Jul 2026

Fragomen Consultant interview: written assessment and same-day offer

I began with a friendly HR call about logistics and my background. Soon after, I completed a written assessment with plenty of time, so it felt more like a check than a trap. I then had two interviews with team staff. They were relaxed but role-related, and the interviewers kept even the challenging parts supportive. I felt they were trying to understand how I would work rather than score points.…

OfferHR Screen0
FinacleSoftware Engineer
Reported Jul 2026

Finacle Software Engineer interview: Java, Spring Boot, and reasoning

The technical discussion focused on Java, Spring Boot, SQL, Azure, and Terraform, then shifted into project-based scenarios. I explained how my project was implemented, the approach I used, and my own contribution. After introducing myself, I worked through a DSA problem by describing a brute-force solution and then an optimized one. The conversation also covered operating systems, OOP, networks,…

OfferTechnical Screen0
FinacleSoftware Engineer
Reported Jul 2026

Finacle Software Engineer interview: campus DSA, SQL, and systems topics

I interviewed on campus for about an hour with two interviewers. The first asked me to solve DSA questions using LeetCode and also covered SQL. The second went into dynamic programming, how a database connects to a backend, APIs, microservices, and questions based on my resume, including altered versions of my own coding rounds. I also discussed merge sort, trees, graphs, React, MERN, and HTTP me…

OfferTechnical Screen0
Intercontinental ExchangeBusiness Analyst
Reported Jul 2026

Intercontinental Exchange Business Analyst interview: poor communication

One short conversation felt like a quick check on whether my background matched what the team needed. It did not, and the process did not move forward. I was also asked a puzzle-style question that felt easy. In a separate screening, I answered basic questions about my experience and Snowflake, then did not receive clear follow-up. Another interview was worse: people were late, one took a persona…

Other0
McKinsey &Business Analyst
Reported Jul 2026

McKinsey & Business Analyst interview: supportive case conversations

I expected a stressful process, but the case interviews felt tightly run and well supported. The interviewers were professional and seemed genuinely interested in helping me do well. It was intellectually demanding without feeling hostile. The cases and discussions had structure, and the interviewers gave detailed answers when I asked questions. They were unusually open about the realities of the…

Other0
Meta PlatformsSoftware Engineer
Reported Jul 2026

Meta Platforms Software Engineer interview: coding and system-design loop

After the recruiter call, I had a technical screen with two coding questions, then an onsite-style loop with behavioral, two more coding questions, and system design. It was structured to test both range and depth under time pressure. The coding was LeetCode-style. I needed to explain the approach, write clean code, and handle follow-ups and optimization. The interviewers were not hostile, and so…

Technical Screen0
Meta LogisticsSoftware Engineer
Reported Jul 2026

Meta Logistics Software Engineer interview: screen, loop, and system design

After the recruiter conversation, I had a technical screen with two coding questions. The next stage was an onsite-style loop with a behavioral discussion, two more coding questions, and system design. The recruiter was accommodating when scheduling was difficult. The coding prompts were LeetCode-like, with follow-ups that required me to explain and revise my approach. System design was about tra…

Technical Screen0
LennarConsultant
Reported Jul 2026

Lennar Consultant interview: repeated delays and Caliper result

The recruiter call felt cold and combative, and it was hard not to take that personally. A later interview with a sales manager felt rigid too. I was told an assistant would arrange another sales-manager meeting, but after my thank-you email and follow-up, I was told there was limited space in my region. When I reapplied in another city, the same recruiter scheduled me with the same interviewer.…

RejectedOther0
L&T Technology ServicesSoftware Engineer
Reported Jul 2026

L&T Technology Services Software Engineer interview: networking and core theory

After the recruiter screen, I had two back-to-back technical interviews. They focused on my C, Linux, networking, and WiFi background, and I had to explain both concepts and the resume work behind them. One round also covered circuits, signals, communication, basic programming logic, and my projects. The manager round was more conversational. I discussed past work from my resume and answered scen…

OfferTechnical Screen0
NutanixAccount Executive
Reported Jul 2026

Nutanix Account Executive interview: recruiter-led offer discussion

I started with a clear, professional exploratory call with a recruiter. Soon after, I spoke with the sales manager who would have been my direct boss and then the country leader. The recruiter followed up to say the process had been positive and discussed what an offer and the next steps would likely look like. That follow-through made the direction of the process much clearer. Leadership was inv…

OfferOther0
NomuraBusiness Analyst
Reported Jul 2026

Nomura Business Analyst interview: responsive fit-focused process

The recruiter was easy to schedule with and responded quickly. The early conversation felt like a friendly fit check built around my background, and I left optimistic about the role and company. Later I had a phone discussion with a manager and an in-person office meeting. The interviewers were calm and professional. They asked thoughtful questions that clarified expectations, but nothing felt ov…

Other0
NIOSoftware Engineer
Reported Jul 2026

NIO Software Engineer interview: coding, React timer, and offer declined

After a recruiter call, I went through a short, fast technical process with a few behavioral touches. One version had four rounds split between coding and a manager conversation. Another was compressed into two rounds in one day, with a mentor or manager discussion and HR. When it was on-site, it took a few hours end to end, and HR was responsive about scheduling. The coding included easy-to-medi…

OfferTechnical Screen0
QualcommSoftware Engineer
Reported Jul 2026

Qualcomm Software Engineer interview: friendly but unexpected technical scope

After the recruiter interaction, I had two technical interviews that mixed behavioral questions about my past experience with coding and other technical prompts. The interviewers were nice, which helped. Still, some questions went beyond the scope I thought had been set ahead of time. The coding was meant to probe how I reason under constraints, not random trivia, but the mismatch meant I had to…

Technical Screen0
Ntt Data Europe & LatamConsultant
Reported Jul 2026

Ntt Data Europe & Latam Consultant interview: same-day offer declined

HR reached out quickly after I applied, and the process had a clear timeline. About a week later, I had the main interview discussions. The interviewers were transparent about the role and what the team needed, and I came away feeling that they were mapping my background directly to the team's priorities. The rounds combined case solving with behavioral conversations. The cases called for familia…

OfferHR Screen0
NTT DATAConsultant
Reported Jul 2026

NTT DATA Consultant interview: offer that did not meet expectations

HR contacted me within about a day of my application, and we aligned on the role and the team's needs. About a week later, I had an interview that was transparent about the position and expectations. They asked about relevant experience and used a practical case to assess my strategic and analytical thinking. The difficulty felt manageable and depended more on clear communication than trying to c…

OfferHR Screen0
MotorolaSoftware Engineer
Reported Jul 2026

Motorola Software Engineer interview: month-long gap after coding case

I started with a LeetCode-style technical case. It took about a month before HR contacted me, then I had a technical interview with my possible manager. The process was direct and meant to assess both practical ability and a discussion about the day-to-day role. I did not receive an offer. What I remember most is the long wait between the case and HR, which made the middle of the process feel slo…

Technical Screen0
OuraSoftware Engineer
Reported Jul 2026

Oura Software Engineer interview: calm and responsive process

After speaking with a recruiter, I met several interviewers across a few coordinated rounds. The process included an HR-style introduction, technical conversations, and later time for HR and final fit. Everyone was prepared and interested in my background, and the questions stayed grounded in my experience and the role. The timeline was clear and communication was responsive, so I did not have to…

HR 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