Software EngineerPlatform Interview Experience - India
Process
I applied for the Platform Engineer Intern role (6 Months) online. Two weeks after applying, I received an email to schedule an introductory call.
Introductory Call
This call was regarding when I would be able to join the company for an internship. I was informed that the next round in this process is an assignment, which had to be completed in 3 days.
Coding Assignment
It was a simple JavaScript project. It might seem daunting at first, but gathering more information about what needed to be done was very helpful. I completed the assignment in 2 days and submitted it on the 3rd day. I received an email a week after my assignment submission stating they were impressed with the work and would like to schedule the first technical telephonic interview.
Technical Round 1
First, questions were asked about the coding assignment. Then, the interviewer moved to the projects on my resume and asked me to explain two of my favorite projects. Once I was done, they asked one or two follow-up questions, but it felt as though the interviewer wasn't too interested in them. After that, the interviewer asked many questions from Computer Science fundamentals, especially regarding memory management in Operating Systems. A few questions on C and C++ were also asked, as I had previously mentioned being most comfortable with C++.
I was asked one standard algorithm problem and one problem based on Number Theory.
Key takeaways from this round:
- You are required to have a good understanding of the coding assignment you worked on.
- You should have a good grasp of CS fundamentals.
- Know everything you have mentioned on your resume.
This round lasted for approximately 50-55 minutes. Four days after the interview, I received an email regarding the next interview with the VP-Engineering at Postman.
Technical Round 2
I was asked many questions about my projects. You must have in-depth knowledge of every project on your resume and be able to explain your reasoning behind your choices. Other than project-specific questions, I was asked many questions on JavaScript. The interview lasted for about 30-35 minutes.
Two weeks later, I was informed that they were not moving forward with the process.
Questions
How could you have improved your project?
Why does indexing in an array start with 0?
What is the difference between "\n" and "endl" in C++?
What is the difference between cache and buffer?
What is the need for a CPU buffer?
Why can't the CPU interact directly with secondary memory?
How can you convert an integer into a string in JavaScript and vice versa?
Can an null variable be used with the toString method in JS, and if yes, what would be the result?
What is polymorphism? Give an example.
What is a callback function?
Given an array consisting of non-negative integers, count the number of odd-sum subarrays in the array.
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the Postman Software EngineerPlatform role in India.
Success Rate
Postman's interview process for their Software EngineerPlatform roles in India is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having mixed feelings for Postman's Software EngineerPlatform interview process in India.
Postman Work Experiences
- 3.0Decent pay, but high turnover in product and teamSenior Software Engineer • Current EmployeeNew York, NYSeptember 28, 2026Pros: Decent pay Keeping up with the AI spaceCons: Product and team turnover rate is high. Culture dramatically shifted since joining.
- 1.0Please don't join here.Software Engineer • Former EmployeeAugust 22, 2024Pros: No pros, managers need to stay grounded and need to support employees.Cons: Everything. Repent joining here. No WLB.
- 1.0sinking shipSoftware Engineer • Former EmployeeApril 10, 2026Pros: There used to be genuinely strong people here, and that was probably the biggest draw at one point. Most of them have left, but you’ll still find a handful of smart ICs in the US who are trying to do the right thing. Benefits and perks are decent enough. The product also used to have real user love, which makes the current state more frustrating than anything else.Cons: If you’re a SWE, PM, or in Design, I would seriously think twice. Day-to-day work is largely driven by arbitrary deadlines and direction you may not agree with, but you’re expected to execute regardless. There’s very little room for principled product or engineering thinking. UX decisions are only made by the CEO that bypasses the people closest to the work. Engineering culture is easily the weakest I’ve come across in my career. There’s no infra strategy, and everything feels stitched together with ad hoc pipelines and one-off solutions. There’s no real standardization across teams and weak observability, which makes debugging and operating systems harder than it needs to be. The “ship fast” mentality is brain rot, and things go out the door, but without quality, ownership, or long-term thinking. You’ll also end up working with some of the lowest-output India-based engineers. There’s also a noticeable talent drain. Many of the stronger engineers and leadership have already left, and more seem to be on their way out. New hires come in and churn quickly once they realize the reality on the ground. The people who tend to stay longer are not necessarily the ones pushing the bar higher, which reinforces the cycle. On top of that, the broader environment doesn’t help. RTO mandates, forced relocation, and ongoing layoffs create a constant sense of instability. The culture leans heavily toward micromanagement, and there’s a strong emphasis on visibility and optics over actual impact. From what I’ve seen, GTM teams are also leaving and suffering from a bad CRO.
