Real, anonymous reports from people who interviewed for Software Engineer at Grow Therapy, newest first and distilled into what to expect across the loop.
Get your personalized Grow Therapy Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
My process felt smooth and unusually human. I started with a recruiter chat where we talked through the role and what they expected day to day, and it already felt practical rather than generic. After that, about a week later, I moved into a sequence that stayed fairly standard: a hiring manager conversation, then coding, followed by cross-functional discussion and some behavioral questions. Everyone I met came across as friendly and sharp, and they weren’t trying to trip me up so much as understand how I thought.
The questions were grounded in the kind of work I’d actually be doing, and the overall pace felt streamlined rather than drawn out. I also had the impression that people enjoyed meeting me, which helped the process feel less transactional. Difficulty stayed in the “reasonable” range for me, and nothing felt overly abstract or contrived.
> 1 year
Average Neutral United States
My first step was a recruiter screen, and then I got an assignment described as a technical writing prompt with a design template provided. The email framed it as something that should take just a few hours, but the scope was so broad and open-ended that I couldn’t really fit it into that window. I ended up spending way longer, trying to cover enough ground to show I could design something resilient and performant.
After I turned it in, I moved into what they called a review interview, where I discussed my plan. The structure felt like the take-home was doing most of the heavy lifting, and the next conversations were mostly centered on walking through choices and handling a few follow-up prompts. Even though I felt I had been thoughtful, the end result was the same feeling many times: they declined to move forward and offered no meaningful feedback. The explanation I received leaned on “company policy” for not providing feedback.
> 1 year
Average Positive United States
After a recruiter screen, I was given a take-home writing-style assignment that I had to complete within a week. Once I submitted it, the process move…
> 1 year
Easy Negative New York, NY
My experience had a common thread: after I did the heavy work, the feedback loop basically didn’t exist. I started with a recruiter reach-out and then…
> 1 year
Average Negative United States
My process started like many others: a quick recruiter screen, then a take-home assignment. The work itself was substantial but straightforward in int…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Recruiter Screen
The interview process typically begins with a recruiter screen that focuses on discussing the role and expectations, setting a practical tone for the subsequent steps. Candidates found this initial conversation to be friendly and informative.
RecruiterExpectationsInitial Conversation
Take-Home Assignment
Candidates are often given a take-home assignment that requires significant time investment and may feel vague or open-ended. This assignment is intended to demonstrate coding skills and design thinking but can lead to frustration due to unclear expectations.
Take-HomeCodingDesign
Live Coding Interviews
The interview loop includes live coding sessions that assess both front-end and back-end skills, with a focus on practical coding tasks relevant to the role. Candidates reported that the questions were fair but emphasized the importance of performance considerations.
Live CodingFront-EndBack-End
Feedback and Communication
A common concern among candidates was the lack of meaningful feedback after interviews, often attributed to company policy. Many felt that the communication could be chaotic, leading to a sense of wasted effort without clear guidance on improvement.
FeedbackCommunicationRejection
Interview Atmosphere
Overall, candidates described the interview atmosphere as friendly and supportive, with interviewers focused on understanding their thought processes rather than trying to trip them up. This positive vibe contributed to a more pleasant experience.
AtmosphereSupportiveFriendly
Outcome and Experience Reflection
Candidates reflected on their experiences with mixed outcomes; while some received offers, others faced rejections without feedback, leading to disappointment. Many emphasized the importance of feeling respected for their time and effort throughout the process.