Solicité el puesto a través de la escuela superior o la universidad. El proceso duró 2 semanas. Acudí a una entrevista en Epic en sept 2014
Entrevista
The interview take 2 weeks. I apply in university career fair. They gave me a phone interview and an online assessment. In phone interview they ask me basic information like when graduation, whether willing to work in WI, and career plans, experience in resume. In the ending they ask me a small algorithm question, the anagram problem that in leetcode, i's easy but i did bad.
The online assessment is challenging. it test your response, skill to learn new things, and programming skills. Practice algorithm and programming exercises before the test! There are 4 programming problem. I only solve 2.
After two weeks, HR told me I was rejected. TOT.
Preguntas de entrevista [1]
Pregunta 1
A number is decomposed into digits (one or more in group), if the sequence of the new numbers are Fibonacci numbers, this number will be called "additive number". For example, "1123" can be divided into 1,1,2,3; "12122436" can be divided into 12,12,24,36. so 1123 and 12122436 is called "additive number". write an algorithm to test whether the input number is "additive number".
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.
