Photoshop Developer, GPU/Imaging
Posted yesterday
adobe systemsBrooklyn (NY)
Software DevelopersSoftware Publishers
SENIORITY
Senior
About the role
Overview
In this role you will design, build, and optimize GPU-based imaging and rendering features for Adobe's Next Gen Engine (NGE) and Photoshop Desktop. You will work on live, non-destructive on-canvas filters, color pipelines, and real-time image processing, collaborating with cross-functional teams to push performance and visual quality. This is a ground-up rebuild offering scope to shape core rendering technology at scale. You will write high-quality, well-documented code and contribute to design reviews and documentation.
Compensation / Benefitscomprehensive benefits programsculture that supports growth and leadershipdiverse and collaborative team environment
Responsibilities Design, build, and optimize GPU-based imaging and rendering features using C++, WebGPU, and WGSLWrite and tune GPU shaders and compute kernels for real-time image processing Profile and optimize rendering performance across GPUs and hardware Extend the engine's compositing and color pipeline (blending, color spaces, precision)Write automated tests for rendering and imaging code Use AI tools to speed up development, debugging, and testing Make architectural calls when specs are open-ended Write clear, self-documenting code and contribute to engineering docs and reviews
Key requirements Bachelor's or Master's degree in Computer Science or equivalent experience Solid grounding in graphics and GPU programming fundamentals (pipelines, shaders, memory, performance tradeoffs)Familiarity with GPU hardware architecture across vendors (integrated vs. discrete)Experience with graphics APIs (Metal, DirectX, Vulkan, or WebGPU)Experience with modern C++ (production-quality, asynchronous)Strong analytical and debugging skills Clear communication and ability to distill complex tradeoffs for diverse audiences Adaptability when plans shiftGPU programming fundamentals Shaders and compute kernelsGPU hardware architectures (integrated vs discrete)
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
More like this
