Senior Engineering Manager, API Catalog

Postman•San Francisco, CA

42d•$280,000 - $320,000•Onsite

About The Position

Postman is hiring a Senior Engineering Manager to lead the engineering behind its API Catalog, the system of record for discovering, ingesting, federating, governing, and reporting on APIs. The role leads a small, senior, US-based team and is focused on scaling a validated product into one that large platform organizations can standardize on. This includes supporting much larger API estates, reaching the environments and gateways enterprises use, and enabling the catalog to serve as a control plane for API governance. The team owns service discovery and ingestion across repository providers, API gateways, and clusters; enterprise reporting and governance evidence; gateway federation; event-driven API support beginning with Kafka; and product maturity, reliability, and telemetry. The catalog’s work depends heavily on other teams, including specification tooling, the API client, integrations and ecosystem teams, and shared platform services. The manager will coach and grow experienced engineers, hire as the team expands, set goals and technical standards, and distribute knowledge across critical systems. They will coordinate delivery across team boundaries, define interfaces with dependencies, and own technical direction across ingestion, federation, service models, reporting, and deployment data layers. They will also own the engineering roadmap, delivery milestones, production reliability, and support burden, with correctness, multi-tenant isolation, cost, reporting accuracy, and on-premises and self-managed deployments treated as core concerns. The position is based in person at one of Postman’s listed office hubs. Roles based in Bangalore currently work in the office three days per week and are expected to transition to five days per week by year-end; roles based in the other listed hubs are in office five days per week.

Requirements

At least 10 years of software engineering experience.
At least 5 years leading engineering teams.
Demonstrable depth on a difficult technical problem personally designed and debugged.
Experience scaling a validated product from 1 to 10, with customers and large-organization adoption.
Production ownership of a broad enterprise integration surface involving many third-party providers and their differing authentication, rate limits, permission models, and cloud versus self-hosted configurations.
Demonstrated ability to deliver work that depends on teams outside the candidate’s management, in an organization where those teams have independent roadmaps.
Experience leading a senior-heavy engineering team and elevating experienced engineers.
Experience with multi-tenant enterprise SaaS, including customers with on-premises or self-managed infrastructure and real compliance requirements.
Full lifecycle ownership from design through production support.
Clear, economical communication with engineers, executives, and customers.

Nice To Haves

Experience with API gateway technologies, cloud provider control-plane APIs (AWS, GCP, or Azure), and Kubernetes.
Experience with CI/CD systems and developer workflow tooling, including understanding adoption of new pipeline gates.
Experience with analytical datastores for customer-facing reporting, such as ClickHouse or similar, including their operational requirements.
Experience with event-driven and asynchronous API technologies, particularly Kafka.
Experience with governance, audit, or compliance reporting for enterprise buyers.

Responsibilities

Manage, coach, and grow a team of experienced engineers, surfacing gaps and enabling senior engineers to own solutions.
Hire deliberately as the team grows and establish a clear technical bar.
Set explicit goals, provide direct feedback, and make the team’s work legible to the broader organization.
Reduce single-owner concentration on critical systems by deliberately spreading context.
Secure commitments, coordinate sequencing, and unblock work that depends on teams outside the manager’s organization.
Define clear contracts between the API Catalog and its dependencies so teams can work independently.
Communicate early about commitments that depend on other teams’ roadmaps and bring options to address blockers.
Drive architecture and execution across ingestion, federation, the service model, reporting, and deployment data layers.
Design for correctness, multi-tenant isolation, and cost per tenant.
Set and measure the quality bar for reporting accuracy.
Treat on-premises and self-managed deployments as first-class variants of connectors.
Maintain engineering fundamentals, including design reviews, testing, safe staged rollouts, and instrumentation.
Own the API Catalog engineering roadmap and balance enterprise commitments, connector breadth, and technical debt.
Break large initiatives into incremental milestones and plan work that extends beyond a quarter.
Own production reliability and the support burden, treating recurring toil as a design problem.
Lead engineering work across service discovery and ingestion, enterprise reporting and governance evidence, gateway federation, event-driven API support, product maturity, reliability, and telemetry.