3 Stages:

• Phone screening
• Skills Assessment
• On-Site

The On-Site interview was not very difficult. They mostly just want to see if you would be a good fit in their company and have soft skills. The overall interview "difficulty" rating is holistic, since the skills assessment was quite difficult.

I'm going to focus more on the on-site interview, since many other people have explained the behavioral questions for the phone screening and the types of problems for the skills assessment.

The onsite interview went from 8:45 AM to 1:30 PM and consisted of the following parts:

1. Tech overview: This was a 30-minute presentation with a software developer where they show you the overarching applications they've built, so you have an idea of what kind of applications Epic makes. If there are other people interviewing for the same role as you, you would have the whole group being presented to.

2. Talk with another software developer: Here you can ask them any/all the questions you can think of, both about Epic as a whole and about their specific projects. If you can't fill the 30 minutes with questions, they have a bullet point list of topics to talk about that was helpful at times.

3. Previous project conversation: This was a 20-minute conversation with a developer about a project you did, where they ask you questions and try to understand how you designed it. I didn't really prep at all for this and just talked about a project I knew I would be able to explain well to someone and was reasonably complicated. It wasn't a presentation or anything, just a casual conversation with a whiteboard if you want to use it. I made sure to really give a good overview of the problem I was trying to solve, and then talked specifically how I did this.

4. Case Study: This was programming related, where I was given the opportunity to design either the front end or back end of a "new" application that Epic would be releasing, tailored for a specific problem. The whiteboard was obviously heavily used during this portion of the interview. I decided to talk about how I would design the back end, since that is where I have the most experience. If you've designed systems to solve problems before, you won't have too much trouble here. The interviewer was slightly surprised that I didn't run into any snags, which he started the interview by saying that most people get stuck and that he is there to help, but I found it relatively intuitive. If you want an idea of what kind of question they would ask, just go online and find some health/fitness app and think about how you would design that app given the problem they are solving.

5. Recruiter spoke with me for 30 minutes, and it was by far the easiest "interview" you could have. It's not really there as a barrier; it's just a wrap-up interview where the hardest question was "Why Epic?". It's mostly just to give you a good last impression with your recruiter and talk about other offers you had.

At EVERY step of the process, you have ample amounts of time to ask questions, so if you forgot to ask someone something, you could ask the next person. It was really nice to have all the interviewers close off a conversation with "Any other questions?"

This is where you give them your unofficial transcript and references. They had me go through all my references, so they knew who they would be talking to, since I assume they called the top 2 references on my sheet.

I dressed casually for this interview.

They got back to me the next week (on Friday) with their decision.

Why Epic?