
Hinge Health Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 76 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Hinge Health.
Software Engineer
Started with a recruiter screen. It was a standard call, where they asked me to talk about myself. The recruiter initially rescheduled, which was fine, but when we finally had the interview, they seemed hurried and eager to wrap things up. Next was a technical take-home assessment. The task involved refactoring and adding code to an ancestry tree structure. I followed their instructions and stayed within the time limit, but was later informed that I wouldn't be moving forward and that no feedback would be provided. This felt like a disregard for my time.
- Could you refactor and add code for an ancestry tree structure?
Software Engineer
The interview process started with a take-home assignment where I was encouraged to use AI, which was an interesting approach. After submitting it, I was told the team liked my work and wanted to schedule interviews with hiring managers. However, communication became very slow after that, with unresponsive recruiters and delays in scheduling, which made me question their seriousness or if they had internal issues. When I finally got to speak with a hiring manager, they seemed very disengaged and kept yawning. It was disappointing to experience such a lack of professionalism after putting in significant effort. A week later, I received a standard rejection without any specific feedback, citing company policy. My overall impression was of a disorganized startup possibly dealing with headcount problems or internal strife. I'd advise against interviewing here.
- I was asked to complete a tech test and I was allowed to use AI.
- There was a technical screen, and then a behavioral interview with the hiring manager that included typical behavioral questions.
Senior Software Engineer
Recruiter reached out via Hired. The interview process took over a month. First, an intro with the recruiter. Then, a 1-hour meeting with the hiring manager. After that, a 1-2 hour coding challenge that could be continued in the final interview, with no time limit. The final interview had 4 rounds: 1) Business requirement analysis - brainstorming a feature request, discussing implementation and risks. 2) Coding challenge continuation, with upgraded questions. 3) Director chat - casual conversation and Q&A. 4) Engineering team chat - behavioral questions and Q&A. 5) Hiring manager closing conversation. It took about 3 weeks for a decision. The culture seems great, the team is awesome, tech stack and benefits are good, but I had to decline for other reasons.
- What are your strategies for handling conflicts?
- Can you explain the React context/provider?
- Describe a situation where you could have improved an outcome by acting differently.
Hinge Health Software Engineer Interview Questions
Quoted word for word from Hinge Health interview reports.
“write a unit test to check a node is deleted from a tree?”
Read reports →“write a unit test to check that a node is added to a tree?”
Read reports →“Write code for an API that can retrieve and insert nodes into a tree structure.”
Read reports →“Given a React app displaying text in a tree-like format, your task is to implement code that replicates this structure, as opposed to the original layout.”
Read reports →“Can you build an API for adding nodes to a tree?”
Read report →“What are some solutions to help user retention, considering users aren't signing into the app after receiving their welcome kit?”
Read report →“Can you pair program and delete a node from a tree?”
Read report →“Create a React tree, given a long list of requirements, for a take-home task.”
Read report →“Could you build a SpringBoot application that manipulates a tree, ensuring it's simple yet complete?”
Read report →Formats, difficulty and experience
Across all 76 Hinge Health interview reports.