Not as bad as the bad rep it has
Not as bad as the bad rep it has
- Smaller teams
- Can control your own growth rate
- Big projects early on, but apt QA makes sure you don't release buggy systems.
- Core software, not web, which is a good thing for me. You have to consider communication between different versions, data migration, etc. Interesting challenges.
- Extremely complex system with thousands of configurations, requires clever thinking to solve problems.
- No stupid SQL queries, never understood why people liked them.
- Excellent in-house bug tracking system.
- Demands hard-working and smart people; if you are not, then you WILL get fired.
- Excellent culture of Staff Meetings, kind of shows that the CEO still cares about her minion workforce, haha. I like them.
- Everything depends on your manager. If he is a sadist, you are screwed.
- I feel software developers should have more say in general functionality.
- Some teams still use VB6; most have moved to C#.
- Too many people to talk to and approvals are needed. I guess they need to maintain standards, but sometimes simple things can take time.
- Does not care about industry trends, such as new technologies, etc. Although recent efforts show a wave of change.
- Lots of old code.
- Huge learning curve due to extremely complex software.
- If you are stuck working with VB6, then career opportunities are zero. I believe Cache is still useful because it is a neat NoSQL language, and what's important is critical thinking, not the language. However, there is no hope with VB6.
- Reduce the number of stupid HR classes.
- Some way to reduce the time it takes from submitting a design to releasing.
- More effort to remove VB6 and improve company rep.
- More Android and iOS dev across the company.
Was this helpful?
Epic Systems Interview Questions
Epic Systems Interview Experiences
Software Developer
I had to take a lot of tests and had a phone interview where I talked about my past projects. The tests were hours long and took a long time.
Software Developer
30-minute phone screen, then an OA around 4 hours long. The OA had mental math, but also a few LeetCode-type problems. They were not very difficult if you studied common patterns and implementation.
Software Developer
One single virtual interview after a multihour OA. The interview was 4 hours long, but only ~2 hours was actual interview stuff. The rest was two presentations from different people about life at Epic. The 2 hours of interview included a case study,
Software Developer
Verona, Wisconsin, United StatesAugust 19, 2025I had to take a lot of tests and had a phone interview where I talked about my past projects. The tests were hours long and took a long time.
Software Developer
Verona, Wisconsin, United StatesJuly 22, 202530-minute phone screen, then an OA around 4 hours long. The OA had mental math, but also a few LeetCode-type problems. They were not very difficult if you studied common patterns and implementation.
Software Developer
Verona, Wisconsin, United StatesApril 9, 2025One single virtual interview after a multihour OA. The interview was 4 hours long, but only ~2 hours was actual interview stuff. The rest was two presentations from different people about life at Epic. The 2 hours of interview included a case study,
