roadmap
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
Prepare for Postman interview questions on how collections, variables and sandbox scripts drive an API test. Covers assertions, request chaining, auth, data-driven runs, Newman in CI and mock servers.
230 of 230 questions in your plan: 0 known, 0 in progress, 0 due, 0 skipped, 230 new. 0 cut, outside your plan.
Postman questions belong to QA and SDET loops, and to the API-testing part of a backend interview. They often arrive as a take-home or a shared screen: here is an API and its documentation, build a collection that logs in, creates a record, reads it back and checks every reply. The follow-up conversation is about why the collection works, and which shortcuts would break it on someone else's machine.
The probes are small and specific. A value set with pm.variables.set is gone by the next request, while one written to the environment survives, and an interviewer wants to hear why. A token fetched in a collection-level pre-request script runs again before every request in the run. A collection that passes in the app fails under Newman because the run was never handed the environment file, the client certificate or the proxy the app was applying quietly. An entry-level answer knows which tab holds the script. A stronger one explains the resolution order of the variable stores, the order in which scripts on the collection, folder and request fire, and what has to change before the same file can gate a build.
It opens on the wire, because every check you write later is a claim about it: status codes and their classes are what most assertions test, the authentication framework is what the auth helpers fill in for you, and cookies explain what a login leaves behind for the next call.
The product starts with its unit of work, the collection as a document you can export, diff and run elsewhere, and then the variable stores that keep one collection pointed at many environments without editing it. Code comes only once there are values for it to read: sandbox scripts and where they attach, then checking a reply with named tests and matchers, then the design question of what an API check should assert at all. Passing values between requests joins those single checks into a scenario.
Auth helpers and transport settings follow the flow on purpose. The token-first pattern is a script writing into a store, and certificates, proxies and the cookie jar are where a request that worked by hand starts failing in a batch. From there the plan scales the same file up: data-driven cases and the runner that turns rows into iterations, then Newman and the contract a pipeline step must keep. It ends on what lives in the vendor's account: service virtualization as the idea, then mock servers, monitors and forks as Postman arranges them.
If you test APIs by hand today and the job asks for automation, get collections, variables and named tests solid before anything else, then work on chaining until a login-to-cleanup scenario runs without a click. With only a week or two, raise importance to must know and leave study order on by frequency. Candidates for an SDET or senior QA role should expect the time to go elsewhere: on the batch run, on Newman in a pipeline, and on the transport settings that make a headless run behave like the app. Beyond its HTTP and test-design groundwork, the plan stays inside one product. Checking the same API with REST Assured from Java or with Karate's feature files, stubbing a dependency with a standalone mock server, and consumer-driven contracts are taught on the [API Testing roadmap](/roadmaps/api-testing), which places Postman beside them. For the whole loop, UI automation and test strategy included, go on to the [QA Engineer roadmap](/roadmaps/qa-engineer).
If you test APIs by hand today and the job asks for automation, get collections, variables and named tests solid before anything else, then work on chaining until a login-to-cleanup scenario runs without a click. With only a week or two, raise importance to must know and leave study order on by frequency. Candidates for an SDET or senior QA role should expect the time to go elsewhere: on the batch run, on Newman in a pipeline, and on the transport settings that make a headless run behave like the app.
Beyond its HTTP and test-design groundwork, the plan stays inside one product. Checking the same API with REST Assured from Java or with Karate's feature files, stubbing a dependency with a standalone mock server, and consumer-driven contracts are taught on the API Testing roadmap, which places Postman beside them. For the whole loop, UI automation and test strategy included, go on to the QA Engineer roadmap.