Affirm Software Engineer interviews typically start with a recruiter call and a live coding screen. Candidates report practical coding, a system design round, and hiring manager conversations.
$172K
Avg. Base Comp
$280K
Avg. Total Comp
3-6 rounds
Typical Rounds
Not reported
Process Length
Candidates describing Affirm's Software Engineer loop most often mention a recruiter call, a live coding screen, a hiring manager conversation and a later technical or system design round. The coding is frequently described as practical rather than classic puzzle-solving. Reported tasks include:
The clearest recurring theme is language-specific fluency. Two candidates tied the coding to Python. One reports that feedback focused heavily on Python syntax even after they had said their background was in Java. Another found a second technical round depended on a particular Python library. Write in the target language under a clock rather than solving problems only conceptually.
For design, one candidate was asked to design a loan repayment payment system that calls an external bank API available only a few hours per day. Another described an hour-long system design round, and a senior candidate faced graph and hashing-style algorithm questions alongside design. All the outcomes in these reports were rejections, so expect a real bar. Reported timelines vary, and two candidates described processes of about two months or longer. Prepare arrays and hashing, a clear walkthrough of a past project with its tradeoffs, and behavioral stories about conflict and teamwork.
Synthesized from 33 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Affirm process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Affirm
Write a function is_subsequence to find out if string1 is a subsequence of string2
| Question | |
|---|---|
| Google Maps Improvement | |
| Hurdles In Data Projects | |
| Alternative Vendor Tradeoff | |
| LRU Cache 1 | |
| Reddit-like Notifications | |
| 2nd Highest Salary | |
| Closest SAT Scores | |
| Employee Salaries | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Merge Sorted Lists | |
| String Shift | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Total Spent on Products | |
| P-value to a Layman | |
| Maximum Profit | |
| Prime to N | |
| Cumulative Distribution | |
| Top 3 Users | |
| Over-Budget Projects | |
| Over 100 Dollars | |
| Minimum Change |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an introductory call covering background, the role, the team and how the process works. One mentions salary expectations and remote work. It is typically a fit check rather than a technical test, so have a short pitch and clear location and level questions ready.
Candidates report a live coding round with easy-to-medium problems. Reported examples include dictionary or hashing problems, a 2-sum style question, a simulation to extend, and filtering user logs by business rules. Several note time pressure and attention to language syntax, so practice in the role's language.
Some candidates describe a manager round focused on past work, going in depth on a previous project. Behavioral topics reported elsewhere include teamwork and handling conflict. Prepare specific project stories with challenges, tradeoffs and what you would change, since interviewers may probe the details.
Reported second rounds include more array and hashing coding, an Affirm-specific coding task relying on a particular Python library, and a system design round. One candidate described designing a loan repayment system around an external bank API available only a few hours a day.
Some candidates describe a virtual onsite or further technical and manager rounds, with total round counts reported from 3 to 6. One candidate waited about two weeks for a final answer, and two describe processes of about two months or longer. Rejections sometimes came with little feedback, though one senior candidate received feedback.
