KPIT Campus Selection Process: 2026 Guide

KPIT’s campus selection splits into two distinct phases: a pre-campus online test on Mettl completed weeks before the drive date, and an on-campus round that starts with a second coding test.

Most IT and engineering companies run everything on a single drive day. KPIT’s staged model is designed so shortlisting happens before the company’s team travels to campus. Registered candidates take the online test from their college or home, and only the shortlisted pool meets the KPIT panel on visit day. That structure matters for preparation: you have a defined window to clear the pre-campus hurdles before the campus visit is even scheduled.

Two-Phase Architecture

The pre-campus phase and the campus visit phase are sequential, not parallel. The pre-campus phase opens two to three weeks before the scheduled visit.

Pre-campus phase (three components, all on Mettl):

• Online MCQ Test (90 marks, 100 minutes)
• Online Coding Test (2 programs, 60 minutes)
• Video Testimonial (3-minute upload, non-eliminatory)

Campus visit phase (all rounds eliminatory):

• Programming Test 2 (90 minutes)
• Group Discussion (conditional)
• Technical Interview (one or more rounds)
• HR Interview

Elimination in the pre-campus phase happens at the MCQ and coding test stages. The video testimonial is assessed but does not create an elimination cut. Once candidates pass the pre-campus phase, they receive a confirmation from the college placement officer with the campus visit schedule.

Pre-Campus Phase: Online MCQ, Coding Test, and Video Testimonial

All three pre-campus components run on Mercer Mettl, a web-proctored online test platform. Mettl uses webcam monitoring and a browser-lockdown mode for the MCQ and coding tests. You will need a stable internet connection, a working webcam, and a laptop or desktop (mobile browsers are not supported for proctored tests).

Online MCQ Test: Section Breakdown

The MCQ test is 90 marks across 100 minutes. The three sections and their question counts are:

Section	Questions	Focus areas
Aptitude	25	Quantitative reasoning, logical reasoning, data interpretation
Technical	40	Branch-specific: ECE/EEE or CSE/IT topics (see below)
Communication and Professional Skills	25	Reading comprehension, sentence correction, business writing

The aptitude section is broadly similar to standard campus test patterns: number series, percentages, time-speed-distance, syllogisms, and data tables. Accuracy matters more than speed here; the time allocation per question is generous.

The technical section is where branch matters. ECE and EEE students should prepare for digital electronics (combinational and sequential circuits, Boolean algebra), microprocessor architecture and instruction sets, Embedded C syntax and data types, and basic signal concepts. CSE and IT students should prepare for data structures (arrays, linked lists, trees, graphs), algorithm complexity, operating system concepts (scheduling, memory management, process synchronisation), DBMS (SQL queries, normalisation), and C/C++ programs.

The Communication and Professional Skills section tests written English and professional comprehension. KPIT develops software for global automotive clients, so this section is not cosmetic. Candidates who clear the technical section but stumble on communication routinely fall off the shortlist here.

For a section-by-section breakdown of what appears most in KPIT’s online test, including sample questions by topic, FACE Prep’s KPIT online test pattern and syllabus has the full reference.

Online Coding Test

The coding test runs separately from the MCQ test in the pre-campus phase. It is 60 minutes with two programming problems. Difficulty stays at a foundational level: array manipulation, string operations, and basic search and sort algorithms come up consistently. You are expected to submit working, compilable code, not a competitive-programming-style optimal solution. Language choices typically include C, C++, Java, and Python.

Two programs in 60 minutes leaves 30 minutes per problem. The practical advice: read both problems first, attempt the one you are more confident about, and leave at least 10 minutes on the other for partial implementation. A partial solution with correct logic earns partial credit on most Mettl configurations.

Video Testimonial

Before the campus visit date, each registered candidate must record a 3-minute video on a topic set by KPIT and upload it through Mettl. The topic is announced with a submission deadline. The video can be recorded on a mobile phone or camera. Mettl displays the acceptable format and file size on the upload page.

This round does not eliminate candidates. KPIT assesses it, but the shortlist from the pre-campus phase is driven by MCQ and coding test scores. That said, the video provides your first real communication sample to the panel. Keep the structure simple: roughly 30 seconds of introduction, 90 seconds on the assigned topic, and 60 seconds on why automotive software interests you and what you want to contribute. Rehearse it twice, not twenty times.

Campus Visit Phase: Second Coding Test, GD, and Interviews

The campus visit phase runs four rounds in sequence. Elimination happens at every round.

Programming Test 2

The second coding test is 90 minutes. Expect harder problems than the pre-campus coding test: two to three programs, with at least one requiring data-structure knowledge beyond basic arrays. KPIT’s focus on automotive software means they value code correctness and clarity. Some problems include constraints that reflect embedded-style requirements: fixed data sizes, defined output formats, or performance bounds.

Prepare by practising two-problem sets in timed windows. The jump from 60 to 90 minutes is not just a time extension; the problems are substantively harder. If you cleared the pre-campus coding test comfortably, add one medium-difficulty DSA problem to your daily practice routine in the weeks before the campus visit.

