Private link · An independent application page by Warren Velázquez · Not affiliated with Amazon

Application · Sr Program Manager, Elevated Content · éShop Content Services

Elevated is a standard.
Standards need someone to run them.

Warren Velázquez runs the operating layer under creative work: intake, coverage, capacity, cadence, reporting, and the calendar it all lands against. The gallery is his coverage across the content types this team produces. The rest of the page is the posting, line by line.

Now
UX Program Manager, Brand, Dow Jones. New York.
Cadence
About 8 events and 6 launches in five months, each a fixed-date go-live.
Coverage
6 of 8 core properties on one design system. Build time cut about 80 percent.
Seniority
13+ years owning how work moves, the last nine-plus at Senior and Director level.
Study
M.A., Digital Media Management. B.S., Advertising Communications.

The posting names four content types: photography, video, 3D and graphic design. He has direct receipts in three, plus motion, which sits between all four in practice. Photography is the honest one. On GE's Better Health Study he ran the asset-production phase that hundreds of media assets moved through, gated by one publishing pipeline. He ran the pipeline. He did not run the shoot.

Measurable target, monitored completion

The glidepath he is running now

Eight core event properties at Dow Jones were eight separate builds. He is consolidating them onto one design system, and the target is all eight. Here is where it stands, drawn against the target rather than against a story about the target.

Core event properties migrated onto the design system, against a target of eight.

The chart scrolls sideways on a narrow screen.

8

core properties in scope. The target is all of them.

6

migrated onto the single system so far.

2

outstanding, and drawn as outstanding.

The benchmark underneath it

Migration count is the progress measure. It is not the point. The benchmark is what a build costs once the system takes over, and that is the number the program is judged on.

Before, per property build

After the system took over

Build time cut about 80 percent, with cross-property inconsistencies eliminated as the second outcome. Both are stated the way the record states them, hedge included.

There are no dates on this chart and no month-by-month split, because the record does not carry them. A glidepath drawn with invented intermediate points would monitor a fiction. Count, target, remainder, measured outcome. That is what is actually known.

The posting, line by line

Sixteen lines, sixteen answers

Every line of the posting, the qualifications and the responsibilities, each with the receipt underneath it. 16 rows: 13 Strong, 3 Partial. The Partials are open when the page loads and say what is missing, because a chip without its reasoning is the one state this page should never render.

Qualifications

Rows 01 to 04 are the basic qualifications. Rows 05 to 10 are the preferred ones.

13+ years owning how work moves, the last nine-plus at Senior and Director level. Digital Producer at Beyond from 2013, then POSSIBLE, then Vertic, then two years at Huge inside Google's Android pod, then Director of Creative Operations at Everyrealm, and today the sole UX Program Manager driving the Brand function at Dow Jones.

The design system is the cleanest one. Eight separate event-site builds, consolidating into one, 6 of 8 core properties migrated, build time cut about 80 percent and cross-property inconsistencies eliminated.

Those numbers exist because he owns the instrument they come out of: the brand marketing team's Asana implementation for reporting, capacity and resource management. GE's Better Health Study shipped with supporting data analysis alongside the assets, not after them.

On GE's global Better Health Study he managed the asset-production phase: executive-level visualizations, a global website and hundreds of media assets, all moving through one gated publishing pipeline. One of GE's largest marketing campaigns.

At Vertic, a structured review cadence aligned skeptical energy-utility executives early, before the design phase had spent anything. At Huge he was the connective tissue between internal executives, Google product marketing managers and strategists, and the designers and engineers doing the work.

B.S., Advertising Communications. Plus an M.A. in Digital Media Management from Hyper Island (Sweden) and Teesside University (U.K.), 2014.

M.A., Digital Media Management, Hyper Island (Sweden) and Teesside University (U.K.), 2014. Graduate study in the management and operations side of digital production, which is the side he has worked ever since.

Three tools taken to launch-readiness on nights and weekends, built solo by directing AI agents. Relay is the one that runs inside the job: the AI intake he built at Dow Jones, receiving and triaging requests from six teams, subscription strategy, product design, product management, performance marketing, CRM and event marketing.

