Contacted via Career Fair, interviewed via phone, standard. Asked by interviewer to confirm test scores, GPA and other numbers/internships/accomplishments on my resume. I actually found this really annoying since it's obviously true if I put it on my resume. If they don't have basic trust in me, why would I want to work for them. Then asked to explain projects on my resume. Got to next level easily, but was forced to take a 3-4 hour online proctored test...
I felt there was a complete lack of trust in the interviewee.
More information, the company has it's proprietary language it uses along with VB6 (who the hell uses this language any more), interviewer was evasive about the number of hours worked, and Madison, Wisconsin? It might as well be in the North Pole relative to the other tech centers.
Recommendation: Don't bother, much better companies around Seattle or the Bay Area chasing good CS majors. Especially out of school, this is a dead-end company with dead-end technologies.
1
Autres retours d’entretien d’embauche pour un poste comme Software Developer chez Epic
J'ai passé un entretien chez Epic (San Francisco, CA)
Entretien
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.
Questions d'entretien [1]
Question 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.
