Solicité el puesto a través de un captador. El proceso duró 3 semanas. Acudí a una entrevista en Epic en oct 2017
Entrevista
I was emailed by a recruiter, giving me a link to apply at. You'll fill out a few forms and submit your resume. There's then a phone interview, that's very casual feeling. Then there's a skills assessment that's very long and difficult. It has three parts: speed round, technical, and programming. I recommend finding some "speed round" practice tests that test you on solving as many problems in short, limited amount of time. The technical part isn't terrible. They explain the syntax of a made up language and you have to answer questions related to how a given expression will be interpreted based on that. The programming part is an ugly beast. First, you have to use a poorly executed service called ProctorU that feels very intrusive and very clunky. Research the service. It's a good idea, but horribly executed. I might recommend having the assessment scheduled at an official testing center as opposed to using your personal computer. There will be 4 programming problems to solve, which can be done in C, C++, Java, or Python, and there's no compiling during the exam. I barely finished the first problem, and didn't finish the others. I had to resort to very vague pseudocode. I highly recommend visiting a website called open.kattis.com and practice as many problems as possible. It will only help. Hope this helps, and good luck.
Preguntas de entrevista [1]
Pregunta 1
Why I want to work at Epic, why I want that particular position, and what projects have I worked on before.
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.