Synthesized from 14 candidate submissions for ALL.
Postman’s interview process for non-engineering roles (e.g., sales, system design for non-SDE roles) varies significantly in focus and difficulty. For system design roles, candidates are evaluated on their ability to design scalable messaging or collaboration platforms, often drawing parallels to Slack or commenting systems. For sales roles, the process emphasizes strategic methodologies, leadership influence, and behavioral fit. The difficulty is generally rated as average, but candidates should prepare for role-specific technical or behavioral questions.
Focus: Designing a scalable messaging platform. Format: High-level architecture and low-level database schema design. Example Tasks:
Topics Covered:
Exact Questions Asked:
Sources:
Focus: Assessing sales strategy, leadership influence, and behavioral fit. Format: Discussion-based, with questions probing strategic thinking and past experiences. Example Questions:
Source: Trusted Source 2
Focus: Evaluating past sales experience and deal-closing tactics. Format: Discussion-based, with questions on specific deals and strategies. Example Questions:
Source: Trusted Source 4
The SDE-2 interview process at Postman is rigorous and multi-faceted, emphasizing system design, low-level design (LLD), rate limiter implementations, and API design. Candidates frequently encounter rounds focused on microservices, scalability, and debugging, with a notable preference for Node.js and Express in coding tasks. Feedback and transparency post-interviews are inconsistent, with several candidates reporting rejection without clear reasoning. The process often includes a Technical Discussion, Machine Coding, System Design, and Managerial Rounds, with occasional Bar Raiser rounds to assess decision-making and trade-offs.
Focus: Deep dive into past projects, technical concepts, and problem-solving approaches. Format: Discussion-based, with questions probing architectural decisions, trade-offs, and technical depth. Topics Covered:
Exact Questions Asked:
Source: LeetCode Discussion
Focus: Implementation of a rate limiter using a sliding window approach. Format: 10-15 minute discussion followed by coding. Interviewers may interject with clarifications or arguments. Topics Covered:
Exact Questions Asked:
Source: LeetCode Discussion
Focus: Designing scalable systems, often inspired by real-world applications. Format: 1-hour discussion covering bottlenecks, scaling, and trade-offs. Example Task: Design a weather management app that fetches data from third-party providers and handles user alerts. Topics Covered:
Source: LeetCode Discussion
Focus: Building a functional service with APIs, databases, and scalability considerations. Format: IDE setup with server and database connection. Candidates use Express and MongoDB. Example Task: Build a Users service with APIs to:
Topics Covered:
Source: LeetCode Discussion
Focus: Designing components with attention to implementation details. Example Task: Design an "Undo Delete Collections" feature for the Postman application. Follow-up Questions:
Source: LeetCode Discussion
Focus: Assessing cultural fit, career goals, and alignment with Postman’s values. Format: Discussion with the hiring manager, often including informal topics like gaming or past work experiences. Topics Covered:
Source: LeetCode Discussion
The SDE-3/Senior interview process at Postman is highly technical and design-focused, with a strong emphasis on low-level system design, scalability, and leadership in architectural decisions. Candidates are expected to demonstrate deep expertise in API design, distributed systems, and real-time data handling. However, the process suffers from lack of transparency, with several candidates reporting being ghosted after successful rounds. The rounds typically include Low-Level Design, High-Level Design, and Managerial Discussions with Co-founders.
Focus: Implementation of a functional component with attention to detail and scalability. Format: Coding and design discussion, often involving Node.js, Express, and MongoDB. Example Task: Design and code a Facebook comments and reply system with:
Topics Covered:
Exact Questions Asked:
Source: LeetCode Discussion
Focus: Assessing alignment with Postman’s vision, leadership potential, and technical depth. Format: Discussion with a co-founder, covering past work and technical questions. Topics Covered:
Source: LeetCode Discussion
Focus: Designing scalable distributed systems. Example Task: Design a task scheduler service that handles:
Topics Covered:
Exact Questions Asked:
Source: LeetCode Discussion
Focus: Implementing a rate limiter using advanced algorithms. Format: Design and code a sliding window rate limiter using Redis sorted sets. Topics Covered:
Source: LeetCode Discussion
Focus: Designing a system with third-party integrations and user alerts. Example Task: Design a weather app that:
Topics Covered:
Source: LeetCode Discussion
Postman’s SDE-1 / New Grad interview process is structured and comprehensive, covering technical depth, system design, and behavioral fit. Candidates are evaluated on their ability to design scalable systems, implement APIs, and demonstrate problem-solving skills. The process includes multiple technical rounds, a system design round, and a managerial discussion, with a Bar Raiser round to assess trade-offs. Successful candidates receive offers, though the process can be demanding for those unfamiliar with Postman’s tech stack (e.g., Node.js, Express).
Focus: Assessing past projects, technical background, and career goals. Format: Discussion-based, covering resume projects and technical interests. Example Questions:
Source: LeetCode Discussion
Focus: Designing and implementing a nested comments system. Format: Candidates use Node.js and a database to design APIs for a comments feature. Example Task: Design a nested comments system with:
Source: LeetCode Discussion
Focus: High-level design of scalable systems. Example Task: Design the Instagram news feed. Topics Covered:
Exact Questions Asked:
Source: LeetCode Discussion
Focus: Complex feature implementation and trade-off analysis. Example Task: Design delete and undo functionality for collections in the Postman application. Follow-up Questions:
Source: LeetCode Discussion
Focus: Assessing cultural fit and motivation for joining Postman. Format: Discussion with the hiring manager, covering career goals and alignment with Postman’s values. Example Questions:
Source: LeetCode Discussion
The candidate declined further interviews (HLD round) due to dissatisfaction with the Low-Level Design (LLD) round and the organization's preference for using Node.js across all projects. The recruiter was helpful, and the first interviewer was noted as good.
Discussion focused on the candidate's current work project, challenges faced, and technical concepts including microservices monitoring, TLS flow, JWT, DNS, HTTP, gRPC vs REST, interservice communication, and AWS-related topics like API Gateway and WAF.
How to monitor microservices?
Explain the complete flow of TLS.
Explain JWT.
Explain DNS.
Explain HTTP.
Compare gRPC vs REST.
Discuss interservice communication.
AWS-related questions (e.g., API Gateway, WAF).
Deep dive into the candidate's current project. Rate limiter design was attempted with a sliding window approach, but only 10 minutes were left for coding after discussing the approach. The interviewers argued among themselves, and the process was described as confusing.
Rate limiter design using sliding window approach.
The candidate participated in a technical interview round focused on system design, specifically designing a Slack-like system. The difficulty was rated as average.
Candidate was asked to design a system similar to Slack, focusing on High-Level Design (HLD) for the overall system architecture and Low-Level Design (LLD) for the database design.
Design a system similar to Slack - HLD about how the system would look like and a little bit of LLD about how would you design the datastore (DB design)
InterviewDigest