The first thing is a phone call with an engineer, mostly to gauge your own interest. They will ask you a simple coding question; you only need to give a high-level walkthrough of your approach.
Next is the famed ProctorU assessment. I got lucky and my proctor left me alone, but your mileage may vary. I've heard of some people getting their test paused because they looked at a wall.
The code questions were:
Not too bad overall if you've done your prep. Overall, slightly easier than some companies' code interviews. If I were to rank, maybe a bit more difficult than Amazon's.
It took me 2.5 hours. You can't run your code, but they're also not expecting 100% correct. I think pseudocode is OK. My solution was correct, but not 100% optimal, so there's leeway here.
The onsite is super easy, mostly presentations and discussion. I talked with a developer about my prior internship project, had a quick discussion about how I would design something, and a final HR interview mostly discussing deadlines and that sort of thing.
Very relaxed onsite, and the whole process was extremely smooth. They take very good care of you.
Something about well-ordered numbers and additive sequences. They have a hard-on for recursion.
The following metrics were computed from 1,026 interview experiences for the Epic Systems Software Developer role in United States.
Epic Systems's interview process for their Software Developer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Epic Systems's Software Developer interview process in United States.