Software Developer applicants have rated the interview process at Epic with 3.1 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 50% positive. To compare, the company-average is 57.4% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Developer roles take an average of 22 days to get hired, when considering 1,924 user submitted interviews for this role. To compare, the hiring process at Epic overall takes an average of 24 days.
Common stages of the interview process at Epic as a Software Developer according to 1,924 Glassdoor interviews include:
Phone interview: 29%
Skills test: 21%
IQ intelligence test: 12%
Personality test: 12%
One on one interview: 10%
Presentation: 9%
Background check: 4%
Group panel interview: 2%
Other: 1%
Drug test: 1%
Here are the most commonly searched roles for interview reports -
I applied through college or university. I interviewed at Epic (Madison, WI)
Interview
Began with a phone screening, then scheduled a skills assessment, which involved a speed section (basic math and logic questions but with a tight time limit), a section where you learn a made-up programming language, and four typical programming questions. If you do well on that, they bring you out to their campus. At that point the only interview parts are a case study where they ask you to think of a solution to a relevant challenge they have faced and explain your thoughts, and a section where you have to explain a past project to a developer. It's overall pretty informal and I actually had a lot of fun on my visit.
Medium level leetcode and then a very basic system design question as a final round interview. Overall, smooth and simple process. Only one technical and it was the first one.
Interview questions [1]
Question 1
How would you design a system to minimize wait time at a health care center?
[OA] OA was fair. Programming part are leetcode easy and easy-mediums, straightforward simulation, backtracking, dfs, strings, etc. No DP/graphs but ymmv.
[Final interview] (Case Study) I think the interviewer came up with their own prompt. It's mostly discussion-based, with a virtual white board. It's not too technical. I'm guessing its testing your communication/logical reasoning than system design skills. (Pair programming) 1 question, same format as the OA on the same platform, leetcode easy.
[Overall] Technical difficulty isn't bad. Interviewers who are current software devs seemed friendly. Had a good experience, yet got rejected.
First round is a thirty minute phone call with one of their developers. The other part of the first round is a three hour exam with IQ test style logic questions and coding questions.