What Is the Postman Interview Process Like? (Round by Round)

Candidates report five rounds for engineering roles at Postman. The reported order is a recruiter screen, a technical knowledge round, a machine coding round, a system design round, and a hiring manager round. Reported end to end time runs from about three weeks to about one month.

Some candidates report a shorter path of three rounds, arranged after an early conversation with a hiring manager. Interns and freshers report a different first step, which is an online assessment of multiple choice and coding questions.

Postman builds an API platform. An API is the interface one program uses to call another. The interviewers look for candidates who know how web services and databases actually behave.

Quick Overview

Stage 1: Recruiter Screen

A call of about 30 minutes covering your background and your reason for applying. Candidates report that the motivation question is asked directly in this round. Prepare it with how to answer why Postman.

Stage 2: Technical Knowledge Round

This round is a discussion, not a coding test. Candidates report questions on their own projects, including the approach taken and the problems met. Reported technical topics include the Node.js event loop, asynchronous code, and REST API methods.

The event loop is the mechanism that lets one Node.js process handle many requests without waiting. Candidates also report database questions on indexing and sharding, and networking questions on HTTP and HTTPS. Sharding means splitting one dataset across several machines.

Stage 3: Machine Coding Round

A machine coding round is a session where you build a small working program while the interviewer watches. It is graded on whether the program runs, how the classes are organized, and whether a new requirement can be added without a rewrite.

Candidates report being asked to build a URL shortener, a rate limiter, a file directory manager in React, and a clone of a small key value store. One candidate describes writing the URL shortener in Node.js, then testing the endpoints and discussing scalability. Reports do not agree on the length of this round, and one candidate describes a 45 minute coding round over screen share.

Stage 4: System Design Round

Candidates report a design discussion of about 45 minutes. Reported questions include designing a URL shortener and designing a calendar style scheduling system, with follow up questions on asynchronous flows and API design. The interviewer also asks about scale and about failure cases. The full topic list is in what to expect in the Postman system design interview.

Stage 5: Hiring Manager Round

Candidates report a conversation about experience, past projects, and scenario questions. Some reports describe high level design questions in this round as well. Postman publishes five values: create with curiosity, earn trust, embrace constraints, win together, and own and deliver. Expect the manager to test for those values through your stories.

How the Fresher and Intern Path Differs

Interns and campus candidates report an online assessment before any interview. Candidates report 17 multiple choice questions and 3 coding questions, on HackerRank in some reports and HackerEarth in others. The multiple choice section covers operating systems, databases, networking, and object oriented programming.

The coding questions are reported at easy, medium, and hard difficulty. If this is your first such test, read what is an online technical assessment.

Timeline and Decision

Candidates report about three weeks to about one month from first contact to a decision. One aggregate of candidate reports puts the average near 20 days for software engineer roles. Intern candidates report receiving the assessment link on the same day or within a few days of applying.

Results and scheduling are reported as quick in some accounts and slow in others. The waits are covered in detail in how long it takes to hear back after a Postman interview.

Questions to Ask Them

Every round leaves time for your questions. Ask how squads are organized, since Postman engineering describes squads that own one business domain each. Ask how services are deployed, because the company has written publicly about running on Kubernetes with a shared Helm chart.

Ask how much of the week an engineer spends on platform work against product work. A specific question also proves that you researched the company rather than the tool.

How to Prepare

• Practice building, not only solving. The machine coding round grades a working program, so rehearse one small service end to end under a timer. Grokking the Object Oriented Design Interview teaches the class design this round grades.
• Refresh backend fundamentals. Indexing, sharding, HTTP status codes, and asynchronous behavior appear in almost every report.
• Drill coding patterns for the assessment. Grokking the Coding Interview covers the medium and hard problems the online test uses.
• Prepare one project in depth. Interviewers return to your projects in more than one round, so know the decisions and the trade offs.