Responsibilities

• Scope every pilot. Sit in pre-sale with the AE and pick the use case that will move a brand-side number inside the trial window.
• Make the call when a number isn’t moving. Every brand’s first-party data is shaped by its own history. You tell a data problem from a definition problem, send the first to our FDEs and fix the second yourself.
• Build the first use case with their marketing team. That means a live audience, activated and measured. You’re done when they run the second one without you.
• Show them the whole map. Prove one thing first, then make sure the customer knows everything else Minerva can do for them.
• Design what doesn’t exist yet. When a customer wants something we have no play for, you design it and the account team sells it.
• Generalize the motion. For each vertical, work out which use case goes first, which audience definitions survive a real campaign, and what the VP needs to see in week two.
• Feed product the specific thing. What you reached for in the middle of real work shapes what we build next.

Requirements

• You’ve owned a brand’s marketing outcome. A campaign or a whole function, with the target and the result in your name. Agency-side counts if the client’s number was yours. Supporting the person who owned it doesn’t.
• You understand the full cycle, from strategy through audience, activation and measurement, and you can speak to every stage without handing off.
• You know enough about data to diagnose. You don’t need to fix a broken pipeline, but you can tell when one is the problem.
• Agent-native. You already do a team’s work with AI and can show us the workflows. We test for this live in the loop.
• Located in or willing to relocate to New York City.

Preferred

• SQL, even basic.