RELX interview process & guide 2026
Everything we know about interviewing at RELX: the process stage by stage, what each round tests, and compensation by level.
- 1Application review and recruiter screenings
- 2Assessments and initial evaluation
- 3Technical and competency interviews
- 4Comprehensive, deep-dive, and final decision stages
Interviewing at RELX
You should expect a multi-stage process that combines recruiter screening with technical and competency checks. Across roles, the interview topics are dominated by Java, QA Engineering, analytics, algorithms and problem solving, and role-specific domains like product and sales strategy.
What they actually test comes through the topic mix. You will see assessments or discussions that touch Java, QA Engineering and testing, SDLC, analytics, and algorithms and problem solving. For non-engineering roles in the dataset, the same “technical skills” framing shows up as case study analysis, technical skills for sales strategy and planning or account territory planning, and technical skills for product management.
From candidate reports, the process appears to lean medium difficulty overall, with 57.4% medium and 29.0% easy. The aggregated offer rate in the dataset is 0.0%, so your main job is to treat every stage as a performance evaluation and make sure your preparation matches the listed topic areas.
The topic distribution is unusually concentrated: Java, QA Engineering, analytics, and product or project management fundamentals each show up at the top percentile levels, so you will likely be evaluated against specific technical foundations, not just role generic fit.
How hard is the RELX interview?
Aggregated from 166 interview experiencesAbout 1 in 2 candidates with a known outcome convert.
The interview process, end to end
4 rounds · based on 166 candidate reports- 1Application review and recruiter screenings
Your application is reviewed first to assess qualifications and fit. Then you go through recruiter screening and possibly an additional recruiter screening or conversational screening to confirm your background and alignment with the role.
- 2Assessments and initial evaluation
You may complete cognitive and aptitude tests to evaluate analytical and problem solving skills. The dataset also references an assessment center format as a high prominence technical theme, so expect structured evaluation beyond a single interview.
- 3Technical and competency interviews
You may have architectural discussions for system design and architecture in the relevant role, plus competency based interviews focused on role capabilities. The topic data indicates heavy coverage of Java, QA Engineering and testing, SDLC, analytics, algorithms and problem solving, and in some roles case study analysis and technical skills for product or sales planning.
- 4Comprehensive, deep-dive, and final decision stages
You may meet a panel in a comprehensive interview, and then continue with deep dive discussions with a hiring manager and key team members. The loop ends with final interviews with business stakeholders and HR representatives, followed by a final decision making stage where the hiring decision is made.
What RELX actually tests for
How prominent each skill is across reported loopsFind the guide for your role
This is your next step: open the guide for the role you are interviewing for. Each one carries the questions RELX interviewers actually ask that position, the loop structure, and pay by level.
What RELX pays, by level
Estimated total compensation: base salary plus stock and annual cash bonus.
What separates offers from rejections
Patterns from candidates who got offers, and the mistakes that most often sink a loop.
Do this
- Prepare to discuss Java clearly, not just syntax. Be ready to connect Java to software development life cycle concepts like how you build, test, and deliver.
- Practice analytics and case study style reasoning. Focus on how you interpret requirements, structure an answer, and justify decisions using data and evidence.
- For QA roles, be ready for testing and quality thinking. Walk through how you would prevent defects, validate behavior, and reason about quality under constraints.
- Be ready for algorithms and problem solving plus an assessment center format. Use a calm, structured approach, and show your reasoning step-by-step rather than jumping to the final answer.
Avoid this
- Do not assume the process is purely behavioral. The topic data shows very prominent technical areas like Java, QA Engineering, analytics, and algorithms, so you need technical preparation alongside any leadership or sales strategy prep.
- Avoid giving high-level answers only. Several listed topics imply analysis and coding under constraints or case study analysis, so you should be ready to demonstrate method, not just opinions.
- Do not ignore SDLC. SDLC is listed as a prominent technical topic, so be prepared to explain how development and quality practices fit together across a delivery process.
- Do not rely on recruiter chat alone to cover the technical gaps. Recruiter screening steps exist, but the dataset also includes comprehensive and final interview stages where deeper technical and competency evaluation is represented.
RELX interview FAQ
Answered from real candidate and workplace dataWhat is the overall difficulty level like?
Across candidate reports, 29.0% of difficulty was easy, 57.4% was medium, 12.3% was hard, and 1.3% was very hard. Plan for mostly medium-level evaluation, but still prepare for harder technical or analytical tasks.
Do candidates get offers in this dataset?
The aggregated offer rate in the provided candidate reports is 0.0%. Treat that as a limitation of the dataset rather than a prediction for your outcome, but it means you cannot count on offers being common in these reports.
What topics should I prioritize most?
Prioritize Java, QA Engineering, analytics, and product management and product-related technical skills, all of which have percentile 100 in the topic data. Also prioritize algorithms and problem solving, and assessment center format topics, both at very high percentiles.
How long is the interview loop?
The provided data lists the process stages and what they include, but it does not include specific durations or total timeline. Use the stage sequence below to map what you will likely experience, but do not expect the dataset to specify exact time ranges.
Is there coding or ML-style work?
The topic data includes coding exercises or writing code under constraints associated with Machine Learning and AI at percentile 93. It also includes Java at percentile 100, so expect coding-focused evaluation where relevant to your role.
Can I re-apply if I do not pass?
The supplied data does not say anything about re-application or retry policies. If you want an official answer, you would need to ask the recruiter during your process.
Ready for your RELX interview?
Practice the exact questions from this guide with AI feedback, and walk into your loop knowing what to expect.






