Candidates describe a Gns Healthcare software engineer process that mixes coding, project deep dives, and behavioral or managerial conversations. One also reports architecture and Java concurrency questions. Reports range from friendly to demanding.
$111K
Avg. Base Comp
$132K
Avg. Total Comp
3-6 rounds
Typical Rounds
1 month
Process Length
Candidates who interviewed for software roles at Gns Healthcare describe a process that leans on explaining your own work clearly, with coding alongside it. Several were asked to walk through past projects, design decisions, and their specific contributions. One candidate said the interviews emphasized communication and problem-solving approach over pure coding speed.
The coding bar looks uneven across reports. One software developer was asked to implement a C++ string class and convert numbers to words. Another had a math-leaning online assessment, then a short Python problem judged on readable naming and clear explanation. A third faced a four-problem, thirty-minute online assessment with one hard question, and later a dynamic programming problem. Treat the language and difficulty as varying by team.
One software engineer reported an architecture round covering REST APIs, microservices, message brokers, GCP, and advanced Java. That candidate said deep Java knowledge was tested, especially multithreading, socket programming, and core concurrency patterns. If your target team works in Java, refresh those fundamentals and be ready to explain why a design works, not just how.
Behavioral questions appear in several accounts, including working with difficult teammates and resolving disagreements. Candidates mostly describe interviewers as friendly. Timelines vary, and one candidate reported waiting longer than expected for updates. Evidence is limited and mixed, so prepare for both conversational and technical formats.
Synthesized from 13 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 Gns Healthcare process.
The process kicked off with an online assessment that wasn't your typical LeetCode grind—it was mostly math questions, surprisingly straightforward. After I passed that stage, a recruiter reached out to help coordinate the next steps. The main interview was a 45-minute call that mixed behavioral questions with one LeetCode problem, then two follow-ups on variations of the same problem. On the technical side, they gave me a simple Python problem—something like capitalizing the first letter of each word in a string. What they really cared about was how I approached it: did I use meaningful variable names, was my code readable, and could I explain my thinking clearly? The vibe throughout was collaborative rather than adversarial. The recruiter was genuinely supportive during prep, and everyone I spoke with came across as kind and approachable. They seemed more focused on understanding how I learn and debug than on tricking me with edge cases. The whole thing felt less about proving I was a genius and more about checking that I could write clean Python, think through a problem step by step, and work well with others.
Prep tip from this candidate
The OA is lighter than typical SDE assessments and leans toward math; focus on clear Python style and naming conventions for the technical interview. Expect behavioral questions alongside coding, so prepare examples of how you learn new things and your debugging 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 Gns Healthcare
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Empty Neighborhoods | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| String Shift | |
| Top 3 Users | |
| Raining in Seattle | |
| First Touch Attribution | |
| Job Recommendation | |
| Minimum Change | |
| Find the First Non-Repeating Character in a String | |
| Daily Retention Summary | |
| Find the Index with Equal Left and Right Sum | |
| Delivery Estimate Model | |
| Find Bigrams | |
| Detecting ECG Tachycardia Runs | |
| Size of Joins | |
| Last Transaction | |
| Friendship Timeline | |
| The Brackets Problem | |
| Level Of Rain Water In 2D Terrain | |
| P-value to a Layman | |
| N-gram Dictionary | |
| Google Maps Improvement | |
| Four Person Elevator | |
| Third Purchase | |
| Nearest Common Ancestor | |
| Basic Regex | |
| Type-ahead Search | |
| Cyclic Detection |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report different openers. One described a math-leaning online assessment, another four LeetCode-style problems in thirty minutes, and others a recruiter or technical screening call. Expect some form of screen before the main interviews, but the format may differ by team.
Candidates report coding tasks that depend on the team: a C++ string class and number-to-words conversion, a short Python string problem judged on readability, binary search and sorting, or a dynamic programming problem. Interviewers typically seem to care about clear reasoning and clean code alongside correctness.
Several candidates report being asked to walk through past projects, their specific contributions, and design decisions. One described an architecture round on REST APIs, microservices, message brokers, and GCP. Prepare concrete project stories.
Candidates describe managerial or techno-managerial rounds with behavioral questions about difficult teammates, conflict, and how they contribute to a team. One candidate described the overall tone as collaborative. Prepare specific examples with clear outcomes rather than generic answers.
Candidates report an HR call covering fit and compensation, followed by a decision. Outcomes in the reports include offers and rejections. One candidate said the update took closer to four weeks than the two weeks they were quoted, so plan for possible delays.
