FIRM INTERVIEW GUIDE

XTX Markets Interview Guide

XTX Markets interview guide for quant research, software engineering and XTY Labs internships. Explore the online test, technical rounds and worked questions.

The short answer

XTX Markets interviews are technical and role-specific. Candidates take an online test in probability, statistics, mathematics and algorithms, followed by four or five interviews with researchers.

Its XTY Labs AI internship advertises a different, four stage process built around a dataset-based modelling assignment. Software engineering applicants have reported hard coding questions, complexity discussions and systems work. The sections below explain each route and how to prepare for it.

How the XTX Markets interview process works

Researchers develop the models; exchange trading engineers build the infrastructure that processes market data and sends orders. That division shapes the interview far more than a generic “quant trading” syllabus.

XTX hiring routes supported by official role descriptions and first-hand interviews
RoleInterview sequenceMain technical work
Junior Quantitative ResearcherOnline technical test, then 4–5 researcher interviews (published Yerevan vacancy)Probability, statistics, linear algebra, analysis and algorithms
XTY Labs AI Research InternshipRecruitment introduction → dataset take-home → Research Director discussion → one-hour researcher interview (2026 advertised process)End-to-end modelling, deep learning and research judgement
Software Engineer / DeveloperCoding and technical interviews; take-home and onsite stages appear in individual candidate reportsAlgorithm design, complexity, C++ or Python internals, Linux and system performance

The junior research and XTY sequences come from XTX-authored job descriptions. The engineering sequence is reconstructed from identifiable candidate accounts, so its precise ordering is less established. If you are applying for a dedicated engineering role, the team matters too: XTX's exchange trading developers work mainly in C++ and Python, while its shared platform engineering vacancy emphasises Go, Linux and developer tooling.

Application and first conversation

Start with the official XTX Markets careers page and choose the research or engineering team that fits your work. For a research application, show a model you designed, tested and improved, including why its result was credible. For engineering, describe a working system, the performance constraint you faced and a difficult implementation choice you made.

In a September 2023 London quantitative-research interview account, the candidate described a recruiter call followed by technical phone interviews. For the XTY Labs internship, the 2026 first stage was explicitly an introductory recruitment conversation. Prepare a two-minute explanation of one project that leads naturally into harder questions: what you predicted or built, what you measured, what failed, and what you changed.

The XTX Markets online assessment

The Yerevan vacancy specifies an online test covering statistics, probability theory, general mathematics (including linear algebra and analysis) and computer science/algorithms. The same posting states that it leads into four or five interviews with researchers.

Prepare to do the mathematics rather than merely recognise terminology. Useful tasks include deriving a conditional expectation, computing the variance of an estimator, explaining what a covariance matrix tells you, finding an eigenvalue in a small example, and tracing the running time of an algorithm. The published subject list supports those families; the examples here are our preparation recommendations, not leaked XTX test questions.

EverythingQuant practice benchmark: take 75 minutes for four questions: one conditional-probability derivation, one regression/estimation problem, one small linear-algebra computation and one algorithmic complexity problem. Review every error afterwards. This is a training session, not a claimed XTX question count or test duration.

One detail worth getting right: the firm-authored junior researcher posting establishes the subjects and broad sequence. It does not identify HackerRank, CodeSignal, a minimum score or an exact test length. Treat numerical claims on unrelated prep pages as unverified unless they are tied to a comparable original candidate experience.

Quantitative researcher and machine-learning interviews

The researcher interviews combine fundamentals with explanations of how models behave on data. In a London quantitative-research account describing an April 2023 interview, the candidate encountered linear models, simple neural networks and a brainteaser, followed by a home assignment. A separate London machine-learning researcher account discussed neural networks, RNNs, transformers, time series, linear algebra and calculus.

