I applied through university. The process took 3 weeks. I interviewed at Epic in Apr 2015
Interview
After a first email saying that they reviewed my resume and application they asked for a phone interview. We spoke about my background, the projects that I worked on and I had many occasions to ask anything that I wanted to know about the company and the job. After a couple of day they asked to go on in the process and I had the technical interview.
The technical interview is not a real interview, is more like an exam. You will use a system called ProctorU, that allows you to do this sort of online exam always having someone proctoring you so that you cannot cheat. The assessments are divided in 4 parts, as described below. The only things allowed during the exam are a calculator and pen and paper.
It wasn't too clear which was the maximum time allowed for the entire exam, probably 2 hours but 2 people at 2 different moments told me different things during the system setup before the start. After the 2 hours nothing stopped me and I went on on my exam. I took 3 and a half hours to complete everything (I know, definitely too slow, but it's a long exam trust me).
3 weeks after the technical interview they sent me an email saying that they have selected other candidates rather than me to go on with the selection process. End of my experience with Epic.
Interview questions [4]
Question 1
First part: general questions about logic and simple math. It's a speed test: you have 2 minutes and you have to try to answer as many questions as possible
Second part: Maths. General questions about logic and math, more complicated than the previous part. It's not a speed test but it's about accuracy. However, time is taken in consideration. No previous math knowledge is required, you won't be asked to prove a theorem or something like that. Logic and familiarity with calculations are the key to solve these problems.
Third part: learning a new programming language. They will test your ability to learn a new programming language teaching you a new and unknown programming language that it's probably the one that they use to create their products. It's different from all the others programming languages and they will start with the basics and step by step they will teach you more complicated stuff, but always remaining on a low complexity. At each step you have to answer questions about what you just learned. You are always able to go back and review all the previous pages if you're not sure about something. Not too difficult, but some questions are very tricky, be careful. Accuracy is the key, but time is taken in consideration.
Fourth part: general programming skills: you will have 4 problems to solve, writing a small program or function(s). You can use any language. Accuracy is the key, but time is taken in consideration. You have no help from the editor and you cannot compile or check any kind of error. The problems are not too difficult, but even the simplest problem can be solved in clever or stupid ways and they probably look at that. Most of the problems include simple mathematics, logic, and working on strings to check or modify them jumping from numbers to characters and vice versa. You don't need to use objects or anything complicated, everything can be solved in simple C if you want, but again is up to you to show your skills to them so use a good balance between time in writing the program, complexity, generality, etc.
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.
