Principal Backend Engineer, Push

#### How you can make an impact:

• Own the technical direction and architecture for Push across backend services, external integrations, data flows, and onchain settlement

• Translate product, regulatory, and operational requirements into a clear engineering roadmap, well-scoped projects, and sound technical decisions

• Design and build resilient services for on-ramp and off-ramp transaction lifecycles, including payment initiation, status tracking, settlement, exception handling, and customer notifications

• Lead integrations with open-banking, payments, identity, compliance, and blockchain infrastructure providers

• Define secure boundaries between fiat systems, non-custodial wallets, and onchain execution, ensuring sensitive data, permissions, and signing-related flows are handled appropriately

• Set and uphold standards for secure development, architecture review, testing, observability, incident response, deployment, and sustainable on-call ownership

• Partner closely with Product, Compliance, Legal, Security, Operations, Finance, and application engineers Remain hands-on in the codebase, particularly for complex architecture, high-risk changes, and critical production issues

---

#### Let's connect if you have:

• 8+ years of backend engineering experience, including senior technical leadership of production systems and teams

• Experience designing distributed, event-driven systems that move or account for real money, with a strong understanding of failure modes and operational risk

• Experience with regulated financial products and understanding how to balance compliance and regulatory requirements with product features and goals

• Strong backend programming skills. Production experience with Rust is highly desirable; deep experience with Go, Java, C++ can substitute

• Strong knowledge of API design, PostgreSQL or another relational database, messaging systems, and service-to-service integration patterns

• Experience in regulated fintech, payments, banking, digital assets, or another environment requiring auditability, controls, and high availability

• Excellent system-design judgement, including migration strategy, build-versus-buy decisions, security boundaries, and the long-term operational cost of architecture choices

• A track record of leading engineers through ambiguous, high-impact work while remaining close to implementation and production operations