RepostedLSEG logo

LSEG · OA → Onsite

In process

LSEG Graduate Technology OA and Interviews: 7 Experiences

Engineering / Technology Graduate · New GradAug 2025
Shared byjanebeingjane

LSEG graduate and campus technology hiring, 2024–2026: 7 reports of an MCQ test, three coding tasks, a group case and a technical interview.

At a glance

  • Process: a 30-minute MCQ test, a coding round with three tasks in 60 to 120 minutes, a group case with a short presentation, then a one-to-one technical interview (02, 04–07). Campus days often ran all of this in one day (05–07).
  • Asked recently: coding or algorithms in 6 of 7 reports, a group exercise in 6, programming and CS multiple-choice questions in 5, and SQL in 3.
  • Difficulty: the London candidate called the technical exercise mostly LeetCode easy (01); the 2025 graduate associate rated the three DSA tasks medium to hard (02); Hyderabad rated its string tasks easy to medium (07).
  • Practise first: Minimum Digit Swaps (2 reports), Student Analytics Dashboard (2) and Crypto Trading Extension (2).

Coverage: seven LSEG graduate and campus technology candidates from 2024–2026: Engineering Graduate, Engineering Graduate Associate, Technology Graduate and Cyber Security Technology Graduate. Locations named: London, Pune and Hyderabad.

What came up

The coding round and the group case are the two steps almost everyone met. One candidate can sit in several rows.

Topic Reports Last seen
Coding and algorithms 6 of 7 Feb 2026
Group exercise or case 6 of 7 Feb 2026
Programming and CS multiple choice 5 of 7 Aug 2025
Projects, resume and experience 4 of 7 Aug 2025
SQL and databases 3 of 7 Aug 2025
Logic and number puzzles 3 of 7 Oct 2024

Questions we found

Dates are interview months where given; report 04 interviewed in 2024 with no month.

Algorithms / Data Structures

Question Reports Last seen
Minimum Digit Swaps 2 Sep 2024 (report date)
Maximum Sum of Three Non-Adjacent Elements 1 Oct 2024
Special Two-Digit Times 1 Oct 2024
Maximum Sentence Word Count 1 Oct 2024
Maximum Non-Adjacent Sum 1 Sep 2024 (report date)
Sentence With the Most Words 1 Sep 2024 (report date)
Smallest String After One Deletion 1 Aug 2024
One-Operation String Transformation 1 2024
Three-Part Minimax Range 1 2024
Delete One Five 1 2024
Stack Operations 1 2024

Group cases

Question Reports Last seen
Student web app or analytics dashboard 2 Oct 2024
Add cryptocurrency trading to a trading platform 2 Aug 2024

SQL and technical talk

Question Reports Last seen
Basic SQL retrieval and joins 1 Sep 2024 (report date)
MongoDB vs MySQL; can one app use both? 1 2024
What does **p mean? 1 2024
Singleton, private constructors and static methods 1 2024
JavaScript vs C++; can C++ build web apps? 1 2024
Explain your project and why you chose MERN 1 2024

Behavioral (BQ)

Question Reports Last seen
What do you know about LSEG? 2 Sep 2024 (report date)
Your career goals 1 Oct 2024
Introduce yourself 1 Sep 2024 (report date)

Puzzles

Question Reports Last seen
Recover a mango pile after three thieves 1 Aug 2024
31:90 :: 43:? (125, 75, 120 or 102) 1 Aug 2024
Rabbits moved between coloured hutches 1 Sep 2024 (report date)

7 detailed candidate timelines, loops, and screens

01: London Engineering Graduate, a mostly easy technical exercise

Interview date: about February 2026 · Role: Engineering Graduate, D&A / Cloud / DevOps · Location: London

  1. The candidate applied to the Engineering Graduate assessment centre and attended it about two weeks before posting on 25 February.
  2. The technical exercise was mostly LeetCode easy; they suggested talking through your reasoning while coding.
  3. Interviewers were relaxed and the day did not feel too long. No task, count, length or group brief was shared.

02: Graduate Associate, online stages then a campus day

Interview date: August 2025 · Report date: July 15, 2026 · Role: Engineering Graduate Associate

  1. Puzzle assessment: unsupervised, logic, patterns and problem solving; it took the candidate more than three hours. No puzzle was shared.
  2. Video interview: asynchronous behavioral answers of 60–90 seconds each, with no strict preparation limit; over three hours in total.
  3. Technical MCQ: an elimination round of about 40–60 questions in 30 minutes on OOP, databases, AI, ML, aptitude and numerical reasoning.
  4. DSA: three tasks in 90 minutes, rated medium to hard, on DP, graphs, bit manipulation and arrays. The tasks were not named.
  5. Group discussion: a business problem solved as a team, with the focus on teamwork and communication. Scenario, size and timing were not shared.
  6. Technical interview: detailed resume questions, a SQL problem the candidate solved, a DSA problem on paper and Unix/Linux questions, plus projects, internships and core CS. There was no HR interview.

03: Cyber Security graduate, rejected over group contribution

Assessment centre: January 23, 2025 · Role: Technology Graduate, Cyber Security · Result: Rejected

  1. A group exercise and a stakeholder conversation.
  2. Feedback after the result call on February 4: the stakeholder conversation went well, but the candidate had not contributed enough in the group exercise. They disagreed about how much they had spoken. No case or technical question was shared.

