Affirm logo
AffirmSoftware Engineer
Updated Aug 2, 2026

Affirm Software Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Software Engineer at Affirm, newest first and distilled into what to expect across the loop.

Get your personalized Affirm Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
Build my free plan
Hot & recentNewest first
4 weeks ago
Average Neutral Poland

After an initial recruiter call, I ended up in a pretty fintech-focused sequence. The recruiter screen ran about 30 minutes and covered my background, my interest in fintech/BNPL, and the usual logistics like compensation and location. Not long after, I had a deeper hiring-manager conversation where we dug into my past projects and the technical decisions I’d made, plus how I’d fit the specific team.

Then came the coding part: a 60-minute HackerRank session. The system design round followed, lasting about an hour and centered on fintech systems, including how to keep a ledger consistent, how idempotency shows up in payments flows, and how loan servicing tends to be handled in practice. The behavioral interview was essentially another conversation with the hiring manager, keeping it grounded in collaboration and past experience. Overall the difficulty felt fairly average for the amount of ground they covered, and the structure made the role’s domain pretty clear.
1 month ago
Average Positive New York, NY

My process started with an OA that felt like a “finance-style” LeetCode prompt, more tailored than just generic algorithms. After that, I had a 30-minute recruiter screen that mostly clarified the role and logistics—compensation, what the work would actually look like, and whether I’d be a cultural fit. The recruiter call wasn’t overly deep, but it gave me the sense of what they were aiming for.

Next was a technical screen where I shared my screen during a timed coding problem. The prompt itself was delivered at the moment, so I had to switch gears quickly once it appeared. After that, I moved into the hiring-manager stage where the interview felt like a more standard live discussion rather than a pure coding evaluation. The overall difficulty stayed around average, and the tone felt businesslike rather than overly stressful.

Unlock every Software Engineer interview experience

Real Software Engineer interview experiences
  • Difficulty, sentiment and outcomes
  • New reports added every week
See all experiences
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.

What to expect

Distilled from the reports

Recruiter & Initial Screening

The process typically begins with a recruiter call that covers logistics, role expectations, and cultural fit, often lasting around 30 minutes. Candidates noted varying levels of responsiveness and clarity from recruiters, which significantly impacted their overall experience.

Recruiter callLogisticsCultural fit

Technical Coding Screen

Candidates generally faced a technical coding interview, often using HackerRank, with questions that were typically LeetCode-style but sometimes tailored to finance-related scenarios. The difficulty varied, with some candidates finding the prompts straightforward while others struggled with the platform's limitations.

HackerRankLeetCodeCoding problems

System Design Interviews

System design rounds were a significant part of the interview process, focusing on practical applications in fintech, such as ledger consistency and payment flows. Candidates expressed the need for preparation in this area, as it was a key factor in their evaluations.

System designFintechPractical applications

Behavioral Interviews

Behavioral interviews often involved situational prompts and discussions about past experiences, with varying levels of engagement from interviewers. Candidates reported that the tone and structure of these interviews could greatly influence their perception of fairness and collaboration.

BehavioralSituational promptsEngagement

Interview Process Length & Communication

The overall length of the interview process varied, with some candidates experiencing delays and a lack of communication regarding their status. Many expressed disappointment over the absence of feedback after multiple rounds, which left them feeling uncertain about their performance.

Process lengthCommunicationFeedback

Overall Difficulty & Outcome

The difficulty of the interviews was generally perceived as average, but candidates noted that specific rounds could feel more challenging depending on their preparation and the interviewer's style. Many left without offers, reflecting on how the process could feel unfair or opaque at times.

DifficultyOutcomeFairness