Candidates describe Experian software engineer interviews as a mix of timed online tests, one-way video questions, and conversations about past projects, Java or JavaScript fundamentals, and design. Experiences vary by team.
$122K
Avg. Base Comp
$150K
Avg. Total Comp
3-5 rounds
Typical Rounds
Not reported
Process Length
Experian software engineer interviews vary by team, but several candidates describe the same opening: a timed Codility assessment. One graduate candidate had two JavaScript algorithm problems in 45 minutes. Another had two coding problems within an hour plus a multiple-choice section, and was allowed to use Copilot but had to verify its output.
A one-way video interview also appears in more than one report. One candidate had four questions with one minute to think and one minute to answer. Another described 75 seconds of preparation and 90 seconds to respond. Prompts covered motivation, teamwork, and learning something new, so short, structured answers are worth rehearsing.
Live technical rounds depend on the role. One candidate faced separate front-end and back-end coding sessions, with JavaScript, Java, concurrency, and Spring questions. Another was pressed on precise Java OOP answers. Others were asked about SOLID and REST APIs, testing levels, React, GraphQL, or SQL query analysis. One candidate was asked to design a real-time trading platform, including CAP theorem trade-offs. Several candidates say interviewers focused on resume projects, so prepare to explain what you built and your own role.
Outcomes were mixed: four reports ended in accepted offers, one in a declined offer, and the rest in no offer. Several candidates mention slow scheduling or little follow-up, so ask recruiters about next steps early.
Synthesized from 11 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 Experian process.
The first question I got was a direct one: explain the SOLID principles. My interview was a relaxed online meeting over Microsoft Teams, and it felt more like a conversation than a grilling. Alongside SOLID, I was asked questions about REST APIs, so I'd make sure you can talk through the concepts clearly rather than just reciting definitions.
What stood out to me was how much the focus seemed to depend on the job scope. The questions I got matched the role I applied for, and that may not be the same for every opening. If you're unsure what a team cares about, ask the HR contact for tips before your interview. That conversation helped me decide where to spend my prep time, and it's worth doing before you spend hours on topics that may never come up.
I accepted the offer in the end. The tone was low-pressure, but I'd still prepare properly, since a relaxed format doesn't mean the questions are shallow.
Prep tip from this candidate
Be ready to explain the SOLID principles clearly and cover REST API basics, since the focus shifts with the job scope. Ask HR what the team emphasizes before the call so you can prioritize your prep.
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 Experian
What are confidence intervals and how are they useful
| Question | |
|---|---|
| Decision Tree Evaluation | |
| Hurdles In Data Projects | |
| Binary Tree Validation | |
| Client Solution Pushback | |
| Your Strengths and Weaknesses | |
| Generative AI Privacy | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Find the Missing Number | |
| Prime to N | |
| Rectangle Overlap | |
| Google Maps Improvement | |
| String Subsequence | |
| Triplet Counting | |
| Nearest Common Ancestor | |
| Groups of Anagrams | |
| Messenger Service Design | |
| Longest Increasing Subsequence | |
| Radix Addition | |
| Most Repetition | |
| Production Model Monitoring | |
| Find Duplicate Numbers in a List | |
| Dijkstra implementation | |
| Filling Supermarket Bag | |
| Target Indices | |
| Evaluate News | |
| Median O(1) | |
| 85% vs 82% | |
| RAG Strict Source Control |
Synthesized from candidate reports. Individual experiences may vary.
Several candidates report starting with a recruiter, talent manager, or HR call about their background and the role. One candidate was also asked about their other interview pipeline. Scheduling and follow-up may vary, so ask about next steps at the end of the call.
Candidates report a timed Codility test early on. One described two JavaScript algorithm problems in 45 minutes; another described two coding problems within an hour plus multiple-choice questions. Typically this appears to be a first filter, so practice clean, working solutions under time pressure.
Some candidates report recording answers to a small set of questions with strict time limits, such as one minute to think and one minute to answer. Topics included motivation for the role, strengths, teamwork, and learning something new. This format may not apply to every team.
Candidates report online or in-person conversations with a manager, team lead, or team members. These often focused on past projects and resume skills, and some included SQL, REST, SOLID, testing, React, or GraphQL questions. Be ready to explain your specific contribution to each project you list.
Technical depth reportedly depends on the role. Candidates describe live front-end and back-end coding, Java OOP and concurrency questions, a short design write-up, and in one case a real-time trading platform design with CAP theorem trade-offs. Preparation should follow the job description closely.
