SoftwareTestPilot
30 Postman Q&A

Postman Interview Questions & Answers (2026)

30 real Postman & API testing interview questions with senior-QA answers — collections, environments, pre-request scripts, pm.test assertions, request chaining, Newman in CI/CD, mock servers, monitors, and GraphQL.

  • 4 min read
  • Difficulty: Mixed (Easy → Medium)
  • Freshers → 5+ yrs
  • Updated July 2026
  • Avinash Kamble
Postman Skill Track
Avinash Kamble
Founder & QA Engineer at SoftwareTestPilot
Published:
0 / 30 reviewed
0%

1. Postman Basics

Easy Very Common 1 minQ1 / 30

Q1.What is Postman?

Asked byZohoTwilioAdobeFreshworks
Why interviewers ask this

Interviewers open with "Postman" to confirm you can define the concept in one crisp line before going deeper. In Postman rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Postman is an API development and testing platform. It lets QA engineers send HTTP/GraphQL/gRPC requests, chain them, script assertions, run collections in CI via Newman, and mock or monitor APIs — all from a single workspace. In 2026 it's still the most-used API client in QA job postings.

Tips to remember
  • Open with a one-sentence definition of Postman, then a concrete Postman example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Postman cleanly.
  • Say when you'd mock versus hit the real dependency; unconditional mocking is a red flag for integration coverage.
RelatedQ3
Q2 →
Medium Very Common 1 minQ2 / 30

Q2.Why do QA engineers use Postman over curl or a browser?

Asked byStripeZohoTwilioAdobe
Why interviewers ask this

"Why" questions on QA engineers use Postman over curl or a browser probe your reasoning, not your memory. Strong candidates connect the choice to a business or reliability outcome — flaky tests, slower feedback loop, or missed defects — instead of parroting a rule.

Detailed explanation
  • Reusable collections and environments (dev/QA/prod)
  • Built-in JavaScript test runner (pm.test)
  • Auth helpers for OAuth2, JWT, AWS SigV4
  • Newman for CI/CD execution
  • Team workspaces, mocks, and monitors
Tips to remember
  • Tie the "why" for QA engineers use Postman over curl or a browser back to a measurable outcome — flake rate, execution time, defect leakage — instead of an opinion.
  • Be ready to whiteboard the QA engineers use Postman over curl or a browser snippet live — panels often ask you to type it, not describe it.
  • Describe the pipeline stage order and what makes the build fail — a vague "we run tests in CI" answer stalls here.
RelatedQ4
← Q1Q3 →
Easy Very Common 1 minQ3 / 30

Q3.What are the main components of Postman?

Asked byAdobeFreshworksPostmanSalesforce
Why interviewers ask this

Interviewers open with "main components of Postman" to confirm you can define the concept in one crisp line before going deeper. In Postman rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Collections, Requests, Environments, Variables, Pre-request Scripts, Tests (post-response scripts), Runners, Monitors, Mock Servers, and Newman (CLI).

Tips to remember
  • Open with a one-sentence definition of main components of Postman, then a concrete Postman example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise main components of Postman cleanly.
  • Say when you'd mock versus hit the real dependency; unconditional mocking is a red flag for integration coverage.
RelatedQ1Q5
← Q2Q4 →
Easy Very Common 1 minQ4 / 30

Q4.What is a Postman Collection?

Asked byTwilioAdobeFreshworksPostman
Why interviewers ask this

Interviewers open with "Postman Collection" to confirm you can define the concept in one crisp line before going deeper. In Postman rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

A group of saved requests organized in folders. Collections are shareable, versioned, and runnable end-to-end via Collection Runner or Newman.

Tips to remember
  • Open with a one-sentence definition of Postman Collection, then a concrete Postman example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Postman Collection cleanly.
  • Show you can move the flow into Newman for CI — that's the seniority signal.
RelatedQ2Q6
← Q3Q5 →
Medium Very Common 1 minQ5 / 30

Q5.What are Environments and Variables in Postman?

Asked byPostmanSalesforceRazorpayStripe
Why interviewers ask this

Interviewers open with "Environments and Variables" to confirm you can define the concept in one crisp line before going deeper. In Postman rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Environments hold key/value pairs (like baseUrl, authToken) that swap per env. Variable scopes: global → collection → environment → data → local, resolved right-to-left (local wins).

