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 online. The process took 2 weeks. I interviewed at Epic
Interview
Overall the interview process was great compared to most other companies. A human resources representative was in contact with me a day after putting in the online application and within the week I had a phone interview with a developer and the online technical skills assessment.
The phone interview was 30-45 minutes and consisted of questions about my professional experience and some softball technical questions on the basics of arrays vs linked lists. The online assessment was much more rigorous. There were three sections: The first was a "speed test" that asked 10 easy math/logic questions--the catch is you have to answer all of them in 2 minutes! I was able to get through about 8 of them before I ran out of time. The second part was a "fake language" section in which the questions describe a made up programming language that didn't work like any language I've ever used. This was the easiest section in my opinion and really was more like reading comprehension.
The third section was a real programming assessment and was the most difficult by far. There were four challenges in total. The first one was pretty easy, but the rest were pretty challenging including one that involved dynamic programming. Ultimately, I think I came up with solutions that were more or less correct; the real challenge here is that you're not allowed to use google to look up any sort of syntax or library function behavior. I think I, like many other developers, tend to use google as a crutch and don't know languages as completely as we should. At the very least it was a wake up call to develop a more comprehensive knowledge of the languages I use.
Two weeks after the technical skills assessment, I received an email saying that they decided not to continue with the interview process.
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.