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

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

Tata Consultancy Services (North America) Software Engineer interview with resume-based API code

I expected a wide range of technical topics, but the conversation stayed close to my resume. The interviewer focused on what I had already listed and did not pull in much outside my background. My panel felt uneven. Some questions were very easy, but for me they went deeper into integration-style code, arrays, and Python basics. That resume-first pattern came up again with AWS because I had a cer…

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

Tata Consultancy Services (North America) Software Engineer campus interview with Java and multithreading

This was a campus-placement setup where TR, MR, and HR seemed to run in parallel. I began with TR, and the questions started with DSA and AI basics. That put the focus on foundational concepts rather than anything especially specialized. Then the discussion moved into Java and operating systems, with extra attention to multithreading. It felt like they wanted to know whether I could handle core p…

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

Tata Consultancy Services (North America) Software Engineer interview with DevOps and cloud topics

My interview had a clear structure: an HR screening, a technical interview on DevOps and cloud, and a final technical and managerial discussion. That last discussion returned to my project experience and expanded into Kubernetes, AWS, CI/CD, security, and Python. After that came another HR conversation. The difficulty felt average, and each stage gave me a clearer sense of what they cared about:…

OfferHR Screen0
Walmart LabsData Scientist
Reported Jul 2026

Walmart Data Scientist interview with supply-chain time series and a missed follow-up

The process felt unusually intense and a little chaotic from the start. After an initial technical screen, I had a supply-chain technical round with several interviewers. It covered SQL, Python, statistics, including a probability question, and deeper machine-learning model details. The session lasted about 1.5 hours and focused heavily on time-series modeling. It was hard to follow every prompt…

RejectedTechnical Screen0
StripeSoftware Engineer
Reported Jul 2026

Stripe Software Engineer interview with coding, bug squash, API integration, and BQ rounds

After finishing an online assessment, I moved to a coding test that was described as very similar to the previous one. That led to more coding and then a series of work-style rounds: bug squash, API integration, and a BQ round. The process kept adding variety while staying tied to practical engineering work. The later stages seemed designed to test real-world debugging and API work, not just isol…

Online Assessment0
ShopifySoftware Engineer
Reported Jul 2026

Shopify Software Engineer interview with pair programming, AI use, and a life-story round

I started with a resume submission. Once my application passed, I moved into an online assessment. The format varied, but it consistently combined several coding problems with a cognitive or IQ-style component and a culture-fit questionnaire. After that, the process moved toward the technical interview stage. My technical round was a pair-programming exercise with an OOP-flavored prompt. I had to…

Online Assessment0
SalesforceAccount Executive
Reported Jul 2026

Salesforce Account Executive interview with a three-stage in-person panel and account strategy

The recruiter process was organized and supportive. I got guidance that made the next steps clearer, along with preparation materials that helped me understand the expectations. The flow appeared to have three stages, with the last round as an in-person panel. The interviews were structured and purposeful. Instead of asking the same behavioral questions repeatedly, each interviewer focused on a d…

Onsite0
SalesforceAccount Executive
Reported Jul 2026

Salesforce Account Executive interview with Dublin relocation questions and mismatched rejection feedback

After a couple of early steps that felt fairly normal, the process broke down at the fourth stage. I had been told that the third interview would focus on my motivations and details around relocating to Dublin, so I prepared for that context and answered accordingly. When the rejection feedback finally arrived, it cited commercial skills that, as far as I understood, had never been asked about or…

Rejected0
JPMorganChaseQuantitative Analyst
Reported Jul 2026

JPMorganChase Quantitative Analyst interview with probability, DSA, and machine learning rounds

The recruiter side was smooth and fast. The recruiter was prompt and answered my questions about what to expect. After that initial call, the process moved into interviews aimed squarely at the core of the role, with the last conversation involving a partner's team. I went through multiple rounds that leaned heavily on probability. One mixed projects and probability theory with a single DSA-style…

Offer0
IBMConsultant
Reported Jul 2026

IBM Consultant interview with a one-attempt recorded assessment and live storytelling rounds

After I applied, the process began with an online recorded assessment. It felt fast and high stakes because I had only one attempt for each answer. The short timed set covered behavioral and consulting-style questions, including working with others, pressure, and close deadlines. In the recording format, I had a brief moment to think and then a couple of minutes to answer. My camera had to stay o…

