Software Engineer, Identity Platform

Responsibilities

• Unify authentication. API keys, management keys, browser sessions, OAuth and OIDC tokens and MCP logins all resolve to a single principal with one authorization model.
• Own sign-in, MFA, passkeys and enterprise SSO (SAML and OIDC) on top of it, plus the full lifecycle of every credential we issue: scoped, expiring, rotatable and revocable.
• Build delegated access for apps and agents. Sign in with OpenRouter, OAuth for MCP clients with dynamic client registration, and consent grants that can be revoked without touching the underlying key. Apps and agents act on a user's behalf without ever handling a secret, and admins can pin that consent to an org or…
• Go secretless with workload identity. CI pipelines and cloud workloads exchange their own identity provider tokens for short-lived OpenRouter credentials under org-defined federation policies, and internal services authenticate to each other the same way. No static secrets to leak or rotate.
• Build composable authorization. A single permission model where every route asks "can this caller do this, here?" instead of checking role names. Org and workspace roles, viewer and restricted roles, read-only automation keys and, over time, custom roles. Deny by default, enforced on the server and reflected cleanly in…
• Make enterprise provisioning just work. SCIM user and group provisioning, group-to-role mapping, domain verification and self-serve SSO that works first try with Okta, Entra ID, Google Workspace and the long tail of identity providers.
• Partner platforms can provision accounts and keys for their own customers programmatically. An IT admin should be able to onboard thousands of seats without filing a ticket.
• Define the core identity model. Users, organizations, workspaces, memberships, apps and guardrails, and how they compose. Clean boundaries, clear ownership semantics and a data model that supports the next five years of enterprise features without a rewrite.
• Protect users and their data. Identity fraud detection, KYC and verification flows, step-up checks on sensitive actions, account-takeover defenses and abuse signals that stop bad actors without adding friction for good ones. Least-privilege access to customer data across every OpenRouter surface.
• Treat auditability and correctness as features. The system ensures every credential has a provenance, every access decision is explainable and every privileged change lands in an audit log. Auth stays fast and highly available on the hot path of every inference request, with clear, standards-based failure modes…

Languages