I applied online. I interviewed at Epic (Madison, WI) in Sept 2019
Interview
The interview process was very smooth. I contacted a recruiter at Epic and applied online in August. Scheduling the online assessment and then a phone interview was in two weeks. The online assessment was proctored and consists of 3 parts: algorithm and data structure, speed test and another technical to assess your learning ability. Phone interview is more like behavioral but informal. My interviewer was very friendly and shared a lot of useful information about working at Epic. After 2 weeks, I received results and moved forward to schedule the onsite interview. The onsite lasted about 5 hours including lunch break. It started with an overview of Epic products/info ~ 45 minutes, then met another developer for more info on working at Epic, then a presentation with a developer (~45 min including QA and behavior), then an open-ended question with a senior developer, lunch break, interview with a recruiter and then a campus tour. I received an offer after exactly 2 weeks. The recruiter who I worked with was super helpful and responsive. He helped me to connect with a developer so I learned potential projects/teams before I accepted the offer.
Interview questions [1]
Question 1
Online assessment: recursion, string and tree for coding; ask you to learn a make-up language and test it, and a speed test (2 minutes) (remember to have a calculator, I did not and was stressed with simple calculations)
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.