Show more filters
I'm looking for a Unity engineer who's shipped enough games to be a little paranoid.
The kind who knows "it worked in the Editor" is not a plan.
And who knows that shipping code is not the same as shipping a game. Merging the PR is the easy part. Getting it to hold up in players' hands, on real devices, under live traffic, at 2am on launch night, that's the job.
We're building a brand-new mobile game in Tokyo!
A worldwide IP, live-service, the kind of thing millions of people end up with open on their phone on the train. I want someone to own the client side of it. Not a ticket-taker. An owner.
You'd be deep in the real work: the gameplay systems, the UI that has to feel right in the hand, the live config and remote content that let us change the game without shipping a new build, the client–server flows where things actually break.
You take a fuzzy "make this feel great" and turn it into something solid that ships!
Design, polish, release, telemetry, the messy post-launch iteration, all of it.
And when it breaks on exactly one Android model, in landscape, after the phone wakes from sleep... that's yours too! (You already know that bug. You've met it before.)
I have a specific person in mind. The kind whose teammates would describe as:
- the one who actually finishes things
- calm when production's on fire
- generous in code review, not precious about their own code
- fast to pick up a new system, codebase, or domain
- someone who raises the bar just by being on the team
What you'd bring:
* 8+ years building games
* 5+ of them in Unity and C#
* A few shipped titles (at least one of them a Unity game, preferably mobile!)
* You know the Unity lifecycle, Addressables, ScriptableObjects, serialization, and async C# the way you know your own hands: including every way they betray you.
* You've built data-driven, live-service systems before.
* You can run solo, but you're a real teammate to designers, artists, backend, QA, and production.
* Get things done attitude! (with humilty)
Bonus points:
* you speak Japanese
* you've shipped free-to-play
* you've made peace with CI/CD, and you hold a healthy respect for null, asset bundles, and the eternal mystery of why *this* is running before *that*.
This isn't a seat for someone coasting on a comfortable codebase. It's for someone who wants the hard, satisfying version of the job: real ownership, real impact, building something close to from scratch, and watching the world play it.
If that's you, complete every field in the application, even the ones that aren't required. That's how you stand out.
And if you already know there's more in you than your current team and codebase are pulling out, if you want people who'll push you to your real limit and put the wind at your back the whole way there, apply yesterday.
Otherwise, keep your seat in the audience and watch the rest of us build the thing everyone's talking about.
