
Schroders Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 10 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Schroders.
Principal Software Engineer
I went through multiple rounds. There was a manager call, then a technical test with live coding and questions, and then another technical leadership assessment. The interviewers were tough, but the engineers were helpful and seemed to want me to succeed, unlike at other places where they feel like they're trying to trick you.
- How would you address a situation where a team is releasing software bi-weekly, and business stakeholders are unhappy with the number of bugs being introduced?
Principal Software Engineer
Applied via recruiter. First was a take-home coding test focused on performance, formatting, and production-level quality. Took 4 business days to hear back after chasing recruiter a few times. Response from recruiter was: 'Unfortunately we don't want to progress with the (candidate). Incorrect approach.' Refused to give more feedback as 'it gives away the game for future candidates'. Challenge was okay, but feedback was bad. Saying an incorrect approach was used when none was specified is weird. Would have expected discussion or useful feedback instead of wasting candidate time. Fine not proceeding, but would appreciate being upfront and/or more detailed.
- Could you identify all keypad sequences that satisfy given conditions?
Application Developer
I had two interviews. The first one had two technical tests that were written and had to be done in 40 minutes. The second interview was an hour long and I talked with two "experts" and someone from the business side who said they were a "developer" too. The whole process was really disorganized. I was given the wrong spec and the recruiter at Schroders gave me bad info about the tests. Even with that, I passed the technical test and got invited to the second interview. In the second interview, they asked more technical questions that honestly could have been part of the technical test, so it felt like a waste of time. I got so bored with it halfway through and lost interest because the questions just kept getting worse. One of the developers then went on a rant about a question, and I could tell they were just reading from a book and didn't really know how to program in the real world. But the biggest issue was they didn't want you to ask any questions about the job. They'd be like "Got any questions?" and I'd start to ask and they'd cut me off saying "Sorry, time's up". It really showed me how dysfunctional Schroders is, or maybe it was just this specific team. I wasn't expecting it because of other reviews I saw on Glassdoor.
- What would you do if you disagreed with a requirement for a project?
Schroders Software Engineer Interview Questions
Quoted word for word from Schroders interview reports.
“Could you identify all keypad sequences that satisfy given conditions?”
Read reports →“Can you fix this bug in the provided React component?”
Read reports →“How would you address a situation where a team is releasing software bi-weekly, and business stakeholders are unhappy with the number of bugs being introduced?”
Read reports →“What are some architectural decisions you've made?”
Read reports →“What would you do if you disagreed with a requirement for a project?”
Read report →“Can you share an instance where you had to make a significant decision? Describe your process and whether you were satisfied with the result.”
Read report →“What made you apply to this company?”
Read report →“Can you share an instance where you came up with an innovative solution to a challenge?”
Read report →“Can you describe your approach to the technical test you completed?”
Read report →Formats, difficulty and experience
Across all 10 Schroders interview reports.