Taro Logo

Software Developer Interview Experience - United States

March 1, 2021
Positive ExperienceGot Offer

Process

I applied through my university’s job board.

An HR person emailed me within a week, and I set up the phone interview.

The phone interview was pleasant and easy. We talked about a project I had worked on, then I asked some questions about the company.

The personality test was fairly standard. I didn’t pay much attention when I took it, which was probably a mistake, since I’ve heard that management uses them to help them pick team leaders.

The online assessment was also pretty easy, although if I had a busier schedule, I’d have been annoyed at how long it took. It was proctored, so I had to install special software on my computer and keep my webcam on, which I don’t love. There were three sections to the assessment.

The first was a 3-minute math/reasoning quiz. It was entirely simple questions like fractions/percentages. I bombed it because I don’t own a calculator, but it didn’t matter at all.

Then there was a multiple-choice quiz where they defined a made-up programming language and asked questions about it. That took a bit of thinking but was ultimately not too difficult. (It does not resemble any popular modern programming language—you have to rely on your logic and reasoning skills.)

Finally, there was the coding section, where there were three Leetcode-style problems. You are given a text editor with syntax highlighting for many languages, but that’s it. You can’t test your code, nor can you use the internet for help. Other people get really stressed about this, but I actually liked it. They know you might have some syntax errors and that you might not remember all of the library functions—they’re just looking for the thought process and the algorithms themselves. I wrote my solutions in Python and forgot how to call some of the library functions, so I wrote a comment at the top of the file describing the functions I was calling and what their input/output looked like. These questions were not hard compared to other big tech companies. I did not practice any Leetcode during my job search, but that didn’t matter.

The on-site interview was laid-back. There was a presentation, a Q&A session with a developer, then a case study. In the case study, they asked how I would implement a solution to a particular problem in the health field. Then they asked about what kinds of problems could arise and how I would address those.

Throughout the process, I never felt that anything was particularly stressful or difficult, and the folks at Epic were kind and professional.

Questions

Why do you want to work at Epic?

Describe a project you worked on.

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.