Engineering Manager, Postman AI

Who Are We?

Postman is the world’s leading API platform, used by more than 45 million+ developers and 500,000 organizations, including 98% of the Fortune 500. Postman is helping developers and professionals across the globe build the API-first world by simplifying each step of the API lifecycle and streamlining collaboration—enabling users to create better APIs, faster.

The company is headquartered in San Francisco and has offices in Boston, New York, Austin, Tokyo, London, and Bangalore - where Postman was founded. Postman is privately held, with funding from Battery Ventures, BOND, Coatue, CRV, Insight Partners, and Nexus Venture Partners. Learn more at postman.com or connect with Postman on X via @getpostman.

P.S: We highly recommend reading The "API-First World" graphic novel to understand the bigger picture and our vision at Postman.

The Opportunity 

Agent Mode and AI Engineer are two of our most exciting AI products. Agent Mode is the foreground product where developers interact with an AI that understands their entire API workspace. AI Engineer handles long-running development and analysis tasks autonomously across an organization's API surface area. You'd be working with the team building and integrating these into Postman’s product surface area

What we actually need from you

You manage by doing. You're not running standups and writing status updates while engineers do the actual work. You're in the code, reviewing PRs, making architectural calls, and shipping alongside your team. You have opinions about what good engineering looks like when a significant chunk of code is AI-generated, and you hold the team to that bar through reviews and design discussions, catching problems early.

You use AI to run a better team. Not just as a product you're building, but as a tool you're using. Tracking work, surfacing risks, managing dependencies. The expectation is that you find ways to get more out of a small team than the headcount suggests, and AI tooling is a big part of how you do that. This is a necessary constraint for us to build a best-in-class AI-native product.

You grow engineers by putting real problems in front of them. You know when someone is ready to take on more scope and when they need support first, and you act on that read rather than waiting for a performance cycle to surface it.

You care about how the system fits together. Agent Mode and AI Engineer sit on top of the Context Graph, Fabric Gateway, filesystem-native collections, and a growing tool surface. You need to understand where the seams are and what breaks when something changes upstream.