About Epic's Hiring Philosophy

Epic Systems is the dominant electronic health records (EHR) company, and its software runs in hospitals and health systems worldwide. The Technical Solutions Engineer (TSE) role sits at the intersection of software, problem-solving, and client management: you implement, configure, and troubleshoot Epic's software for hospital clients, juggle competing deadlines, and learn Epic's proprietary programming language (MUMPS, often called "M"). Despite the "engineer" title, the day-to-day is a blend of technical work and client-facing project management. As one candidate put it bluntly, "This is more like a SALES and CUSTOMER SUPPORT job, not an 'engineering' job" (Technical Solutions Engineer candidate).

Epic hires heavily out of college and through online applications, and it puts candidates through a long, assessment-driven funnel before any real conversation happens. The process rewards raw logic, quick math, and the ability to stay calm while prioritizing chaotic, competing client demands. Epic also screens hard for culture and motivation, since most new hires relocate to its Verona/Madison, Wisconsin campus.

Quick Stats

* Typical process: 4 to 6 stages (phone screen, multiple online assessments, final interview day) over roughly 3 to 6 weeks

* Format: Phone screen, timed online assessments, then a 3 to 4 hour final interview (often virtual via Zoom, sometimes onsite)

* Core focus: Logic and quick math, coding (including a made-up language), case-study prioritization, behavioral fit, relocation willingness

* Difficulty: Moderate (company-wide average 2.83/5); the assessments are long and the case study throws curveballs, but interviews themselves are conversational

What Epic Looks For

* Strong logical reasoning and quick mental math under timed pressure

* Ability to learn a new programming language fast (they teach you M during the assessment)

* Clear prioritization and client communication when multiple deadlines collide

* Genuine motivation for Epic plus willingness to relocate to Wisconsin

"Got an assessment with a 2 minute sections, a math sections, a programming section, and a section where they create a new programming language and you answer questions based on that, then a final interview. The interview was 2 info sessions, a case study, and a conversation with HR/Recruiter." (Technical Solutions Engineer candidate, accepted offer)

Round 1: Recruiter / TSE Phone Screen (~15 to 30 min)

What to Expect

The first contact is usually a short phone call, often with a current Technical Solutions Engineer rather than HR. It is low-pressure and conversational. Expect questions about your background, why you want the role, your long-term goals, and whether you are willing to relocate. One candidate described it as "overall pretty chill, the only behavioral question was asking about a project I did" (Technical Solutions Engineer candidate). Many people receive the online assessment invite at the same time as this call.

Example or Reported Questions

* "Tell me a little bit about yourself and why you're interested in this role?"

* "Tell me about a project you worked on."

* "Where do you see yourself in a few years?"

* "Why did you choose your major?"

Tips

* Have a crisp 60-second "why Epic and why this role" answer ready, and be honest about relocation since they will ask.

* Pick one project you can describe simply, including the problem, what you did, and the result.

* Practice this quick-pitch flow in Nora's Standard Mode so your intro and motivation answers feel natural and unrehearsed.

Round 2: Online Skills Assessments (~3 to 4 hours total)

What to Expect

This is the heart of Epic's funnel and the longest part. Candidates report multiple timed online assessments: a quick-math section, logic and IQ-style puzzles, a personality test, and coding. A recurring twist is a section where Epic invents a brand-new programming language and asks you to answer questions using its rules. The coding section often lets you write pseudocode, and many candidates first learn M (MUMPS) here. One candidate noted, "The hardest part was definitely the leet code section" (Technical Solutions Engineer candidate, accepted offer), while another said the CS questions "were tedious as they kept building off the previous question" (Technical Solutions Engineer candidate). No calculator is allowed.

Example or Reported Questions

* "The skills assessment gave you the specifications of a made-up programming language and asked various questions applying the language."

* "Read code exam, then write code exam (you can write pseudocode)."

* "Quick-time math section with no calculator."

* "Personality and logic/riddle sections that felt like an IQ test."

Tips

* Drill mental math and timed logic puzzles; the no-calculator pace is what trips most people up.