Those accounts give you a practical revision order. First, derive ordinary least squares and explain how ridge regularisation changes the fitted coefficients. Then be ready to discuss why validation on random rows can overstate performance when observations are time-ordered. Finally, explain a neural network you know well enough to work through its gradients, training instability and behaviour under distribution shift.

Statistical reasoning

Derive conditional means, covariance identities, maximum-likelihood estimates and regression estimators. Check assumptions before applying the formula.

Machine learning

Explain regularisation, gradient-based training, sequence models and how you would test whether a model generalises beyond its training period.

Research decisions

Defend your target, feature construction, train/test split, baselines and failure analysis. Explain a negative result as carefully as a successful one.

As a rehearsal, take one of your own research projects and let a friend challenge its label definition, sampling method, leakage risks and out-of-sample evidence. Do this without slides. The Yerevan junior researcher vacancy emphasises economically sound ideas and lower-frequency signals; that makes research judgement, not just a polished model score, worth practising.

XTX Markets internship: the XTY Labs AI research process

For its New York XTY Labs AI Research Internship, XTX has a four-stage interview process in 2026. The archived posting targeted advanced-degree researchers, ideally PhD candidates, and described a 12–14-week internship with prospective start dates from January 2027. This is a specialised AI research programme, rather than a standard undergraduate trading internship.

  1. Recruitment introduction. Discuss your research background and what makes the role a fit. Prepare a concise description of your strongest original result.
  2. Dataset-based take-home. Receive a dataset and build an AI model from beginning to end. Practise forming a baseline, selecting a sound validation scheme, training the model and writing down the result and its weaknesses.
  3. Research Director interview. Discuss your research history, deep-learning knowledge and how you arrive at new ideas. Revisit the decisions in your papers and experiments.
  4. Final researcher interview: one hour. Meet an XTX quant researcher or XTY full-time researcher to discuss technical work and collaboration.

The take-home is the most distinctive part. For a realistic rehearsal, use a small public time-series dataset and build a documented pipeline: clean it, define the prediction target, fit a simple baseline, train a more expressive model, validate chronologically, compare performance and inspect where the model fails. As an EverythingQuant practice benchmark, aim for a reproducible three-hour first pass, then make a short written defence of each choice. The three-hour target is ours; XTX's posting did not specify an assignment time limit.

The same posting listed modern and classical machine learning, linear algebra, analysis, probability, hands-on programming and data engineering as assessment areas. It explicitly said prior finance experience was unnecessary. It also asked candidates to demonstrate serious research experience, so the standard for explaining original work is higher than for a general introductory internship.

Software engineering interviews: coding, C++ and systems

Algorithmic coding and efficient implementations are prominent in the published software interview accounts. A February 2025 developer candidate described LeetCode-hard problems and discussion of how to optimise the solution. Another 2025 candidate recalled being asked to code and analyse both time and space complexity. A separate October 2025 first-hand Blind account described several hard coding questions during the onsite, standard system design and a take-home assignment.

That is useful evidence for hard coding and follow-up analysis, without turning a single candidate's onsite into a universal two-question or 90-minute online assessment. For practice, solve a hard algorithm problem, explain the naive solution first, then improve it and walk through counterexamples. A strong session includes a dry run on repeated values, zero or empty inputs, and performance on large inputs.

For exchange trading C++ engineering, XTX's own vacancy asks for modern C++, data-structure and algorithm trade-offs, caches, memory paging, system calls and CPU execution behaviour. Make sure you can explain where a cache miss hurts a hot loop, why a memory allocation appears in a latency profile, and what can go wrong when two threads share state. Its published exchange-trading team description says C++ and Python are its primary languages.

The engineering details are not identical across teams. A 2026 Yerevan Python Developer candidate reported three technical interviews followed by a system-design/build assignment, with questions about Python memory management, the GIL, generators, asyncio and multiprocessing. XTX's London Shared Engineering posting, by contrast, emphasises Go services, Linux process and networking tools, build systems and CI/CD. Prepare against the actual role description rather than assuming every engineering job is a low-latency C++ seat.

