The events-platform surface, live
10+ event & conference websites, one design system, AI-powered intake for 6 teams, and an ops layer supporting ~8 events + 5 launches in 5 months.
Events techGovernanceOpen record ›
Roadmap. Vendor governance. Adoption. Operations. Warren Velázquez has spent 13+ years owning exactly this operational shape, and championing the Voice of the Marketer while doing it.
The JD asks for four things at once. Warren does all four today.
Built an AI intake tool at Dow Jones that receives and triages requests from 6 marketing-side teams. Needs synthesized into priorities daily.
Owned roadmap planning for Google's android.com portfolio under immovable dates; leads a design-system roadmap at Dow Jones that cut build time ~80%.
Owned the Monaverse platform-vendor relationship end-to-end: implementation, platform testing, coordinated launch. Steered Infosys (28+ engineers) on APS.
Owns the brand marketing team's Asana operating layer (reporting, capacity, resourcing) across ~8 events and 5 launches in 5 months.
Real programs, reframed as records. Click any card to open it. The Fit tab maps each one to the JD.
10+ event & conference websites, one design system, AI-powered intake for 6 teams, and an ops layer supporting ~8 events + 5 launches in 5 months.
Roadmap planning, deployment and localization across android.com, tv.google and wearos.google.com, including the Android 12 launch.
Owned the platform-vendor relationship with Monaverse through implementation and platform testing to a single coordinated launch.
A transactional .com + mobile app for Arizona's energy company: an 11-month design program delivered with Infosys engineering.
Sourced and built a creative team, then the intake, ceremonies and methodology it ran on, across 12 metaverse platforms.
Led 4–6 designers with Google's Search UX Design Director on the future of Search Ads, spanning new formats, including video.
Humans with agents drive customer success together. This one answers hiring-manager questions, including the hard ones.
All real. All from the résumé.
The JD asks for experience using AI tools like Claude to build prototypes. Warren went further. Four operations systems, each one built for a specific problem he ran into in the workplace and designed around that problem rather than around a demo. None of them is a venture, and none is a product he is selling.
Turns what people commit to in a working session into a reviewed, signed record, so a scope or a hand-off cannot quietly evaporate.
Lets a team send unreleased work outside the building without losing control of it, with a record of who saw what.
The resourcing decision gets made out loud in the meeting, and the capacity view updates itself once a human confirms it.
Lets creators team up with attribution and protection settled before the work starts, instead of argued about after.
The same hour goes wrong in every creative team Warren has worked in. Agencies, a startup, in-house teams. 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 plan drifts out of date until the next meeting rediscovers it.
So he built the loop into the meeting itself. The resourcing decision 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. The payoff is that an over-capacity week shows up before the work is promised away.
It is a fully built tool he uses every week, built to solve a problem in his own role. The honest limitation: it is built for and used by him and his own planning, not deployed across his employer. He is happy to walk through it live in an interview.
The resourcing hour
In the meetingThe meeting updates the plan, instead of someone updating the plan after the meeting.
Each one is a real build: several tools integrated so the work does not get re-typed between them, a custom database underneath, AI used where it earns its place, permissions and access designed in, and hosting and infrastructure he set up and keeps running. Real production deployments, not prototypes.
The method is the point. Warren specifies the system, directs AI agents to build it, reviews what comes back and sends it round again, with staff engineer friends advising. He is not an engineer and he does not hand-write production code. The skill on show is knowing what to ask for, and recognizing when the answer is structurally wrong.
Real testimonials from the people who worked with him.
"Warren owned creative, content, deployment and localization on android.com — with meticulous capacity planning to hit targets across all workstreams without burning the team out. Exceptional communication and problem-solving."
"On a year-long, complex multi-part program, Warren carried both project and client management. A team player and problem solver who builds strong client relationships."
The platform is waiting for an owner. Warren is ready to run it with the marketers, the vendor, and the agents, together.