DEV Community

Yeshwanth Valishetti
Yeshwanth Valishetti

Posted on

My Deloitte Interview Experience: On-Campus Placement Drive 2024 (Product Engineering Analyst Role)

Introduction

I recently participated in the Deloitte On-Campus Placement Drive for the Product Engineering Analyst role, held in 2024. The offered package was 7.6 LPA, with a base salary of 6 LPA. Around 600 to 700 students applied for the position, and the entire process consisted of four intense rounds. Here’s my step-by-step experience with the preparation, interview rounds, and key takeaways.

Core Areas to Focus On:

  • DSA Concepts
  • SQL & NoSQL
  • Project Clarity
  • Behavioral Skills

Interview Rounds Breakdown

Round 1: Online Assessment

  • Format: MCQs and two coding questions
  • Difficulty: Easy
  • Topics: Logical reasoning, aptitude, and DSA (basic array and string problems) The coding problems were straightforward. I faced one problem based on array manipulation and another on basic string processing. After the results, only 60 students were shortlisted from the initial pool of 600–700.

Round 2: Group Discussion

  • Topic: “AI Replaces Humans”
  • Duration: 30 minutes
  • Group Size: 10 participants

This round tested our communication, teamwork, and leadership skills. I ensured that I contributed meaningfully to the discussion, while also listening to my teammates. After 15 minutes of group discussion, 38 candidates advanced to the next round.

*Round 3: Technical Interview
*

This round was heavily focused on the technical aspects of my resume and the skills I listed.
Key Questions:

  • Resume Walkthrough: I was asked to explain the key projects mentioned in my resume.
  • Project Discussion: I explained a full-stack MERN project, specifically about how I handled student data management and the overall application flow.
  • API Explanation: The interviewer asked me to define an API and how I would integrate one into my project.
  • Coding Problem: I was asked to identify the next number in the sequence: 5, 10, 35, 75, 195. This required logical reasoning and pattern recognition.
  • Database Query: I was asked to write a join query in SQL to fetch data from multiple tables.
  • OOP Concept: I was asked to explain inheritance and its real-world applications in Java.

Round 4: Behavioral Interview

The final round was aimed at
evaluating my soft skills and understanding my personality.
Key Questions:

  • Self-Introduction: I had to give a brief intro about myself.
  • Academic Performance: The interviewer asked why there was a difference between my intermediate and B.Tech scores.
  • Skills Discussion: I was tested on my problem-solving skills with questions like: — Find the first repeating character in a string. — Write a function to return character frequencies in a string, with a focus on characters appearing more than twice.
  • Project Impact: I was asked to explain the real-world implications of my projects.
  • Unique Qualities: The interviewer asked me to list three qualities that set me apart.
  • Confidence Level: I was asked if I felt confident about being selected when I entered the interview.
  • Future Goals: I had to describe where I see myself in five years.
  • Strengths and Weaknesses: The interviewer asked about my strengths and areas I need to improve. At the end, the interviewer gave me some advice: Avoid using AI-generated resumes and focus on keeping your resume authentic and concise.

*Final Verdict : Selected *

Postmark Image

Speedy emails, satisfied customers

Are delayed transactional emails costing you user satisfaction? Postmark delivers your emails almost instantly, keeping your customers happy and connected.

Sign up

Top comments (0)

Sentry image

See why 4M developers consider Sentry, “not bad.”

Fixing code doesn’t have to be the worst part of your day. Learn how Sentry can help.

Learn more

👋 Kindness is contagious

Discover a treasure trove of wisdom within this insightful piece, highly respected in the nurturing DEV Community enviroment. Developers, whether novice or expert, are encouraged to participate and add to our shared knowledge basin.

A simple "thank you" can illuminate someone's day. Express your appreciation in the comments section!

On DEV, sharing ideas smoothens our journey and strengthens our community ties. Learn something useful? Offering a quick thanks to the author is deeply appreciated.

Okay