Postman Interview Questions and Answers
Last updated 2026-11-19
Postman is built around APIs, so its engineering interviews commonly go deep on HTTP, REST design, authentication, JavaScript and Node.js, and how you test and debug services. This page offers practice questions on those themes, with worked answers.
They are practice questions on the commonly reported topics, not real papers. For coding practice see Postman coding round questions, and for the design round see system design interview questions.
Rounds as commonly reported
Candidate accounts describe a recruiter screen, a coding or practical exercise, technical interviews on data structures, API and backend design, and a discussion of past projects, then a culture or hiring-manager conversation. Postman has not published a fixed process, so use this as a rough pattern and follow your recruiter's instructions.
Topics to revise
HTTP methods, status codes, caching and headers; REST resource design and versioning; OAuth 2.0 and JWT; pagination and rate limiting; JavaScript, async programming and Node.js; testing and mocking APIs; SQL and one NoSQL store.
Hiring status
We hold no sourced hiring dates, numbers or process facts for Postman and there is no /hiring page for it on this site, so none are stated. For current roles, use Postman's own careers site.
Postman Interview Questions and Answers: questions with worked answers
1 Explain the common HTTP status codes and when to use them.
easy200 OK for success, 201 Created with a Location header after creation, 204 No Content for success without a body. 400 for malformed input, 401 when authentication is missing or invalid, 403 when authenticated but not permitted, 404 when the resource is absent, 409 for a conflict such as a duplicate, 422 for a well-formed but invalid payload, 429 when rate limited. 500 for a server error, 502 or 503 when a dependency fails or the service is overloaded. Choosing precise codes helps clients react correctly.
2 Offset versus cursor pagination: which would you use?
mediumOffset pagination (limit and offset) is simple and allows jumping to a page, but gets slower on large offsets and can skip or repeat items when data changes between requests. Cursor pagination returns an opaque token pointing after the last item, uses an indexed seek, is stable under inserts and scales well, but cannot jump to an arbitrary page. For feeds and large collections, prefer cursors.
3 How do OAuth 2.0 and JWT differ?
mediumOAuth 2.0 is an authorisation framework for delegating access: a user grants a client limited access, and the authorisation server issues an access token. JWT is a token format: a signed JSON payload with header, claims and signature that a server can verify without a lookup. OAuth tokens may or may not be JWTs. Validate the signature, expiry, issuer and audience, keep access tokens short-lived, and use refresh tokens to renew them.
4 Design a webhook delivery system.
hardEvents are written to a durable queue; delivery workers POST to each subscriber URL with a signed payload (HMAC in a header so receivers can verify). Treat any non-2xx or timeout as failure and retry with exponential backoff and jitter, up to a limit, then move to a dead letter queue and notify the owner. Include an event id so receivers can deduplicate, since delivery is at-least-once. Isolate slow subscribers with per-endpoint queues and concurrency limits so one bad endpoint cannot delay others.
5 Explain CORS.
mediumBrowsers block cross-origin requests from scripts unless the server opts in. For simple requests the server answers with Access-Control-Allow-Origin. For requests with custom headers or methods such as PUT, the browser first sends a preflight OPTIONS request and the server must reply with the allowed methods and headers. CORS is enforced by browsers; it does not protect your API from other clients such as curl, so authentication is still required.
6 What are Node.js streams, and what is backpressure?
hardStreams process data in chunks instead of loading it all in memory: readable, writable, duplex and transform. Backpressure is the signal that a consumer cannot keep up: write returns false when the internal buffer is full, and the producer should pause until the drain event. The pipeline function handles this and error propagation, so use it instead of manual piping to move large files without exhausting memory.
7 How would you version a public API?
mediumCommon choices are a version in the URL path (v1), a custom header, or media type negotiation. Path versioning is simple and visible. Prefer additive, backward-compatible changes (new optional fields) to avoid new versions; announce deprecations with dates and a Sunset header, and keep old versions running for a published period. Version the contract, not each endpoint, and document changes in a changelog.
8 How would you test an API endpoint?
easyCover the contract (status code, headers, response schema), the happy path, validation failures, authentication and authorisation cases, idempotency on retries, and error handling when dependencies fail. Automate with assertions in a collection or a test framework, run in CI against a staging environment, and use a mock server for dependencies. Add contract tests so consumers and providers detect breaking changes early.
9 Implement a function to get a nested value by a dotted path, like a JSON path lookup.
easySplit the path on dots and walk the object, returning a default when any step is missing or the current value is null. Support array indexes because numeric keys index arrays in JavaScript and Python lists need integer conversion. O(path length).
javascriptfunction get(obj, path, dflt) { let cur = obj; for (const key of path.split('.')) { if (cur === null || cur === undefined) return dflt; cur = cur[key]; } return cur === undefined ? dflt : cur; }10 What is the N+1 problem in GraphQL, and how do you solve it?
mediumA resolver for a list runs one query for the list and then one query per item for a nested field, so 100 posts cause 101 queries. Use a batching layer such as DataLoader, which collects all keys requested in one tick and fetches them with a single query, and caches per request. Also limit query depth and cost.
11 Tell me about a time you debugged a hard production issue.
easyDescribe the symptom and impact, how you narrowed the cause with logs, traces and reproduction, the fix, and what you added afterwards (a test, an alert, a runbook). Emphasise communication during the incident and a blameless review. Concrete numbers, such as error rate or time to recovery, make it credible.
12 Why Postman?
easyTie it to the work: you use APIs daily and care about the developer experience, and you find the engineering of a collaboration platform for API work appealing. Mention a specific feature you have used and something you would improve or want to learn from building it.
Frequently asked questions
Does Postman ask JavaScript questions?
JavaScript and Node.js depth is commonly reported for many engineering roles. Check the role description for the primary language.
Do I need to know the Postman product?
Using it helps in conversation, though interviews test engineering skills, not product features.
Is there a take-home exercise?
Some candidate accounts mention practical exercises. Your recruiter will say what applies to your role.
Where can I find openings?
On Postman's own careers site. This site has no sourced hiring data for the company.
Related guides
More in Company Interview Questions
- Publicis Sapient Coding Round Questions
- Publicis Sapient Interview Questions with Answers
- PwC coding round questions
- PwC interview questions and answers
- Qualcomm Coding Round Questions with Solutions
- Qualcomm Interview Questions and Answers for India Software Roles
- Razorpay Coding Round Questions with Solutions
- Razorpay Interview Questions and Answers
- Salesforce Coding Round Questions with Solutions in Python and Java
- Salesforce Interview Questions and Answers for MTS and AMTS Roles
- Samsung Coding Round Questions with Solutions
- Samsung R&D Interview Questions and Answers for India Software Roles