Candidatei-me por meio de uma faculdade ou universidade. O processo levou 3 semanas. Fiz uma entrevista na empresa Epic.
Entrevista
1st thing is a phone call with an engineer, mostly to gauge your own interest. They will ask you a simple coding question, you only need to give a high level walkthrough of your approach. Next is the famed ProctorU assessment. I got lucky and my proctor left me alone but YMMV. I've heard of some people getting their test paused because they looked at a wall. The code questions were 1 leetcode easy, 1 leetcode easy-medium, and 2 mediums. Not too bad overall if you've done your prep, overall slightly easier than some company's code interviews, if I were to rank, maybe a bit more difficult than Amazon's. Took me 2.5 hours. Can't run your code, but they're also not expecting 100% correct. I think pseudocode is ok. My solution was correct, but not 100% optimal, so there's leeway here. The onsite is super easy, mostly presentations/discussion. I talked with a developer about my prior internship project, had a quick discussion about how I would design something, and a final HR interview mostly discussing deadlines and that sort of thing. Very relaxed onsite, and the whole process was extremely smooth. They take very good care of you.
Perguntas de entrevista [1]
Pergunta 1
Something about well ordered numbers and additive sequences. They have a hard on for recursion.
Fiz uma entrevista na empresa 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.
Perguntas de entrevista [1]
Pergunta 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.