Three candidates who received AXA Software Engineer offers describe different paths: HR calls, a recorded video round, Java questions of varying depth, and English checks. Prepare project stories and Java basics.
$105K
Avg. Base Comp
$125K
Avg. Total Comp
2-3 rounds
Typical Rounds
Not reported
Process Length
Three candidates describe AXA Software Engineer interviews that ended in offers, but the processes were not identical. One reports three rounds, another reports two, and the third describes several conversations without giving a total. Treat the sequence below as a range of experiences rather than a fixed script.
The most consistent theme is background and motivation. Candidates were asked about their experience, why they wanted AXA, and projects they had worked on. One also recalls a question about handling high-pressure situations, and another found the video and manager conversations general and behavioral.
Technical depth differed a lot. One candidate was asked about Maven, Spring and Hibernate during a second HR conversation. That candidate then sat with a team engineer for multiple-choice questions on Java OOP, Struts and programming definitions, plus pseudo-code on paper and questions on RUP and Scrum. Another found the technical questions limited and conversational. The third recalled only basic Java questions tied to earlier work.
Two candidates mention English being assessed, and one of them folded it into a technical round. One candidate faced a recorded video round with about 30 seconds to think and one to two minutes to answer. Another reports a full-day test, with a decision about two weeks later. Prepare clear project stories and basic Java, and ask your recruiter which format applies to you.
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 Axa 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 Axa
In which case would you use a bagging algorithm versus a boosting algorithm
| Question | |
|---|---|
| Stakeholder Communication | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Random SQL Sample | |
| P-value to a Layman | |
| Size of Joins | |
| Hurdles In Data Projects | |
| Type-ahead Search | |
| Cyclic Detection | |
| Three Zebras | |
| Precision and Recall | |
| Success Measurement | |
| Target Indices | |
| RAG Strict Source Control | |
| Transformer Encoder Layer | |
| Duplicate Rows | |
| Modifying a Billion Rows | |
| Type I and II Errors | |
| Same Characters | |
| Swap Variables | |
| Integer String Addition | |
| The Longest Journey | |
| Employee Benefits Outreach | |
| Triangle as Binary Array | |
| Blob Indexing | |
| Why Do You Want to Work With Us | |
| Drink Production Allocation | |
| International e-Commerce Warehouse |
Synthesized from candidate reports. Individual experiences may vary.
Two candidates describe an HR conversation about their background, years of experience and motivation for joining AXA. One of them reports a second HR conversation on personality assessment results and cultural fit, which also covered experience with Maven, Spring and Hibernate. The third candidate instead opened with a recorded video round: about 30 seconds to think, one to two minutes to answer, no pausing or restarting, on academic background, experience and career goals.
One candidate had a technical interview with a team engineer: multiple-choice questions on Java OOP, Struts and programming definitions, pseudo-code on paper, and questions on development tools and methodologies like RUP and Scrum. Another had a technical assessment combined with an English test, covering past projects and pressure handling, and found it conversational. The third recalls only basic Java questions tied to earlier work.
One candidate reports a full-day test evaluating technical ability and performance in a working environment, with a decision after about two weeks. Another reports a live conversation with a hiring manager about specific projects and career aspirations, which was general and behavioral. The remaining candidate does not describe a distinct final stage, so ask your recruiter what to expect.
