Affirm Program / Project Manager Interview Questions

1.Tell me about a project where the status reporting or process you inherited was genuinely confusing people. How did you fix it?

2.Walk me through a time a project started slipping and the root cause turned out to be something outside your team's direct control. How did you find it and what did you do?

3.Describe a project where a risk you identified early wasn't taken seriously at first — how did you keep it on the radar and what eventually happened?

4.Tell me about a time you pushed back on a senior stakeholder's decision on a project you were running. What was at stake, and how did you handle it?

5.Tell me about a time you had to redesign a reporting or tracking process mid-project because leadership couldn't actually use what you were producing. What broke, and how did you rebuild it?

6.Tell me about the most complex cross-team dependency you've ever had to untangle. How did you figure out who owned what, and what did you do when the ownership was genuinely unclear?

7.Estimate how many merchants Affirm would need to onboard in the next year to add $500M in new GMV. Walk me through your assumptions.

8.Affirm's checkout completion rate on a major retail partner's site drops 8% week-over-week with no deployment on Affirm's side. How do you diagnose it, and what do you rule out first?

9.You're asked to help Affirm decide whether to build a dedicated onboarding program for mid-market merchants or continue using the same process as enterprise merchants. How do you structure your analysis?

10.Affirm's consumer app shows a 12% drop in users who complete a second BNPL purchase within 90 days of their first. How would you figure out what's driving it, and what would you propose to fix it?

11.Affirm is considering launching a new merchant category — say, healthcare or home services — where average transaction sizes are lower and use cases are less familiar to consumers than electronics or travel. How would you estimate whether it's worth pursuing, and what are the two or three biggest risks you'd want to quantify first?

12.You're the program manager for a cross-functional initiative to reduce Affirm's merchant time-to-live by 30%. Six weeks in, the data shows you've cut TTL by 8% and the team is out of easy wins. Leadership wants a path to 30%. What do you do?

13.Walk me through how you typically build and maintain a project roadmap when multiple workstreams are running in parallel. What tools do you use and how do you keep it from going stale?

14.How do you define 'done' for a project, and how do you handle the gap between engineering saying it's shipped and the business actually getting value from it?

15.You're coordinating a launch that requires sign-off from legal, compliance, engineering, and a merchant partner, and each group has given you a different 'ready' date. How do you build a realistic launch date and communicate it to leadership?

16.Tell me about a time you had to manage a project where the scope was legitimately ambiguous at the start — not because of poor planning, but because the business problem itself wasn't fully understood yet. How did you structure your work?

17.A critical integration between Affirm's checkout flow and a major merchant partner is scheduled to go live in two weeks, and your QA lead just told you there are 14 open bugs — three of which touch the loan disclosure display. How do you triage and decide whether to launch?

18.You've just been handed a program with three teams that each have their own sprint cadences, OKRs, and definitions of success — and your job is to ship a single coordinated outcome. How do you get alignment without creating a fourth process that nobody wants?

19.You're running a project and a teammate privately tells you the engineering estimate you just presented to leadership is too optimistic — they think it's off by four weeks. What do you do next?

20.A partner team you depend on just told you their work will slip two weeks because they got pulled onto a P0 incident unrelated to your project. You have hard downstream commitments that were built around their original date. What's your first move?

21.You're managing a merchant integration launch and the merchant's legal team inserts a new disclosure requirement four days before go-live — something your internal compliance team hasn't reviewed yet. The merchant says it's standard in their agreements. How do you handle this?

22.You've inherited a program with a hard deadline set six months ago based on assumptions that are no longer true — the scope has grown by 40%, one of the original engineers is gone, and leadership still expects on-time delivery. How do you approach the conversation to reset expectations?

23.You're leading a high-visibility initiative to expand Affirm's BNPL integration with a retail partner into two new product categories. Three weeks before launch, a data analyst on the risk team flags that approval rates in one of the new categories are unexpectedly low in testing — potentially too low for the merchant to see meaningful lift. Product says ship it anyway and iterate. Risk says the data isn't conclusive yet. What do you do?

24.You're six weeks into running a cross-functional program when you discover that two senior engineers on different teams have been making conflicting technical decisions that, if both shipped, would break Affirm's loan servicing pipeline for a subset of users. Neither team flagged it. What do you do?

25.Tell me about a time you had to get a sales or business development team to adopt a new process or reporting cadence they didn't ask for. How did you get them on board?

26.Describe a time you had to brief an executive on a program status and the real answer was 'we don't know yet.' How did you handle that conversation?

27.You're working with a finance partner to lock in budget for a program, and they keep deprioritizing the review because other things are more urgent to them. Your kickoff date is in three weeks. What do you do?

28.Tell me about a time you were the only person in the room who didn't have a strong functional opinion — you were the PM, not the expert — and you still had to drive the group to a decision. How did you do it?

29.You're coordinating a program with a hiring manager who keeps changing the job requirements mid-search — each change effectively resets the recruiter's pipeline. The recruiter is frustrated, the role is now eight weeks behind, and the HM says the requirements are still evolving. How do you intervene?

30.You're running a program where a key external partner — a merchant or financial institution — is consistently late on deliverables and non-responsive to your outreach. Your internal team is blocked. What steps do you take, and how far are you willing to escalate?