READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 60 of 153
Interview experiences · Emma (UK)
Emma (UK) Marketing Analytics Specialist Interview Experience: fast screen and business case
I started with a quick first conversation of about 20 minutes, mostly to get to know each other. It worked as a fast screen to confirm that I was aligned before moving on. The second interview went deeper into my background and role fit. It also included a business case, so the process felt structured and practical instead of overly theoretical. The difficulty felt average, and the pace matched t…
Interview experiences · EPAM India
EPAM India QA Automation Engineer interview: technical breadth and delays
The recruiter call went well. After that, though, the process became a long wait. I heard nothing for about two weeks, followed up by email and LinkedIn, then waited another week for a reply saying the recruiter was waiting on the hiring team. I followed up again about a week later, and the technical interview was finally scheduled almost a month after the first call. That interview covered Java…
Interview experiences · EPAM India
EPAM India QA Engineer interview: Python automation and practical coding
After the recruiter call, I had a technical screen focused heavily on Python and automation thinking. I discussed lists, decorators, generators, and the difference between iterators and generators in real code. They asked about PyTest fixtures, then moved into automation framework design and how I would structure it end to end, including CI/CD pipeline considerations. The coding portion was pract…
Interview experiences · EPAM India
EPAM India Software Engineer conflicting-rounds interview experience
The process felt drawn out and wasteful. I had cleared two technical rounds, and HR scheduled a project interview. After that, HR told me I had cleared it and only needed a final managerial round. The managerial round felt disorganized. The manager did not seem to understand the project I was being considered for and asked questions that did not fit what I expected from the earlier stage. HR late…
Interview experiences · EPAM India
EPAM India Software Engineer interview: LRU cache, technical rounds, and canceled follow-up
My EPAM process was assessment-heavy. It started with an OA covering aptitude, OS, computer networks, and coding. Next came a pen-and-paper coding test in an auditorium, where I worked on an LRU cache problem. Then there was a group discussion where the evaluator let us choose the topic. After that came technical interviews on DSA, DBMS, OS, CN, and more coding, followed by HR. It was not one con…
Interview experiences · EPAM India
EPAM India Software Engineer interview: Spring Security, tracing and Python internals
After the recruiter stage, I had a technical interview of about ninety minutes that went deeply into Spring and distributed systems. I discussed Spring Data JPA, Kafka, Java 8 functional interfaces and Spring Boot. For microservices, I explained the architecture, how services communicate and how security works. JWT questions went into detail: what a token is, how a service validates it, what happ…
Interview experiences · EPAM India
EPAM India Software Engineer interview: technical assignment, stack questions, and project availability
My EPAM process began with a technical assignment rather than an immediate interview. I spent a lot of time on it, and after submitting successfully, an interview was scheduled. The process then became more typical: recruiter contact, a technical session, and a manager conversation. The technical content was mostly stack-aligned instead of unusual puzzles. I had linked-list questions, including b…
Interview experiences · EPAM India
EPAM India Software Engineer interview with Python deep dives and an unaccommodated emergency
My process stretched across many rounds and felt heavy from the start. I had several technical and client-facing sessions with professional interviewers, including positive feedback from one client discussion. I was surprised by how long the process took and how many people I spoke with. The difficulty came from deep-dive topics rather than basic problem solving. I got Python questions on slices,…
Interview experiences · EPAM India
EPAM India Software Engineer interview with Python, SQL, cloud, and system design rounds
The process started with a timed online assessment covering coding, programming, logic, and problem solving. After I cleared it, the recruiter moved me forward. The next stages were straightforward and reasonable. I first had an HR-style conversation where the interviewer was helpful and explained what the company wanted. The technical interviews matched my stack rather than relying on obscure Le…
Interview experiences · Epic Systems
Epic New Grad Software Engineer Interview Experience — Epic Just Switched OA Question Banks, Old One Is Useless
Epic's official guide has been updated — first a phone call with a colleague introducing the role, then an online technical assessment. It's completely different from the old question bank. I'm a new grad currently job hunting, sharing this in good faith. True/False/Cannot Determine — 5 min Each question gives 4-5 facts, and you judge 5 statements as true, false, or cannot be determined. Roughly…
Interview experiences · Epic
Epic Software Engineer, difficult assessment led to an offer
I started with a quick phone interview with an existing employee. It was mainly a fit check, and then I moved directly into scheduling an assessment. The assessment was genuinely hard, longer and more challenging than I expected, and it was the part that required the most effort. After finishing it, I made it far enough to receive an offer. I ultimately declined because a better opportunity came…
Interview experiences · Epic
Epic Software Engineer interview: assessment funnel with math, logic, and coding
I started with a basic phone interview about my resume and why I was interested in the role and company. After that, I completed an assessment with several parts: a personality section, math and logic sections, and coding. Once I finished those, I had a longer final interview that combined a case study with behavioral questions. The final conversations felt fairly normal. They focused mostly on f…
Interview experiences · Epic
Epic Software Engineer Interview Experience — MIIS, Logic Puzzles, and Four Coding Tasks
Online Assessment Format Two minutes: Answer as many short logic/reasoning questions as possible. Twenty MIIS questions. Fifteen math/logic questions. Four programming questions. MIIS Questions MIIS arithmetic Calculate the value of 1 + 1 * 3 / 2 + 7. MIIS strings and type conversion Given A = "JOHN", B = "JANE", and C = "3DOES", find the value of 0.A + B + C - 3. Math / Logic Questions Coins Som…
Interview experiences · Epic
Epic Software Engineer interview with HR call and coding assessment
My process started with a phone call with HR. It had a resume and behavioral focus, with some discussion of my background and questions about how I think and present myself. After that, I completed an assessment test. That was clearly the hardest part. It wasn't described as a single coding-only challenge, but the coding section pushed me the most. The test had to be completed before or after the…
Interview experiences · Epic
Epic Software Engineer onsite: evolving patient-database design and backtracking
I started the day with an online video overview that lasted about forty-five minutes. It covered what Epic does and the software it provides. After that, I moved into one-on-one conversations with engineers. One was a lighter discussion where I could ask questions and hear about their experiences. The next engineer conversation was more technical and felt like a system design prompt that kept bui…
Interview experiences · Ernst & Young
Ernst & Young Consultant first interview nerves despite easy questions
In my first interview, panic took over. The questions were easy, but I blanked in the moment and could not respond the way I knew I could. The difficulty was not the problem. The pressure of being in the room was. I did not move forward. The experience showed me how quickly nerves can erase familiar knowledge, and the miss felt more about nerves than capability. Location: India. Overall feedback:…
Interview experiences · Ernst & Young
Ernst & Young Consultant interview: assessment delays and silence
After the initial recruiter step, I was asked early questions and told I would receive an evaluation afterward. Once I completed it, the process stalled for a long time. I reached out for an update and got silence back, which made the whole journey feel inefficient. Separately, I went through a longer, multi-stage path with video and a psychometric-style component. It never seemed to move much be…
Interview experiences · Ernst & Young
Ernst & Young Consultant interview: basic questions and brain teasers
The interviewers were kind, but the process felt a little unprepared. Most questions were the basic kind I expected early on. A few brain teasers appeared near the end, making the round less predictable and testing how I thought under light pressure. It was manageable rather than brutal, though somewhat scattered. I left wishing I had done a bit more live practice so the brain-teaser section woul…
Interview experiences · Ernst & Young
Ernst & Young Consultant interview: creative in-person stage
The process took a while, but the in-person stage was engaging and mentally stimulating rather than merely formal. I felt encouraged to think outside the box, with a strong emphasis on logic and creativity. It was demanding, but also fun in that sense. The manager interview afterward felt more tense. Some questions did not seem clearly framed, which made it hard to answer confidently because I wa…
Interview experiences · Ernst & Young
Ernst & Young Consultant interview: delayed evaluation response
My first step was a short recruiter phone call. It felt as though the questions were being read from a checklist, and I got very little context about the role or the rest of the process. I had to try to get clarity from the conversation itself. I completed an evaluation they sent afterward, then waited for months with no update. When a response finally came, it was a generic rejection. The long s…
Interview experiences · Ernst & Young
Ernst & Young Consultant interview: two rounds and an SAP implementation case
The process was short, with two distinct rounds: one online and the next in person. Both felt focused on fit, without much pressure from coding. In the first conversation, I walked through my resume and explained how my experience matched what they wanted. The second involved a case study about SAP implementations. My impression was that they wanted clear explanations of the fundamentals rather t…
Interview experiences · Ernst & Young U.S. LLP
Ernst & Young U.S. LLP Consultant first-interview nerves and blanking
My first interview was easy on paper, but I let nerves get the better of me. I panicked and blanked out even though the interviewer asked basic, straightforward questions. I could not answer them properly in the moment. The difficulty did not seem high, but my performance did not show what I knew. I left with the uncomfortable feeling that nerves, not a lack of understanding, had caused the probl…
Interview experiences · Ernst & Young U.S. LLP
Ernst & Young U.S. LLP Consultant interview: delayed HR rejection
My first step was a brief phone call with HR, and it felt mechanical. The interviewer seemed to be reading from a list, without giving me much detail about the role or what the rest of the process would involve. After that call, I heard nothing for months. When I finally received an email, it was a generic rejection with no real feedback. The interview did not feel technically difficult, but the…
Interview experiences · Ernst & Young U.S. LLP
Ernst & Young U.S. LLP Consultant interview: virtual assessment process
My process felt long and somewhat unfocused. I went through several stages, including a video-based step and an assessment, but neither seemed to take me far. Each one felt more like a formality than a route to a final decision. Although everything was virtual and involved several moving parts, it did not feel efficient. I did not receive an offer, and I remember thinking it could have moved fast…