Senior C++ Reverse Engineer

Own our game engine SDKs — Unreal and Unity specifically. You’ll be working on the interface between our mod engineers and the underlying game engine. This entails owning keeping that system working as engines change version to version, extending it to new capabilities, and being the person who diagnoses it when a game update or a new engine release breaks something underneath.

Go deep when the framework meets the metal. When the SDK needs to find something new in an engine, or a title behaves in a way nothing else explains, you're comfortable dropping down to the disassembly, working out what the engine is really doing, and turning that into something the framework can rely on. You maintain the machinery that lets mod engineers ship — you're not shipping the individual mods yourself.

Own the hooking and cross-DLL machinery. Vtable, pointer-slot, and inline hooks across the object lifecycle, and the system that lets multiple mods operate inside one game process without stepping on each other.

Make the architectural decisions that compound. Balance accuracy against latency, safety against performance, surface area against maintainability — and communicate the reasoning so the rest of the team can hold the line later.

Design SDK, scripting, and reflection surfaces other people actually want to build against. Clean lifecycles, sane versioning, defensive boundaries that fail predictably. What you ship here is consumed by the engineers building mods and tools on top of it — a set that only widens as that work gets easier to build with LLMs.

Treat the teams building on the engine layer as your customers. We have internal mod engineers that are using the SDK and you’ll be interacting with them directly to address issues and improve the product. This is an internal team today but this will likely expand to a broader audience as we grow as a platform and you’ll be helping us manage that growth.

Write the docs, examples, and small tools that make the tool chain and SDK self-service. This is even more important given that LLMs might increasingly be the author of these mods and tools.

Provide substantive, thoughtful code reviews. Catch the race condition, the lifetime bug, and the brittle assumption that'll silently break the next time a game or engine updates — before it reaches a player.

Mentor the engineers around you through the parts of Windows and engine internals that aren't on Stack Overflow or answered by Claude. Teach the why, not just the fix.

Contribute to roadmap decisions with an eye on outcomes. What's worth refactoring, deprecating, or shipping fast and rewriting later? What end user outcomes does our reverse engineering work enable? Bring thoughtfulness and genuine passion for the work.

A non-traditional path into this work — security research, vulnerability analysis, CTFs, or time spent taking things apart for the fun of it.

You've built tooling that reconstructs a program's types or structure from the outside — an SDK generator, a runtime reflection system, or similar.

You've embedded a scripting engine (Lua/LuaJIT, AngelScript, a custom VM) and exposed a constrained, safe surface of native systems to other authors.

Code generation or compiler tooling — emitting compilable code from metadata, or writing a compiler / protoc plugin.

Comfortable working full stack — TypeScript in an Electron desktop app all the way down into C++ and back is an expectation on a number of projects.

IPC and wire-protocol design: FlatBuffers, Protocol Buffers, gRPC, named-pipe framing, streaming.

Rust, and FFI / interop between it and C++.

CMake and vcpkg fluency on a non-trivial multi-project build; GitHub Actions CI.

Unicode / encoding-correct native code — you don't assume ASCII (non-ASCII Windows user profiles are a first-class case, not an afterthought).