EV interview questions
HR & Behavioural Questions for EV Jobs Interview Questions & Answers
Technical rounds get you shortlisted; HR and managerial rounds decide the offer. EV companies in India look for genuine interest in the industry, hands-on proof, safety mindset and the ability to work across teams. Use the STAR method (Situation, Task, Action, Result) and adapt these sample answers with your own projects and numbers.
18 questions · 11 for freshers · 7 for experienced · Asked for: All EV roles, Graduate Engineer Trainee, EV Technician, Engineer, Senior Engineer
eMobility Academy — HR & Behavioural Questions for EV Jobs interview questions
Q1.Tell me about yourself.
FresherKeep it to 60 to 90 seconds and structure it as present, past and future. For example: 'I am a final-year Electrical Engineering student from [college] in [city]. Over the last year I have focused on EV systems; I completed an EV battery and BMS programme and built a 48 V, 13S lithium-ion pack with a BMS that logs cell voltages over CAN. During my internship at [company] I helped test motor controllers on a dynamometer. I am now looking for a role in battery or BMS validation, where I can use this hands-on experience and grow into design.' Avoid repeating your resume line by line; pick the two or three points most relevant to the job, and end by connecting to the role.
Q2.Why do you want to work in the EV industry?
FresherShow specific, informed motivation, not generic environmental statements. A good answer connects personal interest, industry understanding and the role: 'India is one of the largest two- and three-wheeler markets in the world, and electrification there is happening at scale, supported by schemes like PM E-DRIVE and PLI for advanced cell chemistry. I enjoy work where electrical, software and mechanical engineering meet, and EVs need exactly that. I have already built [project], and I want to work on products that reach millions of users.' Mention something about the company: its products, a recent launch or its technology. Interviewers want to see you will stay in the industry, not use it as a stopgap.
Q3.Why do you want to join our company?
FresherResearch the company before the interview: its products, recent launches, manufacturing or R&D locations, technology choices (for example, in-house BMS or LFP cells), funding or market share news, and the team you would join. Then link it to your skills and goals: 'Your team designs its own battery packs and BMS in-house, and you have recently expanded production. I want to work where design and validation happen close together, and my pack-building project and AIS-156 knowledge match what this role needs.' Avoid answers about salary, brand name or location alone. Asking an informed question at the end, such as how the team validates thermal propagation, reinforces your interest.
Q4.Describe a project you are most proud of.
FresherPick a project with clear ownership and measurable results, and use STAR. Example: 'Situation: our college team was building an electric go-kart for a national competition. Task: I was responsible for the battery pack and BMS. Action: I calculated the 48 V, 2 kWh requirement from the track profile, selected 21700 cells, designed a 13S configuration, wrote firmware to read cell voltages and temperatures and send them over CAN, and set up thermal tests. Result: the pack completed the endurance event with maximum cell temperature under 45°C, and we finished in [position].' Be ready for deep technical follow-up on every number you mention, because interviewers will dig into your design choices.
Q5.Tell me about a time you failed or made a mistake.
ExperiencedChoose a genuine, technical mistake with a lesson, not a disguised strength. Example: 'In my previous role, I approved a firmware release for a motor controller after bench testing but without a full temperature sweep. In the field, some units showed over-current trips in cold mornings because a current sensor offset drifted at low temperature. I owned it, worked with the team to reproduce it in a climatic chamber within two days, added temperature compensation, and released a fix. I then added a cold and hot test step to our release checklist, which caught two more issues later.' The key is accountability, root-cause thinking and a lasting process improvement.
Q6.How do you prioritise safety when you are under pressure to deliver?
ExperiencedEV companies ask this because HV and battery work carry real risk. A strong answer: 'Safety steps are not optional, and I treat them as part of the task time, not extra time. When a delivery deadline is tight, I look for ways to save time elsewhere, like parallelising tests or asking for more resources, and I escalate early if the timeline is unrealistic. For example, when we were asked to ship a pack build before a customer demo, I refused to skip the insulation test and pre-charge verification, explained the risk to my manager, and we agreed to ship one fully tested pack on time instead of two untested ones.' Mention any HV safety training or certification you hold.
Q7.What do you know about the EV market in India?
FresherShow structured, current awareness. Segments: electric two-wheelers and three-wheelers make up most EV volumes, with e-rickshaws a large share; electric cars are growing from a small base; electric buses are scaling through government tenders. Players: two-wheelers include Ola Electric, TVS, Bajaj, Ather and Hero (Vida); cars include Tata, Mahindra, MG and Hyundai, with others entering. Policy: PM E-DRIVE supports EV adoption and charging, PLI schemes support advanced cell chemistry and auto components, and AIS-156 tightened battery safety. Challenges: charging availability, cell import dependence, cost, and service networks. Quote recent figures only if you are sure of them; interviewers value accuracy over impressive-sounding numbers.
Q8.Where do you see yourself in five years?
FresherShow ambition aligned with the company, not a plan to leave. Example: 'In five years I want to be a strong battery systems engineer who can own a pack design end to end, from cell selection to validation and homologation. In the first two years I want to build depth in testing and BMS, then take ownership of a subsystem and mentor juniors. I would like to grow here, since your team does design and validation in-house.' If you are interested in management or a specialist track, say so honestly. Avoid saying you plan to do an MBA or move abroad unless it is genuinely relevant and you can link it to the role.
Q9.Are you willing to relocate or work in a plant or field role?
FresherMany EV jobs in India are at manufacturing plants and R&D centres in places like Pune, Chennai, Hosur, Bengaluru, NCR and Gujarat, or involve field travel for service and charging roles. Answer honestly. If you are flexible: 'Yes, I am open to relocating. I understand plant and field exposure is valuable early in a career because you see how designs work in real production and use.' If you have constraints, state them clearly with what you can offer: 'I prefer [city] for family reasons, but I am open to travel for commissioning and field trials.' Saying yes and then declining after an offer damages your reputation with recruiters, who talk to each other in a small industry.
Q10.What are your salary expectations?
ExperiencedResearch the market range for the role, city and experience level using career-path guides, peers and recruiters; for example, our career paths pages list typical bands. Give a range anchored on your current CTC and the role, not a single figure: 'Based on my four years in BMS validation and the scope of this role, I am looking for [X to Y] LPA, but I am open to discussing the full package, including variable pay and benefits.' For freshers, it is usually fine to say you are flexible and expect the company's standard package for the role. Know your current fixed and variable split and notice period, and be honest; offers are often verified against payslips.
Q11.How do you keep your technical skills up to date?
FresherGive concrete habits, not just 'I read online'. For example: 'I follow BIS and ARAI updates on standards like AIS-156 and IS 17017, read application notes from TI and ADI on BMS and motor control, take structured courses with hands-on kits, and work on side projects such as a CAN logger or SoC estimator in MATLAB. I also follow industry news on Indian EV launches and policy, and attend webinars and events like EV-focused expos.' Mention one recent thing you learned and applied, for example how you implemented a Kalman filter after studying it. Showing a learning loop of study, building and testing matters more than a long list of sources.
Q12.How do you handle disagreements with a teammate or another department?
ExperiencedEV programmes need tight cooperation between battery, motor, software, mechanical, quality and manufacturing teams, so interviewers want evidence you resolve conflict with data. Example: 'Our mechanical team wanted to reduce the pack's cooling plate thickness to save weight, and my thermal analysis showed cell temperatures would exceed limits during fast charging. Instead of arguing, I set up a joint review, shared the simulation and test data, and proposed a compromise: a thinner plate with improved thermal interface material. We tested both options, the compromise met both targets, and it was adopted.' Highlight listening first, focusing on shared goals and escalating only with clear options.
Q13.Tell me about a time you solved a difficult technical problem.
ExperiencedUse STAR and show structured troubleshooting. Example: 'A batch of fleet scooters showed random power cut-outs. Task: find the root cause within a week. Action: I collected controller and BMS logs from affected vehicles, noticed the cut-outs coincided with a 12 V supply dip, reproduced it on a bench by simulating the dip, and traced it to a DC-DC converter that could not handle a headlamp inrush at low temperature. We changed the converter's soft-start and added a capacitor. Result: cut-out complaints fell to zero over the next two months across [N] vehicles.' Interviewers look for data collection, hypothesis testing, reproduction, fix verification and prevention.
Q14.Why should we hire a fresher like you over someone with experience?
FresherBe confident without dismissing experienced candidates. Example: 'I bring strong fundamentals and hands-on proof: I built a [project], I am comfortable with tools like MATLAB, CANoe or a CAN analyser, and I completed HV safety training. I learn fast, and I am ready to start with testing, documentation and production support to understand your products deeply. A fresher also brings energy and fewer fixed habits, so I can adopt your processes and standards from day one.' Link your skills to the job description, and back each claim with something you can show, such as a GitHub repository, project report, certificate or demo video.
Q15.Do you have any questions for us?
FresherAlways ask two or three thoughtful questions; saying no signals low interest. Good options: 'What would success look like in the first six months in this role?', 'How is the team split between design, validation and field support?', 'What test facilities do you have in-house, and what is done at ARAI or ICAT?', 'What are the biggest technical challenges the team is working on this year?', 'What training or certification support do new engineers get?'. Avoid asking about leave or salary in the first technical round unless the interviewer brings it up. Questions about the product roadmap or standards compliance show you are already thinking like a team member.
Q16.What is your notice period and can you join early?
ExperiencedBe precise and honest. State your contractual notice period (commonly 30, 60 or 90 days in Indian companies), whether it can be bought out, and your realistic joining date. For example: 'My notice period is 60 days. I can request early release after handing over my current project, and I have discussed this with my manager informally, so 30 to 45 days is realistic.' Do not promise an early date you cannot deliver. If you hold other offers, it is acceptable to say so professionally, but avoid using them as pressure unless you are genuinely ready to decide. Recruiters remember candidates who joined when they said they would.
Q17.How would you explain a technical issue to a non-technical customer?
FresherService and sales roles need this skill daily. Use simple language, an analogy and a clear next step. Example for a range complaint: 'Your battery is healthy. Range depends on how the car is used, just like mileage in a petrol car depends on traffic and AC use. At 110 km/h on the highway with AC on, the car uses much more energy than in the test conditions used for the brochure figure. If you keep around 80 to 90 km/h, you will see about [X] km. I have also checked your tyre pressure and updated the software.' Avoid jargon such as SoH or Wh/km unless the customer is interested, listen to their concern fully, and confirm they are satisfied before closing.
Q18.How do you approach working on something outside your expertise?
ExperiencedEV teams are small and cross-functional, so engineers often stretch beyond their training. Describe a method: 'I first clarify what is needed and by when, then quickly build a working understanding from standards, application notes and internal documents, and identify an expert I can check with. For example, as a BMS firmware engineer I was asked to support OCPP integration for a charger project. I read the OCPP 1.6J specification, built a simple test setup with an open-source central system, and paired with the backend team. Within three weeks the charger was passing interoperability tests.' This shows humility, speed and ownership.
More free EV career resources: emobility.academy/career-resources
Turn this into a career
Learn EV engineering hands-on
Courses with DIY hardware kits, live classes, lab practice and placement support — AICTE NEAT 2.0 and ASDC aligned.