Self-taught in AI, agent orchestration, and the production foundations of building scalable AI products. His own phrase for the distinction is that this is not vibe-coding.

What is real. He built creative production from zero at Everyrealm: sourced and staffed a team of 3D artists, UI/UX, motion and visual designers, and introduced the production processes and methodologies that team ran on. Forecasting workforce needs is current practice, not history. Capacity at Dow Jones is computed rather than assumed, and he owns the reporting stack the forecast comes out of.

What is missing. He has not designed or run a formal upskilling or apprenticeship program, and he has not done workforce development at anything like Amazon's operational scale. Standing up a function and staffing it is a different discipline from building a curriculum that scales across an operation, and this row is not going to blur the two.

Six teams into one intake at Dow Jones. At Vertic, Arizona Public Service went from a 3-month UX research phase through an 8-month UX/UI design phase and into production with Infosys and 28+ engineers. At Huge: internal executives, Google PMMs and strategists, designers and engineers, against a fixed launch calendar with creative, content, site deployment and localization all on the line.

The line asks for a willingness to learn. He is well past willingness. He specifies the behavior, directs the agents, reviews what comes back and sends it round again, which is how three tools reached launch-readiness with one person on them.

The prompting is the easy half. The evaluation loop is what decides whether anything ships, and that is the half he has actually practiced.

Relay exists because six teams were sending quarterly plans in six spreadsheet formats and someone was reconciling them by hand every week. He noticed the shape of that before he wrote anything, then built the intake that absorbs all six and returns one resourced plan. The recognition is the part worth hiring. The tool was the consequence.

The work

The responsibilities, as the posting lists them.

He manages design updates across the Dow Jones event and conference websites and their brand assets, spanning content design, UX/UI, motion design and video production. Four content disciplines, one calendar.

The design system he leads is the requirements document in practice. It decides what a compliant build contains before anyone opens a file, which is the same question this line asks in different words: what does elevated actually require, stated precisely enough that a producer can hit it.

The design-system consolidation is a coverage roadmap with a number on it: eight core properties, 6 migrated, build time cut about 80 percent. Drawn at the top of this page rather than described.

Before that, at Huge, the agency maintaining them, he planned and oversaw the design and development updates to tv.google, android.com including the Android 12 launch, and wearos.google.com, delivered against Google's launch calendar across all three at once.

GE's Better Health Study, one of GE's largest marketing campaigns: hundreds of media assets and a global website through one gated publishing pipeline. Petfinder.com's redesign, rebrand and launch campaign at POSSIBLE. Multi-country campaigns for Vodafone, SAP Ariba, Microsoft and Merck at Vertic. At Dow Jones, about 8 events in five months, each with its own content moment.

Brand-provided. He manages the brand assets across the Dow Jones event properties, which is the discipline of taking material an owner outside your team controls and making it hold on a surface you do.

In-house created. At Everyrealm he built the 3D, motion and visual design function from zero and staffed it. And where in-house ran out, he bought: on On The Row he owned the Monaverse vendor relationship end to end, through implementation and platform testing, to a single coordinated launch, and managed the external vendors across motion and 3D-rendering production.

AI-generated. This is the gap. His AI work is workflow tooling, intake and planning. None of it generates content. He can specify, evaluate and run the program around a generative pipeline, and he has the prompting and evaluation habits the posting asks for, but he has not stood up AI content generation and he would not claim otherwise. Two of three sources, said plainly, and the third one taken apart in the sourcing map further down.

At Huge he tracked burn and spend across the three Google properties. At Everyrealm he owned the creative function's spend. At Dow Jones, about 8 events and 6 launches in five months, every one a fixed-date go-live, which is the version of timing where there is no acceptable form of late.

Worth stating for accuracy: this is the operator's chair. He has owned spend and tracked burn. He has not run a formal procurement process with a sourcing team, and that limit is in the known issues rather than buried here.

The mechanisms, yes. He owns the brand marketing team's Asana implementation for reporting, capacity and resource management, and he built the intake that feeds it. The design system carries a measured outcome rather than an assertion: build time cut about 80 percent.

