Senior Software Engineer applicants have rated the interview process at GoodRx with 2 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 17% positive. To compare, the company-average is 39.4% positive. This is according to Glassdoor user ratings.
Candidates applying for Senior Software Engineer roles take an average of 26 days to get hired, when considering 6 user submitted interviews for this role. To compare, the hiring process at GoodRx overall takes an average of 27 days.
Common stages of the interview process at GoodRx as a Senior Software Engineer according to 6 Glassdoor interviews include:
One on one interview: 40%
Phone interview: 40%
Group panel interview: 10%
Presentation: 10%
Here are the most commonly searched roles for interview reports -
I applied online. I interviewed at GoodRx in Feb 2018
Interview
Contacted by internal recruiter via website, set up initial phone call with recruiter. We talked about company basics: size, location, values, etc. The (non-technical) recruiter then asked me some very easy canned questions about Python that clearly had 1 correct answer (see below). I personally think these are a bad way of evaluating someone: if they don't remember the name of a method between the many languages they might know, they get marked down? Rote memorization != good programmer.
Without speaking to anyone else in the company, the recruiter emailed me a few days later saying "at this time we have decided to go with other candidates who have experience that more closely matches our current needs" but that they'd keep me on file in case another position came up.
No harm done but seems they could have known that info before based on my resume and saved us both some time. Maybe the position had just been filled, who knows.
I applied through a recruiter. I interviewed at GoodRx in Jul 2026
Interview
Was a bad overall experience, first round was good with hiring manager and moved to second round and it was not so good experience. They also ask AI experiences and questions.
TL;DR The interviews were fine but extensive (over 6 hrs total), and they couldn't be bothered to send a rejection email. It takes 30 seconds!
The stages were:
1) Phone screen
2) Live coding technical screen (reasonable/practical, also the recruiter sent a great doc about what to expect)
3) Virtual "onsite" with:
- Timed coding exercise, and then a review of it (Practical exercise, but 40 minutes was not a realistic amount of time to complete it or to deliver the code quality they clearly expected. The review felt a bit off, it was nit-picky, not very friendly)
- Architecture and career goals
- API design
- Product, Design and Cross Functional
The recruiting scheduling tool needs an overhaul. It rarely had any available time slots, or only offered 6-hour time blocks that include unreasonable working hours like 6:45am or 7:45pm.
All of this was fine, but after over 6 hours of time spent interviewing, plus scheduling and prep time, it was radio silence for weeks!
Interview questions [1]
Question 1
Practical live coding, practical timed coding, behavioral questions, etc.
Interview took place as 4 different sessions after talking with recruiter.
1. Hiring Manager
2. Coding interview
3. Behavioral
4. System Design
Had a call with VP of engineering.
Everything seemed to go easy and well. They did not get back to me for 2 week after the interview. Until i messaged they did not have any response and failed to even give a feedback.
Interview questions [1]
Question 1
Coding exercise was working with the log file to fetch some data.
System Design was more of a discussion on what you did.