The Opportunity

Every global brand is now a content factory — thousands of on-brand variations a quarter across static, video, and 3D, shipped in days not weeks. We embed with enterprise customers, learn their content supply chain end-to-end, and build the custom AI-powered workflows that get them there — on Adobe Firefly Services, Firefly Creative Production (our node-based workflow builder), and Adobe Brand Intelligence (ABI) for brand validation and compliance.

Here's what most people miss: by the time you arrive, the deal is signed — but the people who have to use what we sold never signed up for it. They're creatives and marketers with tools they already like, and nobody asked them. You can't mandate adoption — you earn it: find the users with a real pain, build something so clearly better they reach for it on their own, and make it the way their team works. Usage that repeats at scale is the only proof that counts — and it's what makes an enterprise customer renew.

We are not pre-sales. We are not consultants. We are technical creators who ship — and who get used.

What you'll do

• Find the real users and the use cases that stick. The signed deal tells you what the buyer agreed to buy — not who'll actually use it, or which use cases earn repeat usage. That's yours to discover.
• Land an undeniable first win, fast. Compose Firefly Services APIs, Workflow Builder nodes, and ABI checks into something that runs — ship ugly first, and meet users inside the tools they already live in (a Figma plugin, a Premiere panel, their DAM), not a new destination.
• Drive it to repeat, at-scale use. You don't convert a 200-person creative org one desk at a time — you run the workshop, the live build, the training that makes them want to switch. Then integrate with their stack (AEM, Workfront, Frame.io, brand portal), own the edge cases, and hand off so they self-serve.
• Clear the blockers, wherever they are. Diagnose what's really stopping adoption — a product gap, a missing integration, a blocking dependency. Build the workaround when the product can't do it yet; take the real gaps upstream and influence the roadmap or commit the fix yourself; chase a cross-team dependency until it moves. You don't file a ticket and wait.
• Make the next engagement faster. Reusable patterns become shared templates and upstream Workflow Builder nodes. Every win compounds.
• Demo your own work — script, produce, edit. Real outcomes, not slides.

What you'll bring

The bar — what we filter hardest for:

• You earn adoption against resistance. You've won over the user who didn't want your tool (they had their own), found another way in when a stakeholder went dark, and turned a roomful of skeptics into users through the workshop or live build. You measure yourself in adoption and renewals, not features shipped.
• You build it yourself. Thin front-ends, light back-ends (App Builder, Lambda/Functions), custom nodes, integrations — a working URL the customer uses this quarter.

The floor — we don't teach this:

• Creative content supply-chain craft. Briefs to assets, brand systems and design tokens, masters to channel variants, the Figma / PSD / INDD → DAM → review-and-approval handoff. A skeptical creative director trusts you in the first meeting.
• A public portfolio (link or PDF at application) — shipped creative and technical work. Hard requirement; no portfolio, no review.

Force multipliers — real, but teachable:

• Firefly Services, Firefly Creative Production, and Adobe Brand Intelligence fluency — or proof you ramp a new API surface in days. Adobe ecosystem (AEM, Workfront, Frame.io, App Builder) and Figma plugin/API/MCP depth are pluses.
• AI-native building with judgment. Cursor / Claude Code / Copilot daily — fast, but you catch when the output is wrong. You explore the frontier (ComfyUI, n8n, LangGraph, MCPs) to stay sharp.

High EQ, low ego. 5–10 years straddling creative production and technical building. Travel 10–20%.

What we're not looking for

• The order-taker. You shipped the deliverable, called it done, and treated whether anyone actually used it as someone else's problem.
• Backend-only engineers with no creative-practitioner background.
• Pure designers or creatives who can't stand up a working integration.
• ML / AI researchers chasing frontier-model R&D over customer outcomes.
• "I'll build my portfolio later." Not ready at application? Come back when it is.