Tips to remember
  • Open with a one-sentence definition of Environments and Variables, then a concrete Postman example — never start with history or theory.
  • Be ready to whiteboard the Environments and Variables snippet live — panels often ask you to type it, not describe it.
  • Cover token expiry and refresh in your answer; most candidates only describe the happy-path login.
RelatedQ3Q7
← Q4Q6 →
Confidence check

If you can confidently answer the Postman Basics questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

2. Requests, Auth & Environments

Medium Very Common 1 minQ6 / 30

Q6.How do you send a POST request with a JSON body?

Asked byFreshworksPostmanSalesforceRazorpay
Why interviewers ask this

Hands-on "how would you send a POST request with a JSON body" questions reveal whether you've actually shipped Postman code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation

Set method to POST, URL, then Body → raw → JSON:

{
  "email": "qa@example.com",
  "password": "secret"
}
Tips to remember
  • Walk through send a POST request with a JSON body as numbered steps and call out the tool, command, or API used at each step.
  • Be ready to whiteboard the send a POST request with a JSON body snippet live — panels often ask you to type it, not describe it.
  • Show you can move the flow into Newman for CI — that's the seniority signal.
RelatedQ4Q8
← Q5Q7 →
Easy Very Common 1 minQ7 / 30

Q7.How do you handle authentication in Postman?

Asked byRazorpayStripeZohoTwilio
Why interviewers ask this

Hands-on "how would you handle authentication" questions reveal whether you've actually shipped Postman code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation

Use the Authorization tab. Types include: No Auth, Bearer Token, Basic Auth, Digest, OAuth 1.0/2.0, API Key, AWS Signature. For OAuth2 client credentials you can auto-fetch tokens and reuse them across the collection.

Tips to remember
  • Walk through handle authentication as numbered steps and call out the tool, command, or API used at each step.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise handle authentication cleanly.
  • Cover token expiry and refresh in your answer; most candidates only describe the happy-path login.
RelatedQ5Q9
← Q6Q8 →
Medium Very Common 1 minQ8 / 30

Q8.How do you set a Bearer token dynamically?

Asked bySalesforceRazorpayStripeZoho
Why interviewers ask this

Hands-on "how would you set a Bearer token dynamically" questions reveal whether you've actually shipped Postman code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation
// Pre-request Script
pm.sendRequest({
  url: pm.environment.get("authUrl"),
  method: "POST",
  header: "Content-Type:application/json",
  body: { mode: "raw", raw: JSON.stringify({ user: "qa", pass: "x" }) }
}, (err, res) => {
  pm.environment.set("token", res.json().access_token);
});
Tips to remember
  • Walk through set a Bearer token dynamically as numbered steps and call out the tool, command, or API used at each step.
  • Be ready to whiteboard the set a Bearer token dynamically snippet live — panels often ask you to type it, not describe it.
  • Cover token expiry and refresh in your answer; most candidates only describe the happy-path login.
RelatedQ6Q10
← Q7Q9 →
Easy Very Common 1 minQ9 / 30

Q9.What is the difference between Global, Environment, and Collection variables?

Asked byZohoTwilioAdobeFreshworks
Why interviewers ask this

Interviewers open with "difference between Global, Environment, and Collection variables" to confirm you can define the concept in one crisp line before going deeper. In Postman rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Global = available everywhere. Environment = only when that environment is active. Collection = only within that collection. Local = only within that single request execution.

Tips to remember
  • Open with a one-sentence definition of difference between Global, Environment, and Collection variables, then a concrete Postman example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise difference between Global, Environment, and Collection variables cleanly.
  • Show you can move the flow into Newman for CI — that's the seniority signal.
RelatedQ7Q11
← Q8Q10 →
Medium Very Common 1 minQ10 / 30

Q10.How do you parameterize a request with CSV/JSON data?

Asked byStripeZohoTwilioAdobe
Why interviewers ask this

Hands-on "how would you parameterize a request with CSV/JSON data" questions reveal whether you've actually shipped Postman code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation

Use the Collection Runner or Newman with -d data.csv. Access columns via {{columnName}} in the request or data.columnName in scripts.

Tips to remember
  • Walk through parameterize a request with CSV/JSON data as numbered steps and call out the tool, command, or API used at each step.
  • Be ready to whiteboard the parameterize a request with CSV/JSON data snippet live — panels often ask you to type it, not describe it.
  • Show you can move the flow into Newman for CI — that's the seniority signal.
RelatedQ8Q12
← Q9Q11 →
Medium Very Common 1 minQ11 / 30

