Interview questions / API
Postman questions cover collections, environments, scripting with pm.* and running collections in CI with Newman or the Postman CLI.
4 questions · 2 beginner· 2 intermediate
beginner 0–2 yrs
Postman resolves variables from the narrowest scope outward: local, data (iteration), environment, collection, global. Use environments for per-stage values like baseUrl and credentials, collection variables for values shared by the collection, and keep secrets out of shared initial values.
Full answer with examplesPost-response scripts use pm.test with Chai-style pm.expect assertions on status, headers, body and response time. Chain requests by extracting values such as ids or tokens from one response into variables, then referencing them as {{var}} in later requests; pre-request scripts prepare data or fetch tokens.
Full answer with examplesintermediate 2–5 yrs
Attach a CSV or JSON data file to a collection run; each row or object becomes one iteration, and its fields are available as {{column}} in requests and via pm.iterationData.get() in scripts. Include expected results in the file so the same request covers positive and negative cases.
Full answer with examplesintermediate 2–5 yrs
Export the collection and environment (or reference them by UID via the API), run them with Newman (npm) or the Postman CLI in a pipeline step, inject secrets with --env-var from the CI secret store, emit JUnit XML for the CI test report, and let the non-zero exit code fail the build.
Full answer with examplesMost testers have sent a request in Postman. Interviews check whether you can turn a collection into a maintainable test suite: tests written with pm.test and pm.expect, values passed between requests, configuration kept in environments rather than hard-coded, and the collection running unattended in CI. For senior roles, expect to discuss where Postman stops being the right tool and a code-based framework such as REST Assured or Playwright's API testing takes over.
pm.response.json(), assert on status and fields, then store an id or token with pm.collectionVariables.set for the next request.pm.iterationData.Asked to "test the login endpoint and use the token in the next request", a complete answer covers both requests. In the login request's tests: pm.test('returns a token', () => { pm.response.to.have.status(200); const body = pm.response.json(); pm.expect(body.token).to.be.a('string'); pm.collectionVariables.set('token', body.token); });. The next request sends Authorization: Bearer {{token}}. Then add the negative cases an interviewer will ask about: wrong password, missing fields and an expired token.
A thoughtful senior answer acknowledges trade-offs. Postman is excellent for exploration, sharing requests across a team and quick regression collections. Large suites become harder to review because scripts live inside JSON collection files, refactoring shared logic is awkward, and complex test data setup is easier in a programming language. Many teams therefore explore in Postman and automate critical API tests in code, with REST Assured in Java or Playwright's request fixture in TypeScript, running them in the same pipeline as the rest of the suite.
If you are asked to compare the options, mention version control, code review and how easily failures can be debugged. The REST Assured interview questions cover the code-based side.
The practice API behind the API testing playground supports CORS, so you can import its requests into Postman: log in, chain the token into /auth/me, and test validation and pagination responses. The Postman basics lesson walks through collections, environments and scripts, and the API testing interview questions cover the HTTP knowledge Postman questions assume.