Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

4437 stories

Likes earn the author +10 XP for the first 3 likes each day

StubhubSoftware Engineer
Reported Apr 2024

Stubhub Software Engineer interview with a 75-minute pair programming round

My interview process started with an HR behavioral round, followed by a CodeSignal assessment and then a face-to-face technical sequence. The technical portion included a 75-minute pair programming round and a system design round. The process ended after the system design interview, and I was rejected at that final technical stage. It felt like a typical multi-round pipeline, but the rejection se…

RejectedHR Screen0
Notion LabsSoftware Engineer
Reported Mar 2024

Notion Labs Software Engineer interview with practical React work

My process started with a recruiter introduction. The technical part quickly made the experience feel practical rather than gimmicky. The first live screen lasted an hour and focused on React. The problem was broken into smaller steps, so I could build the result while explaining my approach. After that, I attended a virtual onsite with more technical rounds and hands-on work tied closely to day-…

Technical Screen0
AmazonProduct Manager
Jan 2024

Five Rounds, All Behavioral Questions

After one round with the hiring manager, I got the result the next business day: move forward to the virtual onsite. There was almost a month gap after that, so I had plenty of time to prepare. I split the 5 rounds across two days, and it was pure behavioral questions the whole way through. I remembered roughly some of the questions, so sharing them here. The first one was with the hiring manager…

OfferOnsite0
KaratSoftware Engineer
Reported Jun 2023

Karat Software Engineer: LeetCode-style coding under time pressure

My interview started with a classic skills screen: brief introductions and basic computer science questions, followed by the main coding portion in a live editor. The opening focused on fundamentals such as time and space complexity, and I remember the questions moving from easier concepts into harder problems. Once the coding round began, I worked through LeetCode-style questions. The first was…

Technical Screen0
Oura RingSoftware Engineer
Reported Jun 2023

Oura Ring Software Engineer interview for a contract role with portfolio feedback

I went through a recruitment process for a contract role, and the team was unusually responsive. They welcomed my questions and gave specific answers instead of generic ones. They even offered feedback on my portfolio, which made the process feel constructive. The feedback was more specific than what I've seen from many other companies, and the conversations felt thoughtful. I didn't get an offer…

0
StubhubSoftware Engineer
Reported Apr 2023

Stubhub Software Engineer interview with no clear decision

I didn't get much information from StubHub during the interview loop. After I completed the process, they didn't seem to communicate a clear decision either way. About two weeks later, I received a survey asking me to rate the interview. The experience left me uneasy. The interview itself wasn't especially brutal, but the recruiting process didn't feel appropriate for the time and effort it requi…

0
StubhubSoftware Engineer
Reported Apr 2023

Stubhub Software Engineer: 90-Minute CoderPad Interview Cut Short

My process felt rough and uncomfortable from the beginning. I was put straight into a coding exercise on CoderPad with little introduction, and the session became stressful quickly. It was supposed to run for 90 minutes, but the interviewer ended it after about 30 minutes, even though I believed I had solved the problem. The interview atmosphere made things harder. There was a lot of outside nois…

Technical Screen0
HeadwaySoftware Engineer
Reported Mar 2023

Headway Software Engineer interview: withdrew after a delayed process

I initially had an easier path into the process, but it became frustrating quickly. The recruiter seemed unprepared, and the timeline took too long to get moving. Eventually, I decided it wasn’t worth my time and withdrew to focus on other interviews. The process felt unprofessional to me. I didn’t like how long things dragged before anything substantial happened. Because I withdrew and didn’t co…

Withdrew0
HeadwayCustomer Success Engineer
Reported Mar 2023

Headway Customer Success Engineer interview with an abrupt manager round

I was contacted through LinkedIn, and someone from the recruiting team arranged a recruiter screen. That interview was fairly normal, covering my work experience along with an overview of the company and role. Afterward, I moved straight to a hiring manager interview that felt very different. The hiring manager barely introduced themselves, didn't ask much about me, and instead went straight to a…

HR Screen0
Circle Internet FinancialSoftware Engineer
Reported Mar 2023

Circle Internet Financial Software Engineer, CodeSignal and Flask booking app

