Discord
Software Engineer, Data Platform
About this role
Discord seeks a Software Engineer to build and maintain large-scale data infrastructure supporting millions of gaming users. You'll design and deploy data systems handling petabytes of information while collaborating with engineers and data teams to power platform insights.
What you'll do
- Build and maintain data infrastructure processing petabytes across millions of users
- Write clean, tested code for data ingestion, transformation, and serving systems
- Own projects end-to-end from design through deployment and production support
- Collaborate with data scientists, engineers, and product teams on data solutions
- Debug complex systems and continuously improve technical implementations
- Explain technical concepts clearly to diverse audiences
What they're looking for
- Software engineering (3+ years)
- Python, Java, Rust, Go, or similar languages
- Distributed systems design
- Computer science fundamentals
- Data pipelines and ETL tools (Kafka, Spark, Flink, Airflow, Dagster)
- SQL and data modeling
- Cloud infrastructure (AWS, GCP, Azure)
- Docker and Kubernetes
Benefits
- Base salary $160,000–$200,000
- Equity compensation
- Relocation assistance available
- Mission-driven work impacting millions of gamers
- Collaborative team environment
- Reasonable accommodations provided
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Discord
Discord builds a real-time communication platform serving millions of daily active users, with infrastructure handling trillions of messages across gaming and community use cases. The company is hiring backend engineers, infrastructure specialists, and data engineers to develop distributed systems, database infrastructure, developer tools, and large-scale data platforms that power its core platform.
- Website
- discord.com
Likely interview questions
- Tell us about your experience building or maintaining data infrastructure. How have you handled scaling challenges when working with large datasets?
- Describe a time you owned a project end-to-end—from design through production. What was your approach to handling unfamiliar systems or technologies?