Affirm - Staff Software Engineer, Affirm Bank

• Set technical direction across the bank's systems. Own the medium-to-long-term technical strategy for the bank's core surfaces — cloud infrastructure, data platform, core banking configuration, CI/CD, networking, and the Bank ↔ Affirm Inc integration — and make the architecture calls the rest of the team builds against. Generalist breadth is expected; you go deep where the risk is highest. • Set technical direction across the bank's systems. • Own the hardest problems end-to-end. Personally design, build, integrate, and operate the most ambiguous and highest-stakes pieces of the stack, and own incident response for them. You take the problems no one else can fully scope and turn them into well-defined systems with clear failure domains, monitoring, and runbooks. • Own the hardest problems end-to-end. • Be the force multiplier on a small team. Set and hold the bar for code review, design review, and examiner-readable documentation. Establish the patterns and standards that let a deliberately small team punch far above its size, and level up every engineer who joins after you. • Be the force multiplier on a small team. • Ship AI-first, and push the frontier of it. Treat AI tools and agentic workflows as a load-bearing capability for code, design review, runbook generation, and operations — and actively push yourself and the team on what an AI-leveraged engineering function can deliver in place of additional headcount. • Ship AI-first, and push the frontier of it. • Lead vendor selection and ownership. Drive evaluation, integration, and ongoing oversight of the bank's third-party platforms across the core, data, identity, observability, and card-processing stacks. Carry the bank's most critical vendor relationships end-to-end: integration, operations, escalation, and audit. • Lead vendor selection and ownership. • Define the integration boundary with Affirm Inc. Set the domain edges, data flows, and integration patterns between the bank and Affirm Inc so the bank's products work seamlessly inside the Affirm ecosystem while preserving the legal and regulatory separation the charter requires. Drive this across Affirm Inc engineering teams whose systems integrate with the bank's. • Define the integration boundary with Affirm Inc. • Build for examiners. Partner with Legal, Compliance, Risk, BSA/AML, Finance, and Internal Audit so compliance is a property of the product from day one. The systems you design are the artifacts FDIC and state examiners will inspect — design and document them to a standard that holds up under examination and audit review. • Build for examiners. • Own the operational posture of the bank's systems. Set the reliability, observability, alerting, runbook, incident-response, and disaster-recovery practices that keep the bank standalone-operable and audit-ready, while keeping the operational footprint intentionally small. You will support the operations and availability of your team’s artifacts by creating and monitoring metrics, escalating when needed, and supporting “keep the lights on” & on-call efforts. • Own the operational posture of the bank's systems. • Influence up and across the organization. Communicate technical strategy, tradeoffs, and constraints with clarity to bank executives, the Bank Board, Compliance, Risk — and to engineers outside the bank across the broader Affirm org. The relationships you build beyond the team shape how cleanly the integration boundary works. • Influence up and across the organization. • Help grow the team and the bar. As engineers join, they inherit a function whose architecture, practices, and standards you helped set. Mentor peers, provide high-signal feedback, contribute to hiring, and lead by example. • Help grow the team and the bar. • What We Look For • 8+ years of software engineering experience, with staff-level, hands-on builder credentials and a track record of owning ambiguous, high-stakes systems end-to-end through launch and operations • Comfortable owning ambiguity at the largest scale on the team — you move fast, make the tough prioritization calls, take ownership before being asked, and balance speed with the engineering judgment the hardest decisions require • Comfortable owning ambiguity at the largest scale on the team • Hungry to leverage AI to drive outcomes — fluent with AI-assisted development tools (Claude, Cursor, Codex, agentic workflows) and actively pushing yourself and your team to use them as a multiplier for code quality, velocity, and what a deliberately small team can ship • Hungry to leverage AI to drive outcomes • Bias toward simplicity — experience building toward a small, lean engineering culture that rewards "buy over build", a default-deny posture, and standalone-operability over an abundance of tooling • Bias toward simplicity • A track record of setting technical direction — you've defined architecture and multi-quarter technical strategy for systems beyond your own projects, and led the execution of it across engineers and teams without needing a management title to do so • A track record of setting technical direction • Deep systems thinking across public cloud infrastructure (AWS preferred), infrastructure-as-code (Terraform), and cloud data platforms (Snowflake or comparable) — you understand their failure modes and tradeoffs, not just their surface APIs • Deep systems thinking • Regulated-environment experience — direct work in banking, payments, securities, healthcare, or another setting subject to external examination, where the work involves examiner-facing documentation and decisions