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

VantaSoftware Engineer
Reported Jul 2026

Vanta Software Engineer interview: concerns about the work environment

What stood out to me was not technical content but the environment I thought I could see through the people I met. From the outside, the culture felt suffocating. The engineers I observed seemed tired and frustrated. Managers came across to me as inexperienced and political, and the recruiting interactions felt biased and unsupportive rather than collaborative. The stated difficulty was average,…

0
Uber DriversData Scientist
Reported Jul 2026

Uber Drivers Data Scientist interview: SQL bottleneck in a timed test

My first step was a 60-minute test with 17 questions: two medium SQL questions and 15 aptitude questions. The aptitude questions felt easier, as though I could get through most of them in under half the time. I spent longer on the SQL section and could not fully solve everything. By the end, I was hoping that the partial progress would be enough to move forward, but I did not get an interview aft…

Online Assessment0
UberData Scientist
Reported Jul 2026

Uber Data Scientist interview: 17-question SQL and aptitude test

My first step was a 60-minute test with 17 questions: two medium SQL questions and fifteen aptitude questions. The aptitude portion felt fairly straightforward, and I think I could have finished it in about half the allotted time. I used more of the clock on SQL because I did not fully solve one problem, then submitted what I had. The process did not continue after that test. The non-SQL portion…

Online Assessment0
TikTokSoftware Engineer
Reported Jul 2026

TikTok Software Engineer interview: projects, systems topics and TreeNode DP

The opening was either a brief resume and role discussion or a direct start to the technical conversation, but it consistently set the direction first. I was asked about my background and then given a coding problem. Early topics included iOS development, backend work, Java, networking, and distributed systems. The interview then narrowed to a LeetCode-style TreeNode and DP challenge. The intervi…

Technical Screen0
TikTokSoftware Engineer
Reported Jul 2026

TikTok Software Engineer interview: demanding technical loop

After the initial HR coordination, I went through a longer technical loop that felt more demanding than typical screens I had seen. The interviewers were polite, but the overall impression was that people were stretched. Several interviewers mentioned heavy hours, so it did not feel like a casual conversation. There were several technical rounds, each built around LeetCode-style medium questions,…

Technical Screen0
TikTokSolutions Engineer
Reported Jul 2026

TikTok Solutions Engineer interview: resume discussion and LeetCode questions

The process was fairly direct. After a recruiter-style introduction about my background, the first technical interview covered my resume and behavioral questions before moving to a LeetCode medium problem in a usual interview format. The early rounds followed that pattern, with behavioral questions and one LeetCode problem each time. The interviewers were encouraging and wanted to hear how my pro…

Technical Screen0
TikTokSoftware Engineer
Reported Jul 2026

TikTok Software Engineer interview: troubleshooting, SQL and ticket prioritization

After I connected with the recruiter, the process moved slowly and felt disorganized. There were timing problems, including a reschedule when the hiring manager did not show up. The pace was the hardest part for me to tolerate. Once the technical interview happened, I introduced myself and discussed how I would approach the role, including what KPIs I would set. I then worked through practical tr…

Technical Screen0
Align TechnologySoftware Engineer
Reported Jul 2026

Align Technology Software Engineer interview: project discussion and a riddle

The technical screen began with a discussion of a project I had worked on. I had to explain the algorithms I used and how the system worked. Then I was given a real-world riddle connected to the job description, which felt like a curveball after the project deep dive. The first part was a direct conversation about engineering choices; the puzzle asked me to reason aloud with more ambiguity. Overa…

Technical Screen0
Wood ConsultingSoftware Engineer
Reported Jul 2026

Wood Consulting Software Engineer interview: a short Teams conversation

I had a 30-minute Teams interview with one other person. It felt more like working through a checklist than having a conversation. The questions were mostly generic competency and HR questions, with a few technical ones mixed in. What stayed with me was the interviewer’s manner. I did not feel as though they were really listening to my answers, which made the conversation feel one-sided and uncom…

HR Screen0
WoodSoftware Engineer
Reported Jul 2026

Wood Software Engineer interview: Teams competency discussion

After a recruiter conversation, I moved quickly to a Teams video interview with one interviewer. It lasted about 30 to 45 minutes and began as a competency and HR-heavy discussion, with some job-related technical questions. We talked mainly about my background, motivation, and how my experience fit their work. The tone was conversational. Technical discussion was manageable and centered on what I…

