Postman

postman.com · 25 open roles in the last 6 months · hiring in 2 countries

Loading…

Postman is investing in Git-native API workflows, automated testing, and AI agents while strengthening the enterprise and infrastructure layers needed to support them.

Inferred from 25 job postings from the last year, with recent ones weighted more · updated 22 Oct 2026. Not a statement by the company.

What changed recently

The newest roles add a concrete push toward Native Git Postman, where API collections and related resources become files managed through repository workflows, alongside more engineering for local, CI, and cloud-based API testing. AI remains a major thread, with a new senior AI engineer role and a principal architect role focused on identity, authorization, and trust for agents; recent openings also reinforce Postman’s longer-running platform and enterprise investments.

Scalinghigh confidence

Building AI agents and the platform around them

1m 23m 56m 51y 5

Postman is adding product-facing AI capabilities, including Agent Mode and an API knowledge graph built from collections, environments, schemas, and usage patterns. Recent leadership and engineering roles point to a broader effort to develop agents and provide the AI platform and reliability needed to run them safely at scale; a separate principal role frames identity, authorization, and trust delegation as platform problems for agents.

The newest AI engineer role names Agent Mode and an API knowledge graph.
Recent roles include a Head of AI Platform Engineering and an AI agent development lead.
Dedicated AI reliability and monitoring work covers production agentic systems.
The Business Platform principal role describes a multi-year architecture serving hundreds of millions of developers and agents.

Scalingmedium confidence

Strengthening API discovery and developer tooling

1m 13m 46m 41y 4

Postman is maintaining and improving the systems that help developers find APIs, including search across team data and the Public API Network, described in the postings as the world's largest public API network. Codegen, SDKs, and client libraries are another active area, with roles tied to API developer tools and a stated need to handle millions of API requests per day.

A senior search role focuses on distributed indexing and search relevance.
The API Network role covers both public discovery and the enterprise Private Network.
Recent Codegen roles include a staff-level position and a senior full-stack role.

Senior Engineer, SearchSenior
Senior Engineer, API NetworkSenior
Staff Software Engineer- CodegenStaff
Senior Fullstack Engineer - CodegenSenior

New betmedium confidence

Making API work Git-native and local

1m 23m 26m 21y 2

Postman is building Native Git Postman around API collections, specifications, environments, flows, and mocks as plain files that developers can manage in repositories. The work includes visual and command-line experiences, synchronization, and handling conflicts and concurrent edits—an approach that could also let AI agents inspect and modify API work within familiar developer workflows.

Two new frontend roles appeared in the last month on the Local Mode team.
The postings describe API resources as plain files that move through branches and pull requests.
The stated focus spans Git, filesystem access, synchronization, and conflict handling.

Scalingmedium confidence

Expanding API testing from local runs to performance testing

1m 23m 26m 21y 2

The Automation Testing team is adding backend and frontend capacity for tests that run locally, in CI, and in the cloud. The newest frontend role specifically starts with performance testing and API load testing; the postings also emphasize reliable, fast-to-debug runs and correct test-data and database integrations.

Two roles posted in the last month are dedicated to Automation Testing.
The work covers local, CI, scheduled, and cloud test runs.
Performance and load testing are explicit areas, alongside test data and database integrations.

Scalingmedium confidence

Improving enterprise monetization and customer journeys

1m 03m 36m 31y 3

Postman is building user-facing pricing, checkout, and subscription-management experiences for global self-serve and sales-led customers. Separate customer-journey and web-product roles focus on onboarding, product discovery, and the path from first visit through evaluation and purchase, indicating work across both the website and the authenticated product.

The monetization role covers checkout, pricing and packaging, and subscription management.
The customer-journey role owns paths from signup through purchase and feature discovery.
The web product role connects public website journeys with the authenticated product.

Scalingmedium confidence

Scaling Fern’s API experience for AI-driven integrations

1m 03m 26m 21y 2

Fern roles focus on API infrastructure and developer experience for software companies, including named customers Nvidia, Square, Twilio, ElevenLabs, and OpenRouter. The postings explicitly anticipate that AI agents will implement most API integrations in the coming year, and call for performant, observable, secure systems and API documentation that works well for agents.

Two recent staff and senior engineering roles are dedicated to Fern.
Both postings connect API infrastructure and developer experience to AI-agent integrations.
The roles cite named software and AI company customers.

Senior Software Engineer - FernSenior
Staff Software Engineer - FernStaff

Scalingmedium confidence

Turning API Catalog into an enterprise inventory and governance layer

1m 03m 26m 21y 2

Postman is investing in API Catalog as a system of record and governance control plane for large platform organizations. The engineering manager role points to expanding discovery across providers, gateways, and accounts, with a goal of supporting estates an order of magnitude larger than today; Kafka is the starting point for extending catalog coverage to event technologies.

A recent engineering-management role leads a small, senior US-based team for API Catalog.
The posting calls out a target of supporting API estates an order of magnitude larger than current ones.
Kafka is named as the first event technology for broader catalog coverage.

Senior Engineering Manager, API CatalogManager
Senior Engineer, API NetworkSenior

Questions to ask in a coffee chat

For Native Git Postman, how is the team deciding which API resources should become local files first, and what has been hardest about synchronization or conflict handling?
How does the Automation Testing team divide its work across local, CI, cloud, and performance testing, and where are the biggest developer pain points today?
How are Agent Mode and the API knowledge graph changing the boundaries between Postman’s product teams and its AI platform or reliability teams?
For API Catalog, what changes when the product needs to serve much larger enterprise estates and include event technologies such as Kafka?
How do the monetization, customer-journey, and web teams coordinate improvements from a developer’s first visit through onboarding and purchase?

What this can't tell you

The postings describe intended work and technical scope, but do not establish what has shipped or how customers are adopting it.
The job data gives limited detail on how Native Git Postman, AI agents, Fern, and the broader Postman platform will be integrated.
Many roles are engineering-focused, so the postings provide less visibility into commercial priorities and customer feedback than into technical investment.