Resmed Software Engineer candidates reported either an online assessment or recruiter screen before a technical interview, with questions spanning coding fundamentals, Java, systems design, and resume-based discussion.
$144K
Avg. Base Comp
$171K
Avg. Total Comp
2 rounds
Typical Rounds
2-4 weeks
Process Length
Resmed Software Engineer interviews in the available reports followed two different entry paths. One candidate completed a broad online assessment covering DSA, DBMS, SQL, coding questions, and multiple-choice questions before a technical interview. Another began with an internal recruiter screen that included software-testing questions, then met with three members of a test automation team. The clearest recurring preparation theme is practical technical breadth rather than a single narrow format.
For the technical conversation, candidates described basic systems-design and algorithm questions alongside Java-specific discussion. Reported prompts included reversing a linked list, whether a computer algorithm can generate a random sequence, Java concepts such as WAR versus JAR and JPA, and explaining why a team chose Spring Boot, microservices, cloud separation, or reusable components. A separate candidate reported direct fundamentals including HTTP 401 versus 403 and mobile application file extensions. Prepare to explain the choices on your resume clearly, because implementation and architecture follow-ups may grow from your past work.
The available Software Engineer accounts describe differing stages, so the exact screening route and technical emphasis may vary. The reported accounts did not result in an offer, so use them to focus preparation rather than to predict an outcome.
Synthesized from 5 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 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 | |
|---|---|
| Cloud-Agnostic Deployments | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Prime to N | |
| Random SQL Sample | |
| The Brackets Problem | |
| Find the Missing Number | |
| Upsell Transactions | |
| Detecting ECG Tachycardia Runs | |
| Size of Joins | |
| Recurring Character | |
| Scrambled Tickets | |
| Cyclic Detection | |
| Maximum Profit | |
| Hurdles In Data Projects | |
| Retailer Data Warehouse | |
| Employee Project Budgets | |
| Integer to Roman | |
| Sum to N | |
| Twenty Variants | |
| Equivalent Index | |
| Get Top N Frequent Words | |
| Bagging vs Boosting | |
| Completed Shipments | |
| Delivery Estimate Model | |
| Paired Products | |
| Groups of Anagrams |
Synthesized from candidate reports. Individual experiences may vary.
Candidates reported either a broad online assessment with DSA, DBMS, SQL, coding, and multiple-choice sections, or a recruiter screen with software-testing questions. Prepare for either route, since the available reports do not establish one universal starting format.
Candidates reported a technical discussion after the initial stage. Topics included reversing a linked list, basic system design, Java and Spring concepts, HTTP status codes, and platform/file-format fundamentals. One candidate described this conversation as 30 minutes.
One candidate was asked to discuss cloud choices, reusable components, data passing, Spring Boot versus Spring, and a move from a monolith to microservices. Be ready to describe the reasoning behind projects and implementation choices on your resume.
