Resmed Software Engineer interview typically runs 2-4 rounds: recruiter screen, online assessment, technical interview, and sometimes team or hiring manager interviews. The process usually takes about 2 weeks and can be broad, with recruiter communication gaps reported.
$93K
Avg. Base Comp
$129K
Avg. Total Comp
3-4
Typical Rounds
2-4 weeks
Process Length
We’ve seen Resmed evaluate software engineers as if they’re joining a product team that has to ship across devices, cloud, and healthcare workflows at once. The recurring pattern is breadth first: candidates report assessments and interviews that span SQL, DBMS, coding, systems thinking, and resume-based discussion, with one experience even surfacing a Java-specific deep dive that wasn’t obvious from the role description. That tells us the company is looking for engineers who can move comfortably between implementation details and practical product constraints, not just solve isolated algorithm problems.
A second theme is that Resmed seems to care a lot about whether you can explain your thinking clearly in context. Multiple candidates described questions anchored in projects, coursework, or recent lessons learned, and the strongest rounds felt conversational rather than scripted. We’ve also seen some inconsistency in how that standard is delivered: one candidate was pushed hard on fundamentals like HTTP status codes and object orientation, while another described a much more supportive, discussion-style interview. The non-obvious make-or-break here is precision under ambiguity — being able to answer basic technical questions cleanly, connect your background to the role, and not get thrown when the interviewer shifts from broad product thinking to stack-specific detail.
Synthetized from 4 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 Resmed process.
I first went through an online assessment, and that was what got me into the technical round. The OA was pretty broad and had six sections touching different areas: DSA, DBMS, SQL, two coding questions, and a set of MCQs. I thought I did reasonably well there — both of my codes compiled, and I felt decent about the multiple-choice portion — so I was invited to the next stage.
The technical interview itself was fairly standard on paper, but it had a few surprises. I was asked some very basic systems design and algorithm questions, and there was also a Java-heavy angle that I wasn’t expecting from the role description. One interviewer kept pushing on Java-specific details, which made the conversation feel more stack-specific than I had prepared for. I also got a question along the lines of whether it’s possible to generate a random sequence using a computer algorithm, which was more of a conceptual check than a deep coding problem. Another review of the process mentioned LC-style problems and architecture/system design in the onsite, and that matches the overall feel: a mix of coding, design, and practical resume-based discussion. In my case, the interviewers seemed satisfied with my answers, but after that I just stopped hearing back. The process was slower than I expected because of recruiter communication gaps, and I ultimately did not get an offer. My main takeaway is to be ready for a broad OA, then review your resume carefully and be comfortable answering Java and basic design questions even if the posting doesn’t emphasize them.
Prep tip from this candidate
Be ready for a broad OA covering DSA, DBMS, SQL, MCQs, and two coding questions, then expect the technical round to lean on basic systems design plus Java-specific follow-ups. Also review your resume closely, since the interview can pivot into resume-based questions rather than just generic coding.
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 Resmed
Make an algorithm to generate uniformly distributed zeros and ones using only an unfair coin toss
| Question | |
|---|---|
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Prime to N | |
| The Brackets Problem | |
| Random SQL Sample | |
| Find the Missing Number | |
| Upsell Transactions | |
| Detecting ECG Tachycardia Runs | |
| Hurdles In Data Projects | |
| Cyclic Detection | |
| Size of Joins | |
| Employee Project Budgets | |
| Retailer Data Warehouse | |
| Sum to N | |
| Integer to Roman | |
| Equivalent Index | |
| Get Top N Frequent Words | |
| Paired Products | |
| Twenty Variants | |
| Delivery Estimate Model | |
| Bagging vs Boosting | |
| Valid Anagram | |
| Groups of Anagrams | |
| Flight Records | |
| Closed Accounts | |
| Target Indices | |
| Sort Strings |
Synthesized from candidate reports. Individual experiences may vary.
An initial conversation with the internal recruiter to confirm background and role fit. In some cases, this included a few software testing or fundamentals questions, and the recruiter also discussed the next steps in the process.
Candidates may complete an automated screening before live interviews. One experience described a broad OA with six sections covering DSA, DBMS, SQL, two coding questions, and MCQs, while another used a HireVue with five timed questions focused on coursework, motivation, and a recent project.
A live technical round that can include coding, basic systems design, algorithms, and stack-specific questions. Interviewers also asked Java fundamentals, HTTP status codes, object-oriented concepts, and conceptual questions, with some candidates noting the discussion was broader and more practical than expected.
A conversational round with the hiring manager or team members that mixes behavioral and technical discussion. Candidates were asked open-ended questions like recent lessons learned, project walkthroughs, and how they approach problem-solving or teamwork.