For the Creative Technology Lead role

I lead creative for Verizon’s CRM program at Publicis, and alongside that I lead our team’s AI work: finding where production slows down, building agents to fix it, and getting producers, writers, and clients to actually use them. Your Creative Technology Lead role describes that second job as a full-time one, which is why I’m applying.

Two examples of the work. Our creative QA system is an orchestrator in Copilot Studio that routes to three specialist agents (content proofing, tone of voice, copy parity) and checks a high-volume email pipeline before anything ships. I designed it around the platform’s constraints and solved the access and file-ingestion problems that had blocked deployment.

On the generative side, I built an image pipeline on the Gemini API with a Claude skill that reviews every frame against written criteria and carries what it learns into the next project. On a recent library, that meant 100 finished frames in under nine hours of production, with more than 130 rejected along the way. That’s the kind of evaluation standard and measurable speed your posting describes.

I’m a creative director who builds, not a software engineer. My systems run on APIs, agent platforms, and workflow automation, and I know when to bring in engineering. What I add is 20 years of knowing what good creative looks like and how marketing teams really work. That knowledge decides whether an AI tool gets adopted or ignored.

The full case studies are at charlesjw.com/ai-work. I’d welcome the chance to walk you through any of them.

Charlie Williamson
charlesjw@gmail.com // 917-414-3869