Postman - interview guide

Postman interview questions - a complete guide

Postman is an API platform, so APIs, databases and practical coding come first in its interviews. Here is preparation from machine coding to the bar raiser.

Language:EnglishHinglish

About Postman

Postman is a developer API platform - for building, testing and sharing APIs. It started in Bengaluru and is now headquartered in San Francisco; a large part of its engineering happens in Bengaluru.

This guide covers 13 Postman interview questions with answers - what each question checks and how to answer it - plus the Postman interview process, round by round, a 7-day preparation plan for freshers, tips and the mistakes to avoid.

Postman hiring process

  1. Hiring manager

    Background and projects.

  2. Coding round

    Reported: building a small service and its database schema.

  3. Machine coding and system design

    Working code within the time, and a design discussion.

  4. Bar raiser

    Questions such as caching LLD and database indexing, and behavioural.

Postman does not publish its India fresher interview process in detail (as of our check). This is based on candidate reports - many of them for experienced roles, so the fresher process can differ. Confirm with the recruiter.

Sources (checked 16 October 2026): Postman Careers. Hiring processes change - read the official notice before you apply.

Postman interview questions and answers

APIs

  1. 1.200, 201, 204, 400, 401, 403, 404, 409, 429 and 500 - when is each status code used?

    What they're checking
    The language of APIs.
    How to answer
    200 OK, 201 created, 204 success with no body, 400 bad request, 401 not logged in, 403 logged in but not allowed, 404 not found, 409 conflict, 429 too many requests, 500 server error.

  2. 2.What is the difference between REST and GraphQL - when would you use each?

    What they're checking
    API styles.
    How to answer
    REST has a URL per resource and a fixed response. GraphQL has one endpoint where the client says which fields it needs - less over-fetching, but more work for caching and complexity.

  3. 3.How would you version an API so old clients don't break?

    What they're checking
    Backward compatibility.
    How to answer
    In the URL (/v1/) or in a header. Adding new fields is safe; removing/changing them is breaking - that needs a new version and a deprecation notice for the old one.

  4. 4.What would you check in automated tests for an API?

    What they're checking
    Thinking like Postman tests.
    How to answer
    The status code, response time, the response schema, values of key fields, the right error for bad input, and 401 without auth.

Machine coding

  1. 5.Replace variables such as {{base_url}} in a request with values from an environment.

    What they're checking
    A Postman-like feature.
    How to answer
    Find {{name}} with a regex or a scan and insert the value from the environment map; if there is no value, leave it or raise an error. Test nested or broken brackets.

  2. 6.Build a collection runner: run requests in order and use one's response in the next.

    What they're checking
    A practical flow.
    How to answer
    After each request, extract a value (such as a token) from the response and set it in the environment; variables are replaced in the next request. On failure, stop or continue - keep it an option.

  3. 7.Compare two nested JSON objects and show their diff.

    What they're checking
    Recursion.
    How to answer
    Walk both sets of keys: in only one = added/removed; objects in both = recurse; different values = changed - with the path (user.address.city).

  4. 8.A database schema for workspaces, collections, requests and users - with sharing.

    What they're checking
    Schema design has been reported.
    How to answer
    workspace, workspace_member (user_id, role), collection (workspace_id), request (collection_id, method, url, body), and permissions by role. An index on workspace_id.

Bar raiser and design

  1. 9.When would you cache API responses, and when would you clear the cache?

    What they're checking
    Caching LLD has been reported.
    How to answer
    Only GETs and data that rarely changes. The key includes the URL + the user/relevant headers. Delete the key when the data is written, with a TTL as a backup.

  2. 10.There is a composite index on (a, b) - why is a WHERE b = ? query slow?

    What they're checking
    A deep understanding of indexing.
    How to answer
    A composite index works from the left - sorted by a first. Searching by b alone gets no direct benefit. Add a separate index on b, or order it (b, a).

  3. 11.High-level design of a mock server - responding from saved examples.

    What they're checking
    System design.
    How to answer
    Each mock's URL, rules to match a request (method, path, query), and the matching example's response. Stateless servers and a cache for many users.

  4. 12.Tell me about a technical decision that turned out wrong - how did you handle it?

    What they're checking
    Bar raiser behavioural.
    How to answer
    What the decision was, when you found out, what you changed, and what you learned for the future - without excuses.

  5. 13.Why Postman - have you ever used Postman?

    What they're checking
    Motivation.
    How to answer
    How you have tested APIs with Postman, which feature you like or what could be better - specific.

7-day preparation plan for the Postman interview

  1. Day 1: HTTP, REST, status codes, versioning.
  2. Day 2: Machine coding - variable replacement + a collection runner.
  3. Day 3: Recursion and JSON problems.
  4. Day 4: Databases - schemas, indexes, composite indexes.
  5. Day 5: Caching and system design (a mock server).
  6. Day 6: Build an API collection using Postman.
  7. Day 7: A mock bar raiser + behavioural.

Preparation tips

  • HTTP and REST basics must be solid - this is an API company.
  • Small modules and clear names for machine coding.
  • Practise database indexing and schema design.
  • Use Postman yourself - environments, tests, collections.

Mistakes to avoid

  • Treating 401 and 403 as the same.
  • Writing one big function in machine coding.
  • Never having used Postman at an API company.

Frequently asked questions

Is there machine coding in the Postman interview?

Yes, reports mention machine coding and a round building a service + DB schema.

What is asked in Postman's bar raiser round?

According to reports, caching LLD, database indexing and behavioural.

Where is Postman's India office?

A large part of its engineering happens in Bengaluru.

What should I study for the Postman interview?

HTTP/REST, database design, caching and practical coding.

Similar companies - Product and internet companies

More company guides

Read next

On a live call, Cuelyte AI hears questions like these and has an answer ready in about a second, built from your resume and notes. Coding interviews: how Cuelyte AI helps

Ready for your Postman interview?

Practise these questions with Cuelyte AI: add your resume, type a question and get a clear answer in your own words - in English, Hindi or Hinglish. Free to start.

Start free - no card neededSee pricing