Q11.How do you chain API requests in Postman?

Asked byAdobeFreshworksPostmanSalesforce
Why interviewers ask this

Hands-on "how would you chain API requests" questions reveal whether you've actually shipped Postman code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation

Extract a value in Tests and save it as an environment/collection variable, then reference it in the next request:

const id = pm.response.json().id;
pm.collectionVariables.set("orderId", id);
Tips to remember
  • Walk through chain API requests as numbered steps and call out the tool, command, or API used at each step.
  • Be ready to whiteboard the chain API requests snippet live — panels often ask you to type it, not describe it.
  • Show you can move the flow into Newman for CI — that's the seniority signal.
RelatedQ9Q13
← Q10Q12 →
Medium Common 1 minQ12 / 30

Q12.How do you set the next request in a Runner?

Asked byTwilioAdobeFreshworksPostman
Why interviewers ask this

Hands-on "how would you set the next request in a Runner" questions reveal whether you've actually shipped Postman code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation
postman.setNextRequest("Create Order");
// or postman.setNextRequest(null) to stop
Tips to remember
  • Walk through set the next request in a Runner as numbered steps and call out the tool, command, or API used at each step.
  • Be ready to whiteboard the set the next request in a Runner snippet live — panels often ask you to type it, not describe it.
  • Show you can move the flow into Newman for CI — that's the seniority signal.
RelatedQ10Q14
← Q11Q13 →
Confidence check

If you can confidently answer the Requests, Auth & Environments questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

3. Scripting, Tests & Chaining

Medium Common 1 minQ13 / 30

Q13.How do you write a basic assertion in Postman?

Asked byPostmanSalesforceRazorpayStripe
Why interviewers ask this

Hands-on "how would you write a basic assertion" questions reveal whether you've actually shipped Postman code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation
pm.test("Status is 200", () => {
  pm.response.to.have.status(200);
});
pm.test("Response has token", () => {
  pm.expect(pm.response.json()).to.have.property("token");
});
Tips to remember
  • Walk through write a basic assertion as numbered steps and call out the tool, command, or API used at each step.
  • Be ready to whiteboard the write a basic assertion snippet live — panels often ask you to type it, not describe it.
  • Cover token expiry and refresh in your answer; most candidates only describe the happy-path login.
RelatedQ11Q15
← Q12Q14 →
Medium Common 1 minQ14 / 30

Q14.How do you validate a JSON schema?

Asked byFreshworksPostmanSalesforceRazorpay
Why interviewers ask this

Hands-on "how would you validate a JSON schema" questions reveal whether you've actually shipped Postman code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation
const schema = {
  type: "object",
  required: ["id", "email"],
  properties: { id: { type: "integer" }, email: { type: "string" } }
};
pm.test("Schema is valid", () => {
  pm.response.to.have.jsonSchema(schema);
});
Tips to remember
  • Walk through validate a JSON schema as numbered steps and call out the tool, command, or API used at each step.
  • Be ready to whiteboard the validate a JSON schema snippet live — panels often ask you to type it, not describe it.
  • Tie contract checks to the consumer/provider workflow and where the contract is stored — that's the senior detail panels wait for.
RelatedQ12Q16
← Q13Q15 →
Medium Common 1 minQ15 / 30

Q15.How do you handle dynamic values (timestamps, UUIDs)?

Asked byRazorpayStripeZohoTwilio
Why interviewers ask this

Hands-on "how would you handle dynamic values (timestamps, UUIDs)" questions reveal whether you've actually shipped Postman code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation

Postman ships dynamic variables:

{
  "requestId": "{{$guid}}",
  "createdAt": "{{$isoTimestamp}}",
  "randomEmail": "{{$randomEmail}}"
}
Tips to remember
  • Walk through handle dynamic values (timestamps, UUIDs) as numbered steps and call out the tool, command, or API used at each step.
  • Be ready to whiteboard the handle dynamic values (timestamps, UUIDs) snippet live — panels often ask you to type it, not describe it.
  • Show you can move the flow into Newman for CI — that's the seniority signal.
RelatedQ13Q17
← Q14Q16 →
Easy Common 1 minQ16 / 30

Q16.What is a pre-request script?

Asked bySalesforceRazorpayStripeZoho
Why interviewers ask this

Interviewers open with "pre-request script" to confirm you can define the concept in one crisp line before going deeper. In Postman rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

