Software Engineer 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 Engineer 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 Engineer 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. The process took 4 weeks. I interviewed at Epic
Interview
A personality test that asks you questions like select certain attributes that most fit you, analogy questions to show how you think, and simple math questions. Then a lengthy proctored skills exam testing you on subjects like math, english, and programming. Then a phone interview that goes over your resume and they ask questions about that. Finally an on-sit interview
Interview questions [1]
Question 1
Asked how you would expand on a past project you have worked on.
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?
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.
[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.