Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso Epic
Colloquio
They started out with a quick phone interview where they ask you a few questions and tell you about the company, nothing super technical. The company has a penchant for grades and standardized test scores so they will ask for your gpa, unofficial transcript, and sat/act (and any other standardizes tests i.e. gre) scores. If they like you enough they will fly you, house you, feed you, and give you a chance to check out the city. Once you get there they will show you around headquarters. headquarters is really cool, all of the buildings are themed and they go all out. You'll learn about the companies software, have a 1 on 1 interview with a software engineer where you will discuss a project you did, take several tests on a computer, and have a closing interview with someone from hr who will ask you things like salary expectations and what not. Overall the process was enjoyable
Domande di colloquio [1]
Domanda 1
I'm not allowed to talk about this, but I will say that for all software engineering interviews regardless of the company you should know: dynamic programming, data structures, graph theory (i.e. dijkstra's algorithm, Kruskal's algorithm, etc.), divide and conquer algorithms, search algorithms, sorting algorithms, OOP, and time complexity. ESPECIALLY oop, data structures, and dynamic programming.
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.