Hiring process consisted of multiple stages:

The first stage was a semi-technical interview with a developer. The developer went over my resume, we talked about projects I had listed, and they asked a conceptual question about how I would design a game.

The second stage consisted of the infamous 3-hour long online exam. Many other posters have already mentioned the layout, so you can look for those posts elsewhere. As far as the programming portion is concerned, Careercup has a lot of great examples. I would recommend running through problems on Careercup to get a feel for the programming problems.

The third stage was the on-site interview. The on-site interview consisted primarily of tours and Q&A sessions with different developers working on different projects. However, there were two interview sessions:

• The first is a case study. The case study presents a problem that Epic may have encountered many years ago, and your job is to figure out, as best as possible, how to implement a solution for that problem.
• The second interview session is basically a conversation between you and a developer about a project you worked on. The developer will ask you a series of questions regarding how or why you chose to implement things the way you did.

Both sessions are straightforward if you have a good understanding of how to tackle conceptual problems and a firm grasp of whatever project you worked on.

Overall, one of the better interview processes I have had. Epic has a lot of money, which translates nicely when it comes to the interviewing process. Everything was taken care of for me as smoothly as possible. I also had other pending offers at the time, and HR did a wonderful job getting back to me in a timely manner.

None. The questions are, for the most part, straightforward. Once again, doing problems on Careercup will help you far more than this post can.