
One Santander Security Engineer candidate reports a technical round on DevSecOps and privileged access management, a manager conversation, a long hold on the vacancy, and an accepted offer after 144 days.
$120K
Avg. Base Comp
$165K
Avg. Total Comp
Not reported
Typical Rounds
144 days
Process Length
The one Santander Security Engineer experience available describes a conversational technical round rather than a trick quiz. The candidate reports that it covered DevSecOps principles, with attention to security foundations, and privileged access management (PAM). The advice was to explain the reasoning behind each principle instead of memorizing lists, so practice explaining why core DevSecOps and PAM principles exist and how security fits into a delivery pipeline.
The candidate also called the conversation with the manager one of the most interesting parts of the process, so expect to discuss how you think about security work with a future manager.
Timing is the main thing to plan for. This candidate reports a 144-day process, 44 days of which were spent waiting after the technical interview because the vacancy was put on hold for internal reasons. Recruiters said the candidate had passed. The candidate suggests asking the recruiter for a status update once you clear the technical stage. This is a single report, so your own timeline may be much shorter. The candidate eventually received an offer and accepted it.
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 whole process took 144 days for me, and 44 of them were spent waiting after my technical interview, which felt like a cold shower. I passed the technical test, and the conversation with the manager was one of the most interesting parts of the whole process. In the meantime, though, the vacancy was put on hold, and I spent those weeks waiting with nothing to do but wait. The recruiters were careful to tell me I had passed, but they were clear the delay came down to internal matters. Apart from the HR side, everyone I dealt with was excellent, and the timing is the thing I would warn people about.
The technical round covered the principles of DevSecOps, with particular attention to security foundations, and the principles of privileged access management (PAM). It was a well-run and genuinely interesting conversation, not a trick quiz, so I'd focus on being able to explain the reasoning behind each principle rather than memorizing lists.
If I had to give one piece of advice, it would be to keep the momentum going yourself. Once you've passed the technical stage, ask the recruiter directly what the status of the role is, because silence can last a long time. I did eventually receive an offer and accepted it, but it took far longer than the process itself suggested.
Prep tip from this candidate
Review DevSecOps fundamentals with a focus on security foundations, and be ready to explain the principles of privileged access management (PAM), since those were the topics covered in the technical round. Ask the recruiter for a status update once you clear the technical stage, because the vacancy can be put on hold for weeks.
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 | |
|---|---|
| Merge Sorted Lists | |
| Find the Missing Number | |
| Get Top N Frequent Words | |
| Find the First Non-Repeating Character in a String | |
| String Shift | |
| Maximum Profit | |
| Scrambled Tickets | |
| Prime to N | |
| Alphabet Sum | |
| LRU Cache 1 | |
| Rectangle Overlap | |
| Sum to N | |
| Minimum Change | |
| Recurring Character | |
| Priority Queue Using Linked List | |
| Hurdles In Data Projects | |
| Over 100 Dollars | |
| Sort Strings | |
| Minimum Absolute Distance | |
| Groups of Anagrams | |
| Shortest Path Algorithms | |
| Level Of Rain Water In 2D Terrain | |
| String Mapping | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| The Brackets Problem | |
| Coin Dispenser | |
| Singly Linked List | |
| Mouse Search | |
| Target Indices |
Synthesized from candidate reports. Individual experiences may vary.
The candidate reports a technical round that covered DevSecOps principles, with particular attention to security foundations, and privileged access management principles. They describe it as a well-run, genuinely interesting conversation rather than a trick quiz, so be ready to explain your reasoning.
The candidate also had a conversation with the manager and called it one of the most interesting parts of the process. The candidate gave no specific questions, so preparing to discuss your security experience and approach is a reasonable inference.
The candidate reports about 44 days of waiting after the technical interview while the vacancy was put on hold. Recruiters said the candidate had passed and that the delay came from internal matters. Asking the recruiter for a status update may help, as the candidate advises.
The candidate reports eventually receiving an offer and accepting it. They describe the whole process as taking 144 days from start to finish, much longer than the interview stages themselves would suggest. Other candidates' timelines may differ.