Full Stack Software Engineer (L5) – Game Developer Tools

Job Description

6+ years of full stack development experience building and operating production systems. Modern frontend experience, ideally with React and TypeScript. Backend experience with at least one of: JavaScript/TypeScript (Node.

js), Java, Python, plus familiarity with GraphQL or similar API technologies. End‑to‑end ownership of features: data models and persistence, API/service design, UI implementation, and instrumentation (metrics, logs, traces). Developer‑facing tooling experience (e. g.

, developer portals, dashboards, configuration consoles, debugging tools, or editors). UX iteration with technical users: gathering feedback from developers, shipping improvements, and measuring impact.

API design and integration experience, including clean, versioned APIs used by web UIs, CLIs, game engines, or services. Operationally thoughtful running live tools/services: observability, production debugging, and attention to stability, usability, and backwards compatibility. Developer insights & performance tooling: building or integrating UIs for metrics/logs/traces and making complex technical data actionable for engineers.

Game engine & runtime awareness: familiarity with Unity and/or Unreal (editor extensions, in‑engine tools, plugins, build/content pipelines, runtime instrumentation) and how content flows from engine → build → runtime. Desktop app experience: building and shipping Electron (or similar) apps, including auto‑update, packaging, offline behavior, and OS integration. Multi‑tenant / multi‑title systems: exposure to auth, authorization, and isolation across multiple games, titles, or tenants.

External/partner‑facing tools: experience building tools used beyond a single internal team. Interest or experience in games: gaming industry, game dev tooling, or game production workflows.

Developer‑focused with a product mindset: You treat game developers as customers, care about responsiveness, clear flows, helpful errors, and strong docs/onboarding, and you actively seek feedback to improve the experience. An end‑to‑end owner: You can take a feature from vague idea to design, implementation, rollout, and long‑term support, doing whatever is needed (backend, UX polish, migrations, documentation) and balancing quick wins with longer‑term platform investments. Operationally thoughtful: You understand that widely used tools need high stability, good UX, and careful versioning/backwards compatibility, and you design for observability and diagnostics to make triaging and debugging issues easier.

Independent and highly collaborative: You’re comfortable with ambiguity, communicate clearly with technical and non‑technical partners, and work closely with production, game developers, PM/TPM, design, and other engineers to identify and solve meaningful pain points.

EWJD3