Process
The interview process was pretty normal. There was an initial interview with a recruiter, followed by an initial tech screen, then a virtual onsite with multiple rounds of technical questions as well as a couple of non-technical rounds.
The questions were quite on-par with what I've come to find as normal in most technical interviews, and nothing really came as a surprise.
The recruiter communicated well and kept me updated. They were also very reliable and easy to get a hold of when I had any questions.
The overall timeline and offer came on a good timeline. It was about two weeks between my first interview and my last, and another few days before my offer. However, the interviewer was able to confirm I would be getting an offer before that. No complaints.
Was this helpful?
Interview Statistics
The following metrics were computed from 28 interview experiences for the Affirm Senior Software Engineer role in United States.
Success Rate
Affirm's interview process for their Senior Software Engineer roles in the United States is fairly selective, failing a large portion of engineers who go through it.
Experience Rating
Candidates reported having mixed feelings for Affirm's Senior Software Engineer interview process in United States.
Affirm Work Experiences
- 5.0Great work-life balanceSenior Software Engineer • Current EmployeeToronto, Ontario, CanadaMarch 1, 2025Pros: Great work-life balance. Great CEO.Cons: Engineers have to do product work sometimes.
- 4.0Very good work environmentSenior Software Engineer • Current EmployeeSeptember 13, 2022Pros: The work environment is great in Madrid. Everyone does their best to make it very easy to learn.Cons: The meetings a little late.
- 1.0Tech stack and eng culture are lackingSenior Software Engineer • Current EmployeeApril 5, 2022Pros: Interesting product space. Great benefits.Cons: Let's be frank, every company has its issues. Affirm is no different. Why do I have such contempt for Affirm these days? Several reasons, but let's start off simple: its immense tech debt. I know, I know, all companies have tech debt. However, I have never disliked working in a codebase/tech stack even close to as much as I do working on Affirm's. From unit tests to integration testing to staging to production deploys to language/repo tooling to telemetry, I cannot think of a single part of our tech stack that meets baseline requirements. It certainly shows. We have regular outages (e.g., a two-part, two-day outage spanning a total of 8 hours in late 2021) and are still running our core services in Python 2 (it is the middle of 2022). It is easy to understand why; we relentlessly prioritize new product initiatives over fixing our decrepit stack. Once again, I will acknowledge this is typical in industry. But the state of our tech stack is simply not tenable and has only gotten worse these past couple of years. I would recommend not joining Affirm solely due to this issue. Don't even get me started on the abysmal engineering culture. Briefly, there is no cultural expectation to support other teams, and doing so is a glorified exception instead of the standard.
Affirm Interview Questions