Online Assessment0
IBMSoftware Engineer
Reported Jul 2026

IBM Software Engineer HackerRank assessment with two timed coding questions

Right after I applied, I received a timed online-assessment request that had to be completed within a week. It ran on HackerRank and consisted of two coding questions to finish in about an hour. The questions were clearly meant to filter quickly for problem-solving ability. My version used classic algorithmic prompts that felt like LeetCode problems. One was more puzzle-like than I expected: coun…

Online Assessment0
BrillioSoftware Engineer
Reported Jul 2026

Brillio Software Engineer interview with three technical rounds and no follow-up

A recruiter contacted me through Brillio Guadalajara. I missed the first call, so they followed up by message to confirm my interest and share the position details. There was no separate HR screening after that. The interviews were simply scheduled. The process became three technical interviews in sequence: one with Brillio, then one with the client, followed by a final technical interview with t…

No response0
AmgenSoftware Engineer
Reported Jul 2026

Amgen Software Engineer interview with recruiter, hiring-manager, and pending panel stages

My process started with a recruiter phone screen about my current work and background from earlier roles. It was not overly technical. It felt more like they wanted to understand my experience and how I might fit the role. About a week later, I had a call with the hiring manager. That was a mix of a vibe check and targeted technical questions. The technical discussion focused on clarifying concep…

In progress0
NVIDIASoftware Engineer
Reported Jul 2026

NVIDIA Software Engineer interview with a 45-minute resume discussion and coin riddle

I started with a short, focused first round that spent about 45 minutes on the details in my resume. The expectation was that I could explain my background confidently before the technical deep dive. Then the conversation shifted to core computer-science topics, and I had to use a whiteboard to show my reasoning. I got a practical DSA question and a brainteaser-style riddle. The riddle was easy t…

0
Capital OneBusiness Analyst
Reported Jul 2026

Capital One Business Analyst interview with a mini case and Power Day

After an initial recruiter call, the process moved quickly to a mini case and then straight into a Power Day. It felt standard for a Business Analyst track: an HR conversation about what to expect, followed by quantitative case-style questions in the mini case. The Power Day was the heavier part, with several back-to-back interviews. During Power Day, I had case interviews and a product-focused r…

HR Screen0
AppleSoftware Engineer
Reported Jul 2026

Apple Software Engineer interview with a full-day final round of eight conversations

The interview cycle was organized but intense. I had four rounds overall, and the final one was a full day with around eight separate interviews running back to back. There were a lot of technical and behavioral questions, and the main demand was sustained focus. Before that full-day round, I had conversations about my background and projects. They started with my CV, then moved into targeted tec…

0
MetaData Engineer
Reported Jul 2026

Meta Data Engineer interview with timed SQL, Python, modeling, and product scenarios

After recruiter outreach, I went through a structured set of rounds built around speed and clear problem solving. The recruiter call covered role fit and process details. Then came a technical screen with several SQL and Python tasks under tight time limits. I had to keep working until each task was fully resolved with the expected results, while the interviewers kept returning to my thought proc…

Technical Screen0
MetaMachine Learning Engineer
Reported Jul 2026

Meta Machine Learning Engineer interview with a conversational-assistant design and declined offer

The process dragged on longer than I expected. It felt drawn out from the early weeks onward. I went through screenings on core ML knowledge, including attention and its variants, before later stages shifted into more high-pressure technical work. Onsite day was intense and tightly structured. In the system-design round, I had to build a conversational assistant and include safety measures. That…

OfferOnsite0
GoogleSoftware Engineer
Reported Jul 2026

Google Software Engineer interview for a PhD ML-focused role with spam-classifier design

I interviewed for a PhD SWE, ML-focused role, and the first real test came in the first interview round. It combined an ML domain section with behavioral questions. In the ML part, I was asked to design a spam classifier and write pseudocode for a bi-gram model. My recruiter had told me the domain round would connect to my projects, but the questions were more design-focused than I expected. When…

Rejected0
GoogleSoftware Engineer
Reported Jul 2026

Google Software Engineer interview with four rounds and onsite C++ implementation

The process felt steady and not especially punishing. I started with a recruiter phone call and, about a week later, a technical screen. There were four interview rounds in total: two coding rounds, a behavioral round, and a system-design round. The coding was LeetCode-style medium algorithm and data-structure work, with the usual need to communicate clearly, get the code right, and think through…

Technical 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