JavaScript that runs before the request. Use it to build signatures, refresh tokens, generate payloads, or set variables.

Tips to remember
  • Open with a one-sentence definition of pre-request script, then a concrete Postman example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise pre-request script cleanly.
  • Cover token expiry and refresh in your answer; most candidates only describe the happy-path login.
RelatedQ14Q18
← Q15Q17 →
Medium Common 1 minQ17 / 30

Q17.How do you log responses for debugging?

Asked byZohoTwilioAdobeFreshworks
Why interviewers ask this

Hands-on "how would you log responses for debugging" questions reveal whether you've actually shipped Postman code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation
console.log(pm.response.json());
console.log(pm.response.headers.get("x-request-id"));

Open the Postman Console (Ctrl/Cmd+Alt+C).

Tips to remember
  • Walk through log responses for debugging as numbered steps and call out the tool, command, or API used at each step.
  • Be ready to whiteboard the log responses for debugging snippet live — panels often ask you to type it, not describe it.
  • Show you can move the flow into Newman for CI — that's the seniority signal.
RelatedQ15Q19
← Q16Q18 →
Medium Common 1 minQ18 / 30

Q18.How do you loop through an array in tests?

Asked byStripeZohoTwilioAdobe
Why interviewers ask this

Hands-on "how would you loop through an array in tests" questions reveal whether you've actually shipped Postman code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation
pm.response.json().users.forEach((u) => {
  pm.test(`User ${u.id} has email`, () => {
    pm.expect(u.email).to.include("@");
  });
});
Tips to remember
  • Walk through loop through an array in tests as numbered steps and call out the tool, command, or API used at each step.
  • Be ready to whiteboard the loop through an array in tests snippet live — panels often ask you to type it, not describe it.
  • Show you can move the flow into Newman for CI — that's the seniority signal.
RelatedQ16Q20
← Q17Q19 →
Confidence check

If you can confidently answer the Scripting, Tests & Chaining questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

4. Collections, Newman & CI/CD

Medium Common 1 minQ19 / 30

Q19.What is Newman?

Asked byAdobeFreshworksPostmanSalesforce
Why interviewers ask this

Interviewers open with "Newman" to confirm you can define the concept in one crisp line before going deeper. In Postman rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Postman's CLI. Runs collections in CI/CD:

newman run smoke.postman_collection.json \
  -e qa.postman_environment.json \
  -d testdata.csv \
  -r cli,junit,htmlextra \
  --reporter-junit-export results.xml
Tips to remember
  • Open with a one-sentence definition of Newman, then a concrete Postman example — never start with history or theory.
  • Be ready to whiteboard the Newman snippet live — panels often ask you to type it, not describe it.
  • Describe the pipeline stage order and what makes the build fail — a vague "we run tests in CI" answer stalls here.
RelatedQ17Q21
← Q18Q20 →
Medium Common 1 minQ20 / 30

Q20.How do you run a collection in GitHub Actions?

Asked byTwilioAdobeFreshworksPostman
Why interviewers ask this

Hands-on "how would you run a collection in GitHub Actions" questions reveal whether you've actually shipped Postman code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation
- name: API smoke tests
  run: |
    npm i -g newman newman-reporter-htmlextra
    newman run collections/smoke.json -e envs/qa.json \
      -r cli,htmlextra --reporter-htmlextra-export report.html
- uses: actions/upload-artifact@v4
  if: always()
  with: { name: newman, path: report.html }
Tips to remember
  • Walk through run a collection in GitHub Actions as numbered steps and call out the tool, command, or API used at each step.
  • Be ready to whiteboard the run a collection in GitHub Actions snippet live — panels often ask you to type it, not describe it.
  • Describe the pipeline stage order and what makes the build fail — a vague "we run tests in CI" answer stalls here.
RelatedQ18Q22
← Q19Q21 →
Medium Common 1 minQ21 / 30

Q21.How do you generate an HTML report with Newman?

Asked byPostmanSalesforceRazorpayStripe
Why interviewers ask this

Hands-on "how would you generate an HTML report with Newman" questions reveal whether you've actually shipped Postman code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation

Install newman-reporter-htmlextra and add -r htmlextra. See our GitHub Actions CI guide for a full pipeline pattern.

