Passa al contenutoPassa al piè di pagina
  • Lavori
  • Aziende
  • Stipendi
  • Per le aziende

      Migliora la tua carriera

      Scopri le tue potenzialità di guadagno, trova lavori da sogno e condividi approfondimenti su lavoro e vita privata in forma anonima.

      employer cover photo
      employer logo
      employer logo

      Epic

      Azienda coinvolta

      Chi siamo
      Recensioni
      Stipendi e benefit
      Lavori
      Colloqui
      Colloqui
      Ricerche correlate: Recensioni su Epic | Offerte di lavoro di Epic | Stipendi di Epic | Benefit di Epic
      Colloqui di EpicColloqui per Software Developer presso EpicColloquio di Epic


      Glassdoor

      • Chi siamo
      • Contattaci

      Aziende

      • Account Business gratuito
      • Spazio per le aziende
      • Blog per le aziende

      Informazioni

      • Aiuto
      • Linee guida
      • Condizioni d'uso
      • Privacy e scelte pubblicitarie
      • Non vendere né condividere le mie informazioni
      • Strumento per l'accettazione dei cookie

      Lavora con noi

      • Inserzionisti
      • Carriere
      Scarica l'app

      • Cerca:
      • Aziende
      • Lavori
      • Località

      Copyright © 2008-2026. Indeed, Inc. "Glassdoor," "Worklife Pro," "Bowls" e il relativo logo sono marchi registrati di Indeed, Inc.

      Aziende seguite

      Non lasciarti sfuggire opportunità e informazioni privilegiate seguendo le aziende dove vorresti lavorare.

      Ricerche di lavoro

      Ricevi suggerimenti e aggiornamenti personalizzati avviando le tue ricerche.

      Colloquio per Software Developer

      19 mar 2019
      Dipendente anonimo
      Verona, WI
      Offerta accettata
      Esperienza positiva
      Colloquio difficile

      Candidatura

      Ho presentato la mia candidatura online. La procedura ha richiesto 3 settimane. Ho sostenuto un colloquio presso Epic (Verona, WI) nel mese di feb 2019

      Colloquio

      After applying, I got contacted within one or two days about scheduling a phone interview. The phone interview was pretty standard, and since the details were so thoroughly documented on Glassdoor and other forums, I was able to have detailed, relevant, and rehearsed answers prepared for all the questions thrown at me. All in all, pretty low stress and the guy I talked to was very kind, patient, and helpful in getting my own questions answered. The skills interview was probably the most terrifying and stressful part of the process. You will be required to download and run a program that proctors you and prevents you from using outside resources (locking the test + webcam to make sure you don't leave in the middle of a part). There were three parts in total, a timed assessment, a multiple choice section, and a coding section. The timed assessment is a collection of short questions that are relatively easy to answer, but you only have a couple of minutes to answer them all. The idea is speed, get through as many as you can before your time is up. If you're decently fast, completing them all is not incredibly difficult, I didn't because I forgot I had a calculator. The big part is the one about coding. There are a few questions that are essentially coding prompts. You are allowed to code in Java, C++, C, and I think a couple of others, but you do not have access to an IDE, it's essentially just a text editor. Brushing up on CS basics like recursion and data structures as well as practicing practice interview code questions online are great resources to you in preparing for this one. It's definitely the hardest part and the biggest time sink of the three. The last part is a multiple choice quiz; there are several questions that are basically general problem-solving MC mostly pertaining to coding with very little actual coding, nothing to be stressed over. The in-person interview was my favorite part of the process as you get to come to the Epic campus in Verona for nearly a full day (5 hours). I can't comment on the travel process since I'm local, but I do know they pay for most if not all your travel expenses including a plane ticket and hotel as well as taxi to and from the campus itself. It's a day long ordeal, with the morning being filled with very cool and low-stress activities pertaining to learning all about Epic. This includes demos of their products (incredibly cool, by the way), chatting with a dev team member and picking their brains about their work and workflow, and a tour of Epic's campus. If you haven't seen it before, just know it's like a three-way cross between Disney World, a modern tech campus, and a garden park; absolutely stunning and probably worth going through the entire interview process just to get a ticket to come see it. Lunch is provided by Epic. The afternoon is where the actual interviewing comes in. There will be three parts, all of them one-on-one. The first was a conversation about a project you worked on. The interviewer will ask lots of questions pertaining to the process of the project, your algorithms, and what you might do to improve it. This part might require a lot of work on your part to dig up an old project and memorize how you made it, why and how you made it work the way it does, and what improvements you might make to it or the process, but if you're passionate about a project it should be a cinch. The second part was a case study. The interviewer gives a specific scenario to you and you have to come up with a solution (you have a whiteboard to help you). This doesn't need to be pseudo code, just whatever helps you and the interviewer visualize the solution. The interviewer is very interactive, pointing out edge cases and other kinks in your ideas as well as encouraging you and providing hints. The last interview was a standard interview for the most part. If you've practiced other interviews, you'll likely also be prepared for this one. Essentially, it's the phone interview part two; if you prepared any questions for the phone interview that they didn't ask already, chances are this is where it'll happen. If you can survive the food coma after lunch and have prepared well, the day is very enjoyable. Epic's interviewers and other employees are magnanimous throughout the whole process, answering all your questions and being incredibly kind and courteous.

      Domande di colloquio [1]

      Domanda 1

      Tell me about a project you've completed in the past, how it works, how you made it, and things you might improve about it.
      Rispondi alla domanda
      4

      Altre recensioni di colloqui per Software Developer presso Epic

      Colloquio per Software Engineer

      2 giu 2026
      Dipendente anonimo
      San Francisco, CA
      Offerta accettata
      Esperienza neutra
      Colloquio nella media

      Candidatura

      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?
      Rispondi alla domanda

      Colloquio per Software Developer

      29 mag 2026
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza neutra
      Colloquio facile

      Candidatura

      Ho sostenuto un colloquio presso Epic

      Colloquio

      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.

      Domande di colloquio [1]

      Domanda 1

      Tell me about a project you've worked on
      Rispondi alla domanda

      Colloquio per Software Developer

      29 mag 2026
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza neutra
      Colloquio facile

      Candidatura

      Ho sostenuto un colloquio presso Epic

      Colloquio

      [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.

      Domande di colloquio [1]

      Domanda 1

      Why [your school]? Why Epic?
      Rispondi alla domanda