Engineering Manager, Partnerships Engineering

Details

• Experience managing engineers in a front‑line role, with ownership over delivery, execution, and team health.
• Strong technical judgment across APIs, SDKs, integrations, and distributed systems.
• Experience working with/building technical systems spanning traditional SaaS infrastructure to AI-native applications.
• Comfort operating in Strategic Partnerships‑adjacent environments and collaborating closely with partnerships, sales, and product teams.
• Ability to balance short‑term partner needs with long‑term platform quality and leverage.
• Clear, effective communication with both technical and non‑technical stakeholders.
• Experience building or scaling partner integration programs.
• Familiarity with developer platforms, security products, or identity‑related systems.
• Prior experience working directly with external partners or customers on complex integrations.
• Serve as the primary engineering owner for external partnership integrations, from discovery through GA launch.
• Act as the technical counterpart in partnership discussions, validating feasibility, scope, and tradeoffs.
• Support deal progression when needed through design proposals, architecture reviews, and technical assessments.
• Establish and own an external integrations program that tracks work reliably across the full partnership lifecycle.
• Define processes, roles, and execution models that enable multiple integrations to run in parallel without heroics.
• Balance near‑term partner delivery with sustained investment in shared infrastructure and self‑service tooling.
• Guide and support hands‑on integration work with partners, including direct consultation and building or extending first‑party components.
• Ensure integrations are well‑designed, maintainable, and aligned with platform, security, and product standards.
• Collaborate closely with Developer Platform and Cognition teams to land changes cleanly and sustainably.
• Own engineering documentation that supports Strategic Partnerships, external partners, and internal engineers throughout integration work.
• Build and maintain reference architectures, integration guides, and design patterns that reduce ambiguity and rework.
• Identify recurring integration patterns and turn them into reusable approaches.
• Use proofs of concept to explore new integration models and reduce risk ahead of production investment.
• Incrementally evolve integrations toward more plug‑and‑play, self‑service experiences.
• External partnership integration program
• IDE integrations
• Browser integrations
• External partner integrations
• Integration documentation and reference architectures