Senior Engineering Manager, API Catalog

Postman · Cupertino, California, United States; San Francisco, California, United Statessenior

In short

▸Liderazgo técnico de un equipo senior en EE.UU. para construir un catálogo de APIs como sistema de referencia empresarial.
▸Enfoque diario en descubrimiento de servicios, gobernanza, federación de gateways y soporte a eventos (ej. Kafka).
▸Destaque: desempeñar un rol clave en hacer que el catálogo sea el único sistema confiable de verdad para empresas grandes.

Proficiency in English is required for collaboration across global teams.

In ~1 minute you get: who interviews you, the likely questions answered from your CV, and your CV tailored to this job. Free, no card.

🎧Land the interview? Bring the copilot. Our free extension listens to the live interview and flashes 3-4-word anchors from your resume and prep — glance, connect, talk. Get the extension →

What they ask for

✓Liderazgo de equipos de ingeniería de nivel senior
✓Experiencia comprobada en productos de plataforma o infraestructura de APIs
✓Capacidad para coordinar trabajo entre equipos
✓Conocimiento en sistemas distribuidos y arquitectura de escala empresarial
✓Habilidades sólidas de comunicación y gestión de stakeholders
✓Enfoque orientado a confiabilidad, datos fiables y evidencia de gobernanza.

Don't tick every box? That's normal — your free dossier shows your gaps and how to cover them in the interview.

PythonGoNode.jsKafkaPostgreSQLRedisAWSGCPKubernetesREST

Who should you write to at Postman?

Your free dossier identifies the people who'd interview you — their background, what they value, and how to reach out so you stand out before applying.

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 A large enterprise runs hundreds of services across multiple cloud accounts, multiple gateways, several repository hosts, and a mix of cloud and on-prem infrastructure. Nobody can produce a complete list. Postman's API Catalog is the system of record that can: it connects to where APIs actually live, brings them into a single inventory, and gives platform teams the means to govern them — ownership, environments, specification compliance, and evidence that release gates were met. What's ahead is: turning a product that works into the system of record that a large platform organization standardizes on company-wide. That means carrying estates an order of magnitude larger than today's, reaching every environment and every gateway an enterprise actually runs, and becoming the control plane through which API governance happens rather than one more inventory somebody has to maintain. We're hiring a Senior Engineering Manager to own the engineering behind it. You'll lead a small, senior, US-based team, and you'll spend a meaningful share of your time landing work that crosses team boundaries — because most of what this roadmap needs, this team does not build alone. What This Team Owns Service discovery and ingestion breadth. Connecting to the systems where APIs are defined and deployed — repository providers across cloud and self-hosted, cloud API gateways, and clusters. Breadth is the growth axis: each provider we support is an enterprise we can serve. Enterprise reporting and governance evidence. Test and CI-pipeline reporting, specification linting, and the records enterprises use to prove a release met its gates. Trust is the product here; a number a customer can't reconcile is worse than no number at all. Gateway federation. Large organizations don't run one gateway; they run several, from different vendors, across many accounts, often with different teams owning each. Federating that estate into a single governed view — and doing it without asking customers to reorganize around us — is one of the defining technical problems of this product's next phase. Event-driven API support. Extending the catalog beyond request/response to event technologies — beginning with Kafka, end to end from client through specification and governance into the catalog. Product maturity, reliability, and telemetry. Metrics you can trust as a single source of truth, a support flow that doesn't consume the roadmap, and datastore reliability that doesn't produce customer-visible incidents. This is treated as a first-class investment area, not overhead. The API Catalog owns the system of record: how services are discovered, ingested, federated, linked to environments, governed, and reported on. What You'll Do Lead a senior team • Ma

Don't apply unprepared

We research who's interviewing you, tailor your CV and rehearse you live — first one free.