Role overview
Build and operate the backend systems that determine who can access resources and what actions they can take across a multi-tenant collaboration product. The work spans authorization, identity, and enterprise administration, with a particular focus on inherited permissions across a hierarchy of resources. Correctness, security, and performance matter on a path used throughout the product.
Responsibilities
- Design authorization services, role and permission models, capability evaluation, sharing controls, and rules for resolving access across nested resources.
- Extend enterprise access controls with reusable profiles, delegated grants, and inherited policies that constrain what local administrators can allow.
- Build and maintain authentication and provisioning flows, including single sign-on, multifactor authentication, OAuth, token and session handling, and SCIM.
- Keep server-side authorization decisions consistent across APIs and product features, and provide audit events that explain access decisions.
- Plan safe changes to live permission data using techniques such as shadow evaluation, dual reads, backfills, and staged releases.
- Maintain reliability and response times, participate in the on-call rotation, and work with product, design, frontend, and security partners on usable controls.
Requirements
- Five or more years of backend engineering experience building production SaaS systems at scale.
- Practical experience building authorization or access-control systems, including policy evaluation or permission models such as RBAC, ReBAC, or ABAC.
- Experience resolving inherited permissions across resource hierarchies, including grants, restrictions, overrides, and revocations.
- Ability to design backend APIs and data models; experience with TypeScript, Node.js, NestJS, PostgreSQL, Redis, or Kafka is relevant, with comparable stacks transferable.
- Working knowledge of identity standards and flows such as OAuth 2.0, OIDC, SAML, JWTs, multifactor authentication, and SCIM.
- Experience with tenant isolation and safe migrations on live systems, plus a security-minded approach to default-deny decisions and privilege boundaries.
Nice to have
- Experience with relationship-based authorization engines, extracting identity services from a monolith, permission administration tools, compliance controls, permission caching, or access for service accounts and AI agents.
Benefits and work setup
The engineering workflow emphasizes daily use of AI tools and agents, asynchronous written updates, and self-serve project reporting. The role includes shared IAM on-call responsibilities.