About the role
Discord has a highly engaged community of millions of daily active users who use the platform for many different reasons, but there’s one thing that nearly everyone does: play video games. Discord plays a uniquely important role in the future of gaming, and we are focused on making it easier and more fun for people to hang out before, during, and after playing games. We're looking for a Senior Software Engineer to join the Growth team at Discord. Our team owns how new users discover, understand, and get started with Discord — from the first moment someone encounters us on the web through the onboarding experience that turns them into engaged members. You'll work across the stack to build the systems that acquire and activate users at scale, whether that means improving how Discord shows up across the web or designing the in-product experiences that help new users find their footing. This is a high-impact role where you'll directly influence how Discord grows. This person will report to the Senior Engineering Manager for Growth. What you'll be doing: Build and optimize user-facing experiences that improve how people discover, understand, and get started with Discord Develop scalable backend systems that serve dynamic, high-performance content at scale Work across the full stack — frontend (TypeScript, React) and backend (Python) — wherever the problem leads Design and run A/B experiments to measure the impact of your work on user acquisition and activation Partner with Product, Design, and Data Science to identify high-impact growth opportunities and iterate quickly Maintain performance and reliability standards for user-facing properties Write code that's readable, reviewable, and built with the next engineer in mind What you should have: At least 5 years of professional software engineering experience Strong expertise in TypeScript and React with a track record of delivering high-performance frontend experiences Practical experience with Python and backend frameworks such as Flask Experience designing and running A/B tests with a focus on data-driven decision making Comfort working across the full stack and taking ownership of projects end to end A habit of asking why before asking how — and the judgment to know when good enough ships and when it doesn't