Senior Software Engineer - Consumer Apps Desktop

The Consumer Apps Desktop team owns the Windows and macOS foundation behind every Roblox session on a PC or Mac: the window, the launch path, and the shell that holds everything together. You will own that foundation with us. We are dedicated to delivering superior performance, reliability, and user experience on Windows and Macs. As a Senior Software Engineer on the Desktop team, you'll be a driving technical force; you will lead complex client work end-to-end and raise the quality bar across our codebase. You will lead projects at that scale end-to-end, set the technical standard in a codebase millions of people depend on daily, and partner with product, design, and platform teams to ship work that is polished and fast at scale.

You Will:

• Shape & improve the Windows and macOS experience that millions of players see every day.
• Own major Windows and MacOS initiatives end-to-end from ambiguous idea to shipped, measured, and iterated on.
• Rebuild the parts of the app every player touches: how it launches, how it renders, how it lives in the OS.
• Set the technical standard through code review, mentorship, and the code you write yourself.
• Make platform bets that pay off for engineering teams beyond Desktop.
• Translate ambiguous product ideas into well-scoped, high-quality engineering plans in close partnership with product, design, and data science.
• Work with our Microsoft and Apple counterparts to ensure feature ubiquity and platform-specific feature excellence.

You Have:

• 5+ years shipping client software, with deep C++ expertise, including the ability to work effectively inside a large, established codebase. Experience with Lua/React is a plus.
• Released significant Windows or macOS applications. You know the platforms and their APIs throughout.
• Debugging and profiling skills that hold up under pressure: tracing, root-causing crashes, and diagnosing performance problems across the full client stack and an enormous range of consumer hardware.
• Fluency with concurrency and memory. Threading models and memory footprint are a must have to excel here.
• A reflex for data. Metrics, logging, and experiments are how you find out whether a feature works, not how you justify it afterward.
• The ability to take an ambiguous problem, break it down, and drive it to done. You communicate clearly, build trust across functions, and make the engineers around you better.