[weitendorf]

Epic is a lot of people's first "real" (full-time, after college graduation) job and first corporate job, and very few of their employees are from Madison proper. I think a lot of people dislike working at Epic once the hours get to them and they start getting tired of Madison, but I also think their employees might overestimate how much greener the grass is on the other side, because they haven't actually experienced any comparable job.

Personally I think Epic actually does a pretty good thing training up and employing so many new grads with skillsets that don't find it as easy to get solid corporate jobs as SWEs (a lot of their TSEs are STEM-but-not-CS grads, implementation people seem to be ~anything). They do expect something back from those employees in return, but they're paid quite well compared to their alternatives and given a lot of support/structure to ease into their first job.

IMO it's a place I appreciate a lot more in hindsight than I did while briefly working there, and I don't think that's an unpopular opinion

[odyssey7]

This defense of Epic really makes it sound like a great opportunity.

> I also think their employees might overestimate how much greener the grass is on the other side, because they haven't actually experienced any comparable job

Many people continue to regret their time at Epic even after having left and having seen the other grass first-hand.

> Personally I think Epic actually does a pretty good thing training up and employing so many new grads with skillsets that don't find it as easy to get solid corporate jobs as SWEs

Count the MUMPS training to essentially be a waste of time, unless you like the idea of writing MUMPS going forward.

Also, your endorsement reads as if Epic should be an option of last resort rather than a place where a software engineer should want to be.