Group Discussion

The Group Discussion round is conditional. KPIT runs it when the shortlist after Programming Test 2 is larger than the interview panel can process. Topics are typically current affairs, automotive industry trends, or scenario-based discussions. If the shortlist is compact, GD is waived and candidates move directly to Technical Interview.

Preparation for GD: read automotive industry news (electrification trends, ADAS regulation, software-defined vehicles) so you can contribute domain-specific points, not just generic arguments. A candidate who can name one specific trend in electric vehicle software stands out in a GD pool.

Technical Interview

The Technical Interview is one or more rounds depending on the interviewer’s judgment. It is the highest-stakes round in the campus visit phase.

ECE and EEE candidates should prepare for embedded systems architecture, microcontroller peripherals, CAN and LIN bus protocols, and C programming. KPIT builds software for EV powertrain, ADAS, and AUTOSAR stacks, so interviewers ask about automotive domain concepts beyond textbook theory.

CSE and IT candidates should expect data structure and algorithm walkthroughs, OS internals (scheduling, memory, IPC), and at least one live coding problem. Interviewers ask you to explain your reasoning, not just produce an answer.

A common question across branches: “Tell me about a project you built.” This is not a social question. The interviewer wants to assess whether you have applied any of your technical knowledge to something working. A short, real project with a clear problem statement and a concrete output answers this better than a lengthy description of a theoretical assignment.

For the full list of KPIT’s technical and HR interview questions with prep guidance, FACE Prep’s KPIT technical and HR interview questions guide covers the patterns by branch.

HR Interview

The HR round is the final gate. KPIT’s HR questions focus on location flexibility (primary offices are in Pune, Bangalore, and Chennai), communication clarity, and stated career intent in the automotive software space. The question “why KPIT specifically, and not a generic IT company?” is standard. An answer grounded in one thing KPIT actually builds (AUTOSAR middleware, EV battery management software, ADAS perception pipelines) lands better than a generic “I want to work with a growing company” response.

Eligibility and Branch Guide

KPIT’s campus eligibility criteria have been consistent across recent drive seasons:

• Degree: B.E. / B.Tech in ECE, EEE, Instrumentation, CSE, or IT
• Academic record: 55% or equivalent CGPA throughout — 10th, 12th, and degree semesters
• Backlogs: No active backlogs at the time of registration or on the drive date
• Year gap: No gap year at any point in the academic career
• Batch: Final-year students only, for the batch graduating in the current placement season

Mechanical, Civil, Aerospace, and other non-electronics non-CS branches are not eligible for software and embedded engineering roles. If you are in an electronics branch but have a pending backlog, resolve it before the registration window opens. KPIT’s placement officers check both registration-time and drive-day eligibility.

Candidates register through a link shared by the college Training and Placement Officer. The link is not posted on public portals. If your college has an active KPIT tie-up, your placement cell will receive the registration details directly.

Prep Roadmap: Four Weeks to the Drive

Use the pre-campus timeline deliberately. A four-week plan from registration to campus visit:

Week 1: Aptitude and Communication Baseline

Work on quantitative aptitude: time-speed-distance, percentages, ratio and proportion, number series, and data interpretation. Aim for consistent accuracy on timed mock sections before moving on. Simultaneously, read one business-English passage per day and practise sentence-correction exercises. The Communication section on Mettl is not grammar-trivia; it is reading and editing under time pressure.

Week 2: Technical Depth by Branch

ECE and EEE students: revise digital electronics (combinational circuits, flip-flops, counters), microprocessor programming (8085 or ARM basics), Embedded C (pointers, memory layout, bitwise operations), and C programming at a systems level.

CSE and IT students: work through data structures (implement and trace arrays, linked lists, BSTs, and graphs from scratch), sort and search algorithms with complexity analysis, OS concepts (scheduling algorithms, deadlock, paging), and SQL query writing.

One coding problem per day, solved completely and reviewed for edge cases.

Week 3: Coding Practice and Video Submission

Practise two-problem coding sets in 60-minute windows. Simulate Mettl conditions: browser open, no IDE autocomplete, clock running. Record your video testimonial draft early in the week so you have time to refine it. Keep the structure tight: introduction, topical response, domain interest close.

Week 4: Interview Preparation

Practise technical interview questions by branch. For ECE: embedded protocols (CAN, UART, I2C), real-time operating system basics, and one walkthrough of a microcontroller project you have done or read about. For CSE: live DSA problem-solving with verbal explanation, OS internals questions, and DBMS queries on a sample schema.

Prepare a direct answer to the technical interview’s project question. If you do not have a deployed project, the gap is real but fixable in the weeks before the drive. A small script that solves a concrete problem (even a terminal tool that does one thing well) is worth more in an interview than three certificates.

The video testimonial round and the technical interview both signal the same thing: KPIT wants candidates who have shipped something, not just studied everything. If your project portfolio is thin, one focused build before the campus visit is your highest-value remaining prep. TinkerLLM lets you ship a working AI-adjacent project at ₹299, the kind of small completed build that answers the project question directly.