Senior Software Engineer, Enterprise Platform
Job description
About the role
You own core enterprise domains so internal systems move at the speed of the product. The role turns manual operations into self-service software for Discordians. It targets developers who need reliable, automated access and device workflows.
Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.
Key facts
What you'll do
Device configuration is expressed as code and flows through versioned APIs and automated workflows instead of consoles. This change replaces manual endpoint management and provisioning with a controlled, repeatable pipeline for Discordians.
Identity and access management is defined as code, linking SSO and SCIM integrations into account workflows managed via version control. Changes to permissions and access move through CI/CD rather than admin consoles, keeping an auditable history for Discord teams.
Deployment pipelines and provisioning patterns are declared in code to establish safe CI/CD standards for internal systems. Internal systems gain reliable, repeatable paths for updates and new environments through these standardized pipelines built as infrastructure-as-code.
Onboarding a new hire becomes one automated, auditable flow through self-service portals.
Core platform components are owned from design through production without strict code boundaries. You author RFCs and documentation for your domains, guiding each stage from initial design to live operation on the platform.
Requirements
The posting states a pay range of $196000 to $220500.
You bring 3+ years of building and operating production software at a technology company, with a record of completing projects end to end across the full lifecycle. This background ensures you can handle platform features from design to production.
You write production code in Go, Python, and TypeScript, designing, testing, and shipping software rather than performing systems administration for the Enterprise Platform. The focus is on developer-facing platforms, not infrastructure-only work.
You practice identity and access management using SSO, SCIM, OAuth/OIDC, and RBAC, working fluently with infrastructure-as-code tools like Terraform and CI/CD pipelines. These skills let you automate security and access at scale for Discord users.
Endpoint and infrastructure configuration is treated as an API-driven engineering surface instead of console-driven manual steps. This shift enables scalability, consistency, and easier reuse across teams building on the platform.
You adopt a platform-as-a-product mindset, caring about user adoption of what you build and not only about shipping features for the platform. Success is measured by how well internal teams use your services and integrate primitives into their workflows.
You operate comfortably within complex, multi-milestone projects amid ambiguity while building in a greenfield environment for the Enterprise Platform team.
Nice to have
Hands-on experience with Okta, Jamf, or Intune is valued and helps you build more effective abstractions for device and identity management.
Experience with identity and access governance for non-human, workload, or AI-agent principals is considered a bonus for advanced platform scenarios.
Background at a high-growth consumer tech company with a highly technical employee base is considered a bonus for understanding product-scale usage.
Practical notes
This role is based in the San Francisco Bay Area.
Good to know
Platform engineering teams build internal tools that enable other engineers to deliver software quickly.
Platform-as-a-product thinking focuses on adoption, usability, and clear interfaces to ensure real usage across the organization.
Infrastructure-as-code and CI/CD are central to modern platform operations, automating environment and configuration management for consistency.
Self-service portals reduce manual work and standardize access for developers, improving speed and consistency across teams.
Designing abstractions simplifies complex tools like identity and device management for everyday use, lowering the barrier for adoption by internal developers.