Epic Systems

The culinary team does a really solid job. The campus is good for the Wisconsin winters and also fun to show to people that have never seen it.

You also get a private office, usually either shared with an officemate if there’s a window or one all to yourself if it doesn’t have one. I’m a fan of that a lot more than an open floor plan or a cubicle.

Most devs here are expected to travel occasionally, which was by far my favorite part of the job. We either assist end users when the system is first live, or we observe end users at healthcare organizations use our software and work with them to figure out how to improve it. I found both of these rewarding and got to see more of the country in the process. It’s not a ton of travel like the other roles might have.

I put these in cons since someone who takes this job without knowing these could easily become unhappy down the road, but depending on your personality and interests, several of these can easily become pros.

As your career matures here, expectations of you will rise, and responsibilities will slowly add up. The flip side of this is that even decent performers are rewarded, and you won’t be bored.

By the time you’ve worked for a team for 2-3 years, your technical knowledge will have only grown slightly, but your knowledge of some super-specific aspect of the healthcare industry will skyrocket. Some people love this aspect, some hate it, and some are just okay with it.

It doesn’t really affect you if you aren’t going into some kind of healthcare consulting, but Epic has a non-compete, which only makes it harder to find employment in that field after leaving. I see no upside for this one.

Get rid of the non-compete.

Be more lenient with WFH.