I went through a multi-stage technical process that felt difficult, and one version was held back by the quality of the interviews. I was told the pipeline included an online assessment, an HR interview, technical interviews with an engineering manager and senior engineer, another engineering manager interview from a different office, and finally a VP interview. Another account described a CodeSi…

RejectedOnline Assessment0
HeadwayBackend Engineer
Reported Dec 2022

Headway Backend Engineer interview: recruiter screen and unclear follow-up

My process started with a quick recruiter screen focused on behavioral questions. We covered the usual background topics, along with how I’d troubleshoot technical issues when something breaks and how I’d explain a technical concept to someone without a technical background. I made it into the hiring process, but it ended without an offer. In one experience, the recruiter interaction had a good t…

0
RemitlySoftware Engineer
Reported Nov 2022

Remitly Software Engineer interview: DFS screen and four-interview virtual onsite

I applied online and went straight to scheduling without a recruiter introduction. My first technical interview involved a simple DFS-style problem. I passed that round and was invited to a virtual onsite. The virtual onsite felt uneven. It included four interviews: two technical coding rounds, a manager round, and a product manager round. Some interviewers were engaged and seemed genuinely inter…

Technical Screen0
RemitlySoftware Engineer
Reported Nov 2022

Remitly Software Engineer interview: two coding interviews and values-based behavioral round

After applying, I didn’t do anything especially elaborate up front. Everything took place online over Zoom, and the process focused heavily on values. The interviews seemed designed to assess how I’d show up, not just how I’d code. My interview day combined two technical coding interviews with a behavioral interview centered on the company’s core values. One interviewer gave me a clear framework…

0
Jane StreetQuantitative Research InternIntern
Oct 2022

Answered Every Question, Still Rejected

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

RejectedTechnical ScreenPremium0
RemitlySoftware Engineer
Reported Oct 2022

Remitly Software Engineer interview with a disputed coding solution

After a recruiter reached out, I entered the process with a decent amount of momentum. I had one technical interview that combined Q&A with a whiteboard-style coding task. The conceptual part focused on DSA and time complexity. Even when the conversation became tense, I felt I understood what they were asking me to do. The process then moved into the loop. One technical interviewer kept insisting…

No responseTechnical Screen0
Circle Internet FinancialSoftware Engineer
Reported Sep 2022

Circle Internet Financial Software Engineer interview: stalled after coding screens

I applied for the Software Engineer role and got caught in a mid-process cycle of one or two online coding assessments, sometimes followed by a conversation, without a consistent path to later interviews. I was sent one or more timed coding challenges through CodeSignal and/or HackerRank, including HackerRank-style tasks. In a few cases, I had a recruiter conversation after the assessment, but it…

Online Assessment0
Circle Internet FinancialSoftware Engineer
Reported Sep 2022

Circle Internet Financial Software Engineer: CodeSignal, 5 to 7 hour take-home, and final interviews

I went through a harder, test-heavy process for a Software Engineer role involving CodeSignal and longer take-home work. It ultimately didn't lead to an offer. The online assessment was proctored through CodeSignal and consisted of timed questions. In one case, I had to complete it within a fixed window and received a rejection shortly afterward. I also encountered take-home coding work described…

Online Assessment0
Circle Internet FinancialSoftware Engineer
Reported Aug 2022

Circle Internet Financial Software Engineer interview ending after CodeSignal

I interviewed for Software Engineer and went through only part of the process. The early assessments were the main focus, followed by either silence or no further interviews. The first step was an Online Assessment through CodeSignal. It was timed, and in one case there was an additional assessment. The questions weren’t strictly classic LeetCode-style. After the assessment, I either spoke briefl…

Online Assessment0
Jane StreetSoftware Engineer
Apr 2022

Tripped Up by a Stack Machine's Int vs String Bug

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

RejectedTechnical ScreenPremium0
The New York TimesData Analyst
Mar 2022

Five Rounds, Three References, Then Rejected

It's been 4 years since this interview without my even noticing, and along with wishing everyone a happy new year, I figured I'd share the general interview process for this company. I went through 5 rounds of interviews with this company in total, and the process was pretty drawn out. At the end they also wanted me to track down three references (a peer, a direct manager, and a manager I had col…

RejectedOnsite0

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