A complete application in a minute
Tailored resume and cover letter, ready to send.
InPvP is seeking a senior graphics engineer to own the render hardware interface (RHI) and the render graph for Dawn's OpenGL and Vulkan backends supporting multiple Minecraft versions. You will optimize front-to-back rendering pipelines, work across 26 versions, and iterate on memory, shaders and performance in a large JVM-based project.
The role emphasizes deep C++ systems work, cross-backend integration, and profiling with tools like RenderDoc, Nsight, and Tracy.
Own the RHI and the render graph behind Dawn's OpenGL + Vulkan backends, across 26 Minecraft versions.
InPvP is one of the biggest companies in the Minecraft space, with four featured Bedrock servers, plus 2 more coming later this year, as well as other major unannounced projects and acquisitions coming by EoY. We deliver high quality experiences and value our partnership with Microsoft/Mojang.
We took over the Feather Client to do right by its community. Dawn, formerly Feather Client, is InPvP's cross-platform launcher + client built for PvP performance and strong modding features. It is the fastest growing Minecraft client in the space and is currently undergoing major rewrites and bug fixing from tech debt accumulated over the past year. We need a perfect product before we start marketing, so it's all hands on deck.
Dawn has 26 Minecraft versions, from 1.8.9 to the latest snapshots, on both Fabric and Forge, with a large active player base. Inside it there's a render graph running over a custom RHI. It was designed to support:
Both backends, OpenGL and Vulkan, are already implemented and rendering the game today. The work isn't to bring Vulkan to life; it's already there. The execution model is fairly new, so part of the work is bringing it down to older Minecraft versions that predate it, back to 1.17.1, across the point where Minecraft moved to core shaders. System should support both Forward-Z and Reverse-Z and switch at runtime.
Java is not required for this track, but if you also happen to be a performance-minded JVM engineer, that combination is rare and we want it badly. We render on a managed runtime, so the CPU side of the frame lives or dies on JVM behavior.
By performance-minded we mean someone who reads JIT compilation logs and knows how C2 inlines, when it bails to a megamorphic call site, and what on-stack replacement and deopt are doing to a hot loop; who watches escape analysis and scalar replacement decide whether an object ever reaches the heap; who tracks allocation rate against GC pauses (G1, ZGC, Shenandoah) and reaches for async-profiler or JFR before guessing. If that's you on top of the graphics background, you're exactly the unicorn we're hoping to find.
None of this is easy and I want to personally say this upfront: if you can't keep up with pressure and a fast-moving environment you will get cut. InPvP, across all of its projects, moves fast, ships fast, and has no tolerance for slacking.