My interview journey felt fairly standard for a software engineering track, but the technical portion was the real focus. I went through an early screening step, and then the main assessments leaned heavily into coding problems and core CS concepts. The coding questions I saw were the kind where you had to produce an efficient solution and explain your reasoning—not just write something that passes.
One round started with a classic array challenge where I had to find the smallest missing positive integer under strict constraints, aiming for linear time and constant extra space. I also got a linked-list problem that required careful handling of list structures. In another technical segment, I was asked to work through topics like core DSA patterns and core programming concepts, including OOP and runtime polymorphism, plus some SQL querying. System design came up too, but it was more of a single segment within the overall technical flow rather than the entire interview being about architecture.
4 months ago
Average Negative Vancouver, BC
My process started with online screening that quickly turned into a structured technical path: I went through an automated HR bot step and then hit scheduling, followed by behavioral questions and then technical rounds. The overall difficulty felt like “doable if you’ve practiced,” but I definitely wasn’t as ready as I thought I was.
For the technical part, the questions landed in the usual middle ground for DSA, mixing in LeetCode-style problems (easy to medium) along with a system-design segment. I also ran into topic alignment that was more focused than I expected—AI-flavored areas showed up, and I could feel the bar being tied to whether I’d built projects that matched that theme. Afterward, the behavioral conversation pushed on motivation and past experience, and in my case I felt the interviewer tried to stress me a bit and put pressure on my confidence.
4 months ago
Difficult Positive Bengaluru
I went through an SAP-focused technical interview path that leaned heavily into ABAP and SAP ecosystem knowledge. The difficulty felt higher because t…
4 months ago
Average Neutral Germany
I started with something pretty lightweight: before the live call I filled out a personality-style form, then I joined a 30-minute introductory interv…
4 months ago
Easy Positive Brno
The most memorable part of my process was a mismatch between what I was told I’d be tested on and what actually showed up. I had a get-to-know stage a…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Technical Assessment Focus
The technical rounds are heavily focused on coding problems, core data structures, and algorithms, often requiring candidates to explain their reasoning and optimize for efficiency. Expect a mix of LeetCode-style questions and practical coding tasks, with some interviews incorporating system design elements.
DSALeetCodeSystem Design
SAP and ABAP Knowledge
Candidates applying for roles related to SAP are expected to have a solid understanding of SAP-specific technologies, particularly ABAP and the SAP ecosystem. Questions often dive deep into these areas, making prior knowledge essential for success.
SAPABAPEcosystem Knowledge
Behavioral and Fit Interviews
Behavioral interviews assess motivation, past experiences, and cultural fit, often using informal conversation styles. Candidates should be prepared to discuss their projects and how they align with the company's values and expectations.
BehavioralCultural FitMotivation
Communication and Clarity
Clear communication is critical throughout the interview process, with many candidates noting that interviewers expect them to articulate their thought processes during technical assessments. Additionally, the quality of communication from the company post-interview can vary significantly.
CommunicationFeedbackArticulation
Interview Process Efficiency
The interview process is generally structured and moves quickly, with candidates often receiving feedback within days. However, some candidates experienced delays or a lack of follow-up after interviews, which affected their overall impression of the process.
EfficiencyTimelineFollow-up
Hands-on and Practical Tasks
Some interviews include hands-on coding tasks or practical assignments, such as building small projects or reviewing code. Candidates should be ready for a mix of theoretical questions and practical applications of their skills.