I applied through a recruiter. The process took 3 weeks. I interviewed at Epic in Oct 2017
Interview
I was emailed by a recruiter, giving me a link to apply at. You'll fill out a few forms and submit your resume. There's then a phone interview, that's very casual feeling. Then there's a skills assessment that's very long and difficult. It has three parts: speed round, technical, and programming. I recommend finding some "speed round" practice tests that test you on solving as many problems in short, limited amount of time. The technical part isn't terrible. They explain the syntax of a made up language and you have to answer questions related to how a given expression will be interpreted based on that. The programming part is an ugly beast. First, you have to use a poorly executed service called ProctorU that feels very intrusive and very clunky. Research the service. It's a good idea, but horribly executed. I might recommend having the assessment scheduled at an official testing center as opposed to using your personal computer. There will be 4 programming problems to solve, which can be done in C, C++, Java, or Python, and there's no compiling during the exam. I barely finished the first problem, and didn't finish the others. I had to resort to very vague pseudocode. I highly recommend visiting a website called open.kattis.com and practice as many problems as possible. It will only help. Hope this helps, and good luck.
Interview questions [1]
Question 1
Why I want to work at Epic, why I want that particular position, and what projects have I worked on before.
I applied through a recruiter. The process took 5 weeks. I interviewed at Epic in Oct 2017
Interview
I was contacted by a recruiter through my universities career website to apply. Very soon after submitting my application I was sent a link to take a Rembrandt personality test and to schedule a phone interview. My phone interview was scheduled for about 7 days later, at which point I was also sent a skills assessment through ProctorU.
I had prepared for my interview by reading other responses here and was expecting to just talk about my project experience and learn more about the position, but I was also asked several technical questions, while most people here didn't report being asked these, so I was caught off-guard. The employee conducting my phone interview sounded pretty monotonous and bored until I asked him about his current work at the end. The interview was 30 minutes but it wasn't enough time for me to go into more technical depth of my project experience like they were asking (and complete the other interview objectives) and I had to skim over pretty important parts of my project and skills just to fit in the allotted interview time.
I felt like I was adequately prepared for the skills assessment from reading other responses but was expecting questions related more to algorithms. It took me 3 hours to complete the assessment. All my programming questions ended up being about different string manipulation problems, which I knew how to solve mostly. However, it was so different from my expectations that it caught me off-guard, and I don't think I did as well as I could have. There's no way to compile your code, so you have to hope what you wrote was correct and understandable. As a CS major I was required to use Java, C, or C++. The other two portions of the assessment were a series of 15-20 logic/math puzzles that I had to solve in 2 minutes, and learning their "fake" language syntax and answering some questions on it. Those two sections of the assessment were fine. ProctorU is kind of annoying to set up, but I got my computer set up with it and through the proctor evaluation at the beginning in under 10 minutes. I really didn't like the ProctorU system, though. Your proctor doesn't actually know anything about Epic or software development or the exam contents, and the ProctorU system requires remote control over your computer. Plus you need a very stable and reliable internet connection or it's almost impossible to use.
I took my skills assessment and then had my phone interview the next day. My interviewer told me that they would get back to me within the next week about whether or not they would continue with my application, but it's been 3 weeks since my interview, so I'm guessing I'm not getting the job. I've even sent a follow-up email with the recruiter who had been in contact with me throughout the entire process, but still have received no response. I'll update this post if/when they ever get back to me.
Interview questions [2]
Question 1
How to iterate through a list (in both directions) without loops? and What are the differences between a LinkedList and a Vector, when would you use one over the other, and how does each insert/delete items? (phone interview questions)
I applied through a recruiter. The process took 4 weeks. I interviewed at Epic
Interview
Had a phone interview with a guy and a ridiculous assessment.
Phone interview was standard. Discussed projects and the company.
The assessment was a waste of time. Expect to spend quite a bit of time setting up software so someone can stare at you through your webcam and listen to everything that goes on in your testing environment. Expect to walk around the room to show the proctor every wall and ceiling so you can't cheat. Expect to have no bathroom breaks. Everything must be quiet.
The exam itself is not difficult but VERY long. I do not know how they expect everyone to have the mental stamina to sit through hours upon hours of questions and coding problems.
My coding solutions were correct but not optimal. I had to pee so I turned it in anyways.
Huge waste of time. Would not recommend.