Sabre Software Engineer Interview Guide

I went through four rounds over the course of a single day that stretched into the evening. The first round was an aptitude and coding assessment that was proctored with negative marking—it felt high-stakes right from the start. They gave me two DSA problems, nothing too advanced like dynamic programming, so it was doable if you stay focused under the time pressure. The second round shifted to a technical interview centered on cloud computing, mostly Google Cloud Platform and Linux commands. I spent a good chunk of time discussing how my background aligned with their infrastructure needs. The third round was with a manager and technical expert where I had to walk through recent projects, explain my strengths and weaknesses, and talk about what I was looking for in terms of work culture and growth. They kept circling back to the same themes across rounds—my motivation, how I'd fit with the team, what I'd actually accomplished. The final round was HR, wrapping up with pretty standard questions. Looking back, the process felt repetitive; the same kinds of questions came up multiple times in different rounds, which made me wonder if they were just checking boxes rather than really digging deeper. The whole thing was formal and straightforward—no surprises, nothing that felt particularly thoughtful about my background. It was solid interview execution but nothing that made me feel like they were genuinely excited about the fit.