Postman Careers

An API platform for building, testing, managing and distributing APIs.

postman.com

About the company

Company launched

2014

Founded in

Bengaluru, India

Headquarters

San Francisco, California

Office footprint

San Francisco, Bengaluru, Boston, New York City and Tokyo

Ownership

Privately held

Developers

More than 40 million

Organizations

500,000

Fortune 500 adoption

98%

Series D funding

$225 million

Series D valuation

$5.6 billion

Postman is a software company whose API platform supports API design, testing, documentation, monitoring, collaboration, governance and distribution.

The product began as Abhinav Asthana's side project in Bengaluru. He later formed Postman, Inc. with Ankit Sobti and Abhijit Kane, and the three founders continue to lead the company.

Postman says more than 40 million developers and 500,000 organizations use its platform, including 98% of the Fortune 500. It is privately held and has offices in India, the United States and Japan.

Interview process at Postman

(271 candidate-shared Glassdoor interviews, updated July 5, 2026)

Interview experience

48.5% positive

Interview difficulty

2.91 out of 5

Interview process length

18 days on average

Overall experience

PoorExcellent

EasyDifficult

Prep for your Postman interview with AI

Practise coding, networking, system design and product conversations.

Postman Interview Questions & Answers

Q: What's your experience with distributed systems?

A: Describe one system you built or operated, then explain scale, failure modes, consistency choices, observability and your personal contribution.

Answer by AI

Ground the answer in a real system.
Explain tradeoffs and failures.
Quantify scale or reliability.

Q: Explain how a request travels from a client to a server, including DNS resolution and load balancing.

A: Trace DNS lookup, connection establishment, TLS, the load balancer, application processing and the response, naming caches and failure points.

Answer by AI

Keep the sequence explicit.
Mention TCP or QUIC and TLS.
Include proxies and observability.

Q: How do you handle authentication and authorization in a microservices architecture?

A: Separate identity verification from permission checks, then discuss token validation, service identity, least privilege, key rotation and auditing.

Answer by AI

Distinguish authn from authz.
Cover service-to-service identity.
Plan revocation and logging.

Q: How would you architect a real-time notification system?

A: Clarify delivery and latency needs, then design event ingestion, durable queues, fan-out workers, preferences, retries, idempotency and monitoring.

Answer by AI

State scale and delivery guarantees.
Handle retries and duplicates.
Discuss channel failure isolation.