Taro Logo

Nice from a non-technical perspective; not so from a technical one

Software Developer
Former Employee
Worked at Epic Systems for less than 1 year
January 22, 2017
Madison, Wisconsin
3.0
Doesn't RecommendNeutral OutlookNo CEO Opinion
Pros

Campus is attractive, and parking is good.

Food served on-campus is good.

People are generally nice and willing to help you if you ask.

Even developers travel to customer sites, a nice touch to remind you why you're doing this.

Positive culture; people want to do the right thing.

Cons

Bureaucracy can be overwhelming with respect to changing code.

Codebase is old and patchy, to the point where the changes you make don't feel useful.

Above two points mean the job feels less like a developer job and more like a generic job with a technology requirement.

Technologies are somewhat out-of-sync with the outside world. This is slowly changing (they are migrating from an old frontend to a newer one), but you aren't on the cutting edge.

Don't take the job if you're a software perfectionist - there's a lot of stuff you'll want to do that you can't.

Amount of time-logging can feel excessive at times.

Advice to Management

Do some centralized technical design, and make your system amenable to unit testing. Right now, all the high-level technical design is being done by UI and business people, and technical plans seem more localized (with some exceptions).

This may require re-design of many modules, which will be a lot of work, but you need to do this in the long run.

Was this helpful?

Epic Systems Interview Experiences