Forward Deployed Creative Technologist, Video

Adobe•Waltham, NY

1d•Hybrid

About The Position

Every global brand is now a video content factory — hundreds of cutdowns, reframes, and localized variants a quarter, shipped in days not weeks. We embed with enterprise customers, learn their video supply chain end-to-end, and build the custom AI-powered workflows that get them there — on Adobe Firefly Services video APIs, Firefly Creative Production (our node-based workflow builder), and the After Effects / Premiere / MOGRT craft that lives beyond the API surface. Here's what most people miss: by the time you arrive, the deal is signed — but the editors, motion designers, and post-production leads who have to use what we sold never signed up for it. They have pipelines they already trust, and nobody asked them. You can't mandate adoption — you earn it: find the team with a real pain, build something so clearly better they reach for it on their own, and make it the way they cut. 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.

Requirements

You earn adoption against resistance. You've won over the editor 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, Azure Functions, AWS Lambda), Premiere / AE panels (CEP/UXP), custom nodes, integrations — a working URL the customer uses this quarter.
Deep video production-pipeline craft. After Effects + Premiere Pro + MOGRT authoring — you've built templates, written AE scripts, worked DGR pipelines, and can crack open a customer's .aep and find the problem.
You know how footage becomes cuts, how aspect ratios get reframed, how brand kits drive lower thirds, how QC and delivery work.
You speak the language of editors and colorists.
Creative content supply-chain craft. Briefs to assets, brand systems and design tokens, masters to channel variants, the Premiere / AE / Frame.io → MAM → review-and-approval handoff.
A skeptical post-production lead trusts you in the first meeting.
A public portfolio (link or PDF at application) — shipped video creative and technical work. Hard requirement; no portfolio, no review.
5–10 years straddling video production and technical building.

Nice To Haves

Firefly Services, Firefly Creative Production, and Adobe Brand Intelligence fluency — or proof you ramp a new API surface in days.
Adobe ecosystem (Frame.io, AEM, Workfront, App Builder) and ExtendScript / UXP / CEP panel development 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 (Runway, Topaz, Captions.ai, n8n, LangGraph, MCPs) to stay sharp.
High EQ, low ego.
Travel 10–20%.

Responsibilities

Find the real users and the use cases that stick. The signed deal tells you what the buyer agreed to buy — not which editors will actually use it, or which cutdown / reframe / localization use cases earn repeat usage. That's yours to discover.
Land an undeniable first win, fast. Compose Firefly Services video APIs (cutdown, semantic-lock reframe, Dynamic Graphics Rendering, dubbing, lip sync, T2V), Workflow Builder nodes, and AE / MOGRT templates into something that runs — ship ugly first, and meet editors inside the tools they already live in (a Premiere panel, Frame.io, their MAM), not a new destination.
Drive it to repeat, at-scale use. You don't convert a post house or a 50-editor team one timeline at a time — you run the workshop, the live build, the training that makes them want to switch. Then integrate with their stack (Frame.io, MAM, Premiere CEP/UXP panels, Workfront, delivery pipeline), 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. Crack open the customer's .aep and fix what's broken; build the workaround when the API 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 cuts, not slides.