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

C3 AISoftware Engineer
Nov 2025

One Interviewer No-Show, One Walked Out Mid-Interview

I mass-applied online, and HR reached out to set up an interview directly — there was no HR phone screen first. They never shared the job details or the salary range, and went straight to scheduling a 30-minute behavioral round with the hiring manager. The behavioral round with the manager went okay. I asked him about salary and he had no idea about anything. After getting through the behavioral…

RejectedOnsite0
OracleSoftware Engineer
Nov 2025

Recruiter Ghosted Me Twice During Scheduling

I got referred to a role on the OCI observability org. About a week and a half later I got an HR call invite. The recruiter was extremely unprofessional — he ghosted me twice total, and I'll complain about it in chronological order below. The first time the recruiter went dark was around scheduling the phone screen in late October. The system-generated interview availability window was a bit shor…

RejectedTechnical Screen0
ChimeData Scientist
Nov 2025

A Schema-less SQL Retention Question in the HM Screen

The first round was just a recruiter screen — they asked roughly about what I'd worked on before. The second round was the HM screen. They changed the process this year: the first round is now a one-hour session split into two parts, 30 minutes chatting about my background and 30 minutes writing SQL. Their SQL question was a format I hadn't run into before — they only gave two tables: users and t…

RejectedTechnical Screen0
DatabricksSoftware Engineer
Nov 2025

Stumped by a 'Fibonacci Tree' Path Question in the Technical Screen

I'd ground the recent high-frequency questions down to nothing, and then they hit me with an old, unprepared-for question: find path within Fibonacci tree. The problem doesn't give you a node structure, and you're not even allowed to write your own. The input is order: int, start: int, end: int. Find the shortest path from start to end. Right away I explained a brute force approach, and the inter…

RejectedTechnical Screen0
Jane StreetQuantitative ResearcherIntern
Nov 2025

A Custom Board-Game Coding Puzzle Instead of LeetCode

A premium story — unlock it to read the full loop.

In progressTechnical ScreenPremium0
UberData ScientistSenior+
Nov 2025

Two Brutal Phone Rounds on Airport Supply and Demand

Overall impression: this one was really hard. First there was a 15-minute recruiter call — a quick chat about my current job, why I was looking, and visa/status questions. They said the interview process would be laid out in a follow-up email. The phone interview was two rounds total, one hour each. Round 1: coding (SQL and Python), plus a case study. The SQL question was built around drivers and…

Technical Screen0
EliseAIData Scientist
Nov 2025

Tic-Tac-Toe Coding Round and a Lease Renewal Take-home

I applied online and a recruiter reached out. The first round was a 30-minute chat with a team member. The second round was coding, a tic-tac-toe variant. I'd suggest looking at all three of these: 348 - Design Tic-Tac-Toe 794 - Valid Tic-Tac-Toe State 1275 - Find Winner on a Tic Tac Toe Game The third round was a take-home: you get 24 hours to do it, and then there is a 30-minute presentation. T…

Take-home Project0
StripeSoftware Engineer
Nov 2025

New Onsite Questions and a Java Coding Grind

Locked — open it to unlock the full story with XP.

OnsiteXP0
BrexSoftware Engineer
Reported Nov 2025

Brex Software Engineer interview delayed for months before I took another offer

My process stretched on for months and felt completely disorganized. The recruiter sometimes couldn't get a response from the hiring team for more than a week, so I was left waiting without any real momentum. The interview steps never lined up cleanly because of the delays. What I remember most is the lack of updates and the way the timeline kept slipping. By the time anything finally moved, I'd…

Offer0
ConfluentSoftware Engineer
Reported Nov 2025

Confluent Software Engineer interview with system design and DSA rounds

My process had three segments. First, I completed a qualifying technical round. Then came the heavier middle section: three rounds combining system design with DSA, with the DSA portion mostly resembling LeetCode medium difficulty. The final segment was a behavioral round with a senior manager. The process felt difficult because the middle block required sustained technical thinking across severa…

Technical Screen0
ConfluentSoftware Engineer
Reported Nov 2025

Confluent Software Engineer interview with two technical rounds and harder follow-ups

