Lead Affirm's Account Management engineering org owning auth, identity, and security-critical self-service surfaces

Affirm is hiring an Engineering Manager to run its Account Management team, the full-stack org that owns customer-facing self-service channels for auth, identity, and account security. This interview probes engineering-management depth (managing managers, OKRs, roadmaps) alongside hands-on technical judgment across a Python/Kotlin/AWS/MySQL/Kubernetes and React/Vue stack. Remote-Canada role at the P/7 level, reporting into a fast-growing BNPL platform.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Managing managers and ICs together, coaching and career development
Setting OKRs/technical roadmap for a fast-growing consumer product
Cross-functional stakeholder management (risk, security, checkout, analytics)
Hands-on technical judgment: architecture/code review on Python/Kotlin/AWS/MySQL/Kubernetes stack
Ownership of system availability/performance for a customer-facing surface
Hiring and scaling a diverse, high-performing engineering org

Common question themes

Tell me about a time you led a team of engineering managers, not just ICs

How did you set OKRs/roadmap for a team supporting a fast-growing business

Describe balancing competing priorities from risk, security, and product stakeholders

How do you stay hands-on technically while managing a growing org

How have you grown or coached an underperforming (or high-potential) manager

How candidates describe it

Real Manager interview stories — retold from candidates' public write-ups, with sources.

Google · L3 Software EngineerOffer

Google L3 software engineer interview: phone screen, four coding rounds, and the Googleyness round

A candidate with two years of experience went from recruiter outreach to offer over about four months. The onsite was four 45-minute coding rounds — three of them featuring binary trees — and one round turned into a 25-minute chain of follow-ups about approximating an optimal solution at scale.

Interviewed June 2020 · Bangalore, IN

Google · L4 Software EngineerNo offer

Google L4 Software Engineer Interview: Eight Rounds, No Offer

An L4 Software Engineer candidate went through two phone screens, three onsite rounds, a culture conversation, and a team-matching call with a Google hiring manager, then watched the process stall for about a month and a half over a tightened experience requirement before an added extended round ended without an offer.

Interviewed February 2024 · Not specified

Google · L5 Software EngineerNo offer

Google L5 software engineer interview: phone screening, three onsite rounds, system design, and a late rejection

A candidate interviewing for an L5 role went through a phone screening, three onsite coding rounds, a mobile system design round, and a Googleyness and Leadership round. Two of the four technical rounds went poorly by the candidate's own assessment, and after roughly two months of silence the recruiter reported that the role had been closed.

Interviewed January 2023 · Not specified

View the original posting

All Affirm interviews