Qodo is building the technical layer that brings AI-native code quality into real engineering workflows. As our partnership ecosystem grows, we’re looking for a principal-level engineer to turn strategic integrations into shipped products.

In this role, you’ll be a technical visionary and builder. You will design and implement the next generation of Model Context Protocol (MCP) servers, APIs, and platform integrations for key strategic partners like cloud providers, Anthropic, Cursor, and OpenAI. This is a high-leverage role where your expertise will directly shape how Qodo- the missing quality-focused system-plugs into the complex, autonomous, multi-agent development environments of tomorrow.

Ideal for someone who thinks deeply about developer experience, moves fast, and enjoys building technical infrastructure that scales through partnerships.

Mission: Make Qodo unavoidable across the Agentic SDLC. Own the integration playbook that brings Qodo into every critical developer surface - IDEs, repos, CI/CD, code review, cloud platforms, and the AI agents shaping how software gets built. Build the technical layer that turns Qodo into the default quality, governance, and trust gate across the SDLC, translating cutting-edge research into integrations that scale, ship, and become embedded in how teams work.

Responsibilities

• Wrap Qodo's capabilities as a public, composable surface. Turn Qodo Review, Aware, and Skills into clean, documented building blocks that any partner's engineering team can adopt without hand-holding. Treat the public API, SDK, and MCP surface as a product - versioned, stable, well-documented, and obsessively focused on DX.
• Be the engineering counterpart on partner conversations. Sit shoulder-to-shoulder with the Product Partnerships Lead in partner discussions. Translate ambiguous "we want to integrate" conversations into concrete technical scopes, integration paths (MCP vs. SDK vs. API), and shipping timelines. Be credible enough that a partner's principal engineer takes the conversation seriously the first time.
• Ship marketplace and cloud integrations. Own the technical execution behind cloud marketplace launches (AWS, Azure, GCP) - deployment artifacts, SaaS metering, private offer plumbing - so the commercial motion is never bottlenecked by engineering.
• Define the integration playbook. Make the path from "new partner interested" to "integration live" repeatable. Document the patterns, build the reusable primitives, and reduce the per-partner engineering cost over time so the team can scale partnership volume without scaling headcount linearly.
• Hold the DX bar across every partner-facing surface. Docs that work the first time. SDKs that don't surprise. Errors that explain themselves. Examples that run. If a partner's engineer can't get to "hello world" in 15 minutes, that's on you.

• 5+ years of backend or platform engineering experience, with at least 2 years building developer-facing products (SDKs, APIs, integrations, or open source libraries that external engineers consumed)
• Preferable to have worked at or with AWS, Microsoft Azure or Google Cloud specifically on dev related products
• Shipped production integrations with third-party platforms - point us to the code, the package, or the partner that went live because of you
• Practical, hands-on fluency with MCPs and SDKs
• Strong API design instincts - knows when to wrap vs. expose, when to version, when to break compatibility, and how to make errors that explain themselves
• Comfortable in customer-facing technical conversations - can scope an integration with a partner's principal engineer in a 30-minute call and walk out with a working spec
• Ships fast under ambiguity - has a track record of going from "partner asked for X" to "something working" in days, not sprints
• Owns the full lifecycle: design, code, docs, release, support. No throwing things over the wall.
• Bonus: Has contributed to or shipped something in the public developer ecosystem that you're proud of