A guide to hiring a DirectX developer
DirectX is a set of Microsoft tools that programs use to talk to the graphics card on Windows. The most familiar part is Direct3D, which draws 2D and 3D pictures. Other parts handle sound, controller input and work that runs on the graphics card. A DirectX developer is a programmer who writes this kind of code. If your software must draw quickly, draw exactly right, or draw something an engine does not give you, ask for DirectX experience by name.
What the job covers day to day
The core of the work is getting pictures on screen and then making them quick and right. That means building the code that sends work to the card, writing small programs called shaders, and tracking down why one frame took longer than the rest. Around that sit regular tasks such as code review, bug fixes and keeping the project working on different graphics cards and drivers.
DirectX beside a game developer
A game developer and a DirectX developer are not the same job. Our game developers build the whole game, from its design to the many systems that tie it together. A DirectX developer works on one layer, the code that draws. Studios that use an engine may never touch it, while studios with their own engine often need a specialist. If your game is headed for consoles, our Xbox developers handle the platform side, and a DirectX developer can work next to them on the graphics code.
Direct3D and the graphics pipeline
Drawing a frame is a chain of steps. Your code describes the objects, the card transforms them, turns them into pixels and sends the result to the screen. Newer versions of Direct3D give programmers more control over each step, and with that comes more to get wrong. A strong developer knows what the card is doing at every stage and can explain it simply. Ask a candidate to describe, in their own words, how one frame is made.
Shaders and HLSL
Shaders are small programs that run on the graphics card. They decide the color of every pixel and the position of every point. DirectX shaders are written in HLSL, a language that looks a little like C. Good shader work is not only about nice effects. It is also about cost, because a clever effect that makes the game stutter helps nobody. Ask for examples of shaders the person wrote and how they checked the cost.
Working with the graphics card
The card has its own memory and works at its own pace. The processor and the card must stay in step, or the program will crash, flicker or wait for no reason. Developers manage buffers and textures, decide when the card can reuse them and use fences to keep the order right. These parts are easy to get almost right, and the faults appear only on some machines. Careful habits matter more here than clever tricks.
Finding and fixing problems
Graphics bugs rarely show up in a log. A good developer reaches for capture tools that record a frame and show every step. PIX is a tool from Microsoft made for this, and RenderDoc is a popular tool from outside Microsoft. Visual Studio also has graphics tools. Ask a candidate about a bug they found with one of them, and how they knew the fix worked.
Beyond games
Many people link DirectX with games, but plenty of other software draws on the graphics card. Design and engineering tools, medical and scientific viewers, simulations, data dashboards and video editors all use it. In these products the picture must also be exact, not only pretty. If your team builds a Windows desktop product, see our C++ developers for the wider systems skills. For 3D that runs in a web page, our three.js developers are a better match.
Older projects and upgrades
Many Windows programs still draw with older versions of Direct3D. They work, but they get harder to support as hardware and drivers change. A developer can move the project to a newer version in steps, keeping the old path alive while the new one is tested beside it. Comparing the pictures from both paths on several graphics cards is the safest way to find differences.
When a DirectX developer is a good fit
- You are building your own renderer or engine and need someone who knows the graphics layer.
- Frames are slow or uneven and the team cannot say why.
- A visual bug appears on some graphics cards but not on others.
- Your Windows product shows 3D models, images or video and the picture must be exact.
- An older Direct3D project needs to move to a newer version.
Common hiring mistakes
- Hiring a general programmer for rendering work and expecting the speed to follow.
- Judging by pictures of nice scenes without asking which code the person wrote.
- Skipping tests on different graphics cards until the week before release.
- Asking for a graphics specialist when the real problem is in the game logic.
Related help: if the project runs on a ready-made engine, where the graphics interface is already handled, see our Unity developers or our Unreal Engine developers.