EverythingQuant coding benchmark: practise one difficult algorithmic problem in 45 minutes, then spend 15 minutes explaining complexity, edge cases and how you would profile or test the implementation.

Three XTX-style technical questions, worked through

These are original EverythingQuant practice problems chosen to exercise the probability, machine-learning and engineering skills described above. They are not represented as past XTX interview questions.

A noisy signal: conditional expectation

Suppose an unknown standardised return is Y ~ N(0, 1). You observe a noisy forecast S = Y + E, where E ~ N(0, 3) is independent of Y. What are the conditional mean and variance of Y given S = 2?

Show the solution

The pair is jointly Gaussian, with Cov(Y, S) = Var(Y) = 1 and Var(S) = 1 + 3 = 4. The normal-conditioning formula gives

E[Y | S = 2] = Cov(Y,S) / Var(S) × 2 = (1/4) × 2 = 0.5.

Var(Y | S = 2) = Var(Y) − Cov(Y,S)² / Var(S) = 1 − 1/4 = 0.75.

The forecast is noisy, so the estimate moves only a quarter of the way from the prior mean towards the observed signal. As the observation noise grows, the estimate moves less. Check both limiting cases: near-zero noise makes the posterior mean approach 2, while enormous noise makes it approach 0.

Why ridge regression shrinks the fit

You fit a one-parameter model ŷ = bx on two observations, (x, y) = (1, 1) and (2, 2). Minimise (1 − b)² + (2 − 2b)² + b². What coefficient do you obtain, and how would you evaluate this model on a time-ordered dataset?

Show the solution

The objective is Σ(y − bx)² + λb² with λ = 1. Differentiating and setting the result to zero gives b = Σxy / (Σx² + λ). Here Σxy = 5 and Σx² = 5, so b = 5/6 ≈ 0.8333. Ordinary least squares, without the penalty, gives b = 1.

For chronological data, fit transformations and select hyperparameters using earlier observations only, validate on a later block, and hold back an even later test period. Never normalise using the full dataset before splitting: doing so allows future information into training. A useful follow-up is to explain how the answer changes as λ → 0 or becomes very large.

A streaming window: update the average in constant time

Implement a Python object that returns the mean of the most recent N prices after each new arrival. A full scan on every update costs O(N); can you make the update O(1) and use at most O(N) memory?

Show the solution and code

Store only the current window and maintain its running total. Subtract the oldest value before inserting a new one once the window is full:

from collections import deque

class RollingMean:
    def __init__(self, size):
        if size <= 0:
            raise ValueError("size must be positive")
        self.size = size
        self.values = deque()
        self.total = 0.0

    def add(self, value):
        if len(self.values) == self.size:
            self.total -= self.values.popleft()
        self.values.append(value)
        self.total += value
        return self.total / len(self.values)

# RollingMean(3): add 10 → 10, add 12 → 11,
# add 8 → 10, add 14 → 34/3.

Each update performs a constant number of deque and arithmetic operations: O(1) time with O(N) stored values. Test a window of size one, a partly filled window and the first eviction. For very large floating-point streams, discuss how accumulating round-off error could change the implementation.

For further exercises, work through EverythingQuant's probability interview problems or the Probability for Quants course. For algorithms, practise coding interview problems and data structures and algorithms in Python.

How hard are XTX Markets interviews?

Expect a high technical bar, especially in areas directly relevant to the job. The published junior quant process tests several mathematical subjects before four or five researcher discussions. Software candidates in 2025 reported hard algorithms and requests to justify optimisation choices. The AI internship adds an open-ended modelling exercise and a research conversation with a director.

The difficult part is often what happens after your first answer. An interviewer can ask you to derive a familiar formula, remove an assumption, find a counterexample, or explain why a result might disappear out of sample. Practise showing each step and correcting mistakes without losing the argument. A strong CV helps you reach a conversation; being able to defend the underlying work helps you finish it.

