Lead Forward Deployed Creative Technologist

Adobe Adobe · Enterprise · San Jose, CA +1

This role involves embedding with enterprise customers to understand their content supply chains and craft custom AI-powered creative workflows using Adobe Firefly Services and Workflow Builder. The technologist will build front-ends, back-ends, and custom workflow nodes, integrate with customer systems, and train teams to deliver tangible business outcomes like time saved and campaigns shipped.

What you'd actually do

  1. 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.
  2. 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.
  3. 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.
  4. Build custom workflow nodes when existing ones fall short. Push reusable ones upstream.
  5. 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.

Skills

Required

  • 5–10 years straddling creative production AND technical building
  • Creative content supply chain fluency
  • Firefly Services + Workflow Builder fluency (or ability to ramp quickly)
  • Vibe-coding with judgment
  • Extreme ownership and a GSD attitude
  • Extreme customer orientation
  • A great nose for the money
  • A passion for coding and tinkering
  • A public portfolio showing shipped creative work AND shipped technical artifacts

Nice to have

  • Adobe ecosystem depth (AEM, Workfront, Frame.io, App Builder)
  • Figma plugin / API fluency
  • Exploration of adjacent orchestration tools (ComfyUI, n8n, Zapier, Power Automate, LangGraph, LangChain)

What the JD emphasized

  • This is a hard requirement; applications without a portfolio will not be reviewed.
  • ship reusable ones upstream
  • ship a working URL the customer uses this quarter, not a PowerPoint
  • ship both: real creative work (motion, design, video, 3D, photography, brand systems) AND real technical work (apps, integrations, plugins, automation)
  • ship ugly first and refuse to let process slow you down
  • ship fast

Other signals

  • customer value
  • shipping working solutions
  • integrating with existing stacks
  • enterprise customers