Maruti Suzuki Interview Experience for Data Analyst Intern On-Campus
Interview Experience
Maruti Suzuki came with three rounds for Internship in my university. The rounds were generic to skills and problem solving and not focused only on Data analyst questions....
Full Details
Maruti Suzuki came with three rounds for Internship in my university. The rounds were generic to skills and problem solving and not focused only on Data analyst questions.
Round 1 [Resume Shortlisting] Mode: [Online] Description: Introduction: A total of around 40-50 students submitted their resume. They kept a criteria of a minimum 7 CGPA. Students having 7+ CGPA were shortlisted, they did not do screening on the basis of skills present in the resume. I was shortlisted with 23 others. Key point - Mentioning CGPA in the resume is a must sometimes.
Round 2 [Online Test] Mode: [Online] Duration: [1hr] Description: : The test was very lengthy and hectic. It was not only on CS skills but also general aptitude, psychometric, and English. There were 4 sections: Aptitude - Easy to medium level MCQ - Based on core fundamentals Psychometric English - The level of questions here was good, it was not just some basic English test, you need to be good in English to clear this with good marks. There were no Data Structure questions asked in this round. Overall Difficulty: Easy to mid easy. Preparation Tips: Prepare your core fundamentals of CS (OOPs, CN, DBMS, OS). Try INDIABIX for Aptitude. Many people failed this, I think because of the English section. I was shortlisted with 5 others. (I am no master in English, so you can say LUCK) Interviews were scheduled for two days later.
Round 3 [Technical] Mode: [Online] Interviewer(s): [Team lead with 5 yrs of experience] Duration: [45-50 mins] Description: Introduction: The interviewer introduced himself and then asked me to introduce myself. I started with my name and went on to briefly explain my projects. Technical Questions: List of the technical questions asked - Puzzles, DSA, projects, core fundamentals Question 1: He gave me a puzzle "How many maximum slices of a cake you can make if you can make exactly 4 slices." - It was easy for me as I knew the formula of ? cuts =(horizontal cut +1)∗(vertical cut +1) n cuts =(horizontal cut +1)∗(vertical cut +1), where horizontal =?/2horizontal = n /2 and vertical =?−?/2vertical = n − n /2. Then he asked me to defend my answer. Tip: I did not tell him about the formula and pretended like I am trying to think about it, I pre-calculated the answer then based on it I thought about the cuts. Question 2: He gave me a data structures question to solve, the question was easy. "You have a string, let's say s = "abcde", you need to convert it into a hash code, the hashing function would work like if s[0] = "a", and s[len(s)-1] = "e" you need to return "b3f", where the first and last characters are the next letters of s[0] and s[-1], and the length of the remaining string is 3." I solved this using the ASCII values. The interviewer was satisfied. Question 3: He started a discussion on my projects. All my projects were on development, I also included my internship which I did in my university on their ERP portal. He started asking questions about Angular.js as I used Angular in it: What is data binding? How do you transfer data from one component to another? I do not remember more about this. Question 4: He asked some questions on OOPs: Explain any one pillar of OOPs - I explained inheritance in detail. Why do we need OOPs? - I gave some demerits of sequential programming. He seemed to be satisfied. His last question to me was "I cannot see any Data Analyst or Scientist related projects in your resume, how will you fit in this role?" I got a little nervous on this, but I gave him some points of my PowerBI experience (I only knew the basics of it), and tried to convince him that I am open to learn in this role and really excited to join. He showed mixed feelings, but I think the last question was something he did not care much about, he wanted to check the general skills only. And all the interviews (6 people) went the same way, They asked questions on DA skills where the interviewee mentioned about it in their resume. Difficulty: I will rate the round as easy to mid easy. Preparation Tips: Prepare your problem solving, be thorough with your resume, fundamentals of CS, try puzzles on GFG, and have good speaking skills. Overall Experience Final
Outcome [Selected with 2 others] | Total of 3 people were selected for this role. Overall Difficulty: Mid easy Advice for Future Candidates: Focus Areas: [problem solving, Puzzles, fundamentals, English & speaking skills, aptitude]
About This Question
This is a candidate experience report from a maruti suzuki interview for a frontend role (intern level) during the oa round reported in 2024.
It covers the following topics: Strings, Sql .
Difficulty rating: Easy
More Maruti Suzuki Interview Questions
About Maruti Suzuki Interview Reports
This question was reported by a candidate who interviewed at Maruti Suzuki. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Maruti Suzuki are the higher-signal extractions to take from this report.
For broader preparation context, the Maruti Suzuki interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Maruti Suzuki reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Maruti Suzuki Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Maruti Suzuki reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.