I applied through university. The process took 4 weeks. I interviewed at Epic in Nov 2014
Interview
Met a campus recruiter and applied online. Received email confirmation in a reasonable amount of time asking to set up a phone interview. This call really isn't an interview, they just wanted to ask 1) why Epic, and 2) why software engineering. They ask a few questions off your resume but let you ask any questions you have of them. Separate from the phone interview, I was given a ProctorU account and told to take an online skills assessment. There are four sections on this test. One is a speed section with math word problems. One section they give you a dead computing language and explain how it works and ask you to evaluate increasingly complicated expressions. Another section is a bunch of math questions which are more like riddles, they were the most interesting part of the exam so do this section when you want a break from the other more dry sections. Last section is 4 programming questions. Pretty intense compared to other technical interviews. Most of the programs involved enumerating sets of strings.
Interview questions [1]
Question 1
Enumerate all possible anagrams of a random string where capital letters, numbers, and symbols are not allowed to move within the string.
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.
