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 oct 2017
Entrevista
The phone screening was very straightforward where I described one project in detail. Then there was an online assessment and a very odd profile building thing (Rembrandt profile) that asked multiple choice questions that would be asked from a psychiatrist or a career match profile. The online assessment seemed very bland. There were 4 not too difficult algorithms that I coded. I had to comment all of the code because there was no compiler and I wasn't sure if those were the correct answers. There was also fast math which was 2 minutes of 10 geometry and algebra questions (can do without a calculator). Finally, there was answering questions on a programming language the assessment made up. This language breaks some of the rules of common programming languages but adds unique and unintuitive features to type parsing, so I needed to be careful. Overall, I did not enjoy the experience, especially having to do this remotely with ProcturU., and not being evaluated live by a real software engineer. I often have a positive learning experience with my interviews, but this is not one of them.
Preguntas de entrevista [1]
Pregunta 1
What was a project you have done and how did you approach it?
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.