I applied through university. I interviewed at Epic
Interview
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.
Interview questions [1]
Question 1
Aptitude-type questions that I haven't solved since high school. Very simple but they may catch you off guard.
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.