Interview Experience – DeltaX (CTC : 7LPA) | Associate Production Engineer | On-Campus

deltax logo
deltax
Associate Production Engineernull
January 12, 20261 reads

Summary

I interviewed for the Associate Production Engineer role at DeltaX through an on-campus drive, successfully navigating four rounds including MCQs, coding, AI-based telephonic, and a personal interview, eventually being one of the two selected students.

Full Experience

🧪 Round 1 (MCQ Round)

  • The round was 45 minutes long and consisted of 50 MCQ questions from topics such as DBMS, Operating Systems, OOPS, and Pseudocode.
  • Out of 1385 students from my college, only 101 were shortlisted for the next round.

🧪 Round 2 (Coding Round)

  • This round was 2 hours long, but each of the five questions had an individual time limit.
  • We were not allowed to switch between questions once a question was started.
  • The questions were mainly based on arrays, strings, and hash maps.
  • One of the questions was Combination Sum II.

🧪 Round 3 (Telephonic Interview)

  • This was an AI-based interview, where the interviewer already had access to my resume.
  • The questions were primarily based on my projects and the skills mentioned in my resume.

🧪 Round 4 (Personal Interview)

  • This interview lasted for approximately 1 hour.
  • It started with a brief self-introduction, followed by an in-depth discussion of my projects.
  • I was then asked one DSA question based on Dynamic Programming, which was a variation of the 0/1 Knapsack problem.
  • Additionally, I was asked to design a database schema for Spotify, followed by several discussion questions on the design choices.

✅ Final Result

  • Only 2 students were selected from my college, and I was one of them.

Interview Questions (3)

Q1
Combination Sum II
Data Structures & AlgorithmsMedium

One of the coding questions was Combination Sum II.

Q2
0/1 Knapsack Problem Variation
Data Structures & AlgorithmsHard

I was asked a Dynamic Programming question, which was a variation of the 0/1 Knapsack problem.

Q3
Design Database Schema for Spotify
System Design

I was asked to design a database schema for Spotify, followed by several discussion questions on the design choices.

Discussion (0)

Share your thoughts and ask questions

Join the Discussion

Sign in with Google to share your thoughts and ask questions

No comments yet

Be the first to share your thoughts and start the discussion!