Ho presentato la mia candidatura tramite l'università. La procedura ha richiesto 3 settimane. Ho sostenuto un colloquio presso Epic (Madison, WI) nel mese di nov 2015
Colloquio
Applied online and got an e-mail to schedule a phone interview after 2 business days. Phone interview was about behavioral questions, like all others...nothing difficult. After the phone interview, you have to schedule an online technical assessment monitoring by ProctorU. This was rather painful because it lasted 3 hours. The technical assessment had 2 parts. In the first part, you have learned a weird new programming language and answer 20 multiple choice question. It was quite tricky because it's very different from the language you're used to. The more you're used to a language, the more likely you're going to make some careless mistake. The second part consists of 4 programming assignment, which was in somewhat okay difficulty. You can do it in any language you wish. Non-CS major can even do it in pseudocode. It was like taking a test. You can't compile your code so you don't whether it works and you can search for library and function syntax so you have to be good at a language. After that, they will fly you to an on-site interview. You talk about your project, hearing them brag about Epic, go through a case study (OOP design), and have lunch.
Domande di colloquio [1]
Domanda 1
Find an occurrence of a word in a NxN matrix and print it. It can be horizontal, vertical or diagnal.
Ho sostenuto un colloquio presso Epic (San Francisco, CA)
Colloquio
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.
Domande di colloquio [1]
Domanda 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.