Senior Partner Solutions Engineer, Technical Partnerships

At Sanity.io , 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 Review partner-built integrations for code quality, security posture, API usage, and joint customer value Give partners clear, actionable feedback, and flag systemic gaps back to Product/Engineering AI & Technical Fluency Be fluent in core AI application architecture and the Model Context Protocol (MCP). You know enough to scope and prototype confidently, not just evaluate on paper Hands-on evaluation of partners' AI product surfaces (model choices, agent tooling, developer experience) to inform scoping decisions Identify where Sanity's content platform creates real technical leverage inside an AI-native partner's stack, and document that opportunity clearly enough for someone else to build it Cross-Functional Collaboration Work with Sanity R&D to hand off scoped opportunities, support them through the build and represent partner needs in the roadmap Support Solutions Architects and Sales Engineering with technical assets (reference architectures, prototypes) from your partners What Success Looks Like The breadth and depth of integrations you own contribute measurably to Sanity product adoption and signup growth from new customers Partners and internal stakeholders treat you as a knowledgeable owner of the relationship: both its technical direction and its business trajectory R&D and partner engineering teams can pick up your specs and prototypes and build from them without re-doing the scoping work Partners treat you as a credible technical peer who understands both their business strategy and their architecture deeply. About you: Required 3–6 years as a software engineer, solutions engineer, or technical partner/integration role, with a track record of scoping technical integrations, handing them off cleanly to a build team, and managing the relationships around them A builder mentality: you generate your own creative ideas for what a joint solution could be, rather than waiting for someone to hand you something to evaluate Comfortable in the room with business and product leaders—able to translate strategic conversation into technical feasibility and back again Hands-on experience with APIs, SDKs, webhooks & modern AI/developer tools; comfortable prototyping directly in partner or third-party codebases Working knowledge of core AI/LLM concepts and hands-on experience with the MCP framework Strong technical writing: able to turn a scoping conversation into a spec someone else can build from Comfortable operating independently across ambigu