04: Campus hire, Bitcoin on a forex platform

Interview date: 2024 (month not given) · Report date: February 22, 2025 · Role: full-time campus technology · Result: joined after first not being selected

  1. MCQ (Codility): 30 questions on aptitude, networking and Java, including one on SQL joins. 16 of 300 candidates were shortlisted; later rounds did not eliminate anyone.
  2. Coding, three tasks in 60 minutes:
  3. Group case: eight candidates planned adding Bitcoin trading to an existing forex platform: 30 minutes of discussion, then 30–40 minutes of presentation and questions.
  4. Technical interview: the candidate's projects and why they chose MERN; MongoDB vs MySQL and whether both can coexist; what **p means; implement a stack; singletons, private constructors, static methods and whether objects can share memory; JavaScript vs C++ and C++ for the web.
  5. Two candidates were picked first. This candidate was not, but was contacted later and joined.

05: Pune campus day, three coding tasks then a student app

Interview date: October 2024 · Location: Pune (campus hiring) · Role: full-time engineering

  1. MCQ: 30 minutes, 30 technical questions plus a few aptitude ones, no negative marking; Java, C/C++, multithreading, OOP and pointers. 20 candidates were shortlisted.
  2. Coding, three tasks in 80 minutes:
  3. Logic and approach mattered; at lunch candidates were encouraged to think about optimizations.
  4. Technical interview: explain the earlier code and improve it, data structures, time complexity, projects, an unnamed logic puzzle and career goals.
  5. Group case: seven candidates, 30 minutes of discussion and a five-minute presentation proposing a web app for students, covering team allocation, staffing and tech stack.
  6. Four of the 20 were selected; the candidate's own result is not stated.

06: Student dashboard, where the existing stack mattered

Report date: September 23, 2024 · Context: campus hiring · Result: Rejected

  1. MCQ: 30 questions in 30 minutes, mostly Java plus C/C++, with two aptitude items (decoding, trains and time). 20 of 200 were shortlisted; this was the only cut.
  2. Coding, any language, 120 minutes:
  3. Technical interview, about 40 minutes: introduce yourself, explain the earlier solutions, two basic MySQL questions on retrieval and joins (Basic SQL Retrieval is our minimal version), what you know about LSEG, and a puzzle: red, yellow and green rabbit hutches, twice as many in green as yellow; sell five red, move half the remaining red to yellow; then a question about the colour on a hutch's left side, with no unique answer given.
  4. Group case: six or seven candidates planned a student analytics web app and dashboard: requirements, development, testing, maintenance and staffing, in 30 minutes of discussion, five of presentation and five of questions. The assessor's feedback: the imagined team had been at LSEG six months, so it should use the company's existing stack.
  5. One candidate was picked after about two hours; HR watched candidates all day.

07: Hyderabad Technology Graduate, crypto plans and two puzzles

Interview date: August 2024 · Role: Technology Graduate Program · Location: Hyderabad · Result: Selected

  1. Four rounds in one day; the candidate rated it moderate.
  2. Aptitude and CS: 30 questions in 30 minutes on Java, C, verbal reasoning, aptitude, inheritance and pointers. 25 of 700 were shortlisted, with no later cuts.
  3. Coding, three string tasks in 60 minutes (easy to medium): Smallest String After One Deletion (abcda → abca, aaa → aa) and Minimum Digit Swaps, minimizing the difference and then the number of swaps. The third task was not described.
  4. Group case: 13 people with printed instructions proposed business and technical plans for adding cryptocurrency trading to a trading system. Discussion ran about 35 minutes and the presentation about ten.
  5. One-to-one interview, about 45 minutes: earlier coding approaches, basic coding questions, hackathon experience, what you know about LSEG, and two puzzles: the mango pile (under 100 mangoes; three thieves in turn find one extra when splitting into thirds, eat it and take a third; 22 remain) and 31:90 :: 43:? with choices 125, 75, 120 and 102.

Patterns across the reports

  1. Three coding tasks after a short MCQ. Reports 04–07 all had a 30-question, 30-minute MCQ followed by three coding tasks (in 60, 80, 120 and 60 minutes); report 02's DSA round also had three tasks.
  2. Explain your earlier code. Reports 05, 06 and 07 all began the interview by walking through their coding-round solutions; 05 added optimization and complexity.
  3. Group cases extend an existing product. Two crypto cases (04, 07) and two student-app cases (05, 06). Staffing came up in both student cases, and 06 was told to reuse the company stack.
  4. Group participation is judged. Report 02 stressed teamwork; report 03 was rejected for not contributing enough.

Common questions

What is the LSEG graduate coding round like?

Three tasks in 60 to 120 minutes after an MCQ test (04–07); 02 had three DSA tasks in 90 minutes. Ratings ranged from easy (01) to medium-hard (02).

What is the LSEG group exercise?

A team case with a short presentation: adding crypto trading to a platform (04, 07) or planning a student web app (05, 06), usually 30 minutes of discussion.

Does LSEG ask SQL in graduate interviews?

Yes in 02 (a SQL problem), 04 (a joins MCQ and MongoDB vs MySQL) and 06 (basic retrieval and joins).

How many candidates pass the LSEG campus MCQ?

Reports gave 16 of 300 (04), 20 of 200 (06) and 25 of 700 (07).

Keep practicing

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.
0 comments

Comments

0

No comments yet — be the first to share what you know.