Two candidates who interviewed for Mirion Medical Software Engineer roles describe a phone screen followed by a technical conversation or panel, with questions spanning .NET, SQL, Node.js, and database design.
$115K
Avg. Base Comp
$137K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Two candidates who interviewed for Software Engineer roles at Mirion Medical describe very different experiences, so it helps to prepare for the substance rather than assume one fixed format. The reports also point to different technical stacks.
One candidate began with a phone screen about background and work experience, followed by fairly straightforward .NET and SQL questions. A second round, on Skype or in person, covered technical skills, communication, and challenges from past projects. This candidate found the questions vague and the hiring manager's style haphazard. They also reported weeks of silence after the first call, unanswered HR emails, and several reschedules, and said the whole process stretched over a month. No offer followed.
The other candidate had a 30-minute recruiter call, then an hour-long technical phone screen with the hiring manager built around a past project: the decisions made and what they would change in hindsight. The final round was a virtual on-site with three interviewers mixing technical and behavioral questions, including Node.js promises, async/await, child processes, and database design. This candidate described the tone as collaborative and received an offer.
The common thread is a past project you can explain in depth, along with practical backend and database fundamentals. Neither report describes heavy algorithm work.
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 Mirion Medical 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 Mirion Medical
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Merge Sorted Lists | |
| P-value to a Layman | |
| Hurdles In Data Projects | |
| Target Indices | |
| 85% vs 82% | |
| Duplicate Rows | |
| Slow SQL Query | |
| DDoS Attack Response | |
| String Palindromes | |
| Pipeline Transformation Failures | |
| Distributed Authentication Model | |
| Client Solution Pushback | |
| Decision Tree Evaluation | |
| Testing Constraints | |
| Your Strengths and Weaknesses | |
| Marketing Workflow Optimization | |
| Why Do You Want to Work With Us | |
| Azure Kubernetes Infrastructure | |
| Duplicate Product Names | |
| Stakeholder Communication | |
| Presentations and Insights | |
| Meta in an Emerging Market | |
| Closest SAT Scores | |
| Employee Salaries | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| String Shift |
Synthesized from candidate reports. Individual experiences may vary.
Both candidates describe opening with a phone conversation about their background and work experience. One report describes a roughly 30-minute call with a recruiter to gauge interest in the role. The other describes the call moving on to fairly straightforward .NET and SQL questions, with an interviewer whose expectations were not always clear.
One candidate had an hour-long technical phone screen with the hiring manager, walking through a past project, the decisions behind it, and what they would do differently. The other candidate describes a second-round Skype or in-person meeting on technical skills, communication, and past project challenges, which felt loosely structured.
The candidate who received an offer describes a final virtual on-site with three interviewers, mixing technical and behavioral questions. Technical topics included promises and async/await in JavaScript, child processes in Node.js, and how to structure a system and database design around Node.js. The other report does not mention a panel round.
One candidate received an offer and joined the team shortly afterward. The other reports weeks of silence after the first call, HR not answering emails or phone calls, multiple reschedules, and no offer, with the process lasting over a month. Timing and communication differed sharply between the two reports.
