READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 43 of 153
Interview experiences · Cadence Design Systems
Cadence Design Systems Software Engineer CEO final round followed by ghosting
The process started promisingly and reached a final conversation with the CEO. Along the way, I felt the team was engaged and that I was a strong match. I was told directly that they really wanted to hire me. After the CEO meeting, everything went quiet. I was completely ghosted and did not hear anything for months. I did not receive an offer. The interviews had gone well, but the lack of closure…
Interview experiences · Cadence Design Systems
Cadence Design Systems Software Engineer interview experience: communication and reasoning
Scheduling moved quickly by email after I applied. The plan included two technical rounds and one behavioral round, with theory and coding-style questions mixed together. In practice, it felt more like a competency evaluation than a pure coding test. Later conversations put me with technical staff, HR, and directors one after another. The technical questions were mostly basic grounding, including…
Interview experiences · Cadence Design Systems
Cadence Design Systems Software Engineer Interview Experience: Memory management and C++ rounds
I started with a recruiter-style resume discussion and then moved quickly into several technical rounds. The first technical round went deep on memory management and pointer reasoning, with stack and queue problems about how data moves and is processed. The focus was on understanding mechanics, not only producing a final answer. The next technical round was more algorithmic and coding heavy. It i…
Interview experiences · Cadence Design Systems
Cadence Design Systems Software Engineer Interview Experience: senior-engineer rounds and a final panel presentation
After I applied, the process moved through multiple structured rounds. A recruiter started the conversation, followed soon by a hiring-manager discussion. The intervening rounds were with senior engineers, and the overall tone was more about the role and my background than trying to catch me with trick questions. The final round was not another one-on-one technical conversation. It was a panel pr…
Interview experiences · Cadence Design Systems
Cadence Design Systems Software Engineer onsite technical rounds
I went through an onsite process that was almost entirely technical. Two deep rounds covered core data structures and system design fundamentals. Each pushed me through complex algorithmic questions where the code needed to be clean, efficient, and well structured. The difficulty was clearly high. It was not enough to make something work; I had to present an organized and efficient solution from…
Interview experiences · Canonical
Canonical Software Engineer interview: Python, Docker, Linux, and Kubernetes rounds
I interviewed for the Software Engineer role through a long, executive-heavy process with multiple technical rounds. The questions covered Python, Docker, Linux, and Kubernetes, and I spoke with senior leaders and team leads. I didn't receive an offer. After all the stages and conversations, the final decision was described as a skills-set mismatch. Location: India. Overall feedback: Negative. Of…
Interview experiences · Canonical
Canonical Software Engineer interview spanning React, C++, Linux, and full-stack JavaScript
I interviewed for a Software Engineer role through a multi-interview, all-technical process. It moved from front-end topics into broader full-stack engineering, including Linux and open source. In the front-end interview, I was asked about React and general front-end topics. The systems and programming interview shifted to C++ and Linux. Another round covered full-stack development fundamentals i…
Interview experiences · Canonical
Canonical Software Engineer interview with a long written stage
I interviewed for a Software Engineer role, and the overall experience felt extremely punishing. It started with an unusually long, essay-style written stage, followed by aptitude and other tests, and ended with a slow or non-specific rejection. For the written interview, or long questionnaire, I answered extensive essay-style questions about my background. They often asked for school-related det…
Interview experiences · Canonical
Canonical Software Engineer interview with multiple assessments and late-stage rounds
I interviewed for the Software Engineer role through a drawn-out but structured process. I completed several assessments, followed by interviews covering coding, systems concepts, and behavioral collaboration. I started with a written-style screen, then completed logic and personality testing. The technical stages included long interview sessions, another technical segment later in the process, a…
Interview experiences · Canonical
Canonical Software Engineer interview with questionnaire and Python assessment
I interviewed for the Software Engineer role through a multi-assessment process that started with a long questionnaire and two tests, before any deeper technical discussion. I answered around 30 questionnaire questions. The first assessment was a non-standard test made up of different types of tasks. The second assessment focused on Python. I didn’t receive an offer. Early filtering leaned heavil…
Interview experiences · Canonical
Canonical Software Engineer interview: written and psychometric testing
I interviewed for the Software Engineer role through a straightforward screening process. First, I completed a written test by listing my achievements, then completed a psychometric assessment. If I had been shortlisted, I would have moved on to a one-on-one interview. I didn’t move forward. My takeaway was that the process depended heavily on scoring well in the written and psychometric tests. L…
Interview experiences · Canonical
Canonical Software Engineer online assessments with unclear follow-up
I interviewed for the Software Engineer role through a process that was quick to schedule but ultimately unclear. It involved questionnaires and online tests, followed by either an early decline, no follow-up, or a rejection with little explanation. I filled out a form-like application and completed a detailed written interview about my background and problem-solving. I also took an aptitude-styl…
Interview experiences · Canonical
Canonical Software Engineer technical rounds on Linux and open source
I interviewed for the Software Engineer role and went through a two-track technical process in the middle of a longer interview sequence. One track focused on architecture and engineering depth. The other covered Linux, open-source topics, and platform fundamentals. In the software architecture and engineering round, I was asked about architecture qualities, engineering methodologies, and how eng…
Interview experiences · Capgemini
Capgemini Business Analyst Interview Experience: Exam-like presentation process
The process had two exam-like stages. First came an hour of rapid competency questions, heavily focused on business-analysis knowledge. It touched my experience, but felt more like checking textbook expectations than a conversation. About two weeks later, I prepared and presented a client-style digital-product journey as though speaking directly to a client. They questioned me on that delivery fo…
Interview experiences · Capgemini
Capgemini Business Analyst interview: referral and on-campus routes
After a referral for a Business Analyst role, I moved quickly into a virtual interview. The panel asked about my resume, projects, internship, SQL, Power BI, and general business-analysis concepts. It felt a little off because they did not seem to have reviewed my resume carefully, so the questions did not always land as expected. I also went through an on-campus style route with two rounds: a te…
Interview experiences · Capgemini
Capgemini Consultant interview: pharmaceutical validation scenarios
I had a demanding, consulting-style process with two face-to-face rounds. Both interviewers were professional and interactive. They concentrated on technical expertise, problem solving, and my real project experience, going deep into the role instead of staying theoretical. The part I remember most was the scenario discussion around pharmaceutical validation and digital quality systems. They aske…
Interview experiences · Capgemini
Capgemini Consultant interview: quick multi-round background discussion
The process began with recruiter screening and continued with the hiring manager and team members. I discussed my experience, technical and behavioral topics, problem solving, and cultural fit. The sequence was organized enough that I always knew what stage I was in. Once it started, it moved quickly across several people and rounds. There was a strong emphasis on talking about myself, my backgro…
Interview experiences · Capgemini
Capgemini Consultant interview: SAP TRM and HR practicalities
After a recruiter stage, I had a technical screen followed by HR. The technical discussion focused on SAP TRM, its related business process, and questions about payments and repayments. The interviewer wanted to know whether my prior experience mapped to that module. The next conversation was resume driven and calmer. It included aptitude and logical-reasoning work with many memory-style question…
Interview experiences · Capgemini
Capgemini Consultant interview: technical, manager, and compensation rounds
I went through a clear three-round process. The first was a technical round where the interviewer asked direct questions to probe my technical knowledge. Then I had a manager round that focused much more on how I worked day to day, including process and work discussion, plus scenario questions about how I would handle real situations. The final step was an HR round covering compensation details,…
Interview experiences · Capgemini
Capgemini Software Engineer interview: business cases, Excel, and VBA
The process was concise: a recruiter phone screen, a technical conversation about a Java or React project, and a behavioral final round. Each stage lasted about half an hour, so it felt designed for quick decisions. The technical part relied on business-case questions and knowledge outside typical coding. I discussed basic Excel and Power BI, Excel and VBA, and how I handled business problems thr…
Interview experiences · Capgemini
Capgemini Software Engineer interview: fast project-based technical round
After a recruiter screen on basic requirements, notice period, and salary expectations, I had a short, fast technical interview. It covered core coding and problem-solving with some system-design concepts, and moved quickly enough that I had to keep my explanations crisp. I discussed a project, then answered design and implementation questions about challenges, technologies, and how the pieces wo…
Interview experiences · Capgemini
Capgemini Software Engineer interview: policy-based rejection
My process included technical interviews, document verification, background verification, and a final HR discussion. Those verification steps made the journey longer and more formal than ordinary interview back-and-forth. After clearing each stage, I expected a positive decision, but my candidature was rejected under hiring-policy criteria. I felt I had cleared the work in front of me, while the…
Interview experiences · Capgemini
Capgemini Software Engineer interview: selection without offer letter
I cleared technical rounds and then had an HR conversation about salary expectations. One stage was face to face, L1 and L2 were held on the same day, and HR confirmed that I had been selected. I was told to expect an offer letter within a few working days. More than a month passed without an offer letter. I called and messaged, but neither recruiting nor HR responded. The interviews themselves h…
Interview experiences · Capgemini
Capgemini Software Engineer interview: ServiceNow scenario troubleshooting
This was technical from start to finish, but unlike a generic software-engineer screen. It began on Microsoft Teams and focused on a specific toolset and real scenarios rather than theory. My questions centered on ServiceNow ITSM, scripting, and troubleshooting. Because the prompts were scenario-based, I had to work out the expected behavior rather than recite definitions. Some were long and not…