LSEG Software Engineer interviews typically start with an MCQ screen, coding assessment, or online assessment. Live technical rounds on Java, SQL, or stack-specific topics follow, then a managerial or HR discussion, and follow-up after final rounds can be slow.
$130K
Avg. Base Comp
$165K
Avg. Total Comp
3-5 rounds
Typical Rounds
Not reported
Process Length
LSEG's Software Engineer interviews combine a broad technical screen with stack-specific follow-up. Most accounts describe an initial filter before any live conversation. That filter might be an MCQ round on OOP concepts with code-output questions, a coding assessment, or an online assessment with behavioral components. Java fundamentals such as OOP, garbage collection, and multithreading come up repeatedly, alongside Spring Boot, Hibernate, AWS services, and SQL. One candidate instead faced .NET, C#, dependency injection, JWT authentication, and Angular questions, so the exact mix may depend on the team. Coding problems reported here center on strings, arrays, sliding windows, and moderate dynamic programming rather than obscure algorithms. One campus candidate said the interviewer wanted to hear as many approaches as possible to their earlier coding solutions, and regretted focusing only on implementation, so practice explaining alternatives out loud.
Expect project discussion as well: one candidate was questioned on the difficulties of splitting a monolith into microservices. Campus and graduate tracks can add a group discussion, such as one on cloud computing and scalability in banking systems. They may also include an assessment centre with maths, logic, and situational questions. Final HR or managerial conversations focus on motivation, teamwork, and handling workplace challenges rather than new technical material. One candidate waited a long time after a five-round walk-in day before hearing they weren't moving forward, so plan for slow follow-up.
Synthesized from 13 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 Lseg (london stock exchange group) process.
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 Lseg (london stock exchange group)
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Triplet Counting | |
| Term Frequency | |
| Hurdles In Data Projects | |
| Deciding Between Solutions | |
| Testing Constraints | |
| Client Solution Pushback | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Merge Sorted Lists | |
| Employee Salaries | |
| Subscription Overlap | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| Maximum Profit | |
| Bagging vs Boosting | |
| String Shift | |
| Prime to N | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| Size of Joins | |
| Google Maps Improvement | |
| Total Spent on Products | |
| P-value to a Layman |
Synthesized from candidate reports. Individual experiences may vary.
Many candidates report an upfront filter before live interviews. This can be an MCQ round on OOP concepts with Java and C++ code-output questions, or a coding assessment (one included a sliding-window problem using a hash map). Others describe an online behavioural assessment or a video interview, and a graduate-scheme candidate faced an online maths test instead.
Technical rounds mix practical coding with language fundamentals. Candidates report Java topics such as multithreading and garbage collection, along with Spring Boot, Hibernate, AWS services, and SQL. One candidate instead described .NET, C#, dependency injection, JWT authentication, and Angular questions, so topics may depend on the team. One campus candidate's interviewer wanted to hear multiple approaches to a problem rather than a single working solution.
Technical rounds can also dig into past projects. One candidate presented a coding solution and then discussed the difficulties of splitting a monolith into microservices, as well as their plans in their current role.
Campus and graduate candidates report extra segments. One was a 30-minute group discussion on cloud computing and scalability in banking systems. Another was an online assessment centre with behavioral questions, a decryption-style problem-solving task, logic tests, and situational questions. These appear specific to campus or graduate tracks rather than every Software Engineer pipeline.
The last stage is usually an HR or managerial discussion covering motivation, background, teamwork, and handling challenges rather than new technical material. Outcomes varied, and one candidate waited a long time after their final round before learning they would not move forward.
