Grow Therapy Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 34 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Grow Therapy.
Grow Therapy
Software Engineer
Senior Easy Negative experience No offer 4 rounds
Interview process
Recruiter call Take home Technical screen Onsite
Interview formats
Technical Coding Behavioral System Design
This place is a complete waste of time, I suspect they're just interviewing to check out the job market or train their staff. It starts with a recruiter call where they read a script and claim to be language-agnostic, but then they only want Python or JavaScript. Next, you get a take-home task: 'Design a system to match clients with therapists based on age and availability, showing top 3 matches based on client preferences.' This is way longer than it seems, taking over 4 hours even for a simple monolith. If you somehow pass that, get ready for another 4 hours of interviews. First, a TDD review where you lead but it's directionless. Then, behavioral questions mixed with system design, which are pretty standard. After that, there's a backend coding challenge involving ranking provider objects and sorting them. Finally, a frontend coding task in React to add a search filter by name. I thought I nailed it after 9 years of experience, but they went with someone else and wouldn't give feedback. Then I saw the job reposted. It's incredibly frustrating, especially from a mental health company. They have no respect for candidate's time or mental health, not even offering feedback. I wouldn't recommend this place to anyone.
Confirmed questions4 questions
- You’re asked to discuss any part of your TDD.
- Typical behavioral questions are asked.
- The backend coding task involves ranking an array of provider objects based on certain rules and returning a sorted list.
Grow Therapy
Software Engineer
Entry Average Negative experience No offer 2 rounds
Interview process
Recruiter call Take home
Interview formats
Technical Coding
I had an initial screening call and then was given an assignment. I had to build an API, not particularly difficult. I delivered a fully functional app with tests and docs. After a few days I got a rejection email saying that they couldn't provide feedback for legal reasons. I found this very disrespectful of my time and effort. When you ask someone to invest hours to build something the least you can do is offer feedback even if it is in the form of an email. As it turns out I'm happy I was rejected since lately I have heard a lot from ex-employees about the extreme crunch culture of the engineering department.
Confirmed questions1 question
- Could you implement a specific feature using the Wikimedia REST API?
Grow Therapy
Senior Software Engineer
Senior Average Positive experience Accept offer 5 rounds
Interview process
Take home Technical screen Phone screen Presentation
Interview formats
Coding Behavioral System Design Presentation
I really liked this interview process. It starts with a take-home design writing task. It's more work than a typical 90-minute online assessment but more relevant to the actual job. I managed to finish it on a 3-hour train ride, so don't overcomplicate your solution. If you pass that, there are four more interviews: Front-end and Back-end coding, a Behavioral interview with the Engineering Manager, and a System Design interview, which is basically a review of your take-home work. The coding interviews were pretty standard and felt relevant. Front-end focused on JavaScript and React fundamentals, not component design. Back-end involved ranking and sorting providers by appointment history. The behavioral interview was standard; just have some good projects to discuss. The take-home review was a bit strange; I expected more questions, but it was mostly summarizing what I'd already done, so review it well. I heard back about 3 business days after the interviews, and the recruiter kept me informed.
Confirmed questions4 questions
- How would you rank and sort therapists based on their appointment history, client retention, etc.?
- How would you implement search, filtering, and pagination for therapists on a webpage?
- Can you share an instance where you received significant feedback that changed how you approached your work?
Grow Therapy Software Engineer Interview Questions
Quoted word for word from Grow Therapy interview reports.
“Can you build a page that pulls top results from Wikipedia from a specific day?”
Read reports →“Build a wrapper for an external API.”
Read reports →“Could you write a wrapper for the Wikimedia API?”
Read reports →“Can you rank an array of providers?”
Read reports →“Build a web server that has API endpoints to fetch the most viewed articles over a week or month (assume 0 views if an article isn't listed on a day), get the view count for a specific article over a week or month, and find the day an article had the most page views in a month.”
Read report →“Create a technical design document based on provided product requirements.”
Read report →“Could you build a frontend for the Wiki API?”
Read report →“How would you add a search function using a search component?”
Read report →“Build a system that'll interact with the Google and Apple Calendar APIs and show the availability of a therapist.”
Read report →Formats, difficulty and experience
Across all 34 Grow Therapy interview reports.