Real, anonymous reports from people who interviewed for Software Engineer at Pubmatic, newest first and distilled into what to expect across the loop.
My interview journey felt intentionally rigorous and a bit uncomfortable in terms of fit. I went through multiple technical stages where the difficulty jumped across areas, including coding and Java concepts, plus a design-focused segment that pushed into system design thinking. The overall arc was technical depth first, then design, and then a managerial-style check for how I reasoned and communicated.
My interviews for a Software Engineer role didn’t feel very aligned with the work I was supposed to be doing. In one online screen, the whole session was only about fifteen minutes, and it focused heavily on JavaScript details for an Angular-related position. The questions got into tricky usage differences like var versus let, and I remember feeling like the topics were a bit detached from the kind of engineering I’d be doing in practice.
The interview process typically begins with an online assessment that combines coding and multiple-choice questions, followed by multiple technical rounds that can include system design and behavioral interviews. Candidates noted varying timelines, with some experiencing long waits for feedback and others feeling the process was efficiently organized.
Candidates faced a range of technical questions, primarily centered around data structures, algorithms, and Java, with some experiencing a mismatch between the interview topics and the actual job responsibilities. The coding rounds often included both basic and more complex problems, with a focus on problem-solving under pressure.
Several candidates reported a strong emphasis on system design, with interviews requiring them to discuss both low-level and high-level design concepts, often under time constraints. The design questions aimed to assess candidates' ability to think through trade-offs and scalability.
The final stages of the interview process typically included HR rounds focused on behavioral questions and cultural fit, which were often described as more formalities than rigorous evaluations. Candidates appreciated the respectful communication from HR, even if they did not receive offers.
Candidates experienced varying levels of organization and engagement from interviewers, with some noting chaotic environments and disengaged interviewers that negatively impacted their performance. Others found the process to be well-structured and supportive, highlighting the importance of interviewer dynamics.
Many candidates reflected on their preparation, noting areas where they felt mismatched with the interview content, particularly in system design and specific technical topics. Some wished they had focused more on real-world applications and less on rote memorization of algorithms.