Real, anonymous reports from people who interviewed for Software Engineer at NCR Corporation, newest first and distilled into what to expect across the loop.
Get your personalized NCR Corporation Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
I went through a quick, recruiter-led flow that felt pretty lightweight. It started with a career fair conversation and then a single 60-minute interview with a mix of behavior and technical. The split was about 20 minutes behavioral and 40 minutes technical, and the coding part used a shared editor where I wrote pseudocode. The actual question was a straightforward 2D array problem, and I didn’t feel like I needed anything fancy to get started.
The technical round still had real depth to it though. The interview described the role clearly—what they expected, plus benefits and salary discussion—and the questions landed heavily on solid Java knowledge, with a noticeable number of behavioral questions designed around the team’s needs. Overall it felt challenging in a “show me fundamentals” way, not a trick-question way.
> 1 year
Average Negative Thessaloníki, Western Macedonia
My journey started with a written assessment and personality questions. The assessment covered a few programming questions across different languages since it was a full-stack role, and after that I met engineers to walk through my answers. The engineer conversation felt positive—I was told they liked how I performed.
After that, HR reached out quickly. I ended up getting a verbal offer call the next day, and I countered with a slightly higher salary. They said they’d consider it, and at first it felt like things were still moving. Then the communication went cold. I didn’t receive anything concrete after my counter, and eventually I only heard back a month later with a rejection, even though the whole process up to that point was surprisingly fast—just a few days.
> 1 year
Average Neutral United States
My process mostly revolved around coding screens that felt fairly standard. I had a LeetCode-style technical round first, and once I passed, I moved i…
> 1 year
Average Positive Israel, TX
I had a quieter, more spoken-style interview that still ended up feeling demanding because of the way the response was measured. It was over Zoom with…
> 1 year
Average Positive Hyderābād
I went through a short pipeline where round one was an online test and round two was an onsite-style conversation. The online portion included two cod…
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
Interview Structure & Timeline
The interview process typically includes an initial online assessment followed by multiple technical rounds, often culminating in an HR discussion. Candidates should expect a structured flow that may involve several checkpoints, with timelines varying from quick to drawn-out depending on the stage.
Interview processTimelineStructure
Technical Evaluation
Candidates will face technical interviews that focus on core programming concepts, particularly in Java, OOP, and data structures. The coding questions often range from easy to medium difficulty, and candidates should be prepared to articulate their thought processes clearly.
JavaOOPData Structures
Behavioral & Managerial Rounds
Behavioral interviews are common and often focus on cultural fit, past experiences, and alignment with company values. Candidates should prepare for conversational-style interviews that assess soft skills and interpersonal dynamics alongside technical abilities.
BehavioralCultural fitSoft skills
Assessment of Fundamentals
Interviewers emphasize a solid understanding of programming fundamentals and may ask candidates to explain concepts in detail. Candidates should be ready to demonstrate their knowledge of algorithms, data structures, and object-oriented principles through practical examples.
FundamentalsAlgorithmsData Structures
Communication & Follow-Up
Candidates have noted varying levels of communication throughout the process, with some experiencing delays or lack of feedback after interviews. It's advisable to follow up proactively to maintain momentum and clarify any uncertainties regarding the next steps.
CommunicationFollow-upFeedback
Overall Difficulty & Experience
The overall difficulty of the interview process is generally described as average, with some candidates finding it manageable while others felt challenged. Preparing for a mix of technical and behavioral questions will help candidates navigate the experience more effectively.