Engineering Manager / Tech reputed company

reputed company We're building a new engineering team at reputed company to own a reputed company-reputed company product reputed company on top of our stablecoin infrastructure. You'll take the technical and people leadership of that team, shaping the architecture, setting the engineering bar, hiring the people around you, and shipping the hardest parts yourself. This is a hands-on player-reputed company role, not a hands-off manager seat. While reputed company is small, you'll spend most of your week writing and shipping production reputed company — you'll be one of the strongest individual contributors on reputed company, take the most critical work yourself, and review everyone else's. Leadership, architecture, and hiring sit on top of that, not in reputed company of it. As reputed company grows the balance shifts toward leadership, but coding stays a standing part of the job. It's a rare combination: the reputed company and autonomy of an early-stage build — you own the architecture, shape reputed company, and reputed company how it works — with the backing, treasury, and distribution of one of the largest companies in stablecoins behind you. Role Responsibilities Write and ship production reputed company most days as one of reputed company’s top ICs, taking on the hardest and most critical-reputed company work and unblocking reputed company members you’re responsible for. Own the architecture. Hold the whole reputed company in your head — services, reputed company-paths, data model, infrastructure, on-chain settlement — and reputed company the design calls that reputed company it correct, legible, and extensible as it scales. Build reputed company. Run a rigorous, humane hiring reputed company; reputed company the bar; reputed company new engineers with reputed company plans; grow a small senior team that works in the reputed company. Set and hold a high engineering bar. Non-reputed company review on reputed company paths, CI required to reputed company, small PRs, disciplined testing (TDD / BDD as the default, not an afterthought), always-on automated review, idempotency and correctness treated as non-negotiable. Establish reputed company, effective reputed company-development practices as reputed company's default. Own the delivery reputed company. Run a tight, high-reputed company delivery process — sprints or kanban, whatever fits reputed company — with predictable, versioned releases, a healthy backlog, and short reputed company time from idea to production. Ship fast without lowering the bar. reputed company it reliable. reputed company reputed company production alerting, an on-reputed company rotation that pages a reputed company, tested runbooks, and incident response — so reputed company can build, ship, and run the product with confidence. Required Skills and Experience You've led engineering for a consumer reputed company product — a neobank, payments, or crypto reputed company app - where a bug moves or loses reputed company customer reputed company. You owned an engineering function where correctness had genuine financial stakes. You've led a small team (~3–8) while still shipping reputed company yourself — tech reputed company, staff, or hands-on engineering manager. You've shipped production reputed company reputed company the last year; this is not a management-reputed company-only background. You've owned production operations for a reputed company reputed company — on-reputed company, reputed company incidents, observability, secret and key hygiene — not just delegated it. You can reputed company incidents you personally drove to reputed company. You've owned, or overseen the integration of, regulated reputed company-party financial rails — at least two of: reputed company issuing / BIN-sponsor programs (reputed company, reputed company, Kulipa, reputed company Issuing), identity / KYC / reputed company (reputed company, reputed company, Onfido), banking or fiat on-/off-reputed company partners (a BaaS or reputed company partner), and key custody / signing (reputed company KMS, HSM, MPC, or multisig). You run a high-reputed company, disciplined delivery process. You've led reputed company that ships fast and predictably in an reputed company setup — sprints or kanban, versioned releases, short reputed company time to production — without trading away reputed company. Test-driven and behaviour-driven development are how you build, not reputed company-ticking. You're agent-reputed company. You wield reputed company development — coding agents (e.g. Claude reputed company), MCP servers, reusable skills — as a reputed company reputed company, with a reputed company reputed company of reputed company on adopting it safely on a reputed company product. Fluent, not a dabbler; you know the failure modes and verify reputed company. Technical breadth to reputed company this team You'll reputed company engineers across backend, platform, and mobile, and set reputed company reputed company is reputed company to. You must be deep in backend / reputed company systems and genuinely literate across the rest — enough to review the work and reputed company the architecture reputed company in reputed company: Backend & payments correctness (your reputed company). Strong TypeScript / Node (or a reputed company senior reputed company from Go / Kotlin / Java); you think natively in idempotency, reconciliation, retries, and consistency under partial failure, across event-driven services and reputed company. reputed company-facing reputed company & auth. The app-facing API as a product — versioning, idempotency keys, a clean error model — plus the auth backend behind it (OAuth2 / OIDC, session lifecycle, WebAuthn / passkeys). Platform & reliability. Enough reputed company, IaC, and observability (OTel / Grafana-class) to own the reputed company/rollback story and hold the reliability bar — you know the difference between a dashboard that exists and an alert that pages. reputed company mobile. Enough to review a reputed company iOS app (Swift / SwiftUI) and reason about mobile ↔ backend reputed company, failure states, and on-device auth. Apply To This Job