Interview Experiences

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

Share yours, earn XP

11 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
Reported Jun 2026

Chime Software Engineer interview with coding, system design, and manager rounds

I went through a fairly standard Software Engineer process at Chime, with a recruiter conversation followed by coding, system design, manager, and product-style rounds. The difficulty was mostly average, although I had mixed feelings about how clearly some interviewers ran their sessions. The recruiter screen was a phone call about my background, the role, and expectations. The technical intervie…

Technical 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
ChimeSoftware Engineer
Reported Oct 2025

Chime Software Engineer interview: basic SQL without window functions

I interviewed for a data engineering-oriented SDE role where the questions were unusually basic. They focused on my past work and simpler algorithm and SQL knowledge. The recruiter screen covered my background and how it matched the role. The technical portion covered SQL and algorithms. The SQL questions were very basic and explicitly did not include window functions. The algorithm problems lean…

HR Screen0
ChimeProduct Manager
Reported Jun 2025

Chime Product Manager interview with two panels and a 90-minute PRD exercise

My process moved quickly once it started, but the bar felt high and a few details didn't land the way I expected. I went through a recruiter screen, then a hiring director conversation, followed by two panel interviews. The first panel went reasonably well, and I got good feedback. The second was rougher for me. There was also a PRD writing exercise that took about 90 minutes, although it sounded…

RejectedHR Screen0
ChimeSoftware Engineer
Reported Jun 2025

Chime Software Engineer interview: React and JavaScript component task

I faced a front-end-focused technical challenge centered on building React/JavaScript components and implementing the data logic behind them. In the first round, I worked in a shared virtual environment to create components in a React/JS app. The components had to render data, and I had to implement the logic that processed the data before rendering. The UI scaffold was already provided. The diff…

Technical Screen0
ChimeProduct Manager
Reported Mar 2025

Chime Product Manager interview: organizational structure, emerging technologies, and case study

Round 1 set the tone quickly with three interviews. I started with a conversation about organizational structure, then worked through an emerging technologies prompt that required me to generate many ideas and prioritize them. The third part was a case study that felt designed to test how I’d turn my thinking into decisions. The part I remember most is how concentrated and targeted that first sta…

Other0
ChimeSoftware Engineer
Reported Mar 2025

Chime Software Engineer interview with a complex game-design question

I had a difficult start when a phone screen turned into an extremely complex game-design question that I couldn't get clear enough to understand. The recruiter call came first. During the technical phone screen, I was asked to design a game with complicated rules. The interviewer struggled to explain how the game worked, and the prompt felt unrealistic without prior knowledge. I didn't make it to…

Technical Screen0
ChimeProduct Manager
Reported Mar 2025

Chime Product Manager interview: five rounds with case panels

I remember this process as an intense stretch. I spoke with a lot of people, and every round took real mental effort. It included a recruiter screen, a hiring manager conversation, and two full rounds of panel interviews, for five rounds altogether. The panels were demanding, with case-focused sessions in each one, and the final step was a conversation at the CPO level. The hiring manager experie…

HR 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