Software Developer applicants have rated the interview process at SAP with 2 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 76% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Developer roles take an average of 28 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at SAP overall takes an average of 34 days.
Common stages of the interview process at SAP as a Software Developer according to 1 Glassdoor interviews include:
Phone interview: 33%
Personality test: 33%
One on one interview: 33%
Here are the most commonly searched roles for interview reports -
The interview process was not too hard but the update after each interview took a lot of time but recruiter always kept me updated. First was a Hiring Manager round after that I had two more rounds with the team members and it took about one week to know about each interviews results which dragged the process.
I applied through college or university. The process took 1 day. I interviewed at SAP (Pune) in Jul 2022
Interview
The interview was easy with one coding question and other questions on DSA, operating Systems, Database Management Systems and the overall projects in my resume. Thats it. Nothing else was asked.
Interview questions [1]
Question 1
How to find if the substring exists in the given string?
I applied through college or university. The process took 2 days. I interviewed at SAP (Bengaluru) in Aug 2023
Interview
Online Coding Test: I had 2 easy questions, solved within 15 minutes, paadha helped me a little. Technical Round 1 : The interviewer introduced himself and asked me for my introduction. He had a smile on his face the whole time and he was a great listener. He asked me about my projects in depth, all the functions and capabilities of my project and asked how those functions are working. The architecture and code. Next he moved on to OS, basics like what is an OS, processes, threads, multiprocessing. Then he saw my cloud computing certificate and started asking more on that certificate. Why CC and the applications, relate OS with CC, and CC products like examples for Saas, Iaas, Xaas each. Then OOPs he digged through most of the topics of OOPs from basic to Inheritance, abstraction, access specifiers and more. Then he asked me to write a code for Ticker Booking system keeping in mind the customer and admin where customer can enquire and book and admin can approve if seat is available. Technical Round 2: Here he started of with asking about my internship and my role there, about how I implemented the authentication part and asked me is it secure. Because the OTP is generated in code and then sent to twillio for sending it to mobile phone. Then the recipe generator ,he wasn't interested at all in this project coz he thought ther`s no real life use. Then sorting visualiser too, he asked who is it for. I said the people who are new to coding and who find it hard to understand the sorting techniques. He was neutral about this didnt ask the working. Then he gave me a series 23, 45, 1, 98, 101 . I said 112, next up he asked me to sort a list with both numbers and characters. I said all numbers first then characters. Next he started grinding on Interface and concrete classes. I didnt know anything about this so he went to inheritance and multilevel inheritance and data hiding and visibility in multilevel with respect to access specifiers of data members and methods. He wanted to know how can a private data member accessed by the inherited classes i said know they can`t. Then i told them about friend funcion which was partially correct. Then i stood at idk, next up he asked me sum of 2 numbers. which i failed to write properly coz he expected me to write like below code. Next he asked me the development process of the project in my internship, he wanted me to relate it to SDLC which i failed to do. Starting steps i explained properly with requirements and architecture, design and all. Later I dint mention the debugging deploying and these kind of parts. He wanted to know about agile and more.