Senior Software Engineer, Supercell ID (Client SDK)

About the role

LoadingScreen_UP69_Back to school [https://media.ffycdn.net/eu/supercell/ruJakHeSMGHS2SeL8byA.png?width=2400]

WE ARE LOOKING FOR A SENIOR SOFTWARE ENGINEER TO JOIN THE SUPERCELL ID PRODUCT TEAM. SUPERCELL ID CONNECTS HUNDREDS OF MILLIONS OF PLAYERS TO SUPERCELL’S ECOSYSTEM. WE BUILD THE ACCOUNT AND IDENTITY SYSTEM THAT CONNECTS OUR GAMES AND WEB SERVICES INTO A COHESIVE PLAYER EXPERIENCE, COVERING EVERYTHING FROM REGISTRATION AND LOGIN TO ACCOUNT SAFETY, COMPLIANCE AND IDENTITY.

This is a hands-on product engineering role with significant responsibility for the success of our initiatives. You’ll build player-facing features in the client SDK embedded in every Supercell game, while helping decide what we should build and how it should work. You’ll collaborate directly with game teams and other teams across Supercell.

Our client codebase is currently a mix of C++, Flutter and web technologies. Supercell's games are built in C++, and much of the integration between the games and the SDK you'd be working on is native code. Player-facing experiences and flows are currently mostly built with Flutter, while we're moving toward a future where most of our UX is delivered through webviews.

You'll work with the codebase as it exists today while helping us make that transition. We don't expect you to have prior experience with every technology we use. What matters is that you can work across native and web boundaries, learn unfamiliar parts of the stack and choose solutions that work well for players and game teams.

[https://app.ashbyhq.com/api/images/user-content/1246dead-d30e-4c70-a1d3-ef7e5023d542/7a053edc-bf2e-4db4-85ee-5630e2b5d305/banner_narrow_customs.jpg]

YOU MIGHT BE THE RIGHT FIT IF

- You think like a product owner as much as an engineer. You care whether what we build is understandable, useful and successful. You form opinions from data, feedback and firsthand experience, and advocate for changes when you think we can do better.

- You have a strong sense of ownership. Getting a PR merged is only the beginning: you follow your work through testing and release and care about whether it actually solved the problem. When something isn’t working for players or game teams, you’re inclined to do something about it even if nobody has explicitly asked you to.

- You’re comfortable starting with a problem rather than a specification. You work with others to understand what actually needs solving, challenge assumptions when needed, and turn ambiguity into incremental solutions that deliver value.

- You collaborate directly and naturally across disciplines. You seek out the people closest to a problem rather than working through layers of intermediaries.

- You care about engineering quality in a product used at enormous scale: testability, backward compatibility, maintainability and avoiding surprises for the teams and players who depend on your work.

- You’ve taken meaningful ownership of cross-team projects and are comfortable working with both engineering and non-engineering stakeholders.