Interview Experiences

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

Share yours, earn XP

7 stories

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

HeadwaySoftware Engineer
Jul 2026

Onsite with a Rate Limiter, an Airbnb Design Question, and an AI-Assisted Debugging Round

Coding The problem: implement a Fixed Window Rate Limiter. Implement a rate limiter middleware for a web service built on FastAPI and Uvicorn. Every request has to satisfy both of these at the same time: Global limit: at most 100 requests per minute Domain limit: at most 3 requests per second per domain If either limit gets triggered, the request should be rejected. They wanted the fixed-window v…

Onsite0
HeadwaySoftware Engineer
Reported May 2026

Headway Software Engineer interview with a three-part virtual onsite

After an initial recruiter conversation, the process moved into a technical screen and then a virtual onsite. The recruiter call stood out because it walked me through what would happen next and helped set expectations for the final loop. The technical screen focused on live problem solving with algorithms and data structures. I was expected to finish the task and communicate clearly as I worked.…

Technical Screen0
HeadwaySoftware Engineer
Reported Feb 2026

Headway Software Engineer interview: unclear onsite design expectations

My process started with a recruiter touchpoint, followed by a technical screen and then a three-round onsite. Scheduling and feedback were responsive, but the actual evaluation didn't line up with what I expected. The onsite design segment especially didn't feel like a classic system design round. The constraints made it hard to tell what direction they wanted, so I spent more time guessing than…

Technical Screen0
HeadwaySoftware Engineer
Reported Mar 2025

Headway Software Engineer interview with role homework and employee interviews

I went through a multi-step process that felt unusual in how quickly it ramped up. It started with a recruiter meeting where I answered basic questions. Then I was assigned homework tied to the role, which I had to complete before the next technical conversation. After that, I had a technical interview with the hiring manager. The format shifted again when I interviewed with current employees. Th…

HR 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
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

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