0
WiproSoftware Engineer
Reported Jul 2026

Wipro Software Engineer interview: resume-based technical rounds

After a recruiter call, I had two technical rounds and one HR round. Technical questions stayed close to my resume, so they felt grounded in my experience. One section began with multiple-choice questions and then a coding test. The MCQs were basic concept checks. The coding portion had multiple moderately difficult problems, moving from theory to implementation in one sitting. The HR discussion…

OfferHR Screen0
AmazonSoftware Engineer
Reported Jul 2026

Amazon Software Engineer interview: organized coding and leadership

I began with an online coding assessment on data structures, algorithms, and problem solving. After passing it, later interviews combined coding, design fundamentals, and Leadership Principles. Follow-up questions tested my thought process rather than only whether I reached a solution. Leadership discussion was woven into the technical evaluation, so it felt broader than a coding test. I did not…

Online Assessment0
AmazonSoftware Engineer
Reported Jul 2026

Amazon Software Engineer interview: recruiter to live coding

I had a 30-minute recruiter phone screen about my background and resume. About a week later, I had an approximately one-hour technical video interview with a senior engineer. After introductions, I completed a live coding challenge in a shared editor. The round ended with system-design basics and questions about how my past projects worked in practice. It was average in difficulty: nothing entire…

0
AmazonSoftware Engineer
Reported Jul 2026

Amazon Software Engineer interview: assessment and waitlist

I took an online assessment with two DSA questions and multiple-choice scenarios about leadership qualities. After being shortlisted, I completed an online technical round with two DSA problems. Leadership was already part of the assessment rather than a separate afterthought, while the technical work felt straightforward by comparison. I was waitlisted rather than offered, so the result felt mix…

Online Assessment0
AmazonProduct Manager
Reported Jul 2026

Amazon Product Manager interview: organized PM scenarios

A recruiter first covered my background and asked about specific PM problems I had worked on, why I chose my approaches, and their impact. Scheduling then came with clear notice of timing and what each next round would involve. Later I had two video rounds. One was a greenfield product/design problem where I framed the problem and discussed tradeoffs. The other focused on PM routines and a diffic…

0
NatWest GroupSoftware Engineer
Reported Jul 2026

NatWest Group Software Engineer interview: delayed VAC invitation

The assessment was fairly straightforward, and the coding felt manageable. The video interview mattered most to me. I didn't hear back a week or so after finishing the test; the invitation for the VAC came much later, after roughly six weeks. Once it was scheduled, the VAC moved quickly. The video questions focused on my background and how I approached problems. It didn't feel like harsh technica…

OfferOnline Assessment0
HCL TechSoftware Engineer
Reported Jul 2026

HCL Tech Software Engineer interview: five-round systems focus

The process felt like a marathon: I completed five rounds. It relied heavily on LeetCode-style problem solving but also went beyond surface system design. I had to discuss time-related concepts and how time-series data is handled in a production environment. The difficulty felt average to demanding. What stood out was the expectation to link algorithmic thinking to real operational concerns aroun…

0
EPAM IndiaSoftware Engineer
Reported Jul 2026

EPAM India Software Engineer interview: Spring Security, tracing and Python internals

After the recruiter stage, I had a technical interview of about ninety minutes that went deeply into Spring and distributed systems. I discussed Spring Data JPA, Kafka, Java 8 functional interfaces and Spring Boot. For microservices, I explained the architecture, how services communicate and how security works. JWT questions went into detail: what a token is, how a service validates it, what happ…

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

Tata Consultancy Services (North America) Software Engineer interview: Java fundamentals

The process began with aptitude and reasoning, then coding. I received two coding questions: one easy-to-mid level and one mid-to-hard DSA problem. Each part seemed to require clearing before the next advanced. The technical discussion went deep into Java and CS fundamentals: String versus StringBuilder/StringBuffer, string immutability, equals and hashCode, ArrayList versus LinkedList, checked a…

Other0
ServiceNowSoftware Engineer
Reported Jul 2026

ServiceNow Software Engineer interview: positive start, months of silence

I applied online, spoke first with a recruiter, and then had a video conversation with the hiring manager. During that call, I was told my skills matched what they wanted. Then I heard nothing for months. Eventually I received an automated rejection while the role kept appearing again. The recruiter also stopped responding after I reached out twice. It was frustrating because the process seemed t…

No response0

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