A focused XTX Markets preparation plan

Use the route that matches your application. The plan below is an EverythingQuant recommendation, not a description of the firm's scheduling or training requirements.

Suggested two-week preparation sprint
WhenQuant research / XTY LabsSoftware engineering
Days 1–4Derive conditional expectation, variance, OLS/ridge and basic eigensystems. Explain each step aloud.Practise two challenging algorithm patterns; review data-structure performance and prove complexity.
Days 5–8Build a small prediction pipeline with a chronological holdout; prepare to defend its leakage controls and baseline.Study the actual team's stack: C++ memory/cache behaviour and Linux for ETD, or Go, Linux and CI/CD for Shared Engineering.
Days 9–12Defend one neural-net architecture and one failed experiment; repeat the 75-minute maths drill.Complete a 45-minute hard-coding drill plus a 15-minute review; explain threading and performance trade-offs.
Days 13–14Mock research interview: assumptions, implementation, validation, critique. XTY applicants should rehearse a model take-home discussion.Mock screen: write code, test it, analyse costs and discuss the design of a small reliable service.

The fastest way to improve is to look at the specific errors you make. Re-derive formulas you could only recall, fix implementation edge cases you skipped and practise explaining the research choices you initially left vague. If your weakness is probability, start with the Probability for Quants foundations before adding more mock interviews.

XTX Markets interview FAQs

How many rounds does the XTX Markets interview have?

An XTX-authored Yerevan junior research listing specifies an online test plus four or five interviews. The 2026 XTY Labs AI internship posting specifies four stages, ending in a one-hour research interview. Software candidates report technical screens, coding and sometimes take-home work; there is no one verified engineer-wide round count.

Does XTX Markets use HackerRank or CodeSignal?

The published junior research vacancy confirms an online test but does not name a platform. The specific HackerRank or CodeSignal provider is not established by the reviewed first-hand evidence. Practise writing and testing code or maths answers in a timed environment rather than preparing for an assumed brand of assessment.

Are XTX Markets coding interviews LeetCode hard?

Some are. A February 2025 developer interview report explicitly describes hard LeetCode questions and optimisation discussions. An October 2025 first-hand software-engineering account also recalls multiple hard problems during an onsite. Include hard algorithm questions and complexity analysis in engineering preparation.

What is the XTX Markets internship assessment?

The documented XTY Labs AI research internship uses an end-to-end model-building take-home on a provided dataset, followed by conversations about research and deep learning. It is aimed at advanced-degree researchers. That is different from the junior quant researcher online maths test.

Do I need financial-market experience?

Not necessarily. XTX's XTY AI internship and C++ exchange-trading engineering postings both explicitly say previous finance experience is not required. Strong mathematical, research or systems skills come first. You should still be able to explain how the target team uses those skills.

How long does the hiring process take?

Candidate examples show a broad range. Two London quantitative-research interview accounts from 2023 reported roughly two weeks and two months respectively. An April 2026 Yerevan Python Developer candidate described a process extending beyond two months. Those are individual experiences, not a firm-wide average.

Is there an XTX Markets online assessment passing score?

No verified public cutoff emerged from the reviewed official material and original candidate accounts. A useful practice target is to solve each problem completely and check your derivation or code under time pressure, rather than optimising for an unsupported percentage.

Sources behind this guide

Interview details were checked against XTX's careers material, role descriptions and dated first-hand candidate reports. The technical examples and timed drills above were created by EverythingQuant.

Join our Newsletter and Receive the Latest Updates!

Main Links

Trade Courses Assessments Interview Prep Contact Us

Social Media

Facebook Instagram YouTube

Legal

Terms and Conditions Privacy Policy Privacy settings

Talent Acquisition

Looking to hire exceptional quant talent?
See how we can help.

© 2026 EverythingQuant. All Rights Reserved.