Process:
Phone screen, skills assessment, on-site interview, offer
The skills assessment involved a math speed test (2 min; 10 questions), a coding challenge (4 non-trivial coding problems), and an interesting learning test where you were given information about how a made up programming language works and had to answer questions based on the rules so far given to you.
The on-site interview was pretty casual. The first two interviews for me mostly involved people telling me about their experiences at Epic (make sure to have some questions in mind to show interest and learn more about what you care to know about. In the third interview, I chose between front end, backend, and middleware and got a related question, I chose middleware and they gave me a question about a previous problem they have solved at the company and asked me how I would approach it.
Perguntas de entrevista [1]
Pergunta 1
On the skills assessment:
Create a function to determine if a number adheres to goldbach’s conjecture.
Fiz uma entrevista na empresa Epic (San Francisco, CA).
Entrevista
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.
Perguntas de entrevista [1]
Pergunta 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.