Hinge Health logo

Hinge Health Staff Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 8 interview experiences · FREE TO READ

3.9 Rounds average
Average Typical difficulty
75% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Hinge Health.

Showing 3 of 8
Hinge Health logo
Hinge Health

Staff Software Engineer

Engineering · more than a year ago

Staff Average Positive experience Accept offer 5 rounds
Interview process
Recruiter call Phone screen Take home Technical screen Onsite
Interview formats
Behavioral Technical Coding System Design

I interviewed for a Staff Backend Software Engineer role and it was a great experience. The recruiters were super helpful and the process was well-organized. They were really responsive and gave me lots of info. The phone chat with the hiring manager was good for understanding the team and expectations. The take-home test was a good way to see if I could do the job, it was like real work. The onsite interviews with engineering and product folks were organized and they asked good questions about my technical skills. I liked that they talked about moving from monoliths to microservices. It would be cool to meet the people I'd work with directly to see how we'd vibe and if we'd fit well together. Also, maybe add a data structures and algorithms question in the onsite. Big thanks to the recruiters though, they were awesome and really cared about fit, asking tons of behavioral questions. They really helped me decide.

Confirmed questions2 questions
  • What are your strategies for migrating from a monolithic architecture to microservices?
  • Tell me about your experience transitioning from a monolithic architecture to microservices.
Hinge Health logo
Hinge Health

Staff Engineer

Engineering · more than a year ago

Staff Average Negative experience Decline offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral

The first step was a 45-minute screening interview with a recruiter. It involved a lot of questions about my past experience. However, the recruiter couldn't answer basic questions about the role, which made me wonder how they'd even evaluate candidates. It's pretty weird when technical hires have long calls with non-technical recruiters. They should either do a quick intro and then move to the actual process, or have the first call be with someone who actually knows about the job.

Confirmed questions2 questions
  • Can you describe your past projects?
  • What makes you interested in this position?
Hinge Health logo
Hinge Health

Staff Software Engineer

Engineering

Staff Easy Positive experience Decline offer 5 rounds
Interview process
Recruiter call Phone screen Take home Technical screen Onsite
Interview formats
Coding Technical Presentation

The interview process was pretty standard, maybe a bit longer than usual. It started with a recruiter call, then a chat with a developer, followed by a take-home coding test that took several hours. After that, there was a full-day onsite interview, which was virtual for remote roles and could be split into two sessions. The take-home test was a good, realistic one. One of the onsite interviews involved discussing the take-home project, explaining what was done, and how it could be improved or scaled. The whole recruiting process was quite slow, taking over a month from start to the compensation negotiation stage. At that point, I declined because they initially offered $190,000 based on hired.com but then lowered it to $175,000 during negotiations. It felt a bit ethically questionable, though unfortunately not uncommon. I'm not sure how they expect to be competitive with such a long interview process and lower salaries. It would have been a neutral experience if they hadn't changed the compensation offer at the last minute.

Confirmed questions6 questions
  • Implement a one-dimensional tree structure using strings to represent animal types, allowing for hierarchical relationships where one animal can be a sub-type of another.
  • Initially, implement the user interface and manage offsets for the animal tree without using spaces.
  • Refactor the implementation to extract the animal tree data into a JSON file and then parse it back.

Hinge Health Staff Software Engineer Interview Questions

Quoted word for word from Hinge Health interview reports.

Implement a one-dimensional tree structure using strings to represent animal types, allowing for hierarchical relationships where one animal can be a sub-type of another.

Read reports

Could you implement a REST API using a tree data structure?

Read reports

Can you create an express.js application that handles rendering and modifying a tree structure?

Read reports

Could you elaborate on microservices, including their pros and cons and any associated issues?

Read reports

What are your strategies for migrating from a monolithic architecture to microservices?

Read report

Tell me about your experience transitioning from a monolithic architecture to microservices.

Read report

Can you describe the overall dynamic of the organization?

Read report

Were there many questions regarding the technical architecture decisions you would make and the reasoning behind them?

Read report

Tell me about how you handle conflicts with teammates.

Read report

Formats, difficulty and experience

Across all 8 Hinge Health interview reports.

Interview formats

Technical 30.4%
Behavioral 26.1%
Coding 26.1%
System Design 8.7%
Presentation 8.7%

Interview difficulty

Easy 12.5%
Average 75%
Difficult 12.5%

Candidate experience

Positive 75%
Negative 25%