I applied through college or university. The process took 2 days. I interviewed at Epic (Verona, WI) in Nov 2012
Interview
I was invited to Epic's Campus for an interview about 2-3 weeks after their recruiter had visitied my University and I took some of their tests. (Programming, Math, and Logic). They flew me out to Madison/Verona for a couple days; 1 was spent exploring the city and surrounding area (my choice, self-lead), and the other was spent doing the all-day event that is the interview process. I was in a group of probably 50-75 other candidates being interviewed that day. Some of the day was spent seeing demos of their software, talking about what interns get to do during their time working, and having actual one-on-one interviews with other software developers. Dress code was as relaxed as I've heard. No suits, no ties. T-Shirt, cargo shorts, and sandals are perfectly acceptable. I was regularly offered snacks and refreshments which were readily available just about anywhere.
The best way I would describe the process is very warm and friendly. It didn't feel like an interview at all; like they were more focused on getting me to like them instead of vice-versa.
Interview questions [1]
Question 1
I don't think any were unexpected or difficult. They'll ask you about past project experience. They'll prompt you to go into the details of your personal design and development process. Nothing I hadn't expected, and nothing that wasn't reasonable to be asked.
I applied through a recruiter. The process took 5 weeks. I interviewed at Epic (Verona, WI) in Oct 2012
Interview
I initially spotted Epic at an internship fair at my university. They asked about my GPA as well as my SAT/ACT scores. One of their first questions was something along the lines of "What percentage of the time are you willing to travel?" Which I thought was interesting for a software company, but all full-time employees are required to participate in immersion trips to help educate you on how the end-user is actually using the software. (I think it's a great idea). and some positions in the company do require a lot of travel. Anyways, so I left my resume and was later contacted to take a qualifying test, a 3 hour exam with subjects of math, learning a new programming language, and 4 coding problems. They tried calling me twice to do what I assume would have been a phone interview, but I was in class both times and they didn't leave a message. A week later I got an e-mail asking when would be the best time for them to fly me to Wisconsin for on-site interviews. They flew me out, got me a hotel room, covered all of the costs, and I had an enjoyable interview process there. The first night an Epic employee gave me and two other applicants a brief tour of Madison and took us to dinner. The next day, there was an interview with a developer which was more of less what you'd expect. There was a "group interview" which really was just a setting for applicants to ask a developer any questions they might have about the job, company, etc. There was also an interview with HR going over the basic HR sorts of questions. They also gave us a tour of the campus, and it really is amazing and beautiful.
Interview questions [1]
Question 1
At the end of the HR interview they gave me a 2 minute quiz. There was a page with 10 math questions on it, and you had exactly 2 minutes to do as much as you could.
They came to recruit on campus. Talked to rep, filled out a short application online. Took a ~3hr programming/math test on campus, was then flown up about a month later for on-site interviews. Campus tour, software presentation, got to eat lunch at the very cool cafeteria. Two interviews, one with a software developer, one with a HR personel. Everyone was very friendly, the software interview was not very technical, asked me more about projects I had worked on and why I had made management/technical decisions. HR interview was standard personality interview.
Interview questions [1]
Question 1
The programming/math test introduces a "made up" programming language, and tests you on how it would work. Not terribly difficult, but definitely different then most technical interview questions (there were also some standard "write pseudocode/code to solve x" questions as well)