Director of Engineering, Platform

Oscar Faye; United States; On-site; USD 180,000 - 270,000; Full time

Job summary

Oscar Faye is seeking a senior platform engineering leader to shape the core platform and infrastructure that power its rapidly growing lending platform. You will own how the system ships, runtimes, and the tooling that engineers rely on to move fast and safely.

You will build structure where none existed, place capable leads, and drive delivery cadence across distributed teams in the US and LatAm, aligning with security and governance requirements.

Qualifications

• Seven years in engineering with three to five years leading engineers.
• Deep depth in two or more areas: platform/infrastructure, reliability/SRE, or DevOps/delivery.
• Strong cloud-native experience in AWS, containers, and durable execution.

Responsibilities

• Define and structure platform and infra teams; set standards and leads.
• Own delivery velocity, observability, and incident practices aligned with business needs.
• Collaborate with product and security to ensure SOC 2-ready controls.

Skills

Platform & infra

Reliability & SRE

DevOps & delivery

Cloud-native AWS

Kubernetes / EKS

Infrastructure as code

Tools

AWS

Kubernetes

Terraform

CI/CD

Job description

My client is a profitable home equity lender backed by a multi-billion dollar alternative asset manager. They built their lending platform themselves and own the whole loan lifecycle in house, from application through underwriting, closing documents, money movement and servicing. That is why they can close a home equity line in as little as one day while the rest of the industry takes weeks. They originate hundreds of millions a month and are scaling toward a billion, serving hundreds of lender partners and tens of thousands of loan officers. They also run their platform white-labelled under other lenders' brands, so they are part lender and part embedded finance business.

The Role:

You would lead their platform organization: the systems the product runs on, and the tooling their engineers ship through. Where their Director of Engineering, Product owns what ships, you own what it ships on, and the speed and safety with which it ships.

Engineering there is still taking shape. One function, platform and infrastructure, has a lead and a defined team today. The others do not. Your first job is to bring structure to the functions that need it, put the right leads in place, and set the standard for how they build. Ten people on the platform team today, five full-time and the rest on contract, spread across the US and South America, and they are in midst of scaling in a big way!

What you would own:

Core, and where they need you strongest:

• Platform and infrastructure. The AWS estate, account structure, environment strategy, infrastructure as code and the direction of their compute.
• Reliability and SRE. Observability that surfaces a problem before a partner reports it, on-call and incident practice where the review changes the system rather than the ticket, and service level objectives tied to what the business actually needs.
• Developer experience and delivery. The path from commit to production, and environments engineers can trust. Product engineering is your customer and their velocity is your measure.

Also yours, with room to shape how:

• Quality engineering. Test automation and frameworks that let every team test its own work.
• The AI engineering platform. They build AI-first. You would set the direction on harnesses, guardrails and evaluation tooling. In regulated lending the boundary is firm: the deterministic result is the source of truth, a human makes the loan decision, and the agent path never writes or gates it.

Partnered, not yours to absorb: security and GRC report separately, architecture owns cross-cutting design, and corporate IT runs endpoints and identity.

The work in front of you:

The platform works and the business is growing on it, but it was built for a fraction of the volume it now carries.

Ahead of you:

• Tenant isolation for enterprise partners, moving from switch-based partitioning to real separation.
• A shift from function-per-endpoint serverless toward containerized services on EKS with durable execution on money-path workflows.
• Synchronous request handling moving to event-driven processing with proper queueing and failure handling. And SOC 2 Type 2 supported by real technical controls.

All of it happens while origination volume grows, not during a pause. That constraint is the job.

What they are looking for:

• Around seven years in engineering, with three to five years leading engineers
• Real depth in at least two of: platform and infrastructure, reliability and SRE, or DevOps and delivery
• Cloud-native and deep in AWS, with a considered position on infrastructure as code, containers and durable execution. Kubernetes or EKS in production
• You have built structure where there was none: installed leads, set standards, and made delivery predictable
• Technical enough to read a design doc and a diff and form your own opinion. Writing production code is not the job, but you have not lost the ability
• You can share ownership. CI/CD, observability, incident practice and SOC 2 are collaborations between you, the VP of Engineering and your peer on the product side. That is deliberate, and it suits people who would rather build something together than draw a boundary around it

Nice to have:

• Regulated financial services: lending, mortgage, home equity or payments, where correctness, auditability and security are first-class rather than overhead
• Multi-tenant platforms where enterprise customers required real isolation
• SOC 2 or equivalent owned from the engineering side
• Hands-on experience with agentic development tooling in production
• Leading distributed and contract teams across time zones

If this is you, or you know someone it fits, let's get in touch!