READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 70 of 153
Interview experiences · IMC
IMC Software Engineer interview with coding, system design, and team fit
The process was structured and felt comprehensive. After applying, I completed an online activity and then had an initial screening call. The technical portion moved into coding interviews where I could choose the programming language. The work combined problem-solving discussions with system design questions. There were also team fit and culture checks, along with a feedback step where they revi…
Interview experiences · IMC
IMC Software Engineer interview with graph and scheduling assessments
After I applied, I was asked to complete two online assessments, both focused on programming-style problem solving. One centered on graphs, and the other covered scheduling. A short time later, I moved to a one-way online interview with three questions. They were technical and focused heavily on how I think about programming languages and core data structures. The format was straightforward, but…
Interview experiences · IMC
IMC Software Engineer interview with no update after round two
After I got through the early stages, the process seemed to be moving normally. I completed what I believed was round two and waited for the next step. The silence afterward threw me off. I never received an official message saying that I hadn’t made it to round three. Instead, I was left to infer what had happened, with no real closure. The lack of communication made the experience drag on even…
Interview experiences · Impact Recruitment Group
Impact Recruitment Group Backend Engineer interview put on hold after onsite
I cleared the interviews, including an in-person technical round, but then waited about a month for an offer letter. After everything was finished, I was told the position was on hold. I found that disappointing because it felt political rather than practical. They had already taken my details, yet they did not reimburse my travel expenses. At least one technical interviewer also came across to m…
Interview experiences · Imperial College London
Imperial College London Research Analyst interview: presentation and competency discussion
The process felt rigorous but friendly. After the initial steps, I had a round with a presentation and a competency-style discussion led by two interviewers. They were personable and the mood was positive, even though the questions were clearly testing whether my background matched the role. The interview lasted about forty-five minutes. They asked a mix of competency and knowledge questions tied…
Interview experiences · Imperial College London
Imperial College London Research Analyst interview: presentation then panel questions
It took roughly three months after I applied to reach the interview. On the day, they covered my transportation to the venue. The session began with a presentation, and I had to communicate my key points quickly before the panel asked about my methods and the choices I had made. The whole interview lasted about forty minutes. I presented relevant work first, then the interviewers led the question…
Interview experiences · Indeed
Indeed Machine Learning Engineer Interview Experience — Indexing and Insertion in an Unrolled List
The author describes a tricky coding exercise from an Indeed virtual onsite involving a linked structure whose nodes each hold an array, an occupancy count, and a next-node reference. The first task was to retrieve an element using its position across the entire structure. The report discusses locating the relevant node and relates lookup cost to the number of nodes traversed. The second task add…
Interview experiences · Industry-Leading National Security Consultancy
Industry-Leading National Security Consultancy Software Engineer interview: core fundamentals
The interview leaned heavily on core engineering fundamentals. Data structures and algorithms were part of the technical work, but computer networks and operating systems came up too. The overall emphasis felt closer to cybersecurity-adjacent fundamentals. The DSA questions were medium difficulty. That mix changed the pacing for me: algorithm practice alone was not enough, because I also needed t…
Interview experiences · Industry-Leading National Security Consultancy
Industry-Leading National Security Consultancy Software Engineer Interview Experience: job description alignment
After a recruiter screening, I had a technical discussion and then a final HR round. The format was simple and professional, and it felt organized from the beginning. Across the rounds, the questions kept returning to my background and how I approached problem solving instead of trying to catch me off guard. The process took a long time and felt somewhat difficult as it built up. I came away with…
Interview experiences · Industry-Leading National Security Consultancy
Industry-Leading National Security Consultancy Software Engineer interview: logic test to onsite
I applied through Workday and chose an interview time after a recruiter reached out. The process began with an online step before moving to an onsite conversation. The initial round included a cognitive or logic test, followed by a Teams interview and then an in-person office interview. The people involved were connected to the department: a team lead or responsible person, HR, and sometimes addi…
Interview experiences · Industry-Leading National Security Consultancy
Industry-Leading National Security Consultancy Software Engineer interview: quick offer
The process was quick and simple: one behavioral interview of about 30 minutes. It felt easygoing, and I had time to ask questions instead of watching the conversation race by. An offer arrived about 15 minutes after the interview. The whole experience felt smooth, and I left with the impression that they were organized and responsive. Getting an offer almost immediately made this feel unusually…
Interview experiences · Infineon Technologies Americas
Infineon Technologies Americas Software Engineer interview experience: code snippets
After a recruiter stage, I had an online interview that began with introductions and an explanation of the role's work. The technical part was tied to the systems they actually use. I spent much of it explaining snippets from their codebase and talking through what the code did. The interview also covered analog-oriented subjects such as circuitry and filters, framed around my Computer Science ba…
Interview experiences · Infineon Technologies
Infineon Technologies Software Engineer interview experience: circuitry and codebase
The conversation started from my resume and then covered the day-to-day work of the role before becoming technical. The technical questions drew on analog fundamentals and circuitry, including filters. They framed those questions around the assumption that my study background aligned with computer science. Another technical portion focused on code from an existing codebase. Rather than discussing…
Interview experiences · Info Edge
Info Edge Software Engineer interview: DSA, Java, SQL, and design
After an HR touchpoint, I went through several structured rounds. The first technical round combined DSA, core Java, SQL, and my prior work. The next moved into low-level design and development concepts, with DevOps basics, cloud fundamentals, and more discussion of my experience. The manager round still included DSA, alongside behavioral questions. The difficulty felt average and the tone profes…
Interview experiences · Infosys (Finacle)
Infosys Finacle Consultant interview: projects, .NET and core software concepts
The process was challenging in a useful way and ended with an offer. I discussed my projects and answered .NET questions, along with object-oriented concepts, APIs and basic AI ideas. The interviewers wanted technical understanding and clear explanations of what I'd built and why. Those conversations helped me understand which points mattered most to the team and manager. I felt the interviews te…
Interview experiences · Infosys (Finacle)
Infosys Finacle Consultant interview: smooth process with one slow round
Most of the process felt smooth and organized. Once interviews began, I moved through technical discussions and HR and managerial conversations, and the offer side came quickly after the later steps. Scheduling the second round was the one part that took time. There was also an account of a different result: after several technical and HR rounds, there was no offer and a long period without much…
Interview experiences · Infosys (Finacle)
Infosys Finacle Consultant interview: technical depth, management and scenarios
The interviews felt smooth and well organized, and they gave me new ways to think about difficult situations. Different stages covered technical depth, management skills and how I'd respond to scenarios. The technical questions pushed me to reason beyond recalling facts. The managerial discussions focused on keeping a team effective and working efficiently when things became difficult. I received…
Interview experiences · Infosys (Finacle)
Infosys Finacle Consultant interview: virtual technical discussion and in-person HR
I had a couple of calm, straightforward rounds: a virtual technical interview and a separate face-to-face HR conversation. The smooth format made it easy to stay focused. The technical discussion covered topics relevant to the role, and I felt I had room to explain my answers. HR concentrated on fit. Results and feedback arrived quickly enough that the process didn't feel drawn out. I received an…
Interview experiences · Infosys (Finacle)
Infosys Finacle Full Stack Engineer interview: virtual technical round and waiting
The hiring process had a couple of stages and felt time-bound but structured. I began with a virtual interview that included technical and system-style questions. It was described as having a DSA segment, then follow-ups on Java with Spring Boot and system design. The interviewer also went deeply into my AI experience, making that part of my resume feel central. After the virtual stage, there was…
Interview experiences · Infosys (Finacle)
Infosys Finacle Software Engineer interview: a three-hour competitive-programming OA
The online assessment had four CP and DSA coding questions and took around three hours. It felt medium to hard, mainly because I had to stay consistent through a full block of problems. I then moved directly into an interview round with the same general tone. The questions were still tough, and they seemed to expect comfort with competitive-style problem solving, not only textbook DSA. The proces…
Interview experiences · Infosys (Finacle)
Infosys Finacle Software Engineer interview: assessments to onboarding
My process was straightforward: an online assessment, an in-person assessment, and then the final interview. It was organized and professional, and I appreciated that it did not drag on without a reason. In the combined technical and HR conversation, I introduced myself, explained my background and final-year project, and discussed my technical skills and software knowledge. HR asked about streng…
Interview experiences · Infosys (Finacle)
Infosys Finacle Software Engineer interview: broad technical and reasoning questions
My interview lasted more than an hour. It covered DSA, system design, computer science concepts, communication, puzzles, and teaser-style questions. The puzzles surprised me because they were not limited to coding or design; they tested how I thought with ambiguity. The conversation reached into math-leaning prompts, conceptual reasoning, and how clearly I could explain myself while solving. It f…
Interview experiences · Infosys (Finacle)
Infosys Finacle Software Engineer interview: calm core-subject and IoT discussion
The interview was calm and structured because the interviewer was friendly and patient. Questions began with basics and gradually went deeper through core subjects. It felt like they wanted to see whether I understood concepts rather than just repeat surface answers. I could connect my answers to projects and internships, explaining what I worked on and learned. My specialized branch also came up…
Interview experiences · Infosys (Finacle)
Infosys Finacle Software Engineer interview: Catia, AutoCAD, and thermal science
The interview opened with a self-introduction and resume questions. It then became heavily focused on core and skill-specific material from my area of study. I was asked about tools and software, including Catia and AutoCAD, before the conversation moved into thermal-science topics such as conventions, radiation laws, and heat-exchanger design. The interviewer was thorough. The detailed questions…