Lead Forward Deployed Creative Technologist

Adobe•San Jose, CA

9d•$159,200 - $301,600•Hybrid

About The Position

Every global brand is now a content factory. They need thousands of on-brand asset variations every quarter — static, video, and increasingly 3D — and they need to ship them in days, not weeks. The customer who figures this out first wins the next decade of marketing. We are the team that gets them there. We embed with enterprise customers, learn their content supply chain end-to-end, and craft custom AI-powered creative workflows on top of Adobe Firefly Services and Firefly Creative Production (our node-based workflow builder). We are not pre-sales engineers. We are not consultants. We are technical creators who ship. You will own the bridge between what the customer's CMO sketched on a whiteboard and what their creative team actually uses on Monday morning. Then you'll bring what you learned back so the next FDCT moves faster. This role is for someone who is maniacally focused on customer value. If the customer cannot point to time saved, dollars earned, or campaigns shipped because of your work, nothing else matters.

Requirements

5–10 years straddling creative production AND technical building. You have shipped both: real creative work (motion, design, video, 3D, photography, brand systems) AND real technical work (apps, integrations, plugins, automation).
Creative content supply chain fluency. You understand how briefs become assets, how brand systems and design tokens work, how master files become channel variants, how creative teams hand off through Figma / PSD / INDD to DAM and review-and-approval. This is the skill we cannot teach and the one we filter hardest for.
Firefly Services + Workflow Builder fluency — or evidence you ramp on a new API surface in days, not months.
Adobe ecosystem depth (AEM, Workfront, Frame.io, App Builder) is a strong plus, as is Figma plugin / API fluency.
Vibe-coding with judgment. You use Cursor / Claude Code / Copilot daily and ship fast. You also know when AI output is wrong, when error handling is missing, when the prompt needs more context.
Production code, not prototype-only.
Extreme ownership and a GSD attitude. When the integration breaks before a CMO demo, you fix it — you don't escalate. You own outcomes end-to-end, from broken auth to a missed brand-compliance check.
You ship ugly first and refuse to let process slow you down.
Extreme customer orientation. You hold the room with CMOs, creative directors, and heads of IT. You hear a customer pain and respond with a credible, impact-focused, creative solution — not a science experiment.
You translate tech to ROI without losing the engineers in the room.
A great nose for the money. You instinctively connect what you build to business outcomes the customer's exec sponsor cares about — time-to-activation, cost per variant, brand-compliance pass rate, campaign velocity.
A passion for coding and tinkering.
A deep interest in generative AI and creative workflows.
You explore adjacent orchestration tools — ComfyUI for visual workflow prototyping, n8n / Zapier / Power Automate for low-code connectors, LangGraph / LangChain for agentic flows — because that's how you stay sharp.
A public portfolio — link or PDF at application. Must show shipped creative work AND shipped technical artifacts. This is a hard requirement; applications without a portfolio will not be reviewed.
High EQ, low ego.
Willingness to travel 10–20%.

Nice To Haves

Adobe ecosystem depth (AEM, Workfront, Frame.io, App Builder) is a strong plus, as is Figma plugin / API fluency.

Responsibilities

Embed with enterprise customers.
Learn their brand, their creative team, their content supply chain, and the metrics their CMO cares about.
Become a trusted advisor in 90 days.
Translate a customer brief into a working creative workflow.
Compose Firefly Services APIs (Firefly, Photoshop, InDesign, Illustrator, Express, Lightroom, Substance 3D, Audio/Video) and Workflow Builder nodes into something that actually runs.
Build Figma plugins or design-system integrations when the customer's creative team works there.
Build thin front-ends (or conversational experiences) and light back-ends (App Builder, Azure Functions, AWS Lambda).
Ship a working URL the customer uses this quarter, not a PowerPoint.
Build custom workflow nodes when existing ones fall short.
Push reusable ones upstream.
Integrate with the customer's stack — AEM Assets, Workfront, Frame.io, their DAM, their PIM, their brand portal.
Negotiate auth, debug API quirks, own the edge cases.
Train the customer's team.
Document.
Hand off cleanly so the customer self-serves when you rotate to the next engagement.
Demo your work yourself — script, produce, edit.
Show real creative outcomes, not abstract slides.
Feed the org. Reusable patterns become shared repo templates, workflow templates, or upstream WFB nodes.
Every engagement makes the next one faster.