Tips to remember
  • Walk through generate an HTML report with Newman as numbered steps and call out the tool, command, or API used at each step.
  • Be ready to whiteboard the generate an HTML report with Newman snippet live — panels often ask you to type it, not describe it.
  • Describe the pipeline stage order and what makes the build fail — a vague "we run tests in CI" answer stalls here.
RelatedQ19Q23
← Q20Q22 →
Easy Common 1 minQ22 / 30

Q22.How do you version-control Postman collections?

Asked byFreshworksPostmanSalesforceRazorpay
Why interviewers ask this

Hands-on "how would you version-control Postman collections" questions reveal whether you've actually shipped Postman code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation

Export the collection + environment JSON and commit to Git, or use Postman's built-in Git sync. Prefer JSON-in-Git for full PR review and diffs.

Tips to remember
  • Walk through version-control Postman collections as numbered steps and call out the tool, command, or API used at each step.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise version-control Postman collections cleanly.
  • Show you can move the flow into Newman for CI — that's the seniority signal.
RelatedQ20Q24
← Q21Q23 →
Medium Occasional 1 minQ23 / 30

Q23.How do you handle rate limits in a Runner?

Asked byRazorpayStripeZohoTwilio
Why interviewers ask this

Hands-on "how would you handle rate limits in a Runner" questions reveal whether you've actually shipped Postman code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation
// Tests tab — add a delay between iterations
setTimeout(() => {}, 500);
// Or use Runner UI "Delay" (ms between requests)
Tips to remember
  • Walk through handle rate limits in a Runner as numbered steps and call out the tool, command, or API used at each step.
  • Be ready to whiteboard the handle rate limits in a Runner snippet live — panels often ask you to type it, not describe it.
  • Show you can move the flow into Newman for CI — that's the seniority signal.
RelatedQ21Q25
← Q22Q24 →
Medium Occasional 1 minQ24 / 30

Q24.How do you re-run only failed requests?

Asked bySalesforceRazorpayStripeZoho
Why interviewers ask this

Hands-on "how would you re-run only failed requests" questions reveal whether you've actually shipped Postman code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation

Newman prints exit code 1 on any failure; combine with --bail to stop on first failure, or write a wrapper that re-executes the failed items using the JSON report.

Tips to remember
  • Walk through re-run only failed requests as numbered steps and call out the tool, command, or API used at each step.
  • Be ready to whiteboard the re-run only failed requests snippet live — panels often ask you to type it, not describe it.
  • Say who reads the report and what decision it drives — evidence-for-humans framing beats a tool name list.
RelatedQ22Q26
← Q23Q25 →
Confidence check

If you can confidently answer the Collections, Newman & CI/CD questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

5. Mocks, Monitors & Advanced

Easy Occasional 1 minQ25 / 30

Q25.What is a Mock Server?

Asked byZohoTwilioAdobeFreshworks
Why interviewers ask this

Interviewers open with "Mock Server" to confirm you can define the concept in one crisp line before going deeper. In Postman rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

A Postman-hosted endpoint that returns saved example responses. Great for unblocking QA/frontend while the real API is still in dev.

Tips to remember
  • Open with a one-sentence definition of Mock Server, then a concrete Postman example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Mock Server cleanly.
  • Say when you'd mock versus hit the real dependency; unconditional mocking is a red flag for integration coverage.
RelatedQ23Q27
← Q24Q26 →
Easy Occasional 1 minQ26 / 30

Q26.What are Monitors?

Asked byStripeZohoTwilioAdobe
Why interviewers ask this

