LSEG Software Engineer interview typically runs 1–5 rounds: MCQ, technical, managerial, and HR. The process can be completed in one day face-to-face, with notably delayed post-interview feedback.
$119K
Avg. Base Comp
$208K
Avg. Total Comp
4-5
Typical Rounds
1 day to 2-4 weeks
Process Length
Our candidates report that LSEG is less interested in a single narrow specialty than in whether you can operate across a real production stack. The recurring pattern is a mix of backend fundamentals, frontend awareness, and implementation detail: .NET, Java, Spring Boot, Angular routing, JWT authentication, dependency injection, SQL, and OOP all showed up across separate experiences. That tells us the bar is not just "can you code," but can you explain how the pieces fit together when the interviewer pivots from language syntax to architecture and security within the same conversation.
A second theme is that the company values practical reasoning over polished theory. Multiple candidates described being asked to walk through a solution live, then defend choices around multithreading, garbage collection, microservices migration, or the software development life cycle. The coding tasks themselves were deliberately small — a sorted-array check, a Hibernate exercise, sliding-window problems — but they were used as a springboard to probe how clearly you think under pressure. We've seen that the strongest signal here is structured, concise explanation: interviewers appear to reward candidates who stay organized while covering a lot of ground, especially when the conversation shifts quickly between code, system behavior, and prior project tradeoffs.
One non-obvious thing worth flagging: both candidates who went through this process ended up without an offer and without meaningful feedback. The lack of post-interview transparency seems to be a consistent pattern rather than an exception, so going in with realistic expectations about closure matters as much as the preparation itself.
Synthesized from 2 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.
The interview process was fairly straightforward, but the technical focus was broader than I expected. My first round was a 30-minute conversation that started with a few generic questions and then moved into how I approach problem solving and how I think through the software development life cycle. It felt more like a discussion of fundamentals and communication than a deep coding screen, and the pace was quick enough that I had to keep my answers concise.
What stood out in the technical portion was how stack-specific the questions were. I was asked about .NET, dependency injection, JWT authentication, Angular routing, JavaScript closures, and OOP concepts in C#. There was also a small coding task to check whether an array is sorted, plus some SQL and general .NET questions. The interviewer seemed to want to see whether I had practical familiarity across the full stack rather than just one language. The questions were not especially algorithm-heavy, but they did cover a lot of ground, so it was important to stay organized and not ramble.
From what I understood, the process can also include multiple rounds, with Java and Spring Boot in the first round for followed by a system design round and then managerial or technical discussions with a manager. In my case, the round I had was enough to make the outcome clear, and I did not move forward. My main takeaway is to be ready for a broad backend/frontend mix and to explain your reasoning clearly, especially around architecture, authentication, and core OOP concepts.
Prep tip from this candidate
Brush up on .NET fundamentals, DI, JWT authentication, Angular routing, and C# OOP, and be ready to explain your approach to problem solving and SDLC clearly. Also practice a simple array-sorted check and be prepared for a broad stack discussion rather than a deep algorithm round.
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 | |
|---|---|
| Hurdles In Data Projects | |
| Deciding Between Solutions | |
| Triplet Counting | |
| Testing Constraints | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| Bagging vs Boosting | |
| String Shift | |
| Prime to N | |
| Comments Histogram | |
| Maximum Profit | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| P-value to a Layman | |
| Google Maps Improvement | |
| Cumulative Distribution | |
| Rectangle Overlap | |
| Over-Budget Projects | |
| Slacking Employees Salaries | |
| Top 3 Users |
Synthesized from candidate reports. Individual experiences may vary.
The first conversation is a broad technical screen that starts with generic questions and moves into problem solving and software development lifecycle thinking. Candidates should expect stack-specific questions covering .NET, dependency injection, JWT authentication, Angular routing, JavaScript closures, C# OOP, SQL, and a small coding task such as checking whether an array is sorted.
In walk-in or on-site processes, candidates may begin with a multiple choice question round covering core technical concepts before moving into face-to-face interviews.
One or more deeper technical interviews focus on Java and backend engineering, including coding exercises with on-the-spot explanation, Java multithreading and garbage collection, Spring Boot, batch basics, AWS services, Hibernate, and string or sliding-window style coding problems. Interviewers also discuss prior project experience such as splitting a monolith into microservices.
A managerial discussion follows the technical rounds, focusing on communication, project ownership, and how you approach architecture and engineering tradeoffs. Interviewers may ask about your current role, future plans, and how you think through broader technical decisions.
The final stage is an HR conversation that closes out the interview day. A final decision is not given immediately and is communicated afterward, sometimes with significant delay.