Epic candidates in 2024 and 2025 reported a 15-30 minute phone interview, online skills assessments lasting several hours (math, logic, reading comprehension and coding), and a final interview of three to four hours in which roughly half the time was presentations about Epic. Developers had a technical interview or pair programming exercise, sometimes a case study such as designing a system to identify patients, and a recruiter behavioral interview. Quality manager candidates had a brief case, a 10-minute presentation without slides and behavioral questions such as “What are five things you are not?”
Candidates who did not get offers most often stopped at the assessments. Two developer loops and two quality manager loops in these reports ended in offers.
Epic interview process round by round
| Step | Duration | What it tests |
|---|---|---|
| Phone interview | 15-30 min | A project you are proud of, teamwork, why Epic |
| Skills assessments | ~3-4 hours online | Math, logic, reading comprehension, coding |
| Final: technical | ~30 min, or a pair programming exercise | Coding with a developer |
| Final: case study | Part of the final | A system design or business case |
| Final: recruiter behavioral | ~30-45 min | How you work with others |
| Final: presentations | Rest of the day | Epic’s campus, culture and products |
Epic interview reports from 2024 and 2025
- Software developer, Verona (December 2024, accepted). 15-minute phone screen, an asynchronous math, logic and coding assessment, and a three-hour final with a 30-minute technical and a 30-minute recruiter behavioral interview.
- Software developer, Verona (April 2025, offer declined). A multihour OA, then a four-hour virtual final with a case study, pair programming and a recruiter interview; about two hours were interviews.
- Software developer, Verona (July 2025, no offer). 30-minute phone screen, then about four hours of OA with mental math and a few LeetCode-style problems.
- Software developer, Verona (August 2025, no offer). Many hours-long tests and a phone interview about past projects.
- Software engineer, Verona (February 2025, no offer). Phone interview (“Why Epic?”), a coding and math test with no IDE, and an onsite.
- Software engineer, Verona (October 2025, no offer). 30-minute phone interview on the resume, then a four-step skills test.
- Quality manager, Verona (March 2025, accepted). Role introduction, a call with someone in the role, a brief case, a 10-minute presentation without slides, and a behavioral interview.
- Quality manager, Verona (April 2025, no offer). Math, rates and coding tests plus a personality assessment, then a multi-hour session with about an hour of interviews.
- Quality manager, United States (July 2025, offer). A phone call, a proctored online exam with a Rembrandt personality test, and a full onsite day.
- Integration engineer, Verona (March 2025, no offer). An online interview with a wide group of people.
Detailed interview experiences
Experience 1: Software developer, Verona, December 2024
Source: Taro, posted December 7, 2024. Accepted offer; rated positive.
Phone screen (about 15 minutes)
- A developer checked basic information and asked about a project the candidate was proud of and a time they compromised with a teammate.
Asynchronous assessment
- Math, logic and coding. The candidate found it easier than other companies’ assessments.
Final round (about 3 hours)
- 30-minute technical interview with a developer.
- 30-minute behavioral interview with the recruiter.
- The rest was informational sessions about Epic’s campus, culture and products.
Takeaways
- What stood out: Only an hour of the final was evaluation, so each 30-minute interview carries a lot of weight.
- How to practice: Prepare a two-minute project story and a compromise story before the phone screen.
Experience 2: Software developer, Verona, April 2025
Source: Taro, posted April 9, 2025. Offer received, then declined; rated positive.
Online assessment
- Several hours; details not given.
Virtual final (about 4 hours)
- Case study: Design a system for identifying patients.
- Pair programming: A coding exercise with an Epic developer.
- Recruiter interview and wrap-up.
- Two presentations from Epic staff about working there filled the remaining time.
Takeaways
- What stood out: A healthcare-specific case study in a developer loop.
- How to practice: Practice record matching and data privacy trade-offs for the patient identification case.
Experience 3: Software developer, Verona, July 2025
Source: Taro, posted July 22, 2025. No offer; rated neutral.
Phone screen (about 30 minutes)
- Behavioral: describe a time in a project you had a conflict.
Online assessment (about 4 hours)
- Mental math and a few LeetCode-style problems. The candidate said these were not very difficult if you had studied common patterns and implementation.
Takeaways
- What stood out: The length, not the difficulty: the candidate found the problems manageable but the test ran about four hours.
- How to practice: Take one full-length timed practice session before the real one.
Experience 4: Software engineer, Verona, February 2025
Source: Taro, posted February 20, 2025. No offer; rated negative.
Phone interview
- “Why Epic?”
Technical test
- Coding and math. The coding challenge had no IDE: code was typed as plain text, with no way to run or debug it.
Onsite
- Mentioned without details.
Takeaways
- How to practice: Write solutions in a plain editor and trace them by hand.
Experience 5: Quality manager, Verona, March 2025
Source: Taro, posted March 2025. Accepted offer; rated positive.
Final interview
- About an hour of company and role introduction.
- A short call with someone in the role describing a typical day.
- A brief, simple case interview.
- A 10-minute presentation on any subject; slide decks were not allowed.
- A casual behavioral interview. Reported question: “What are five things you are not?”
Takeaways
- What stood out: The presentation topic was the candidate’s choice, so pick something you can explain clearly without notes.
Experience 6: Quality manager, Verona, April 2025
Source: Taro, posted April 22, 2025. No offer; rated positive.
Assessments
- Basic math, rates and coding tests, plus a personality assessment the candidate believed was used for placement.
Interview
- Several hours including orientation content, with about one hour of targeted interviewing using STAR-style questions.
- Reported questions: tell me five words that do not describe you; describe a time you took charge to change something at your job.
Epic interview questions that come up often
Phone interview
- Tell me about a project you are proud of
- A time you compromised with a teammate
- A time you had a conflict in a project
- Why Epic?
- Which libraries or technologies have you used?
Assessments
- Mental math and rates
- Logic and pattern recognition
- Reading comprehension
- Easy to medium coding problems, possibly without an IDE
Final interview
- Design a system for identifying patients
- Pair programming with a developer
- What are five things you are not?
- A time you took charge to change something at work
- Where have you shown initiative in your own life?
Epic interview tips from these candidates
- Block a full quiet afternoon for the assessments; reports describe them as three to four hours.
- Practice coding without running the code.
- Expect half the final to be presentations, and save your questions for the interview segments.
- Quality and project manager candidates: prepare a 10-minute talk without slides.
Epic behavioral round in these reports
Developers had a 30-minute recruiter behavioral interview in the final; quality managers had STAR-style questions and self-description prompts. Sample answers are on the Epic behavioral interview questions page, and each step is explained on the Epic interview questions hub.
Epic interview tips from these reports
Phone interview
- 15-30 minutes with a developer or recruiter.
- Expect a proud-project question and a teamwork question.
Assessments
- Math, logic, reading and coding over several hours.
- One 2025 report had no IDE for the coding part.
Final interview
- About half evaluation, half presentations about Epic.
- Developers may get a case study or pair programming.
Sources
- Taro: software developer, Verona, December 2024
- Taro: software developer, Verona, April 2025
- Taro: software developer, Verona, July 2025
- Taro: software developer, Verona, August 2025
- Taro: software engineer, Verona, February 2025
- Taro: software engineer, Verona, October 2025
- Taro: quality manager, Verona, March 2025
- Taro: quality manager, Verona, April 2025
- Taro: quality manager, United States, July 2025
- Taro: integration engineer, Verona, March 2025
Similar companies
Optum · Oracle · Intuit · ServiceNow · AMD