Build and ship gameplay systems in Luau — core mechanics, UI, effects, and live content — and obsess over how they feel in players’ hands.
- Build and ship gameplay systems in Luau — core mechanics, UI, effects, and live content — written tidily enough that the next person can extend it without archaeology.
- Take features the whole way. You’ll scope the idea, build it, sweat the polish, test it hard, and push it live to a large player base.
- Obsess over feel. Controls that respond, feedback that lands, flows that make sense without a tutorial — getting this right is most of the job.
- Range widely. One week you’re deep in a movement system, the next you’re wiring particles or laying out a shop screen. We’d rather you be curious across areas than boxed into one.
- Shape the games, not just build them. Pitch mechanics, poke holes in designs, and push ideas in reviews. Engineering opinions carry real weight here.
- Work shoulder to shoulder with design, art, production, and QA. Most of the job is communication — do it plainly and kindly, on calls and in writing.
- Move quickly from idea to playable. Rough something in, put it in front of people, and let feedback and player data tell you what to keep.
- Size the work honestly with production, name the risks up front, and surface blockers before they bite.
- Hold the bar. Review other people’s code, write things down, kill bugs, and tidy as you go. Nothing ships untested or unprofiled.
- Back your teammates. Pair on the hard bugs, pass on what you know, and protect the studio’s habit of careful work without ego.
None of these are hard requirements — strong candidates tend to have most of them. If a couple are missing but you make up for it elsewhere, apply anyway.
- A year or more building games, whether in a job, a serious solo project, or some mix of the two.
- Hands-on Luau / Roblox work, or comparable game-dev experience with things like controllers, cameras, animation, or effects.
- Something you’ve shipped, or a portfolio that shows how you make a game feel — be clear about which parts were yours.
- An instinct for when something’s off, and the stubbornness to keep tuning until it isn’t.
- The ability to drop into a big, unfamiliar codebase and start building without hand-holding.
- Comfort moving between code, effects, and interface work rather than staying in one lane.
- Self-direction — you unblock yourself quickly and are happy owning outcomes.
- Clear communication in English, written and spoken.
- You actually play games, and you care about making them.
Not needed to apply — but any of these will strengthen your case.
- Something you designed and shipped yourself: a Roblox place, an indie build, or a game-jam entry.
- Even better if you’ve kept a live Roblox experience running and updated over time.
- A genuine read on what Roblox players want and how the community ticks.
- A working sense of client/server trust boundaries and keeping multiplayer honest.
- Comfort with REST APIs and component-driven Roblox UI (React-Lua and the like).
- Time spent in remote, self-managing teams.
- Extra strings to your bow such as UI/UX, design, art, audio, VFX, or modelling.