* For the made-up language, read the spec carefully and treat it like applying rules, not memorizing syntax; a couple of intro programming classes is enough background.

* Use Nora's Technical Mode to rehearse explaining your reasoning out loud and walking through code logic quickly, which builds the speed this round demands.

Round 3: Final Interview Day - Info Sessions + Case Study (~3 to 4 hours)

What to Expect

The final round is a multi-hour day (often via Zoom) that combines info sessions about Epic's products and the role, a software demo, and the only true "interview" parts: a case study and a behavioral conversation. The first sessions are usually group; the later ones are individual. The case study is the centerpiece. You are given a list of competing client tasks and deadlines, and you must explain how you would prioritize and communicate. Interviewers then layer on "what if" curveballs to see if you stay consistent. As one candidate advised, "have a framework for prioritization and stick with it as new things come up" (Technical Solutions Engineer candidate, accepted offer).

Example or Reported Questions

* "You arrive at work to find urgent emails from three different hospital clients, all with impending deadlines. How do you prioritize them, and how would you tell them a fix will take longer than expected?"

* "A client asks for a bug-fix by the end of the week, but you determine it to be a larger fix that requires months. How do you respond?"

* "How do you handle a situation where there are two clients experiencing critical errors? How do you prioritize your schedule and communicate with them?"

* "If three clients had approaching deadlines, what is the first thing you would do in the morning for 30 minutes before your first meeting?"

Tips

* Bring a clear prioritization framework (urgency, client impact, deadlines, effort) and apply it consistently as they add new wrinkles.

* Always pair prioritization with communication: explain how you would set expectations and tell a client a fix will take longer than hoped.

* Practice these prioritization and client-scenario questions in Nora's Behavioral Mode so you can think aloud calmly while interviewers throw "what if" follow-ups at you.

Round 4: HR / Recruiter Interview (~30 to 60 min)

What to Expect

The final conversation is with HR or a recruiter and is described as very conversational and friendly. It covers your background, motivation, self-awareness, and culture fit. Expect classic "why Epic," major/school, and five-year-plan questions, plus some quirky self-reflection prompts. Salary often comes up here, and candidates report it mattering; one noted they "said a number too high for them because they ghosted me after that" (Technical Solutions Engineer candidate). Base pay was reported around $75k with $10k relocation.

Example or Reported Questions

* "Why do you want to work at Epic?"

* "Where do you see yourself in 5 years?"

* "Name 5 things you are and 5 things you are not."

* "What did you hear about Epic that you didn't like?"

Tips

* Prepare a sincere "Why Epic" and be ready to name parts of the job that may not be a perfect fit; honest self-awareness reads well here.

* Know Epic's pay range going in so a salary question does not catch you off guard or price you out.

* Run mock salary conversations in Nora's Salary Negotiation Mode to practice giving a reasonable, well-anchored number without underselling or overshooting.

Frequently Asked Questions (FAQ)

1) How many rounds are there?

Typically 4 to 6 stages: a short phone screen, multiple timed online assessments, info sessions and a software demo, a case study, and an HR/recruiter interview. The assessments and final interview day are the two biggest hurdles.

2) What topics are most common?

* Quick math, logic/IQ-style puzzles, and coding (including a made-up programming language and M/MUMPS)

* Case-study prioritization of competing client deadlines plus behavioral and motivation questions

3) How long does the process take?

Usually about 3 to 6 weeks, though the multiple assessments and scheduling for the multi-hour final day can stretch it. Some candidates report long waits and even being dropped after the webinar stage.

4) How should I prepare?

* Drill timed mental math and logic puzzles with no calculator, and brush up on basic coding and pseudocode.

* Build one prioritization framework and practice applying it to client-deadline scenarios out loud.

* Prepare honest answers for "Why Epic," your five-year plan, relocation, and salary expectations.

* Use Nora AI to rehearse end to end: Standard Mode for the phone screen, Technical Mode for the coding and logic speed, Behavioral Mode for the case-study and "what if" prioritization questions, and Salary Negotiation Mode for the HR pay conversation.