Experian Software Engineer candidates report a recruiter call, manager discussion, team technical interview with front-end and back-end live coding, and a later short design exercise.
$125K
Avg. Base Comp
$145K
Avg. Total Comp
4 rounds
Typical Rounds
3-5 weeks
Process Length
One reported Experian Software Engineer process began with a recruiter phone call, followed by an online conversation with the hiring manager. That candidate described the manager discussion as largely fit-oriented, while also noting that details about the team and technical stack were not always presented consistently. Prepare a concise account of how your prior work matches the role, and use the conversation to clarify the team’s actual needs.
The reported technical interview involved team members and split practical work across front end and back end. Expect to explain your code as you write it, not simply arrive at an answer: the candidate encountered live coding in both areas, discussion of JavaScript and Java functions, and questions on concurrent collections, locking mechanisms, and Spring. Review those topics at the level of work you can genuinely discuss, especially the tradeoffs behind implementation choices.
A later design challenge was described as a one-page exercise centered on explaining tradeoffs rather than completing a full system-design build. Practice structuring a short design explanation: state the assumptions, identify alternatives, and justify the choice. This sequence comes from one detailed candidate account, so its order and emphasis may vary by team.
Synthesized from 3 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 process felt a bit drawn out, but it was fairly straightforward once it got going. My first round was a basic online Codility test, and that was followed by an in-person round at the office about 2 to 3 weeks later. I interviewed in March for a senior software engineer role, so the timeline was not immediate, but it also wasn’t completely chaotic. The first screen was pretty light and focused on fundamentals, while the second round was more of a face-to-face conversation.
What stood out most was that the in-person round leaned heavily on my background and previous work. I was asked to explain the projects I had worked on and walk through them in detail, so it was less about tricky algorithm questions and more about whether I could clearly discuss real experience. The overall vibe was professional and not overly aggressive. I did notice some delay between steps, which made the process feel longer than it needed to be, but communication was still good enough that I knew where I stood. I ended up receiving an offer, so despite the wait, the process was manageable. My main takeaway is to be ready to talk through your past projects clearly and to expect a basic online coding test before any onsite conversation.
Prep tip from this candidate
Be ready for a basic Codility-style online test first, then practice explaining your previous projects clearly in an in-person conversation. The second round seemed to focus more on walking through real work than on deep algorithm puzzles.
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
Describing a data project and its challenges
| Question | |
|---|---|
| Binary Tree Validation | |
| Confidence Interval Explanation | |
| Decision Tree Evaluation | |
| Client Solution Pushback | |
| Your Strengths and Weaknesses | |
| Generative AI Privacy | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Prime to N | |
| Find the Missing Number | |
| Rectangle Overlap | |
| String Subsequence | |
| Google Maps Improvement | |
| Triplet Counting | |
| Nearest Common Ancestor | |
| Groups of Anagrams | |
| Messenger Service Design | |
| Longest Increasing Subsequence | |
| Radix Addition | |
| Most Repetition | |
| Production Model Monitoring | |
| Filling Supermarket Bag | |
| Find Duplicate Numbers in a List | |
| Dijkstra implementation | |
| Target Indices | |
| Median O(1) | |
| 85% vs 82% | |
| RAG Strict Source Control | |
| Target Value Search |
Synthesized from candidate reports. Individual experiences may vary.
One candidate reported starting with a recruiter phone call. They found the conversation fast-paced, so prepare a brief introduction and a clear explanation of the experience most relevant to the Software Engineer role.
The same candidate described an online manager interview as primarily fit-focused. Candidates may be asked to connect past roles to the job needs, while using the discussion to clarify team and stack expectations.
One reported technical round with team members included live coding for both front end and back end, plus discussion of JavaScript and Java functions. Be ready to narrate practical implementation decisions.
A later round included a one-page design challenge. The candidate characterized it as explaining tradeoffs rather than delivering a full system-design exercise, so practice communicating assumptions and choices succinctly.
