Comcast reportedly has more than twenty Creative Technologists on staff, per Adobe's report. JPMorgan Chase is hiring them, according to the same report. So are Coca-Cola, Apple, and Microsoft. The average one earns $104,131 a year, per Glassdoor's 2026 figures, with the top end pushing $142,189.
And almost nobody can tell you what the job is.
The role has reportedly gone by many names — UX engineer, design technologist, creative developer, UX prototyper, design engineer — and even the people who hold the title admit it "still sounds entirely made up." Ask them to define it with specificity and, in the words of one practitioner who nearly took a Principal AI Technologist role at Adobe, most simply can't.
The reflexive move here is to disambiguate. Every explainer on this role opens by promising to finally pin it down. I want to do the opposite, because the confusion isn't a gap in the coverage. It's the finding.
As AI collapses the distance between idea and implementation, who actually gets staffed on the rare, high-leverage assignments? The anxiety was real but abstract. This week the answer has a name, a salary band, and a list of enterprises writing the checks.
The name is Creative Technologist. And the reason nobody can define it is that companies aren't hiring for a skill set. They're hiring for an outcome.
The reason nobody can define it is that companies aren't hiring for a skill set. They're hiring for an outcome.
Look at what the job descriptions actually ask for, and the fog lifts into a pattern. Per Adobe's report on the role, the most rigorous postings ask candidates to own work from concept through delivery — selecting the tools and platforms, deploying generative AI and agents and automation where useful.
And the single most crucial requirement: the ability to decide when AI improves an outcome versus when another approach is more appropriate.
Read that again as a hiring instruction rather than a job spec. It names no stack. It lists no years of experience in a named tool. It names a scope — concept to delivery — and a judgment: knowing when the fast path is the wrong path.
That's not a job description. It's a rubric. A job description enumerates competencies; a rubric describes the shape of a person who can be trusted with an ambiguous mandate and produce a shipped thing at the end.
This is why the taxonomy is a mess, and why the mess is the signal. You cannot standardize the title because the title isn't tracking a discipline. It's tracking ownership.
The Adobe framing makes the mechanism explicit. Enterprises kept buying AI tools expecting ROI and kept discovering the bottleneck wasn't the model — it was that "design files built for human flexibility don't easily translate to automation needs," and brand guidelines "live in static PDFs instead of codified systems."
Someone has to sit between the creative intent and the automated system and translate one into the other. Adobe quotes a Senior Art Director at a potato chip brand who asked for ads that felt "light and airy, like a potato chip," and the challenge of turning that subjective ask into something that renders reliably at scale.
That translation work is not a specialism. It's the whole span. And the roughly 60% agency / 40% enterprise split in the job postings tells you it's happening inside the companies, not just being contracted out to studios.
Now stack the