Santander Software Engineer interview typically runs 3 rounds: initial HR interview, technical test, tech lead conversation. It usually finishes quickly and is straightforward, with a practical, efficient process.
$114K
Avg. Base Comp
$171K
Avg. Total Comp
3-4
Typical Rounds
2-4 weeks
Process Length
Our candidates report that Santander is less interested in abstract frontend theory than in whether you can operate comfortably in a real product codebase. The strongest signal in the experience we saw was the emphasis on practical React work: the technical evaluation centered on applied problem-solving, and the conversation with the tech lead dug into how the candidate actually builds and validates UI features. That tells us Santander is looking for engineers who can explain decisions clearly, not just recite patterns.
A recurring theme is the weight placed on testing maturity. Multiple candidates mentioned being asked about specific tools like Playwright and Vitest, which is a good clue that they care about how you think about reliability, not just whether you can ship a component. We’ve also seen that the team pays attention to whether your experience feels grounded and current — the candidate who received an offer noted that it helped to speak concretely about tools and workflows they had really used. In other words, this process rewards specificity: what you built, how you tested it, and why your approach made sense for the team.
We also see a clear people-fit layer early on, but it’s not fluffy. The initial conversation focused on work history, studies, and motivation, which suggests Santander wants a candidate who can connect their background to the role in a credible way. The non-obvious make-or-break factor here is coherence: when your story, your React experience, and your testing setup all line up, the process feels straightforward and fair. When they don’t, the gaps are likely to stand out quickly.
Synthesized from 1 candidate report 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 was pretty straightforward and didn’t drag on. I went through three phases: an initial interview to get to know me better, a technical test focused on React, and then a conversation with the tech lead. The first round was more personal and conversational, with HR asking about my work experience, studies, and motivation. It felt like they wanted to understand whether I’d fit the team and the role before getting too deep into the technical side.
The technical part was the most important round for me. I had a senior developer involved, and it was split into two parts: a technical interview and then a take-home exercise to solve at home. The React test was practical rather than theoretical, and the tech lead also asked about my experience with testing. I was specifically asked whether I had worked with Playwright and Vitest, so it helped to be ready to talk about real tools I’d used rather than just general frontend concepts. Overall, the interview felt engaging and fair, and I appreciated that it was efficient instead of being stretched out unnecessarily. I ended up receiving an offer, so my main takeaway is to be ready to explain your React experience clearly, talk through your testing setup, and have a solid story for your background and motivation.
Prep tip from this candidate
Be ready for a React-focused technical round that includes a take-home exercise, and make sure you can speak concretely about testing tools like Playwright and Vitest. Also prepare a concise explanation of your work experience, studies, and motivation for the HR conversation.
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 | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| Bagging vs Boosting | |
| String Shift | |
| Comments Histogram | |
| Prime to N | |
| Maximum Profit | |
| Like Tracker | |
| P-value to a Layman | |
| Hurdles In Data Projects | |
| Google Maps Improvement | |
| Cumulative Distribution | |
| Monthly Customer Report | |
| Rectangle Overlap | |
| Find the First Non-Repeating Character in a String | |
| Over-Budget Projects | |
| Slacking Employees Salaries | |
| Top 3 Users | |
| Size of Joins | |
| Total Spent on Products | |
| Sum to N | |
| Over 100 Dollars |
Synthesized from candidate reports. Individual experiences may vary.
An initial conversational interview with HR focused on your work experience, studies, and motivation. The goal is to understand your background, fit for the team, and interest in the role before moving into technical evaluation.
A practical technical round with a senior developer focused on React. Expect questions about your hands-on frontend experience and testing tools, including whether you have used Playwright and Vitest.
A practical assignment to solve independently at home, centered on React. This stage appears to be part of the technical evaluation and is used to assess how you approach real implementation work.
A final discussion with the tech lead covering your technical background and testing experience. The conversation also serves as a deeper check on your fit for the team and role before the final decision.