Taro Logo

Software Developer Interview Experience - United States

March 27, 2013
Neutral ExperienceNo Offer

Process

The overall interview process looked more like a product presentation to a customer rather than a dialogue 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 the candidate's thought process by asking us to solve a problem on the whiteboard, and instead had us solve them alone on the computer.

Questions

Aptitude-type questions that I haven't solved since high school. Very simple, but they may catch you off guard.

Was this helpful?

Interview Statistics

The following metrics were computed from 1,026 interview experiences for the Epic Systems Software Developer role in United States.

Success Rate

18%
Pass Rate

Epic Systems's interview process for their Software Developer roles in the United States is very selective, failing most engineers who go through it.

Experience Rating

Positive54%
Neutral36%
Negative10%

Candidates reported having very good feelings for Epic Systems's Software Developer interview process in United States.