
Santander Software Engineer interviews reported by six candidates usually start with an HR conversation, then a technical or team round covering SQL, Java, React or other stack fundamentals, plus behavioral questions.
$110K
Avg. Base Comp
$130K
Avg. Total Comp
2-3 rounds
Typical Rounds
Not reported
Process Length
Santander Software Engineer interviews, as six candidates describe them, usually open with an HR or recruiter conversation about your background and motivation. Technical content follows, and it varies a lot by team. Expect fundamentals tied to the team's stack rather than heavy algorithm drills.
Two candidates mention SQL questions: one asked about the HAVING clause and reading query output, another about UNION versus UNION ALL and join types. Java came up for others, including removing an element from a list, ACID principles, heap versus stack, and the Singleton pattern. One candidate reports a bitwise task: add two numbers without the addition operator. A React candidate who received an offer describes a practical technical round with a take-home exercise and questions on Playwright and Vitest. Another candidate says a .NET/C# and Oracle PL/SQL track would follow an initial HireVue video screen with five questions and two game-based assessments.
Behavioral questions matter too. Candidates describe being asked about teamwork, working under tight deadlines, how they keep up with technology, and their career story. Two offers and four rejections are reported. One offer report describes conversational, low-pressure video interviews, while one rejected candidate describes an interviewer who interrupted often. Practice giving concise, structured answers, and prepare concrete examples from your own projects. With only six reports, treat the exact round order as team-dependent.
Synthesized from 6 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Santander process.
The process took a few weeks from initial CV submission to final feedback. A recruiter got in touch first, then the hiring manager scheduled what turned out to be a three-round interview loop. The first round was with HR and included a quick English proficiency check—nothing intensive, just to confirm basic communication skills. It lasted about 15 minutes and felt more like a screening than an assessment.
The second round was with the actual project team, and this is where the technical questions came in. It was fairly relaxed overall, honestly. They asked about SQL fundamentals—for instance, what the HAVING clause does and how to interpret query output—along with some JavaScript and TypeScript concepts. Nothing felt overly algorithmic or pressure-filled; they seemed more interested in understanding how I thought through problems than in seeing a perfect solution. The conversation was extended and conversational, which actually helped me explain my reasoning clearly.
The final round was another HR conversation, this one considerably longer. It shifted away from pure technical content into personal questions and behavioral territory. Some of the questions felt a bit off-topic or unusual for a software engineer role—the kind where you wonder why they're asking. They also wanted to know how I stay current with technology, my approach to code maintenance, and my general professional background in detail. The interviewers seemed friendly throughout, but by the end I wasn't entirely sure where I stood. A week or so later, I learned the position wasn't moving forward with me.
Prep tip from this candidate
Be ready for SQL-specific questions (HAVING, query interpretation) and basic backend concepts like microservices, but also prepare for HR rounds that dive into soft skills, how you handle feedback, and your approach to staying current in tech. The process can be lengthy and span multiple rounds with different focuses—pace yourself and don't assume technical strength alone will carry you through.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Santander
Given a list of locations that your trucks are stored at, return the top location for each model of truck (Mercedes or BMW).
| Question | |
|---|---|
| 2nd Highest Salary | |
| Employee Salaries | |
| Closest SAT Scores | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Find the Missing Number | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Top 5 Turnover Risk | |
| Size of Joins | |
| Payments Received | |
| Total Spent on Products | |
| P-value to a Layman | |
| Find the First Non-Repeating Character in a String | |
| Get Top N Frequent Words | |
| Top 3 Users | |
| Maximum Profit | |
| Bagging vs Boosting | |
| Duplicate Rows | |
| String Shift | |
| Scrambled Tickets | |
| Google Maps Improvement | |
| Prime to N | |
| Comments Histogram | |
| Employees Before Managers | |
| Last Transaction | |
| LRU Cache 1 |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report different entry points. Several describe an HR or recruiter conversation about work history, studies and motivation, and one mentions a brief English check. One candidate reports a HireVue video screen with five questions and game-based assessments. Prepare a short, clear career story.
Candidates report technical conversations with an engineering manager, project team or tech lead. Topics mentioned include SQL (HAVING, joins, UNION), Java, JavaScript/TypeScript, memory management, and design patterns. Depth appears to vary by team and is usually fundamentals-focused rather than heavily algorithmic.
Some candidates report a hands-on element: a bitwise addition problem, Java coding with a case study, or a React exercise completed at home. Not every candidate describes one, so it may depend on the team. Practice explaining your reasoning aloud while you work.
Candidates report HR or manager-style conversations on teamwork, deadline pressure, staying current, and CV walk-throughs. One offer recipient describes these as friendly and conversational, so have specific project examples ready rather than rehearsed scripts.