
Parachute Health Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 29 interview experiences · FREE TO READ
Which role are you interviewing for?
16 roles · 29 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Parachute Health.
Software Engineering Manager
I went through five rounds of interviews. First, a take-home programming test that took about 45 minutes. Then, a behavioral interview, followed by a technical pairing session. After that, there was an architecture interview with a staff engineer and a product manager, and finally, a system design interview with another staff engineer. I didn't get an offer or any feedback, which was disappointing after investing so much time.
- Take-home programming assignment: Leet code type question.
- Behavioral: Typical behavioral questions. How do you handle conflict? What project are you most proud of an why?
- Pairing interview: Implement auction system in ruby where a person can only bid once and at the end of the auction it spits out the winner.
Tech Lead
The interview process was pretty standard. It started with a practical coding screen, then we discussed some technical projects I've worked on. They also asked behavioral questions like, 'Tell us about a time you mentored someone.' Unfortunately, they completely ghosted me after the last interview. I tried to follow up but never heard back. I consider it a negative signal that they didn't bother to respond, even to my follow-up.
- Can you share an instance where you mentored someone?
Director of Engineering
This was one of the longest and most frustrating interview processes I've ever been through. It took almost 3 months and involved 9 interviews. They even added new interviews late in the process, after I thought I was in the final stages. These later interviews weren't focused on leadership or decision-making as expected. Instead, they turned into detailed technical discussions about how systems and processes worked at my past companies. It felt less like they were assessing if I was the right leader for the job and more like they wanted to extract specific operational knowledge to fix their own problems. They cared more about the specific tools, implementations, and internal workings rather than the outcomes or impact, which felt really off for this stage. Communication was also really bad. There were long delays and silence, followed by generic rejection emails after weeks of waiting. After putting in so much time and effort, the lack of respect for my time was really disappointing. The whole hiring process here seems to show that the organization is indecisive, provides a poor candidate experience, and lacks proper interview discipline. I wouldn't recommend interviewing here unless some serious changes are made.
- Can you tell me about the planning process at your previous company?
Product Engineer
So the interview process was pretty long, it had 7 rounds total. First was a 30 min phone screen with HR. Then a 30 min paired coding challenge with a SWE and an EM where I had to write a method to parse a CSV file. After that, a 1 hr behavioral interview with two EMs. Then another 1.5 hr paired coding challenge with one SWE, this time I had to update a live auction app to support silent auctions. Next was a 1 hr architecture design interview with two SWEs and a PM, where I had to figure out the DB tables for adding a survey to a GrubHub-like app. This was followed by a 1 hr system design interview with 2 SWEs, continuing on the architecture topic, where I had to design the system for the GrubHub-like app. The 7th round was supposed to be a culture fit interview with all the EMs, but I didn't make it that far. Everyone I talked to was really nice. Just a heads up, they give you a README to read the problems instead of explaining them verbally. Since I have dyslexia, this added some pressure and I wasn't sure I understood everything perfectly. If they had explained it verbally, I think I would have performed better. But honestly, the problems themselves weren't too hard.
- Tell me what you found interesting about Parachute Health and discuss your previous jobs.
- What stood out to you about Parachute Health? Talk about your past roles.
Parachute Health Interview Questions
Quoted word for word from Parachute Health interview reports.
“Can you take a given set of Tweets and transform them into a Python dictionary, and then sort and filter them by word?”
Read reports →“Can you write a Javascript or Python function named 'checkTicTacToe' that accepts a 3x3 matrix and outputs a value based on the provided response key?”
Read reports →“Could you update an "auction app" to add a silent bid type auction, transitioning from each auction having multiple rounds where each bid is announced to each auction having one round with silent bids?”
Read reports →“Could you explain the distinction between a product manager and a project manager?”
Read reports →“Could you write a program to simulate an auction site based on specific criteria?”
Read report →“Can you design the architecture for a survey system that allows doctors to send patients' dietary restriction information to hospital food vendors?”
Read report →“Have you ever encountered a bug?”
Read report →“Can you share a story about a bug?”
Read report →“How would you redesign an auction app built with Typescript/Ruby to handle different use cases?”
Read report →Formats, difficulty and experience
Across all 29 Parachute Health interview reports.