Experian Software Engineer interview typically runs 3 rounds: recruiter call, online coding test, technical interview. Timeline is about 1 to 3 weeks between steps, and the process is structured and fairly straightforward.
$116K
Avg. Base Comp
$141K
Avg. Total Comp
4-5
Typical Rounds
3-5 weeks
Process Length
We’ve seen Experian screen for a very specific mix of fundamentals and relevance: candidates who can move through a basic coding check, then immediately connect their past work to the role without drifting into theory. Multiple experiences point to the same pattern — the company is less interested in flashy algorithm puzzles than in whether you can explain real projects clearly and show that your background maps to what the team actually needs. That shows up in the senior-level conversations, where the discussion leaned heavily on prior work, and in the more technical path, where questions were tied directly to JavaScript, Java, Spring, concurrency, and the job description itself.
A recurring theme is that Experian’s process can feel a little opaque at the start, but once you’re in the conversation, the evaluation is fairly concrete. Our candidates report timed assessments with tight constraints, plus interviews that are structured and sometimes strict, especially around motivation and fit. The non-obvious make-or-break factor here is not just technical correctness; it’s whether you can stay crisp when asked why Experian, why this role, and why your experience is the right match. We’ve also seen that the company values candidates who can discuss tradeoffs in design work and speak comfortably about implementation details, especially when the role spans both front end and back end.
Synthetized from 3 candidates 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.
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
Given the root node, verify if a binary search tree is valid or not.
| Question | |
|---|---|
| Confidence Interval Explanation | |
| Your Strengths and Weaknesses | |
| Subscription Overlap | |
| Prime to N | |
| Find the Missing Number | |
| Rectangle Overlap | |
| Hurdles In Data Projects | |
| String Subsequence | |
| Google Maps Improvement | |
| Nearest Common Ancestor | |
| Groups of Anagrams | |
| Longest Increasing Subsequence | |
| Radix Addition | |
| Find Duplicate Numbers in a List | |
| Most Repetition | |
| Filling Supermarket Bag | |
| Target Indices | |
| Dijkstra implementation | |
| Median O(1) | |
| Messenger Service Design | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Check Matching Parentheses | |
| Moving Window | |
| String Palindromes | |
| 5th Largest Number | |
| NxN Grid Traversal | |
| Data Stream Median | |
| Rearranging Digits | |
| Impossibly Iterative Fibonacci |
Synthesized from candidate reports. Individual experiences may vary.
The process often starts with a recruiter call to confirm basic fit, background, and interest in the role. Candidates described it as professional and communicative, though sometimes brief and a bit rough on connection quality.
Candidates are typically sent a timed Codility test, usually focused on JavaScript and algorithmic problem solving. One experience included two coding problems in 45 minutes, with little context provided ahead of time.
After the assessment, some candidates had an online interview with the manager that focused on motivation, role fit, and team alignment. This round was described as a fit conversation, with questions about why the candidate wanted the role and what they knew about Experian.
The technical round can include live coding and is often split into front-end and back-end sections. Candidates reported questions on JavaScript, Java, concurrency, Spring, and practical experience, along with a design-style prompt that emphasized tradeoffs over pure coding.
Some candidates were brought onsite for a face-to-face conversation after a delay of about 2 to 3 weeks. This stage leaned heavily on discussing past projects and walking through previous work in detail, with less emphasis on tricky algorithm questions.