Pros: Decent pay and benefits for the Madison area, good hours, and a good work environment.

Cons: Despite what the recruiters say, this is not a Silicon Valley company. Expect decades-old technology, an incoherent database structure, and frequent outages. If you are passionate about software development, this is not the job for you.

Pros: Almost everyone I work with is very talented, friendly, and eager to help, across all roles: SD, QA, Training, HR, TS, IS, etc. The campus COVID-19 precautions are extraordinary. It was a very clean and great campus pre-COVID. But to bring everyone back to campus with maximum safety, they've made a number of changes recently, including giving EVERYONE who wants a solo office a solo office. To achieve this, they did have to do some construction to convert single offices into two rather small offices. I was already on a team & role that had solo offices as long as a window wasn't required. That's a great perk as far as concentrating on code goes. Our culinary team is fantastic. It's the most healthy I've ever eaten in my life. For COVID-19, they've switched to providing everything in to-go containers and payment online. I find the work challenging and fun. As a software developer, you will have opportunities to collaborate with customers on enhancements and learn a lot about an industry that you probably don't know a lot about before Epic.

Cons: For me, the number one con right now is that several hundred employees are quite upset about Epic's plan to have almost all employees working on-site within a few weeks. These employees feel that any amount of added risk from WFW compared to WFH (Work from Home) is not acceptable. Epic's leadership has decided that (a) working on-site produces higher quality software more quickly and (b) there isn't any future time period in sight where it would be viewed as completely safe to cease WFH. I understand the angry employee's perspective, but I also disagree and think the anonymous complaints aren't realistic in acknowledging that it's much easier to work on-site. A simple example is masked-up and working with one or two developers on a whiteboard. This is already happening for those of us who've been WFW for a couple of months now. The other thing that isn't being acknowledged is that Epic's campus is a great example of how to safely open up facilities with a large amount of people. I don't want to get COVID-19 and I don't want other people to contract the disease either. But I've been on campus with 3000+ coworkers for a couple of months and coworkers are being courteous and following safety procedures. 10,000 employees doing the same logically won't make a difference when we can see how the rest of the county, state, and country are returning to more and more in-person activities. If you don't want to work on-site as described, then definitely look elsewhere for work. As far as the dozens and dozens of negative reviews on here, I'd take into consideration how angry they seem to be. It's true leadership hasn't bent 100% to their demands. But I'm personally glad leadership hasn't. Having a few hundred anonymous coworkers whipped up in a frenzy with you doesn't make you "right". Nor does having a billion dollars. Nobody knows for sure who's "right" and there's a lot of disagreement.

Pros: Good pay, decent benefits, subsidized sabbatical, occasional travel, writing code that helps save lives, learning about healthcare. That’s about it!

Cons: Having your own office might be nice for some, but it creates a culture of isolation. I found myself calling a teammate on the phone while this person was sitting across the wall from me! No social events (except one in the summer). Their organization is left up to the teams. And even when they are organized, people feel weird hanging out with each other because they are not used to it. Some teams do better than others at it, though. No alcohol is allowed at social events, even if a team goes for lunch and dinner somewhere on their own dime, even on weekends, so any attempts to have a good team-building activity are failing because we are bound by Epic rules. This forces people to organize in cliques so they can hang out, drink, and have fun, and not be “perceived” as Epic employees. Some teams are more casual and hang out wherever they want and don’t mind drinking and talking about work. Even the president of Epic, Carl Dvorak, called Epic culture “fake” during his 25-year employment anniversary address (he had to apologize later via email for the wrong word choice). The technology is so customized that your knowledge is barely transferable outside of the company: Visual Basic 6 (still, it’s 2017!!), Cache (MUMPS) that is probably still supported only because Epic uses it (not transferable either). Some of the half-lucky ones use Objective-C and Java for mobile development (I’m saying half-lucky because you’re still writing nearly half of your code in Cache, and because only one out of the two major mobile teams - Haiku - is good. It’s more chill as far as culture goes and it’s usually on the cutting-edge technology. This is because they are serving physicians, who usually own the newest iPhones. The other one - Rover - writes applications for hospital-owned devices that are low-spec. Plus the team works long hours and never hangs out. Innovations usually happen on Haiku, and Rover just adopts it). There are also web teams that use HTML, CSS, Java Script, and C# (don’t expect to use any third-party frameworks like AngularJS, Node.js, React, Rails), but that experience is barely transferable because Epic builds its own frameworks. Also, by the time they are done building them, the industry is 3-5 years ahead. Work-life balance doesn’t exist: Epic CEO Judy Faulkner said she doesn’t like this phrase. There is “work-life integration,” she said, advising to take care of work things in your free time, and allowing to take care of personal things during work time. Still, it seldom works, as each employee has to log time every 15 minutes (which a lot of people hate). This practice is unheard of in software industry leaders like Google and Amazon. Prepare to log at least 45 hours a week. This means you really need to work at least 50 hours because you can’t log reading industry news or read up on new technology during the hours you log. Pretty much, if you are taking a long break, you can’t log it (your metrics will hurt otherwise, and you will hear from your team lead, “Why did it take this long?”). Also, if everyone on your team logs 50-55 hours a week and you log just 45, you complete fewer tasks than other people and will hurt your metrics (which affects your raise, bonus, and can get you fired based on performance). Judy said once, “Everyone is replaceable,” that’s how Epic takes care of their employees. Note on family friendliness: no benefits for new parents outside of the federally mandated ones - you have to use your sick or vacation time. The teams are not forgiving. I know at least one employee who had a baby and went to work part-time in about a week and came back full-time in another week or two. The demands are high. The fact that you have a family means nothing. Conclusion: Epic doesn’t give a crap about employee happiness. Unless you love healthcare or you’re introverted, choose another place!