Content performance itself, no. What is not in his record is measuring creative against engagement or conversion, tying a specific piece of content to what it did commercially. He has built the instrument. He has not been the person reading that particular dial. It is learnable, the reporting stack is the hard half and he already owns that, but a Strong chip here would be the page lying about the one thing it is for.

Where elevated content comes from

Three sources, one honest read

The posting names three ways elevated content arrives: brand-provided, in-house created, AI-generated. Each one carries a coverage chip on its own tab, so the weak one is visible before you open it.

Content someone else owns, on a surface you do

At Dow Jones he manages the brand assets across the event and conference properties alongside the design updates themselves. JournalHouse and the WSJ Leadership Institute each arrive with material shaped by an owner outside the build team, and it still has to sit correctly on the page.

What makes that answerable rather than argued is the design system he leads. It sets what a compliant build contains, so the question of whether a supplied asset is good enough has a written answer before anyone has an opinion about it.

Nearest thing to a brand-provided catalog in his record: eight properties, one standard, assets he does not own moving onto surfaces he does.

The function he built, and the vendors he bought

Everyrealm is the receipt. He built creative production from zero, sourced and staffed 3D artists, UI/UX, motion and visual designers, and introduced the production processes and methodologies the team ran on. Output: metaverse real estate across 12 platforms, plus web2 properties and brand work.

Where in-house ran out, he bought. On The Row is the clean example: he owned the Monaverse relationship end to end, through implementation and platform testing, to a single coordinated launch, and managed the external vendors across the motion and 3D-rendering production and the promotional video.

Deciding which of those two a given piece of work should be, and being right about it often enough that the calendar survives, is the actual skill this line names.

Operating layer, not the image

He has built with generative AI seriously. Three tools to launch-readiness, solo, by directing agents, plus Relay, the AI intake running inside his job at Dow Jones and absorbing six teams' requests.

All of it is operating layer. Intake, triage, planning, reporting. None of it generates content, and he has no receipt for image, video or 3D generation at production quality.

So the honest position on this column: he can specify, evaluate and run the program around a generative pipeline, and he brings the prompting and evaluation practice from having shipped with it. He has not stood one up. On a team weighing three sources against each other every day, that is worth knowing before the interview rather than during it.

This is the one column where the answer is a plan rather than a receipt, and labelling it anything else would make the other two worth less.

The lead evidence

A 3D, motion and visual function, built from nothing

Everyrealm was a web3 metaverse start-up with $50M+ raised from a16z and others. He arrived as Director of Creative Operations and there was no creative production function to inherit. He built one: sourced and staffed a team of 3D artists, UI/UX designers, motion designers and visual designers, and introduced the production processes and methodologies they ran on.

What it produced: metaverse real estate delivered across 12 platforms, plus web2 properties and brand work. On The Row is the single clearest delivery. He owned the external vendor relationship with Monaverse end to end, through implementation and platform testing, into one coordinated launch, and managed the outside vendors across the motion and 3D-rendering production and the promotional video.

He owned the creative function's spend while he did it.

The chapter ended when the board pivoted toward game development as the web3 and metaverse market turned down. The chapter ended with the market, not with the work.

The operating layer

What he builds so the program runs

Programs run on mechanics, not on effort. These are the mechanics he has built, two of them inside the job and two of them on his own time.

Reporting

The Asana implementation

in production

He owns the brand marketing team's Asana implementation for reporting, capacity and resource management. It is not a preference about tools. It is the instrument every number on this page comes out of, including the migration count in the glidepath above.

Why it matters for a content program. Coverage against a target is only monitorable if something computes it. Otherwise a glidepath is a slide.

Intake

Relay

in real weekly use

Six teams were sending quarterly plans into his function in six spreadsheet formats: subscription strategy, product design, product management, performance marketing, CRM and event marketing. Relay is the AI intake he built to receive and triage all of it and return one resourced plan.

The honest limit. Exactly one user, him, weekly, on real planning data. It has not been hardened for a team, and that is a real limitation rather than a roadmap item.

Agreements

An agreements system he built

private build

