CVS Health Principal Software Engineer interview questions
based on 1 rating - Updated Jan 9, 2025
Averageinterview difficulty
Very negativeinterview experience
How others got an interview
100%
Applied online
Applied online
Interview search
1 interviews
CVS Health interviews FAQs
Candidates applying for Principal Software Engineer roles take an average of 14 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at CVS Health overall takes an average of 20 days.
Here are the most commonly searched roles for interview reports -
I applied online. The process took 2 weeks. I interviewed at CVS Health in Dec 2024
Interview
I applied for two different Principal Software Engineer roles. A week or so later a recruiter setup a phone screen, which was a typical initial screen. I then got handed off to another recruiter to set up a time for the next round. I asked if I was still in consideration for the other role I applied to, but got not response. Next round was with the hiring manager, where we talked about my background, the position, etc. Again, pretty typical. Recruiter #2 reaches out again (CC'ing Recruiter #1) to set up a time for round 3. I once again ask if I was still under consideration for the other role, and what this next round interview would be about. Again, no response to either question. Turns out the next round was a system design round with one of CVS' "architects" who's been at the company like forever. OK, totally wasn't prepared for that, but let's go! He asks me to design Twitter (seriously? we're still doing this in 2024?). I start designing what a hypothetical API would look like and the basic components involved (api, db, job processing, etc), I don't get 1 minute into it and he starts interrupting me saying he was looking for more "lower level" components at the network level. After some back and forth trying to clarify what he means, he starts talking about "gateways". Well he said "network level" so I'm thinking, "is this guy asking me to design things like the internet gateway configurations for a VPC in AWS"? He won't give me more info, but after me dragging it out of him, turns out he's talking about API GATEWAYS. Ok, that's not what I'd call the "network level" but yeah, I was going to get to the API Gateway if you didn't interrupt me 1 minute into sketching this thing out. Then he gets all wrapped around the wheel about using CDNs and why my solution doesn't use a CDN. Again, I would have gotten there if you gave me more than 1 minute to come up with the design!
This guy was so rude and kept interrupting me every 30 seconds that at this point I was frustrated and turned off and I didn't want the job anymore anyways. No way would I want to work with someone like this who's going to ivory tower every little thing (and a terrible communicator at that)
Needless to say a few weeks later got an automated email that they wouldn't be moving further with me. Fingers crossed for that other role I applied for! (not)
Interview questions [1]
Question 1
System design to design a Twitter clone. *facepalm*