Solicité el puesto a través de la escuela superior o la universidad. Acudí a una entrevista en Epic (Chicago, IL) en oct 2020
Entrevista
The behavioral interview is a pretty standard 30 min long interview where the recruiter would ask you some questions about your background. The technical interview is where the problem is. They are two parts which take about four hours to complete, even if you are allowed to take a bathroom break, it is still a bad expereince.
Preguntas de entrevista [1]
Pregunta 1
Given a made-up programming language and asked some simple operation questions
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.