MultiCoreware Interview Experience

Last Updated : 11 Oct, 2024

Recently, I appeared for an interview at Multicoreware for the position of Software Engineer. The process was comprehensive and involved multiple rounds designed to test different skill sets.

Round 1: Aptitude Test

The first round was an Aptitude Test consisting of logical and quantitative questions. This round was aimed at evaluating problem-solving abilities, and it served as the initial screening phase for candidates.

Round 2: Coding Round

In the second round, I was presented with a coding challenge that included three programming problems to be solved within 85 minutes. I successfully completed all three problems in 60 minutes. The difficulty of the coding questions ranged from easy to medium, and passing this round secured my invitation for the technical interviews.

Round 3: First Technical Interview

The first technical interview lasted approximately two hours and covered both my project work and core technical knowledge, especially focusing on C programming.

  • Introduction & Projects: The interview began with an introduction and a detailed discussion of my major projects, highlighting the technical challenges I faced and the solutions I implemented.
  • C Programming:
    • The interviewer delved into my understanding of pointers and dynamic memory allocation, with questions on malloc, calloc, and free functions.
    • I was also asked to analyze pseudocode involving unsigned pointers and predict the output.
  • Coding Questions:
    1. Reverse a Linked List: I had to write code to reverse a linked list, testing my understanding of data structures.
    2. String Search: I was given a sentence and a word, and I had to determine if the word existed in the sentence and return the memory location of the word.

Round 4: Second Technical Interview

After clearing the first technical round, I moved on to the second technical interview, which lasted around 90 minutes. This round focused on data structures, algorithms, and object-oriented programming (OOP) concepts.

  • Introduction & Projects: The interview once again began with an introduction and a discussion about my projects. The interviewer was keen to understand the complexity of the tasks I had undertaken and the technologies I had used.
  • Data Structures & Algorithms:
    • I was asked how to reach the end of a linked list quickly and how to copy a linked list, returning a new one pointing to the head.
  • OOP Concepts:
    • The interviewer tested my knowledge of key OOP principles such as function overloading, function overriding, polymorphism, and inheritance.
    • The focus shifted to C++, with questions on C++ functions and object-oriented concepts.

Conclusion

Although I successfully answered the majority of the questions, I received a regret email from the company. While I didn’t secure the position, the interview process was an enriching experience. It gave me valuable insights into areas where I can improve and helped me identify key focus areas for future opportunities.

Comment