Job description
🎯 What you’ll do
You will:
write and review production code,
design and evolve game systems,
debug real production issues,
and set the technical standard for the team.
You’ll own the technical side of the product lifecycle: idea → implementation → QA → release → live ops. You’ll work daily with Product, QA, Art, Animation, and Platform - through collaboration, not handoffs.
You’ll help the team ship with:
clearer scope,
fewer surprises,
better technical decisions.
🔧 How hands-on is this? Very.
You will:
code regularly,
review PRs and architecture decisions,
jump into debugging when things break,
pair with engineers to unblock and teach by example.
You will not:
become a delivery coordinator,
manage people full-time,
or disappear into meetings.
🧠 What you need to bring
Must-have
Strong hands-on engineering background.
Experience building and shipping production systems.
Comfort owning technical decisions end to end.
Experience working with real users, releases, and production incidents.
➕ Strong plus (not required)
Experience in iGaming / games / real-time or high-frequency products.
Live Ops experience or work on always-on systems.
Parallel development and frequent releases.
Working in regulated or high-risk production environments.
🧰 Tech you’ll work with
Node.js (TypeScript / JavaScript)
Pixi.js / Phaser.js
Spine
Performance-sensitive systems and live environments
🔁 How we work
Ship fast, then improve.
Fix problems early.
Prefer simple solutions over clever ones.
Fewer meetings, more real work.
Direct, respectful communication.
🔥 What we offer
Fully remote (Europe-friendly)
Unlimited vacation + paid sick leave
Quarterly performance bonuses
Learning budget (courses, conferences)
Real technical ownership
No micromanagement
👉 This is not the role if…
You’re done with hands-on engineering.
You want a pure management role.
You prefer coordination over problem-solving.
You avoid production responsibility.
👉 This is the role if…
You’re a mature engineer who still loves building things, wants more technical influence, and is ready to lead by example while staying close to the code. If that sounds like you - let’s talk!
