Pros: If you're a software developer, and you're alright with working in an arcane system with aging tools, the pay, working conditions, and opportunities to do cool stuff that makes a difference for many thousands of people are good. Your results may vary, however, depending on what team you're assigned to. If you're an outgoing business type, the Implementation role is a chance to act like a salesperson without selling anything. It's highly stressful and there's an ugly, hidden rat-race, but the cool thing is that you'll be pitching a product that, while it isn't perfect, has proven it gives good results, and you'll be doing it in a way that's more focused on progress and people than on profit. If you're in neither category and just need a dang job, the tech service and quality assurance roles are waiting to catch you. Unlike the above two, these two jobs are just that, jobs. You do something uninteresting and uninspiring for a few hours a day, they pay you. Pros of TS: * Pays better * More chances to distinguish yourself and climb the ladder * Some tasks of the many you'll do are interesting Pros of QA: * Low stress * Rarely exceeds 45 hrs/wk (unlike all the other roles) * Most teams have a 5-o-clock, go home culture.

Cons: Cons of SD: You'll develop your professional skills along a pathway that takes you further and further away from other branches you might wish to jump to in the future, because of Epic's ancient and unusual code scaffolding. If, 5 years in, you decide you don't much like developing for Epic, but you need the income of a senior SD, you're in trouble. Cons of IS: Don't expect fun travel. It's brutal, draining, bloodshot travel. If you're picturing chances to visit friends or even see the towns you go to, picture again. Cons of TS: Hour creep is prevalent on many teams. You often hear about TS getting slammed with 55 and 60 hour weeks month after month, with no graceful way to escape. Also, be honest. No one dreams about technical support. Cons of QA: Pay is low. Other roles don't really respect you. Few opportunities to shine or do innovative stuff, if that's your thing. And no one dreams about doing QA for a living, either. My role at Epic was Test Plan Runner. This is QA's mentally challenged little brother, and is a terrible role. Don't under any circumstances get weaseled into being a TPR; they'll always give you a choice to do QA instead. The story of how I lost my job: I had a hard time concentrating on boring, overly complicated, unstylish systems. My pace of work didn't pick up at the expected pace, and management, nothing if not attentive, noticed right away. After running out of ways to sound hopeful, with it, or eager to keep trying to improve, I was told to resign or be fired, 1 year and 4 months in.

Pros: Food is good, work is hard.

Cons: I don't have any cons.

Pros: A valuable working experience. They demand a lot but compensate well.

Cons: Not great for people fresh out of college, like they claim. You won't get that much real development experience; it will be mostly meetings.