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

      Circa
      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. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" e il relativo logo sono marchi registrati di Glassdoor LLC.

      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

      9 dic 2013
      Dipendente anonimo
      Madison, WI
      Offerta accettata
      Esperienza positiva
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura online. La procedura ha richiesto 4 settimane. Ho sostenuto un colloquio presso Epic (Madison, WI)

      Colloquio

      I applied online in late October, received an email a day later to schedule a phone interview. After the phone interview, I took a skills assessment through ProctorU a week later. Then I had an on-site interview 2 weeks later. All told, the process took 4 weeks, from application to offer. The phone interview is about an hour long chat with a current developer. Standard interview questions are asked; be prepared to talk about a few projects and your roles in them. After this, you'll talk about the culture at Epic, the benefits of working there (the guy I talked with emphasized the lack of cubicles and perks like the subsidized cafeteria), the typical software stack, and Madison, WI. The skills assessment is done on ProctorU. I had never taken a test using the service, but apparently it's common in certain universities for final exams and the like for online courses. When you're taking the test, you'll have another person monitoring you through a webcam looking for suspicious movement. Before the test starts, they will gain access to your computer and check your process list to close down any unnecessary programs (it irked me that they shut down Dropbox without even asking). They'll also ensure that your screen does not have any sticky notes on it, that your workspace is cleared, and so forth. They see your screen at all times. You're allowed a calculator and some scratch paper. The assessment consists of 4 parts, the first 3 are written about elsewhere (Glassdoor has annoying post limit which necessitated truncating this part). Final part is a four question programming test. This is pretty challenging; my biggest problem is that I often look at reference websites when writing code that uses standard libraries, and I had no such luxury for this test. As a result, much of what I wrote was pseudocode, as detailed as I could make it, and using real code when I could remember it. I also commented well and provide thoughts about time complexity and efficiency when appropriate. You can write in C, C++, Java, Python, etc. Javascript and other functional languages are unlisted if I recall correctly. You should have an excellent grasp on string manipulation and data structures (both standard and custom). I'd recommend working out some problems on Project Euler, as one question would resemble those sort of math-based programming challenges. I won't state the specific problems, since it is worth more to a programmer to prepare generally and to be able to solve these problems on the spot. They recommend to allow 2-3 hours to take the test, and this was pretty accurate for me. The first three sections fly by; I took 3 hours on the last section, however. It took five days for Epic to get back to me after the assessment. Along with selecting a date for the on-site interview, I had to also take a Rembrandt personality test which is short and easy. The on-site interview was actually the best part of the process. They covered my airfare and hotel room. You can choose to have dinner with some current employees and a few other candidates (Madison has excellent restaurants by the way, so I strongly recommend you do this!). I arrived at the Epic campus at 8 AM the next morning. There is software demo with a current developer, who will talk about their project, the impact Epic has in healthcare, and will answer any questions. This is in a group of about 8 candidates. This group splits off so that four candidates have a conversation with a project lead about working at Epic. After this, I met another developer and had an interview where I presented a project I had worked on and answered questions about implementation, challenges, etc. Following this was a case-study interview with yet another developer. They present a general problem to solve and you have to create the basic system to solve it. When you are doing this they are constantly asking questions about how your system will handle extreme/odd cases. This can get pretty stressful, I suppose, but any programmer should be able to prototype a system fairly quickly. The last person I met was my recruiter from HR who looked over my application, transcripts, and references, and asked me general questions like my strengths/weaknesses and what I was expecting in terms of salary, career growth, and so on. Be sure to know how much you are worth and ask accordingly! After this I had lunch, toured the campus, went home. I received an offer 1.5 weeks later. It is extremely competitive with other tech companies (the pay is basically equivalent to Google/Microsoft when considering the low cost of living in Madison) and with comprehensive benefits.
      89

      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

      Le migliori aziende per "stipendio e benefit" vicino a te

      avatar
      AnyVan
      4.0★Stipendio e benefit