Epic Software Engineer interview questions

The overall interview process looked more like a product presentation to a customer rather than a dialog with a potential team member. There was very little interaction where I had a chance to learn something new about the company or development process that I hadn't read on career sites already. Perhaps it was my fault for not interrupting small talk and other irrelevant chatter with questions that matter, but the interviewers should also assume some responsibility for keeping the discussion on-topic. There are major disadvantages that you can read on career sites that were not addressed at all - Epic using outdated and non-transferable technology, long working hours, strict non-competes, Madison not being a tech hub, etc. Omitting crucial details like using MUMPS did not reflect well on their interview process. The on-site interview process was the same as others reported - campus tour, software demo, presentation of my project, lunch, and assessment. No questions were particularly difficult, but it surprised me that they were not interested in observing candidate's thought process by asking us to solve a problem on the whiteboard, and instead had us solve them alone on the computer.

The initial call was from an HR to ask me about my preferences. After that I had a phone screen which went really well. They asked a few basic questions and in the last few minutes, the interviewer asked me to interview them.