Evidation Health Interview Questions
& Process

It was a pretty easy interview, as expected for just an internship position. First, I had a phone call with the recruiter where we had a light conversation about my background and experience. Then, there was an onsite technical interview, which I solved using a whiteboard and marker.

A recruiter reached out on a Monday, and I didn't even apply. I was asked to do a data assignment, but I first wanted to chat with someone technical about the role. I ended up speaking with someone on Thursday who seemed great and enthusiastic about Evidation. Later, an executive called to discuss my background and the company. I spent the weekend on the data analysis assignment. The following Tuesday was my onsite interview, where I met with different team members. Surprisingly, there wasn't a clear agenda or job description ready. The conversations went well, and it felt like a potential match. They asked about my salary expectations, but without a job description, I couldn't give a concrete answer, stating I'd provide it once I received the description. I was told I'd get it that evening or the next morning and hear back in a few days. However, I never heard anything back. I did the usual post-interview follow-ups via email to the recruiter and my interviewer. After a week and a half of silence, I tried again but received no response. It's a shame, as Evidation seems like a company with a lot of potential, but they could improve their communication and courtesy by closing the loop with applicants, even if it's a rejection. Applicants invest time in interviews and assignments, and a timely professional response is the least they deserve.

The interview process was nice and organized. It lasted about 3.5 to 4 weeks. After first contact with Hiring/HR, I had an initial chat with a director to learn about the role's specifics and answer questions about my background, mainly to check for a fit. Then came a take-home assessment with general software engineering and database questions. After that, a full-day interview was set up. This day was divided into four parts. Two parts were semi-technical, involving questions about code, practices, experience, and discussions about the work environment and my background. One section was entirely technical: solving a problem with an interviewer available for questions, which felt more like pair programming than an exam due to the calm atmosphere. The last part was with management, diving deeper into job specifics.

I went through the final round interviews with the digital study operations team. It began with a recruiter call, followed by two calls with the hiring manager. Then, I had the final round interviews with the larger team, which included five new interviews and a debrief with the hiring manager. The entire process spanned about a month. The recruiter, Caitlin, was really great. She communicated clearly, was thoughtful, organized, and respectful. Since I don't really enjoy looking for a job, I always felt it was easy and comfortable to talk to her.