Interview Experiences

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

Share yours, earn XP

4 stories

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

ChimeProduct Manager
Reported Jul 2026

Chime Product Manager interview: intensive loop and missing recruiter follow-up

I started with a recruiter screen that felt fast and responsive. After meeting the hiring manager, the pace stayed high. I was moved into the next round on such a tight timeline that they wanted me to begin the technical interview before I had much chance to prepare. After that second round, the process went quiet. I followed up, got no reply from the recruiter, then received a standard rejection…

RejectedTechnical Screen0
ChimeSoftware Engineer
Nov 2025

Two Back-to-Back Phone Screens, Rejected for Pipeline Fit

A recruiter reached out. I looked up the company online and felt the culture seemed okay, so I went ahead and interviewed. The recruiter call was just casual chatting, and we quickly landed on an interview time. I hadn't grinded LeetCode in a long time so I was a little worried, so I scheduled the phone screen slot for two weeks out and started grinding through interview experience posts. In the…

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
ChimeData Scientist
Oct 2025

SQL and a Business Case in One Technical Screen

This round is split into two parts: one hour of SQL and one hour of a case study. SQL: They give you a transaction table and a user table. If you're fast you'll probably get through 5-6 questions. The time field is a timestamp, so you need to use date_trunc to handle it. The first few questions are pretty basic and you can knock them out with a few CTEs. It involves several window functions like…

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