Senior Engineering Manager

Multi-vendor orchestration: The same user journeys run across multiple external partners with different APIs, SLAs, and failure modes. Keeping this reliable and debuggable is genuinely hard.

Regulated complexity: Compliance-mandated flows, deduplication, and third-party verification checks aren't optional. Your systems need to be both correct and auditable under regulatory scrutiny.

Stateful, complex workflows: Core flows involve many states, retry logic, and idempotency requirements. Making these resilient and testable — while the product team wants to add new flows — is an ongoing engineering challenge.

Scale without rewrite: We need to go from where we are to 10x the load without a greenfield rebuild. That means thoughtful incremental improvements, not big-bang migrations.

3+ years managing backend engineering teams directly — you've hired, grown, and occasionally had hard conversations with engineers.

Strong backend engineering depth — you can read a distributed systems design and find the flaw, even if you're not writing the code day-to-day.

Track record of improving team reliability and delivery — not just shipping features, but making the team better at shipping them.

Comfortable with ambiguity — Scapia moves fast, priorities shift, and you'll need to bring structure rather than wait for it. Nice-to-have

Experience with fintech, payments, or regulated financial products — you know what 'idempotency' means in a banking context.

AWS / cloud-native infrastructure experience — our stack runs on ECS, and you'll need to care about how services are deployed, not just written.

Prior startup experience — you know the difference between good process and process theatre.