My interview had a small set of core stages: recruiter coordination, two technical interviews, and a manager round. The problems were medium overall, with some harder follow-ups that required me to stay sharp after I thought I’d settled into the first question. I had a generally positive impression of the process. The recruiters were responsive and supportive, and it took only a few weeks from my…

RejectedTechnical Screen0
Notion LabsSoftware Engineer
Reported Nov 2025

Notion Labs Software Engineer interview: TypeScript team and canceled virtual onsite

The process felt scripted from the start. A recruiter matched me with a team whose role required TypeScript, even though I hadn't applied specifically to that team. After a phone screen that sounded positive, I heard nothing for two weeks, including after I followed up. When I finally heard back, I had a conversation with the hiring manager. He was surprised to learn that the technical step had a…

RejectedHR Screen0
BairesDevBackend Engineer
Reported Nov 2025

BairesDev Backend Engineer interview with junior-level expectations and technical lead discussion

I entered the process expecting something aligned with the role, but it quickly felt disrespectful and poorly scoped. During the interview, the recruiter seemed impatient and interrupted my answers, moving to other topics before I could finish. That made it difficult to stay comfortable. Although the job was described as junior, the expectations felt closer to full mastery of advanced technologie…

0
BoeingSoftware Engineer
Reported Nov 2025

Boeing Software Engineer interview with HackerRank and panel rounds

I went through a fairly standard entry-level process that began with a recruiter conversation and moved quickly into a technical assessment. We discussed the role and reviewed my resume, and the recruiter explained what the process would look like. About a week later, I had a screen that combined behavioral prompts with a coding component. The technical assessment used a HackerRank-style platform…

Online Assessment0
RoktSoftware Engineer
Reported Nov 2025

Rokt Software Engineer interview: aptitude screen, LeetCode, and onsite rounds

I went through an assessment-heavy funnel that felt disconnected from actual software work. After applying, I completed a cognitive aptitude and personality-style screen, followed by a one-way video interview where I recorded responses to behavioral prompts. By then, the process already felt automated and generic. The later stages followed a more traditional technical path, but the pacing and com…

Onsite0
RoktSoftware Engineer
Reported Nov 2025

Rokt Software Engineer process with a room exercise, one-way video, and take-home

My first step was a cognitive and personality-style evaluation. After that, I quickly reached rounds that felt more like assessments than engineering interviews. One memorable part was a room-based exercise that had nothing to do with building software. It was meant to see how I performed under pressure during an activity unrelated to day-to-day development. The process also included a one-way vi…

Online Assessment0
Clipboard HealthSoftware Engineer
Reported Nov 2025

Clipboard Health Software Engineer take-home PR review

I completed an async take-home PR-style submission. I cloned the repository, followed the specification, created a pull request, and submitted it. The review felt abrupt, and the feedback didn’t clearly explain what I should change. I received a rejection citing "attention to detail" and saying that I hadn’t followed the task requirements, but it didn’t include specific pointers. I didn’t move fo…

Take-home Project0
GustoSoftware Engineer
Reported Nov 2025

Gusto Software Engineer interview with a Codesignal GCA-style assessment

After I applied, I moved forward only after completing a Codesignal GCA-style assessment that wasn’t automatic. Once I passed, I had two technical rounds with LeetCode-style questions drawn from the company’s tagged topics. The rounds felt sequential and fairly structured. I solved each problem, reviewed my approach, and moved to the next step after clearing the previous one. After the technical…

Online Assessment0
BoeingSoftware Engineer
Reported Nov 2025

Boeing Software Engineer interview: waiting for the technical round

My first interview for the role went well, and I was told I would move on to a technical interview. I spent time trying to understand what Boeing usually asks in that round because the first conversation gave me little detail about the format beyond the expectation that it would be technical. Although I felt good about how the initial call went, the uncertainty about what would come next stayed w…

0
BoeingSoftware Engineer
Reported Nov 2025

Boeing Software Engineer interview: C++17, concurrency, and architecture

I entered the process through an in-person recruiting event where I met the hiring manager. The next step was an online assessment that felt similar to HackerRank. One problem asked me to work with a decimal-to-binary print format. After that, I had an hour-long interview over Zoom. The Zoom session started with questions about my resume and background. The rest of the hour became a slide-deck di…

Online Assessment0

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