Senior Partner Solutions Engineer, Technical Partnerships

At , we’re building the future of AI-powered Content Operations. Our AI Content Operating System gives teams the freedom to model, create, and automate content the way their business works, accelerating digital development and supercharging content operations efficiency. Companies like SKIMS, Figma, Riot Games, Anthropic, COMPLEX, Nordstrom, and Morningbrew are using Sanity to power and automate their content operations.

The Senior Partner Solutions Engineer owns both the technical work and the relationship for a portfolio of Sanity's technology partners. You scope, prototype, and review the technical side of partner solutions and you also manage the partner relationship itself, the business conversations and day-to-day project management. You report to the VP, Technical Partnerships.

Most integrations ship through the partner's own engineering team or Sanity R&D—your job is to make sure what gets built is the right thing, built the right way, and that the partnership itself stays healthy and productive.

What you would do:

• Partner Relationship & Strategic Advisory

• Own the relationship with a portfolio of partners: the project plan, the roadmap, the business conversation, and the technical scoping, as one continuous thread

• Lead conversations with partner business and product leaders, moving fluidly between strategic and technical framing

• Assess technical feasibility and effort on the spot well enough to keep a strategic conversation moving, then follow up with real scoping

• Shape partner pitches and joint roadmaps with grounded technical input, so commitments made in the room are ones R&D or the partner can actually deliver

Technical Scoping & Prototyping

• Identify and document the technical opportunity for a partner integration or MCP-based solution: architecture, API surface, data flows, and integration points

• Build prototypes and proofs of concept where they de-risk a build or clarify a design decision. You don’t need to create production-bound code, but enough to validate the approach

• Produce clear technical documentation so a partner's engineering team or Sanity R&D can build to production without re-doing the scoping work

• Navigate partner APIs, SDKs, and technical documentation directly; speak credibly with partner engineers about integration design and trade-offs

• Partner with R&D during build and launch to answer scoping questions and validate the implementation against the original opportunity

Technical Review