Data Partnerships

Required

• Translation and specification. Author partner-facing specs that a non-ML operator can execute against with no follow-up call. Define the unit of delivery, what passes, what fails, and what to do when it is ambiguous.
• Commercial terms. Structure pricing, rate cards, minimums, milestones, and acceptance language. Work with legal on MSAs and SOWs. Own the unit economics and know what we are paying per unit of usable data, not per unit delivered.
• Scaling a partnership into a network. When one partner hits capacity, stand up the next without dropping quality or blowing up cost.
• Operating cadence. Trackers, weekly partner reviews, forecasts against the research roadmap, and a clear picture of cost, volume, and quality that anyone at the company can read.
• Closing the loop. Report back to research on what the data actually produced and use it to change the next cycle's spec.
• Travel. Periodic domestic and international travel to partner sites and collection operations.
• You might thrive in this role if you:
• 6+ years owning external partners or vendors who delivered a product or service to you — supply chain, vendor management, outsourcing/BPO management, data operations, or partnerships with a delivery obligation.
• Demonstrated experience standing up a new vendor from zero: selection, diligence, contracting, ramp, and ongoing management.
• A track record of translating technical or specialist requirements into unambiguous instructions that a non-technical execution partner delivered against successfully.
• Fluency with commercial mechanics — pricing structures, SOWs, acceptance criteria, unit economics — and the judgment to know which terms actually protect quality.
• Exceptional written communication. You will write documents that people you have never met execute without you present.