Staff Software Engineer, Enterprise Platform

Discord's Enterprise Technology org is building a software engineering discipline from the ground up, and this is the founding engineering hire. There is no Enterprise Platform team yet. You will not be maintaining a status quo or joining an existing backlog: you will define the discipline, set the technical foundation, and build the platform that lets the internal systems enabling Discordians scale with the company.

Discord's mission is to cultivate belonging, and doing that at scale requires internal systems that move as fast as the product itself. The mission of this role is to turn our enterprise infrastructure into self-service software. Your job is to replace manual consoles and tickets with a platform of reusable primitives, building blocks like "provision a device" or "push an IAM policy or app integration through code," exposed through clean APIs and self-service portals. As a code-forward Staff engineer, you will design abstractions that hide the messy reality of Okta, Jamf, and Terraform (our identity, device management, and infrastructure-as-code tools) behind interfaces people actually want to use, operating with a platform-as-a-product mindset.

What You'll Do

• Manage the device fleet as code: Move device configuration off consoles and into versioned, API-driven infrastructure for endpoint management and hardware provisioning.
• Automate the identity layer: Manage identity systems and their connections to downstream apps as code, from SSO and SCIM integrations to account workflows, so changes ship through version control and CI/CD instead of an admin console.
• Own app delivery and Infrastructure-as-Code (IaC): Build deployment pipelines and provisioning patterns that let internal systems be built and changed safely, establishing CI/CD standards.
• Build the self-service layer: Design and ship the APIs, CLIs, and portals that compose primitives into paved paths, like a new hire's first day, where software access and group memberships land in one automated, auditable flow.
• Set the foundation: Define the technical direction and architecture for the discipline, writing the RFCs and documentation that future hires will build on.

What You Should Have

• 6+ years building and operating production software and systems at a technology company, with a track record of owning ambiguous projects end to end.
• Strong software engineering fundamentals. You write production code (we lean on Python, TypeScript and Rust), and design, test, and ship it. This is not a systems admin role.
• Deep, hands-on IAM experience (SSO, SCIM, OAuth/OIDC, RBAC) and fluency with infrastructure as code (Terraform) and CI/CD.
• Experience treating endpoint and fleet management as an API-driven engineering surface at scale.
• A platform-as-a-product mindset. You have built self-service tooling that people chose to adopt.
• Comfort with ambiguity and a founder's temperament; energized by building from scratch.

Bonus Points

• Hands-on experience with Okta, Jamf, or Intune.
• Experience with identity and access governance for non-human, workload, or AI-agent principals.
• Background at a high-growth consumer tech company with a highly technical employee base.