Milliman software engineer candidates describe conversational interviews built around fundamentals: Python, SQL, OOP, resume projects, and clear communication. Formats varied, from two chat-style rounds to a longer multi-stage process.
$103K
Avg. Base Comp
$120K
Avg. Total Comp
2-5 rounds
Typical Rounds
Not reported
Process Length
Milliman software engineer interviews, as candidates describe them, lean toward fundamentals and clear explanation rather than heavy algorithm drilling. Across four reports, the common thread is that interviewers wanted to hear how you think.
One candidate reported a technical sequence of Python basics (data types, functions, syntax) with small coding tasks, a logic puzzle segment, SQL on aggregation, joins and filtering, and an object-oriented discussion of encapsulation, inheritance, polymorphism and abstraction. Another described a one-way video screen mixing behavioral prompts with Python, SQL and Excel questions. It was followed by a roughly three-hour block of three conversations with team members who went deep on resume projects and career goals.
A third candidate, who accepted an offer, described two conversational rounds with no whiteboarding. Questions included explaining recursion to a grandparent, a controversial opinion, and views on AI. A fourth reported an online aptitude and computer science test, a group discussion, a technical interview that began with resume projects before moving to Java multithreading, SQL joins, OOP and DSA, then an HR round and a final presentation. That candidate did not receive an offer.
The formats differ, so confirm your own schedule with your recruiter. The practical takeaways are to be ready to defend every project on your resume, to practice talking through SQL and Python solutions aloud, and to prepare plain-language explanations of technical ideas. Expect some personal and motivational questions as well.
Synthesized from 7 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 Milliman process.
I started with a phone screen that was pretty relaxed—mostly behavioral stuff designed to get a sense of who I was and how I think. The interviewer asked me to walk through a time when I had to tackle something completely new, which felt less like a tech grilling and more like a genuine conversation about my learning style and adaptability.
The on-site round was where things got more technical. I met with the team, and they mixed in some coding questions alongside the behavioral ones. The vibe was still collaborative rather than adversarial. I remember being asked about OOP principles, particularly encapsulation, since I'd mentioned Java as my strongest language. There was also a logic puzzle—something like determining whether a given number was prime—that required me to think through the problem and write out pseudocode or actual code. The questions weren't meant to be trick questions; they felt like they were genuinely trying to understand how I approach problem-solving and whether my technical foundation was solid.
What surprised me most was how much the interview was structured around getting to know my thought process rather than hammering me with obscure algorithmic challenges. They seemed to care more about how I'd learn on the job and work with the team than whether I could solve a LeetCode hard in fifteen minutes. The overall experience felt more like a working interview than a traditional technical gauntlet.
Prep tip from this candidate
Focus on articulating your OOP knowledge clearly, especially if you mention Java—be ready to explain encapsulation and other core principles with concrete examples. For logic puzzles like primality checking, practice writing clean pseudocode or actual code under mild time pressure, and talk through your reasoning as you solve.
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 Milliman
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Employee Salaries | |
| Random SQL Sample | |
| Bagging vs Boosting | |
| Size of Joins | |
| Hurdles In Data Projects | |
| P-value to a Layman | |
| Type-ahead Search | |
| Three Zebras | |
| Precision and Recall | |
| Cyclic Detection | |
| Target Indices | |
| Production Model Monitoring | |
| RAG Strict Source Control | |
| Transformer Encoder Layer | |
| Success Measurement | |
| Duplicate Rows | |
| Type I and II Errors | |
| Swap Variables | |
| Modifying a Billion Rows | |
| Same Characters | |
| Integer String Addition | |
| The Longest Journey | |
| Solo ML Deployment | |
| Triangle as Binary Array | |
| Drink Production Allocation | |
| International e-Commerce Warehouse | |
| Shortest Path Algorithms | |
| Client Solution Pushback | |
| Your Strengths and Weaknesses |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report different openings. One described a one-way video interview with about five questions mixing behavioral prompts with Python, SQL and Excel. Another reported a timed online test covering aptitude, logical reasoning and computer science. Ask your recruiter which format applies to you.
One candidate reported a first round on Python basics with small coding tasks, then a logic puzzle segment, SQL covering aggregation, joins and filtering, and an OOP discussion. Another reported Java multithreading, SQL joins, OOP and DSA questions. Expect to explain your reasoning aloud as you answer.
Candidates report that interviewers spent significant time on resume projects and career goals. One described a three-hour block split into three parts, each with two team members. Another said the technical round opened with project walk-throughs. Be ready to explain what you built and why you made each choice.
Reported prompts include explaining recursion simply, a controversial opinion, views on AI, and the best or worst part of college. Candidates describe the tone as collaborative, and one said interviewers gave space to reconsider an answer. These questions appear to test communication and fit alongside technical skill.
One candidate reported an HR round and a final presentation to company leadership after the technical stage. Another reported that the process wrapped up quickly after the final team conversation. Outcomes among the four Software Engineer reports were mixed: one accepted an offer and three did not receive one.
