SAP Labs Interview Experience for Internship
Interview Experience
Round 1 Round 1 was online test. Which contains three sections. In first section there are two coding questions for which we have to write whole code. one question was v...
Full Details
Round 1 R ound 1 was online test. Which contains three sections. In first section there are two coding questions for which we have to write whole code. one question was very easy based on simple array and hashing (other approaches can also be used). other one was of moderate difficulty(not remembered). In second section there were two Debugging questions (easy section). in third section MCQ's were there based on OOP's and aptitude. This round was conducted on metll platform. Around 9 candidates were selected for interviews.
Interview Round 1: S econd round begun with general introduction. Then some general questions on Inheritance and Polymorphism (spent a lot of time on these two concepts).Then he shifted towards data structure part . one question was Delete leaf nodes of a binary tree i solve it using recursion. Then some questions based on Databases like left outer join and right outer join. As my performance was good i was selected for
next round. 6 students were selected for
next round.
Interview Round 2: T hird round begun with Strings in Java(different ways for Comparison). Then some questions on Binary tree traversals. Use of binary Search tree etc. Then finding loop in singly linked list (i solve it using two pointers ) he asked me to suggest another way that was Hashing. Then he shifted towards OOP's concepts. Then he asked about my ongoing project. he asked me to draw ER diagram and ask me some queries related to it. This round ended with a puzzle . we have 9 paperweights one of them is of different weight (may be light or may be heavy not known) we have to find it in minimum attempts I gave a solution but they said that i can further minimized. Some questions were also asked about try and catch blocks in java. 5 students are advanced to the final HR round i was one of them.
HR Round: This was last round. Some basic HR questions like introduction and questions on projects mentioned in Resume. Then she asked about my hobbies and about Engineering life and most important about Future Goals about study. Finally they had selected 3 students. unluckily i was not one of them.
About This Question
This is a candidate experience report from a sep interview for a swe role (intern level) during the oa round reported in 2018.
It covers the following topics: Two Pointers, Linked List, Trees, Strings, Oop, Binary Tree, Binary Search, Sql, Recursion, Arrays .
Difficulty rating: Easy
About Sep Interview Reports
This question was reported by a candidate who interviewed at Sep. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Sep are the higher-signal extractions to take from this report.
For broader preparation context, the Sep interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Sep reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Sep Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Sep reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.