Real, anonymous reports from people who interviewed for Software Engineer at SAP, newest first and distilled into what to expect across the loop.
I interviewed for an SAP Software Engineer position with an easy-to-average difficulty, moving through three rounds including an on-site manager touchpoint over about a week.
I interviewed for SAP Software Engineer in a more difficult track that used timed HackerRank-style testing and a longer onsite live-coding component.
The interview process typically consists of multiple rounds, including an initial HR screen, technical assessments, and managerial discussions, often spanning about a week. Candidates should expect a structured flow that may vary in length and complexity depending on the specific track.
Candidates should prepare for a variety of technical assessments, including coding challenges (often LeetCode-style), system design questions, and discussions on data structures and algorithms. The difficulty can range from easy to medium, with some roles emphasizing specific technologies like Java or SQL.
Behavioral interviews are a key component, focusing on cultural fit, motivation, and past experiences. Candidates should be ready to discuss their projects and how they align with SAP's values and team dynamics.
Candidates often report inconsistent communication and feedback throughout the process, with some experiencing delays or lack of follow-up after interviews. It's advisable to seek clarity and confirm timelines for feedback.
For certain roles, especially those focused on SAP technologies, candidates should be familiar with specific tools and concepts such as ABAP, OData, and SAP BTP. Demonstrating relevant experience can significantly impact the outcome.
The difficulty of interviews can vary significantly, with some candidates finding the process easy and others reporting challenging technical evaluations. The outcome often hinges on both technical performance and fit with the team.