Data Scientist applicants have rated the interview process at Aetna with 2.5 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 35% positive. To compare, the company-average is 63.4% positive. This is according to Glassdoor user ratings.
Candidates applying for Data Scientist roles take an average of 40 days to get hired, when considering 26 user submitted interviews for this role. To compare, the hiring process at Aetna overall takes an average of 27 days.
Common stages of the interview process at Aetna as a Data Scientist according to 26 Glassdoor interviews include:
Phone interview: 34%
Presentation: 24%
One on one interview: 17%
Group panel interview: 7%
IQ intelligence test: 7%
Other: 5%
Background check: 2%
Drug test: 2%
Here are the most commonly searched roles for interview reports -
Spoke with recruiter, then a team member, then was declined for the position, then spoke to another recruiter, then was magically offered an onsite.
During the onsite I was scheduled to speak with 4 or 5 people. At least 2 of which were remote. The recruiter in the office set up some terrible headset for me to use to video interview with one person which didn't really work at all so it became my responsibility to make the technology work for the interview. Obviously, a strained interview over the phone or through video isn't going to have the same impact as in person communication, especially when you don't change your questions from those that are designed for whiteboarding.
Aetna spent over $1000 to bring me in person and have me talk to everyone and no one important or critical to the interview showed up.
Interview questions [1]
Question 1
Extrapolate how many blood testing centers there are in the United States.
I took a technical test, a technical phone screen, and had a virtual onsite interview. The position I was being considered for was changed in the middle, which could have been communicated better, though I applied through a recruiter. The change resulted in extra interviews and a lengthier process.
Phone screen, tech phone screen with coderpad sql, on site w/ couple of people from different teams. Overall heavy emphasis on the stats, not much actual coding. Roles are not for engineers, may want to pay attention to it
Total three rounds interview, pretty typical. Talk about projects, previous working experience, asking machine learning questions, ab testing and case study. They much care about how you solve the problem.