The COVID response was/is very poor- everyone is now back in office (originally with no vaccine mandate! although there were masks mandated for unvaccinated staff, and now masks are mandatory and I think a vaccine mandate goes into effect in October) with a negative impact on team morale. There was also an attempt to bring everyone back last year that ended at the last minute and got a bit of national news coverage for how bad of an idea it was.
There have been several disheartening communications to some employee groups with respect to what company values are. Search for Epic Systems Diversity for more context--before that I would have said Epic has poor diversity/inclusion but it's comparable to the overall tech industry, but after receiving that email my trust in the company was severely eroded. The CEO did do some amount of damage control, and the executive who sent out the email did send out a follow up, but compared to larger software firms diversity/inclusion feels like an afterthought.
Leading up to my departure I felt that talented engineers were/are leaving at an extremely high rate. Compensation that--while high and far more than anybody needs to live very comfortably for the location--is lower than other software firms, combined with the ease of interviewing now that everything is virtual, the forced return to office at Epic, and poor treatment of employees throughout the pandemic makes it difficult for me to see Epic retaining even above average engineers at the company. Several of my very skilled colleagues responsible for some of the good stuff in the pro section left with no job lined up. I personally regret having secured several job offers before resigning--a month is more than enough time to go from hello to offer at a top tier firm in this market.
The campus is in the middle of nowhere, and commuting from Madison--a lovely little city where it's very pleasant to live--is unpleasant. One could live in Verona for a less unpleasant commute, but Verona is generic suburban sprawl/not appealing. Walls are also thin (you'll hear your neighbor's conversations--mildly disrupting, although easily mitigated with headphones), and many employees have depressing windowless offices that are sometimes shared, even with the whole pandemic thing going on.
Some lower/middle management employees are not very good at managing product, pushing for meeting short term deadlines/goals when that will likely lead to longer term delays from having to urgently backport fixes to alpha quality software.
For all management levels, I think there is an unfortunate pattern of rewarding those that blindly support whatever the next person higher up on the food chain is proposing or agreeing to any request even if it's unreasonable or impossible. This really came to a head w/ the pandemic, where people dissenting against the forced return last summer moved into non managerial roles. It might also contribute to the above noted desire to get projects out the door even when the project is clearly not ready.
You are "required" to log each 15 minute increment of time you were working throughout the day if you are unfortunate enough to have a manager that's not OK with you ignoring this. I never did this, but had colleagues whose managers expected it. This also seemed correlated with managers that used hours worked as a primary metric/were bad managers.
On most teams there is essentially zero automated testing--with reliance on manual QA. On most teams there is also a severe shortage of QA staff. This results in a large bottleneck.
Internal deployments are broken with some regularity due to under or untested changes moving in.
As a company many internal frontend frameworks are actively hostile to testing and (internal) users. Lots of this is necessary complexity, some of this is just poor tooling largely stemming from teams being understaffed.
Internal processes and tooling around "client" development are extremely poor and probably cost the company millions of dollars per year in wasted employee time on the low end.