Senior Staff Engineer, Payments Compliance

Airbnb Airbnb · Consumer · United States · Software Engineering

Senior Staff Engineer, Payments Compliance at Airbnb. Owns technical vision and architectural direction for the Compliance engineering landscape, focusing on Policy Enforcement, Identity, Screening, Auditing, and Compliance Experience. Ensures compliance systems are scalable and aligned with global regulatory requirements like AML, KYC, and sanctions screening. Partners with cross-organizational teams and stakeholders to drive high-stakes design tradeoffs.

What you'd actually do

  1. Own the end-to-end system design vision for the Compliance organization, setting the architectural direction for an engineering organization of nearly 30 engineers across multiple teams.
  2. Drive foundational architectural shifts, including the move from an account-centric model to a customer-centric one — rethinking how we model identity, risk, and enforcement across the platform.
  3. Lead the technical strategy for expanding KYC capabilities — supporting small and medium businesses, reimagining business onboarding and account structures, enabling KYC through third-party APIs, and extending verification to third-party payees.
  4. Architect systems that adapt to the evolving digital identity landscape — including new verification standards, government-issued digital credentials, and shifting privacy regulations — without requiring costly re-platforming.
  5. Ensure our technical foundations are flexible enough to absorb unforeseen regulatory mandates with aggressive timelines, without destabilizing existing systems or requiring disproportionate engineering investment.

Skills

Required

  • 15+ years of technical experience
  • 10+ years of relevant industry experience in a fast-paced tech environment
  • Prior knowledge of Regulatory Compliance standards (AML, KYC, sanctions screening)
  • demonstrated experience designing and implementing those controls at scale
  • Proven track record of setting technical direction and architectural strategy for a large engineering organization
  • ability to drive alignment across organizational boundaries
  • Experience designing systems that span multiple teams and domains, with a focus on cohesion, reusability, and long-term maintainability over initiative-by-initiative solutions
  • Excellent communication skills
  • ability to influence senior technical and non-technical stakeholders across the company
  • Strong problem solver
  • deep experience operating and leading on-call for production systems at scale
  • Technical leadership: hands-on experience leading large project teams, making high-stakes design tradeoffs, and translating regulatory requirements into scalable system architectures
  • Proficiency in one or more back-end server languages (Java/Ruby/Go/C++/etc.)
  • Deep understanding of architectural patterns

Nice to have

  • BS/MS/PhD in Computer Science, a related field, or equivalent work experience.

What the JD emphasized

  • own the technical vision and architectural direction
  • compliance systems are cohesive, scalable
  • increasingly complex global regulatory environment
  • operate at the intersection of deep systems expertise and organizational influence
  • connective tissue across Compliance's multi-year strategic initiatives
  • drive high-stakes design tradeoffs across team boundaries
  • Own the end-to-end system design vision
  • architectural direction
  • foundational architectural shifts
  • technical strategy
  • Architect systems
  • technical foundations
  • drive alignment on shared capabilities and cohesive system design
  • Prior knowledge of Regulatory Compliance standards (AML, KYC, sanctions screening)
  • demonstrated experience designing and implementing those controls at scale
  • Proven track record of setting technical direction and architectural strategy
  • drive alignment across organizational boundaries
  • Experience designing systems that span multiple teams and domains
  • long-term maintainability
  • influence senior technical and non-technical stakeholders
  • deep experience operating and leading on-call for production systems at scale
  • Technical leadership
  • making high-stakes design tradeoffs
  • translating regulatory requirements into scalable system architectures