Senior Full-Stack UI Engineer; remote​/onsite

Role Description

We are focused on creating a state-of-the-art, real-time, soft‑body physics engine and making it widely available for entertainment and simulation purposes. Our most widely known product is our game BeamNG.drive, which is now available on Steam in Early Access.

We are in the process of enhancing and modernizing our in‑game user interface. This interface utilizes web technologies within the game, all while adhering to game‑like limitations, including real‑time data handling, stringent responsiveness standards, enduring session durations, and diverse input/navigation methods beyond just mouse and keyboard.

• Frontend:
  Vue 3 SFCs using Composition API, JavaScript, SCSS
• UI "backend":
  Lua extensions are the source of truth. UI should mostly render and forward user intent
• Realtime data: discrete events + high‑frequency data streams (telemetry) for frequent/authoritative updates
• Input & navigation: scoped navigation and gamepad/keyboard‑first UI, backed by engine input bindings (Action Maps)
• Bridge layer: a JS↔engine bridge used for calling Lua, receiving hooks/events, and managing stream subscriptions

• Build UI features end‑to‑end: implement Vue UI, define clean UI↔Lua contracts, and collaborate with Lua specialists (you can handle basic Lua glue when needed)
• Make UI fast and stable: profile and optimize rendering/layout/update frequency to reach a 60 FPS feel where it matters, and keep long‑running sessions leak‑free
• Keep business logic in Lua: keep Vue focused on presentation and simple UI state; avoid moving backend logic/data conversions into JS
• Work with real‑time data: design UI that stays responsive while receiving frequent updates from the game/simulation
• Own navigation/input correctness: integrate scoped navigation and UI event handling so screens behave correctly with gamepad/keyboard and don’t leak inputs to parent scopes
• Improve developer experience: small, practical improvements to tooling/pipelines, debugging helpers, and performance instrumentation
• Support the team: review code, help juniors grow, and keep quality high without over‑engineering

• You’ll pick up a meaningful migration area and ship improvements incrementally (not a big‑bang rewrite)
• You’ll spend time profiling and fixing real UI performance/stability problems (we care about 60 FPS feel and long‑session reliability)
• You’ll learn the bridge, data flow, and navigation/input patterns, and start owning a feature area while still helping across the UI when needed

• Deep web fundamentals: strong understanding of browser rendering (layout/paint/compositing), the JS runtime (event loop, GC), and how to diagnose performance issues with real tools (performance + memory profiling)
• Proven performance experience: you’ve shipped UI where performance mattered (large UI surface, frequent updates, long‑running sessions) and can explain the trade‑offs you made
• Strong JavaScript: pragmatic, readable code; understands costs of allocations, reactive churn, and excessive DOM work
• Vue 3 expertise:
  Composition API, component architecture, reactive patterns, and debugging reactivity/performance issues
• Lua (basics): you’re not scared of Lua and can collaborate effectively with Lua specialists; you’re willing to learn the basics and follow Lua‑first architecture
• Small‑team mindset: reliable follow‑through, comfortable with both "interesting problems" and routine work
• Platform awareness: you can think about performance and reliability across targets from high‑end PCs down to Steam Deck
• Excellent communication skills in English, able to convey complex information in a clear and suitable manner to a diverse audience

• Deep web fundamentals: strong understanding of browser rendering (layout/paint/compositing), the JS runtime (event loop, GC), and how to diagnose performance issues with real tools (performance + memory profiling)
• Proven performance experience: you’ve shipped UI where performance mattered (large UI surface, frequent updates, long‑running sessions) and can explain the trade‑offs you made
• Strong JavaScript: pragmatic, readable code; understands costs of…