Cadence Interview Experience for Software Engineer (On-Campus)

Hello, I recently attended an interview with Cadence for the position of software engineer (Pune, India).

The interview’s difficulty level was pretty high but reasonable. Following interviews, there was the following:

Round 0: (Shortlisting of Resumes)
The CV is crucial to your selection at any company because first impressions are always lasting impressions. Due to the large number of candidates, the resumes were first shortlisted in accordance with the desired role and positions.

Round 1.1 : (Aptitude test plus coding test) 
There were 2 coding questions in addition to the 20 MCQs. MCQs were built on the robust foundational ideas of C++ and Java. Another novel concept for me was coding questions. As part of GFG practice, the coding questions were of medium difficulty. After this round, this round was continued with another round.

Round 1.2: (Face-to-face interrogation about the Round 1.1 answers)
Since I had never seen this before, I found this round to be a little unexpected. Each and every person from round 1.1 participated in a face-to-face interview in this round, which was based on the responses they provided during the coding and aptitude tests. In essence, each person was asked why they had responded in a certain way to a certain set of questions. In order to assist us understand the concepts better, they clarify the questions to us if we have answered them incorrectly.

Advice: Always answer questions in aptitude tests that you are 100% certain about, as giving incorrect answers can damage your selections for subsequent rounds.

Round 2: (Technical Interviews)
The person who made it through round one has asked to participate in this round.
All of our knowledge of the OOPS, DSA, DBMS, OS, and CPP languages was put to the test in this round. First, the interviewer asked simple questions, and then the difficulty of the questions gradually grew.

Here are some of the interview questions that were posed:

• Concerns about the projects’ restrictions listed on the résumé.
• Maximum and maximum salaries from a table of employees
• The oops pillar.
• what page fault and paging are.
• Describe segmentation.
• and a lot more queries about Core OS and SQL.

Students were shortlisted for the final round after this round.

Round 3: (Behavioral + HR round) 
For the students, this round was really laid back. Essentially, this was a casual conversational session. First, questions about our day, our experience today, and a bit about our family history were asked. Following that, we underwent behavior tests based on scenarios that could occur in the workplace. The candidate who demonstrated confidence in their responses and skill in handling situational interview questions was chosen and given the opportunity to pursue an internship.