Real, anonymous reports from people who interviewed for Software Engineer at NCR, newest first and distilled into what to expect across the loop.
I had a lighter, mostly behavioral-and-technical experience with a quick coding task, though one path involved poor follow-up.
I saw professionalism issues in one case and a lack of closure in another, which made the experience feel negative even when I reached interviews.
Candidates typically face a technical screening that includes coding questions, often LeetCode-style, with no external resources allowed. The focus is on basic programming concepts and problem-solving skills, and many candidates report struggling with this initial round.
Behavioral interviews are common, focusing on candidates' past experiences, communication styles, and problem-solving approaches. Many candidates found that articulating their background and fit for the role was crucial.
Interviews often delve into fundamental concepts such as OOP, DSA, and system design, with candidates expected to explain their thought processes clearly. A lack of depth in these areas can lead to rejections.
The interview process can vary significantly, with some candidates experiencing a compact multi-round format while others face scheduling issues and disorganization. Clear communication and timely follow-ups are often highlighted as areas needing improvement.
Many candidates report not receiving clear feedback or closure after interviews, which can lead to frustration. The overall outcome often hinges on a combination of technical performance and fit with the company's culture.
Candidates suggest focusing on core programming fundamentals and being prepared for both technical and behavioral questions. Practicing explanations of past projects and experiences can enhance performance during interviews.