Healthify logo

Healthify Software Engineer Interview Questions
& Process

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

Based on 7 interview experiences · FREE TO READ

4 Rounds average
Difficult Typical difficulty
85.7% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Healthify.

Showing 3 of 7
Healthify logo
Healthify

Software Engineer

Engineering · more than a year ago

Mid Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Take home Technical screen Onsite Panel Presentation Background check Offer
Interview formats
Technical Coding System Design Behavioral Presentation

Started with an initial phone screen with HR to get some basic info about Healthify. Then, I had a take-home exercise that was a full-stack task, pretty similar to what the company actually does. After that, I had a code review session where I joined a call with two engineers and we reviewed code together. The final part was a 4-hour remote interview, which included an architecture/planning exercise with a senior engineer where I had to break down a big task, some live coding with a few engineers to build on my take-home exercise, and a casual chat with the COO to learn more about the company.

Confirmed questions1 question
  • Can you explain your approach to breaking down a large task or epic into smaller, manageable stories?
Healthify logo
Healthify

Software Engineer

Engineering · more than a year ago

Entry Difficult Positive experience Accept offer 6 rounds
Interview process
Recruiter call Phone screen Take home Technical screen Onsite Panel Offer
Interview formats
Technical Coding Behavioral Presentation

Applied through Workable, got a phone screen set up within 48 hours for the next week. About a week after that, they said they liked my application and sent a coding exercise, which I got the following week. I had 7 days to finish it. After sending it back, it took a few days for them to confirm they got it, and then a few more days to figure out the next steps. The next step was a week later, where we scheduled a meeting to talk about my coding exercise submission. We discussed my decisions and how I'd handle some situations, and it went well. Then I got scheduled for the final interviews. This involved pair-programming with engineers and a chat with the CEO about what motivates me. The day after, I spoke with the CTO and gave them my references. Finally, within 24 hours of talking to the CTO, I got the job offer. It was a long and tough process, but felt right for what the job entails. I think it could be better, and sometimes I felt stressed waiting for confirmation that they received my work. But I'm glad I stuck with it because I really like it here!

Confirmed questions2 questions
  • What makes a good team member?
  • Describe how you would connect Entity-A and Entity-B.
Healthify logo
Healthify

Software Engineer

Engineering

Mid Difficult Negative experience No offer 5 rounds
Interview process
Recruiter call Phone screen Take home Technical screen Onsite
Interview formats
Coding Technical Behavioral

The interview process started with a phone screen and a take-home test. Then, there was a technical review of the take-home test with engineering management, followed by three more hours of coding exercises, partly with the same engineering managers. The process felt excessively long; I felt the team could have assessed my technical skills after reviewing the coding exercise with the leads, without needing two more extensive coding tests. The take-home assignment was substantial and demanded too much of a candidate's time. Engineering management didn't seem to have a well-defined approach for evaluating candidates for this role. The final part involved pairing with an engineer on a live production ticket, which I find inappropriate as candidates shouldn't perform actual work for the company. I had a non-negotiable requirement that I communicated at every stage. Initially, they provided vague assurances that it wouldn't be an issue, but only in the final interview did they acknowledge it would be a dealbreaker, and only after I pressed the same managers again. Although I was ultimately rejected (and would have declined the offer anyway), I would have preferred an earlier rejection or more honest and direct communication about their expectations from the first manager interview. The lack of clarity and decisiveness about the team's actual needs for this role was incredibly frustrating and a significant waste of time. I'm uncertain if the team was genuinely considering me or just leveraging my experience for free technical advice; their questions and tests felt more like they were probing for insights and seeking guidance rather than assessing me against set criteria. I'm hoping this stems from a lack of management experience rather than intentional unprofessionalism, but it still reflects poorly on Healthify's candidate treatment.

Confirmed questions1 question
  • What is your definition of a completed engineering task?

Healthify Software Engineer Interview Questions

Quoted word for word from Healthify interview reports.

Could you extend the provided Rails application according to the given requirements and mockups?

Read reports

Can you describe your involvement with the Rails community outside of your professional work?

Read report

Can you explain your approach to breaking down a large task or epic into smaller, manageable stories?

Read report

What are your career aspirations and what do you hope to find in your next position?

Read report

Formats, difficulty and experience

Across all 7 Healthify interview reports.

Interview formats

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

Interview difficulty

Easy 0%
Average 42.9%
Difficult 57.1%

Candidate experience

Positive 85.7%
Negative 14.3%