Interview Experiences

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

Share yours, earn XP

6 stories

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

AffirmSoftware Engineer
Reported Aug 2026

Affirm Software Engineer Interview Experience: payments design and poor recruiter communication

After an initial recruiter call, I entered a fintech-focused process. The roughly 30-minute screen covered my background, interest in fintech and BNPL, compensation, and location. A deeper hiring-manager conversation followed, covering past projects, technical decisions, and fit for the specific team. The coding portion was a 60-minute HackerRank session. Next came about an hour of system design…

RejectedHR Screen0
AffirmSoftware Engineer
Jul 2026

A Log-Matching Question That Fed Into a Trust Score

Affirm phone screen — should be for an SDE2 role. The interviewer started with casual mutual introductions for about 10-15 minutes (didn't feel like it needed to take that long, but she kept talking and I didn't want to interrupt). The question was about two days of logs — find users who show up in both days and have loan type >= 2. The second part was to calculate a trust score. I finished writi…

In progressTechnical Screen0
AffirmSoftware Engineer
Reported Jul 2026

Affirm Software Engineer interview: finance-style coding and a timed technical screen

My online assessment felt like a finance-specific LeetCode problem. Afterward, I had a 30-minute recruiter screen about the role and logistics, including compensation, the actual work and cultural fit. It wasn't a particularly deep conversation, but it gave me an idea of what they wanted. Next came a technical screen where I shared my screen for a timed coding problem. I only saw the prompt when…

Online Assessment0
AffirmSoftware Engineer
Apr 2026

Fraud Detection Coding and a Payment System Design Round

Four rounds total: one hour of coding + half an hour of behavioral questions + one hour of system design + half an hour of behavioral questions. The two behavioral rounds were just the standard questions. Coding round (the prompt was long, but not hard): Part 1: Live Fraud Detector (Debug Existing Function) Description One of Affirm's competitive edges is our ability to do credit underwriting and…

Onsite0
AffirmSoftware Engineer
Mar 2026

Nailed the Coding Round, Rejected Anyway

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

RejectedOnsiteXP0
AffirmSoftware Engineer
Feb 2026

Five Onsite Rounds, One Shaky HM Round

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

In progressOnsiteXP0

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