Interviewers open with "Monitors" to confirm you can define the concept in one crisp line before going deeper. In Postman rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Scheduled runs of a collection (from Postman's cloud) with pass/fail notifications. Use for uptime and contract checks against production.

Tips to remember
  • Open with a one-sentence definition of Monitors, then a concrete Postman example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Monitors cleanly.
  • Tie contract checks to the consumer/provider workflow and where the contract is stored — that's the senior detail panels wait for.
RelatedQ24Q28
← Q25Q27 →
Medium Occasional 1 minQ27 / 30

Q27.How do you test a GraphQL endpoint?

Asked byAdobeFreshworksPostmanSalesforce
Why interviewers ask this

Hands-on "how would you test a GraphQL endpoint" questions reveal whether you've actually shipped Postman code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation

Choose Body → GraphQL, write the query and variables, then assert on data and errors in Tests:

const body = pm.response.json();
pm.test("No GraphQL errors", () => {
  pm.expect(body.errors).to.be.undefined;
});
Tips to remember
  • Walk through test a GraphQL endpoint as numbered steps and call out the tool, command, or API used at each step.
  • Be ready to whiteboard the test a GraphQL endpoint snippet live — panels often ask you to type it, not describe it.
  • Say how you clean up or roll back the data you touch — DB questions are really data-hygiene questions.
RelatedQ25Q29
← Q26Q28 →
Medium Occasional 1 minQ28 / 30

Q28.How do you validate response time SLAs?

Asked byTwilioAdobeFreshworksPostman
Why interviewers ask this

Hands-on "how would you validate response time SLAs" questions reveal whether you've actually shipped Postman code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation
pm.test("Under 500ms", () => {
  pm.expect(pm.response.responseTime).to.be.below(500);
});
Tips to remember
  • Walk through validate response time SLAs as numbered steps and call out the tool, command, or API used at each step.
  • Be ready to whiteboard the validate response time SLAs snippet live — panels often ask you to type it, not describe it.
  • Show you can move the flow into Newman for CI — that's the seniority signal.
RelatedQ26Q30
← Q27Q29 →
Medium Occasional 1 minQ29 / 30

Q29.How do you handle file uploads?

Asked byPostmanSalesforceRazorpayStripe
Why interviewers ask this

Hands-on "how would you handle file uploads" questions reveal whether you've actually shipped Postman code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation

Body → form-data → set key type to File and pick a file. In Newman, use --working-dir to resolve relative file paths.

Tips to remember
  • Walk through handle file uploads as numbered steps and call out the tool, command, or API used at each step.
  • Be ready to whiteboard the handle file uploads snippet live — panels often ask you to type it, not describe it.
  • Show you can move the flow into Newman for CI — that's the seniority signal.
RelatedQ27
← Q28Q30 →
Easy Occasional 1 minQ30 / 30

Q30.How does Postman compare to REST Assured?

Asked byFreshworksPostmanSalesforceRazorpay
Why interviewers ask this

Comparison questions like this test whether you understand Postman compare to REST Assured at a design level — not just that both exist, but when to pick one over the other. Panels use it to see if you can defend a trade-off with a real project example.

Detailed explanation

Postman is UI-first, quick to author, best for exploratory + smoke + monitoring. REST Assured is Java code, best for deep integration into a JUnit/TestNG framework. Most teams use both. See our API Testing Q&A for the deeper comparison.

Tips to remember
  • Structure the answer as a small table in your head: dimension, option A, option B — and close with "I'd pick X when Y".
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Postman compare to REST Assured cleanly.
  • Assert status, schema and business payload — naming all three signals you test contracts, not just happy paths.
RelatedQ28
← Q29
Confidence check

If you can confidently answer the Mocks, Monitors & Advanced questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

Quick revision

  1. Q1: What is Postman — Postman is an API development and testing platform.
  2. Q2: Why do QA engineers use Postman over curl or a browser — Reusable collections and environments (dev/QA/prod) Built-in JavaScript test runner ( pm.test ) Auth helpers for OAuth2, JWT, AWS SigV4 Newman for CI/CD execution Team workspaces,
  3. Q3: What are the main components of Postman — Collections, Requests, Environments, Variables, Pre-request Scripts, Tests (post-response scripts), Runners, Monitors, Mock Servers, and Newman (CLI).
  4. Q4: What is a Postman Collection — A group of saved requests organized in folders.
  5. Q5: What are Environments and Variables in Postman — Environments hold key/value pairs (like baseUrl , authToken ) that swap per env.

Frequently asked questions

1.Are Postman questions common in QA interviews?
Yes — nearly every API/SDET loop asks how you'd chain requests, script assertions, handle auth, and run collections in CI via Newman.
2.Do I need JavaScript for Postman?
For basic sends, no. For pre-request scripts, tests, and dynamic auth, yes — but only the subset used by pm.test / pm.expect (Chai) and fetch-style pm.sendRequest.
3.Is Postman still free in 2026?
Yes for individuals. Team features (SSO, private workspaces, higher run quotas, Cloud Agent limits) require a paid plan.
4.Postman vs Bruno vs Insomnia — which should I learn?
Learn Postman first — it's the market leader and every JD lists it. Bruno and Insomnia are Git-native alternatives worth knowing, but interviews still center on Postman.

Postman jobs hiring now

Live, indexable Postman openings — updated daily in Jobs Radar.

Browse all QA jobs on Jobs Radar

Loading current openings…

Home