Open In App

DeltaX Interview Experience for Associate Product Engineer

Last Updated : 14 Sep, 2023
Improve
Improve
Like Article
Like
Save
Share
Report

I’m thrilled to share my interview experience with you as I successfully made it through the selection process for contributing to Geeks for Geeks. Here’s how it went:

Round 1: MCQ Round

  • The initial round was a multiple-choice question (MCQ) test covering topics such as Data Structures, Networking, Micro-Processors, and Operating Systems.
  • There were 50 questions to answer in a 45-minute time frame.
  • It’s crucial to note that there was no auto-submit feature, and no timer was visible, so keeping track of your time and aiming to submit within 40 minutes is advisable.

Note : During this round, both the microphone and camera were active. Avoid switching tabs as there was a tab counter, and incrementing it could result in rejection.

TIP: Cheating is discouraged since different candidates receive different sets of test questions. After submitting the test, remember to close the tab before proceeding to other tasks.

Out of 95 candidates, only 2 were selected for the next round.

Round 2: Coding Round

  • The second round was a coding challenge with a 2-hour time limit.
  • It consisted of 5 questions: 3 related to Data Structures and Algorithms (DSA) and 2 application-based questions.
  • Among the DSA questions, 2 were of medium difficulty, and 1 was considered hard.
  • Each question had its own time limit, and you couldn’t view the next question before completing the current one.
  • There were no hidden test cases, only one test was given to check your code, and submissions were done automatically at the end.
  • You couldn’t revisit previous questions, so be thorough and cover all edge cases.
  • The hard question involved finding unique combinations with a specified target sum.
  • The application-based questions included checking if an email is valid and converting a string into JSON format.

Note : During this round, only camera was active. Screen will be proctored.

Tip : My advice is not to spend too much time optimizing code, just write the correct code whatever is your time complexity and space complexity, correctness is paramount. I managed to solve 3 questions, including the challenging one, but couldn’t complete the JSON formatting due to a minor mistake. Pay attention to small details.

Round 3: Interview Round (Final Round)

  • In this round, I was the sole candidate interviewed by a friendly interviewer.
  • The interview began with introductions, and she asked me about my projects.
  • She then asked me to revisit the email validation question from the coding round on a shared, editable page, assessing my logical thinking and ability to apply instructions.
  • Next, she presented an encoding sequence question and requested a step-by-step code explanation. The interviewer was supportive and offered guidance.
  • I was asked to perform a dry run of my solution.
  • We discussed Object-Oriented Programming (OOP) concepts, focusing on encapsulation.
  • Then, she guided me through implementing an application using OOP principles, composition, constructors, and inheritance. The interviewer was interested in assessing my OOP knowledge.
  • The interview concluded with an opportunity for me to ask questions.

TIP : Try to be real, Focus on OOPS and your introduction. You must know common interview question and the way to answer them. Wear Formal . Get a nice comfortable place with clear background to sit.

Overall, it was a rigorous but rewarding interview process. The interviewers are supportive, and it’s essential to focus on understanding the problem and demonstrating your problem-solving abilities.


Like Article
Suggest improvement
Previous
Next
Share your thoughts in the comments

Similar Reads