Graphics Engineer Resume
Skills & ATS Keywords

Plan for 20 to 34 specific tokens across 6 to 8 labeled rows. Below 18 the file reads thin past Junior; above 40 it reads padded to a rendering lead. Every token should resurface in a shipped-rendering bullet, a frame capture you can talk to, or a pass you authored. If you cannot point at it inside a build, take it off.

HLSL / GLSL / MSL, a primary graphics API (DirectX 12, Vulkan, Metal), the rendering pipeline class you ship (forward+, clustered, deferred, tiled), PBR plus a real-time GI flavor (Lumen, RTGI, light propagation volumes, Enlighten), one upscaler (TAA, DLSS, FSR, XeSS), and a console-target profiler (PIX, RGP, Razor, Nsight Graphics) are the locked must-haves. Render graph, descriptor management, shader permutation pipelines, volumetric fog, virtual textures, and GPU-driven culling round out the supporting band. DXR / Vulkan RT, Slang, Nanite, mesh shaders, and tile-based deferred on mobile separate the senior pile at AAA rendering shops.

Lead with the pair: the API you ship against and the shader language you author in. DirectX 12 plus HLSL reads natural on Xbox / Windows shops, Vulkan plus GLSL or Slang on cross-platform AAA, Metal plus MSL on Apple-platform work, OpenGL ES plus GLSL or Vulkan plus SPIR-V on mobile-first studios. A rendering lead wants the stack you authored real passes in, not a catalogue of every shader language you have ever opened. If you ship across two APIs through a unified backend, say so and name both, but keep the primary first.

Directly under the Profile Summary, on top of Work Experience. Rendering leads scan the first screen in roughly seven seconds and the parser generation studios run rewards keyword position over keyword frequency. An HLSL token, a DXR reference, or a PIX capture string sitting in the Profile Summary or the top Skills row ranks higher than the same token tucked into the education section. Hold the block to 6 to 8 labeled rows, then back every row with a shipped-rendering bullet that names the pass, the platform, and the GPU figure.

Graphics Engineer authors the renderer: pipeline class, shaders, lighting, post-processing, upscalers, GPU-driven culling, ray tracing, and the artist-facing debug viz that lighting and material artists rely on. Engine Programmer owns the runtime everything else hangs off: ECS, allocators, the job system, the RHI, asset streaming, platform abstraction. Technical Artist sits between Art and Engineering on look-dev shaders, content pipelines, and material graphs. If your week is in HLSL passes, render-graph nodes, RenderDoc and PIX captures, and PBR balance walks with the lighting lead, this is your page.

Pull six rendering-team postings inside the studio class and platform mix you want next (AAA console rendering team, mobile-first graphics R&D, simulation / training rendering pipeline, VR / XR runtime, in-house renderer at a publisher-owned studio). Underline every pipeline class, shader language, API, lighting model, upscaler, and profiler that recurs in three or more of them. The recurring set is the spine your file has to carry. Reconcile against your Skills rows and your shipped-rendering bullets, fix the honest gaps, then push it through an ATS Checker before you submit.

Yes, NDA permitting. A Graphics Engineer resume that names the renderer class (deferred-cluster, forward+, visibility buffer, hybrid raster + RT, mobile tile-based deferred), the title that shipped on it, the platform, and one GPU-ms or memory figure reads as senior in one paragraph. A file that lists HLSL, Vulkan, PBR, and post-FX with no renderer and no figure reads as a hobby file. Where the title is under NDA, describe the renderer class, the platform target, the GPU vendor (AMD RDNA, NVIDIA Ada, Apple GPU, Adreno / Mali) and the pillar you owned.