Get a reply from this employer
Your resume and cover letter, tailored to exactly what they’re hiring for.
InPvP is seeking a Minecraft Client Engineer focused on Java performance and modding. You will work on the Dawn client, maintaining 100+ modules, hooks, and JVM-side performance optimizations while collaborating across feature modules, mixins, and rendering backends.
The role emphasizes low-level engineering, with opportunities to contribute to Vulkan/OpenGL backends and profiling, aiming to deliver a fast, stable client in a rapidly moving project environment.
Ship Dawn's 100+ in-game modules, mixins, and JVM-side performance work. Performance role first.
We're hiring multiple people for this. This one is for people coming from Java and Minecraft modding. If you come from low-level graphics or C++ engine work, read the Graphics Engineer listing instead.
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.
This track is broad. Depending on what you're good at and what's currently on fire, you might work on any of:
You're a strong low-level engineer who is deep in at least one of two areas: low-level graphics, or JVM internals plus Minecraft modding. Be strong in one and willing to get deep in the other. What we actually care about is that you debug by understanding what's happening, not by trying things until the error goes away.
This is a performance role first. A Minecraft client spends its whole frame budget in a few milliseconds, and most of what eats it is on the JVM side: allocation churn, boxing, oversized object graphs, cache-unfriendly data, and call sites the JIT can't inline. If you enjoy driving that number down and proving you did, this is the job.
Graphics is a plus here, not a requirement. If you've got Vulkan or OpenGL experience too, great, and there's plenty of rendering work to pick up if you want it. But you can do this job well and never touch a shader.
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.
26 versions and multiple mod loaders is a lot of surface area, and a fix in one version is sometimes a new bug in three others. You'll still meet AMD driver bugs, NVIDIA quirks that only show up on Linux, and macOS doing its own thing entirely. Validation layers will confidently lie to you. We support Vulkan because Mojang added it in 26.2, and a graphics backend that new comes with plenty of its own surprises. And every so often there's no documentation at all and you reverse-engineer behavior until it makes sense. If that sounds miserable, this isn't the job. If it sounds a little bit fun, apply.