Platform Engineer — Backend & Product Infrastructure

About the Role

Every new firm arrives with its own systems, identities, data sources, and workflows. Your job is to turn that variety into shared software, so the fifth customer launches in days rather than the weeks the first one took. The marginal cost of the next customer is the number you own.

This is a backend engineering role that includes infrastructure. It is not an infrastructure role that occasionally touches code. The ideal candidate is a strong backend engineer who can design multi-tenant application systems, write production services, and own the cloud infrastructure those systems run on.

What You Will Build and Own

The shared application platform behind every customer deployment
Multi-tenant architecture with secure customer and data isolation
Identity, authentication, authorization, and tenant-provisioning systems
Reusable integrations against customer source systems, built from what the forward deployed engineers hit in the field
Internal APIs and tooling that let customer-facing engineers ship faster
Production backend code in Kotlin and Python, plus customer-facing product code when a deployment needs it
The delivery path and the reliability of everything you build: local development, preview environments, testing, CI/CD, observability, and incident response
Technical architecture and long-term engineering direction, alongside the CTO

What Our Client Is Looking For

Strong backend or platform software engineering experience
A history of writing and operating production application code, not only managing the systems it runs on
Experience designing APIs, backend services, or distributed application systems
Experience with multi-tenant SaaS architecture, customer isolation, identity, or access control
The ability to look at five bespoke customer builds and find the one abstraction underneath them
Strong cloud experience, preferably AWS
Comfort building the first version of important systems with no existing platform team behind you
Strong technical judgment and the ability to balance speed against long-term architecture
Willingness to move between backend, infrastructure, internal tooling, and product engineering in the same week
Able to work in person in New York City and travel occasionally