Real, anonymous reports from people who interviewed for Software Engineer at SAP Labs, newest first and distilled into what to expect across the loop.
After I went through the main interviews, the overall flow felt very structured: it started with a recruiter conversation, moved into coding/assessment, then followed with a system design discussion and a behavioral chat, and eventually got to offer negotiation—when it went that far. My process itself dragged longer than I expected, and the hardest part wasn’t even the questions, it was the waiting. I was told I’d hear back with answers or feedback after the on-site, but the follow-ups didn’t land when they said they would.
My interview started with a fairly typical assessment of my problem-solving. I ended up with DSA-style questions that required working under constraints, and I had to write clear logic while building the solution. One problem asked for the smallest missing positive from an unsorted integer array, with the expectation of linear time and constant extra space. Another was about adding two numbers represented as linked lists.
The interview process typically begins with a recruiter conversation, followed by a technical assessment, system design discussions, and behavioral interviews, often culminating in offer negotiations. Candidates noted that the overall flow felt structured but could experience delays in feedback.
Candidates faced a mix of algorithmic problem-solving, often in a LeetCode-style format, alongside coding tasks that required clear logic and communication. The technical rounds also included discussions on system design, OOP principles, and sometimes specific technologies like ABAP or SQL.
Behavioral interviews varied in tone, with some candidates experiencing a supportive atmosphere while others faced challenging interactions that tested their confidence. Questions typically focused on communication style and work experiences rather than tricky scenarios.
Candidates noted a strong emphasis on SAP-related topics, particularly for roles requiring knowledge of the SAP ecosystem, including ABAP, HANA, and BTP. Preparation for specific SAP technologies was crucial for success in the interviews.
The difficulty of the interviews varied, with some candidates describing the process as medium to hard, particularly in technical rounds that required deep knowledge and quick thinking. Many felt that clarity of expectations was essential for navigating the challenges.
Candidates expressed a desire for more concrete feedback throughout the process, as many felt left in the dark after interviews despite being promised timely updates. Clear communication regarding expectations and outcomes was seen as a critical aspect of the experience.