J'ai postulé en ligne. Le processus a pris 3 semaines. J'ai passé un entretien chez Epic (Verona, WI) en nov. 2023
Entretien
After applying for the role, I got an email to schedule an initial interview that was all about someone talking about the role, Epic and Madison City. There was many candidates in the the zoom meeting and not the typical 1 on 1 interview. You can't open your mic but you can ask questions via chat.
After the zoom meeting, I received an email with a link to the OA.
The OA was 4 parts, 2-minutes rush questions part where you answer as many questions as you can.
Second part was math (some were tricky and not math questions although they seems so) and third part was learning new language (They introduce a new language to you and you should read the short documents and answer the questions).
Last part was the programming section, It was 4 problems and you have write your code in a non-compiler IDE. Comparing to Leetcode there were 2 easy and 2 medium problems. The problems were straight forward, nothing tricky but need to know basic DSA.
I got the rejection email 2 weeks after my OA.
Questions d'entretien [1]
Question 1
The programming topics I had:
- Hash Map
- Matrix
- Recursion
J'ai passé un entretien chez Epic (San Francisco, CA)
Entretien
Medium level leetcode and then a very basic system design question as a final round interview. Overall, smooth and simple process. Only one technical and it was the first one.
Questions d'entretien [1]
Question 1
How would you design a system to minimize wait time at a health care center?
First round is a thirty minute phone call with one of their developers. The other part of the first round is a three hour exam with IQ test style logic questions and coding questions.
[OA] OA was fair. Programming part are leetcode easy and easy-mediums, straightforward simulation, backtracking, dfs, strings, etc. No DP/graphs but ymmv.
[Final interview] (Case Study) I think the interviewer came up with their own prompt. It's mostly discussion-based, with a virtual white board. It's not too technical. I'm guessing its testing your communication/logical reasoning than system design skills. (Pair programming) 1 question, same format as the OA on the same platform, leetcode easy.
[Overall] Technical difficulty isn't bad. Interviewers who are current software devs seemed friendly. Had a good experience, yet got rejected.