Senior Engineering Manager

Scapia; Bengaluru; On-site; INR 2,500,000 - 3,500,000; Full time

Job summary

Scapia is seeking an Engineering Manager in Bengaluru to lead a critical product domain, focusing on building reliable systems and enhancing team performance. You will manage a team of backend engineers, making key architectural decisions and ensuring high-quality delivery in a rapidly changing environment.

The ideal candidate has strong backend engineering skills and experience in fintech or related sectors. This role offers the opportunity to grow a high-performance team in a dynamic fintech setting.

Qualifications

• 3+ years managing backend engineering teams directly.
• Strong backend engineering depth with distributed systems design.
• Track record of improving team reliability and delivery.

Responsibilities

• Lead a team of 5–10 backend engineers.
• Own architecture decisions for APIs and service design.
• Drive uptime, incident response quality, and RCA process.

Skills

Team leadership

Backend engineering depth

Improving reliability and delivery

AWS/cloud-native infrastructure

Payment/fintech experience

Job description

About Scapia

Scapia is a fintech company building a travel‑focused credit card experience that converts everyday spending into travel rewards. The company aims to deliver seamless financial products and travel experiences through cutting‑edge technology and customer‑centric innovation. We’re building a high‑performance engineering team that thrives on ownership, speed, and solving complex fintech challenges.

Role Overview

We’re hiring an Engineering Manager to own one of our most critical product domains—a complex, regulated, high‑stakes backend that sits at the heart of our fintech platform. This is the kind of domain where reliability, correctness, and scale all matter equally, and where the engineering decisions you make have direct business consequences. You’ll be joining at an inflection point: the product has real traction and the next chapter is about building the engineering foundations that allow us to grow 10× without breaking.

What you’ll own

• Lead a team of 5–10 backend engineers, with scope to grow. This isn’t a reporting role—you’ll be deeply involved in technical direction, hiring, and making the team measurably better every quarter.
• Run a tight, high‑trust engineering squad. Set the bar for code quality, system reliability, and engineering culture. Make your team better at their craft, not just faster at shipping.
• Own architecture decisions across your domain—APIs, service design, data flows, and third‑party integrations. Review designs and challenge trade‑offs, not just sign off.
• Scale the team deliberately. Own the full hiring funnel—sourcing, bar‑raising, onboarding. Develop senior engineers into tech leads.
• Drive SLA discipline. Own uptime, on‑call health, incident response quality, and RCA process for your domain.
• Partner with Product, Risk, Compliance, and external partners. Translate business constraints, including regulatory ones, into clean technical solutions.
• Help us build the right amount of process—enough to ship reliably, not so much that we slow down. Own shipping quality changes to production and regression suites that ensure stability.
• Leverage AI to transform our software development lifecycle, building an AI‑first engineering culture that boosts team productivity, innovation, and code quality.

The Real Challenge

This isn’t a simple CRUD product domain. You’re dealing with:

• 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 10× the load without a greenfield rebuild. That means thoughtful incremental improvements, not big‑bang migrations.

Profile

Must‑haves

• 3+ years managing backend engineering teams directly—we’ve hired, grown, and occasionally had hard conversations with engineers.
• Strong backend engineering depth—can read a distributed systems design and find the flaw, even if 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 bring structure rather than wait for it.

Nice‑to‑have

• Experience with fintech, payments, or regulated financial products—you understand idempotency in a banking context.
• AWS/cloud‑native infrastructure experience—our stack runs on ECS, and you care about how services are deployed, not just written.
• Prior startup experience—you know the difference between good process and process theatre.