I applied through an employee referral. The process took 2 months. I interviewed at Epic (Madison, WI) in Mar 2012
Interview
I got a call from Epic within 2 weeks of applying for Rembrandt test . It was very easy. Soon after got a telephonic call from a member of the HR. I was just asked about my research work. The overall conversation was a casual one and he explained a lot about Epic..a lot. I received an email after about a month that I have to schedule for a 4 hr exam in a test center here..The test consisted of basic math and 4 programming questions. The programming questions were not difficult and anyone from CS background will do very well on it. I received an email from them after 2 weeks that I did not make it to the next round, without stating any reasons for it. Honestly, I do not understand what their selection criteria is....it cannot be the score of the test...as I was very confident about the test. I know people who got into their onsite interview just after the telephonic process. Some people not confident about their tests went through to the next round.
Interview questions [1]
Question 1
find well-ordered numbers for n digits..i.e. say for 3 digits..138 is a well ordered number as 1<3<8, but 154 isnt as 1<5>4.
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.