Decent pay considering the location.
After several years, you lose track of popular technology, either stick with Epic or invest time and money to learn (but you still lack industrial experience). A Microsoft dev manager once told me they don't think engineers from Epic make good candidates.
Poor management. Team leads lack knowledge of management and have no idea how to communicate. A great portion of leads are young developers because older people want to avoid being a lead.
No sense of belonging. You know you will leave the company after a few years for sure because most of your co-workers are young students, and older co-workers keep leaving. But considering point 1, it will be hard to find your next job.
Private holding, so you actually have no idea how the company does. Boss boasts sales on monthly staff meetings, while you see otherwise on media.
Go-live is absurd. You HAVE to go to hospitals all over the country to 'help' them use the software, while you have no idea how the software works. It is a huge system, and as a focused and busy developer, there is no way to know how. Sometimes you end up in clinics in dangerous neighborhoods with drunken doctors. If you like to travel, you may like it, but for me, it was not a good experience.
Does not treasure its employees. Years back, Epic built new offices and recruited developers crazily from India (500 new developers per month) to get prepared for the big contract from DOD. Then they lost the contract to Cerner. So Epic began to lay off developers with absurd reasons. I have a friend who got laid off because he didn't log his time every day. Another developer got laid off because the TL thought he could not communicate with the team, which makes no sense.
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.
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.
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,
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.
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.
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,