Pros: The work is interesting from time to time. Most employees have either a single or double office; there are no "open office" layouts. There are lots of food choices in the cafeterias. The campus is nice.

Cons: There is no technical vision in management. Promotion has nothing to do with merit; sycophantic yes men get ahead, and people who actually know what they're doing stay put. Management is obsessed with metrics about bugs. A good metric is supposed to be a means to achieve the end of producing quality software, but at Epic, the metrics are the end. No matter how severe a problem is, TLs close or deprioritize bug reports about it to make their numbers look better. If customers complain, TLs make up excuses to shift the blame onto something else (e.g., the customer's hardware, their network, Windows, or anything but Epic) or convince the customer that the problem is impossible to fix. When underlings point out that the problem is, in fact, quite easily solvable, their proposals are stonewalled. Meanwhile, TLs invest thousands of man-hours in pet projects that accomplish nothing (and frequently make the software worse). The TLs have so little technical knowledge that they often don't have a clue how much damage they're causing to our customers. But even when they do know, they don't care. There are no consequences for poor decision-making by employees. As I mentioned above, most customer complaints are suppressed by TLs in order to keep quality metrics looking good. So, there is no feedback mechanism to expose bad employees; people who slap together mountains of garbage code are praised for their productivity, while those who take the time necessary to build high-quality, high-performance systems are criticized for their low output. Much of the software is based on obsolete technology like Visual Basic. The amount of time a developer spends on such unpleasant languages is highly dependent on their team; a lucky developer might work mostly in C#, while an unlucky one could spend their days wading through unbelievably bad M and VB code. On a related note, because the software is so large, there exists a huge body of Epic-specific knowledge. Some people fall down the rabbit hole of trying to learn as much as they can about our software, but that expertise is unlikely to be of much use outside of Epic. Spending years writing VB code and getting certified in 10 Epic applications probably won't look very good on a resume. Of course, some TLs are better than others, and some teams are better than others. With luck, you can work with intelligent people on challenging problems and really improve the software. But one day, your luck might run out.

Pros: Great job out of college.

Cons: Hope you can set your own boundaries.

Pros: Culinary is great. Not as good as it used to be, but for a corporate cafeteria, the variety for the price is awesome. Smart coworkers who genuinely want to help you. Lots of opportunity for ownership on projects and a lot of opportunity to move laterally into other areas or teams of Epic software. Pay is great for developers, especially in the first few years and especially compared to cost of living.

Cons: Upper management is opaque, inflexible, and uncaring. Our inclement weather policy is that if the local schools close, you can work from home for the day. In December, they didn't, so people tried driving in; multiple accidents, people driving into ditches continuously, and an average commute of 2 hours. When questioned about updating the policy internally, they closed the discussion thread and said they'd make no changes. After the Dobbs supreme court decision, employees asked for additional resources for women employees needing to travel out of state for care, which Epic closed the thread about and emphasized they care about the patients, not us. Bad track record with diversity, equity, and inclusion, including proactively reaching out to DEI groups during the George Floyd protests to discourage involvement. The COVID response was atrocious, enough to get us on the national news. See other reviews and the CBS news segment. The same attitudes remain today that caused it. The man they put in front of the interviewer was a sock puppet for upper management (none of us knew who he was) and has since left the company. Understaffing by design. Most, if not all, teams are stretched and stressed. Packed parking garages and a fairly high chance of sharing an office. Our rate of building new office buildings is woefully inadequate for our numbers, even with our understaffing. Time-logging required down to 15-minute granularity even for time not billed to customers. This time is reviewed, available for team leaders to use to micromanage you, and factors into your bonuses. Bad burnout and a pretty high turnover rate, which HR is all too quick to point out is in line with the healthcare software industry. Average tenure is very low. The underlying database that's primarily used (Intersystems Cache) is a relic, and your experience with it will not be transferable anywhere else. PTO is extremely underwhelming. You get two weeks paid vacation for your first 2 years, then three weeks a year beyond that. The sabbatical every five years is great until you hear about all the strings, like restrictions on when you can take it (if you're supporting multiple installing customers, good luck!). Statistically, you won't even make it to 5 years here to take it. 6 sick days a year. 5 work from home days a year. 7.5 holidays, with 1 day you can use on any other holiday Epic doesn't observe. The line for the number of holidays is, "This is how we've contracted with customers, per the days we've seen them take holidays for support staff," but when asked why this policy applies to people who don't support customers and excludes days all our customers have off, radio silence. The non-compete can be anywhere from 1.5 to 2.5 years, depending on if you've taken Epic stock and your start date. This precludes you from working with a binder-full of customers, competitors, and other software companies that ostensibly don't compete with Epic. For TS and IS, this is a pretty huge deal. For developers, just don't take a job here expecting to stay in healthcare software after you leave.