Solicité el puesto a través de la recomendación de un empleado. El proceso duró 4 semanas. Acudí a una entrevista en Epic (Verona, WI) en may 2014
Entrevista
- phone screen: basic questions about interest and maybe a technical topic. mostly familiarizing with Epic's industry
- skills test: programming test that focuses mostly on dynamic programming. Can generally use whatever language you're most comfortable with (python, java, C#, whatever). is remotely proctored by somebody over the internet via webcam, which was very weird
- I think there's a personality test too. Pretty straightforward.
- on-site: Epic pays for you to stay in Madison and come to Verona for on-site interview. Meet with several different people to discuss past projects (likely school projects). pretty low-impact interview questions. walking tour of campus, lunch with other candidates. have option to go out to dinner with Epic employees in Madison.
- call with offer
Epic hires a lot. Expect to have several other people interviewing at the same time as you. Don't dress up like you might for interviews at other companies - Epic is very casual and you'll stand out if you're wearing a suit. Khakis and a polo shirt is sufficient. If you pass the skills test you're basically in, just be relaxed and comfortable chatting with other folks during the on-site and you can reasonably expect an offer.
Acudí a una entrevista en 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.
Preguntas de entrevista [1]
Pregunta 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.