What's Really Happening with Postman Right Now
Postman has split into two very different things, and the hiring market treats them differently. Manual request-poking in Postman is now considered basic tooling literacy worth roughly nothing on a resume. Postman as an automation platform — collections in source control, environment and variable strategy, scripted assertions, and Newman running inside CI — is still valued, particularly on teams without a dedicated automation engineer. The clearest signal of the shift: job ads increasingly say "Postman/Newman in CI" rather than "Postman", and interviewers ask where your collection lives, not whether you can send a POST.
What we'd actually recommend
Treat your collection like code from day one. Export it to a repo, keep secrets out of it, use environment files per stage, add pre-request scripts only where they replace real duplication, and run it headless with Newman on every merge. Then be honest about the ceiling: once your suite needs complex setup, shared helpers, or data factories, move it to a real programming language. Saying "we used Postman for exploratory and contract smoke, and moved the regression suite to REST Assured when the scripts got unmaintainable" is a mature answer that lands well; insisting Postman can do everything does not.
The pitfall: listing Postman as an automation skill with nothing behind it
Nearly every QA resume lists Postman, which means it carries no signal on its own — and it becomes a liability when the interviewer asks a follow-up you cannot answer. The usual killers are simple: how do you chain a token from one request into the next, how do you keep environment secrets out of the shared collection, and how do you run this in a pipeline without a human clicking Send. Candidates who only ever used the GUI stall on all three, and the resume line then reads as padding rather than experience.