Turns what people commit to in a working session into a reviewed, signed record, so a scope or a hand-off cannot quietly evaporate.

Why it exists. Vendor scoping, partnership talks and hiring conversations all start before anyone has signed anything, and he kept watching the commitments made in them go unrecorded. Built for that, not for a market.

Capacity

The resourcing tool

in real weekly use

The same hour goes wrong in every creative team he has worked in. The resourcing meeting happens, real decisions get made out loud, and then somebody has to remember them and write them up afterwards. Usually late, usually thinner than what was said.

The loop. The resourcing decision gets made out loud in the meeting. It is captured as it happens and staged for a one-click yes, so nothing changes unless a human confirms it. Once confirmed, the capacity view and the team's plan of record update themselves.

Where the human stays. On the yes. Capacity is computed rather than assumed, so PTO, standing meetings and partial weeks come off the top before anything is promised, and an over-capacity week shows up before the work is promised away.

Built for and used by him, for his own planning. It is not deployed across his employer, and that is a real limitation.

Content intake, coverage tracking, capacity math and status reporting stop costing a person's week, so the team's hours and his go to standards, sourcing strategy and the calls that need judgment. That is why the role covers more ground than the headcount suggests.

There is a second reason this matters for a content program specifically. Every vendor and agency in this market now quotes AI-assisted timelines. Someone who has built these systems can tell a real efficiency claim from a markup, and can write a scope that does not get gamed. Happy to walk through it live if this turns into a conversation.

On record

People who ran work with him

Meticulous capacity planning to hit targets across every workstream without burnout. Exceptional communication and problem-solving.

Hulya G. Director, Web Marketing Strategy, Google

A great PM. Diligent on the financial, creative and timing details, and a strong voice on UX and design.

Gary Goldsmith Design Operations, Meta

It turned our weekly planning meeting from a doc-readout into a real conversation, and now the conversation updates the board itself.

Clare Smythe Design Lead, Dow Jones, on the resourcing tool

Before anyone has to ask

Known issues

Three things a careful reader would find anyway. Better here, in his words, than in a reference call.

  1. Catalog scale

    He has run content programs across a portfolio of properties and campaigns. Not across tens of millions of products in multiple countries. The mechanisms transfer: standards, coverage targets, intake, capacity, a publishing gate. The scale is new, and he would rather say so now than discover it in month two.

  2. Luxury and premium retail

    No luxury retail receipt. What he has is thirteen years of making a brand look like itself on every surface it appears on, for Google, GE Healthcare, Vodafone, Merck and a metaverse start-up that needed to look expensive before it was. That is the same discipline pointed at a different shelf, and he is not going to dress it up as category experience.

  3. AI-generated content

    His AI work is the operating layer, not the image. He has not run a generative content pipeline. On a team weighing brand-provided against in-house against AI-generated, that is worth knowing up front, and it is why row 14 and the third sourcing tab are both marked Partial rather than talked around.

Two more limits, stated for completeness: he has not run a formal procurement process with a sourcing team, and he has not owned an annual budget through a Finance cycle. He has owned spend and tracked burn from the operator's chair, which is a different job with the same arithmetic.

The question that gets asked in minute forty

Why this, why now

About the seven months

He is about seven months into the Dow Jones role. He is not running from anything. The work is real, he is doing well at it, and he would say the same thing in a reference call from that team.

The reason he is writing is a preference that took thirteen years to get clear, not seven months. He has spent those years running creative production for brands that cared about the standard, and the years he would do again are the ones where the standard was high enough to be inconvenient. That is a small number of teams.

Why éShop specifically

Because the remit is the interesting part. Elevated content only means something if there is a standard behind it that survives volume, and holding a standard across tens of millions of products in multiple countries is a program problem before it is a taste problem. Photography, video, 3D and graphic design, all four running at once, with coverage targets and a source mix to argue about every quarter.

That is the job he has been doing at a fraction of the scale, in four disciplines at a time, for years. He would like to do it here, where the answer actually has to hold.

Contact

No form. Just the three ways to reach him.

Warren Velázquez, M.A. Senior Program Manager: digital products, creative production and live launch operations.