Manufacturing, automobile and engineering
Havells India Embedded Engineer Interview: Rounds, Questions and Preparation
For Embedded Engineer roles at companies like Havells India
What the job involves
An embedded engineer in manufacturing, automobile, and engineering companies designs and maintains firmware for products such as motor controllers, smart meters, switchgear, and automotive ECUs. The day-to-day work involves writing C code for microcontrollers, debugging hardware with oscilloscopes and logic analyzers, and ensuring reliable operation in noisy industrial environments. You collaborate with hardware, testing, and quality teams to meet safety, EMC, and production standards.
Role and Technical Knowledge
- 1
Explain the difference between a microcontroller and a microprocessor. Which one would you use for a smart switch and why?
Cover integration of peripherals, cost, power consumption, and real-time constraints. A strong answer links the choice to the product's needs like GPIO, timers, and low power.
- 2
What is the difference between UART, SPI, and I2C? Give an example of where you would use each in an industrial product.
Mention speed, number of wires, multi-master capability, and typical use cases like EEPROM (I2C), display (SPI), and debug console (UART). Relate to sensors or memory in motor drives.
- 3
How do interrupts work in a microcontroller? What are the key points to remember when writing an ISR?
Explain vector table, priority, and latency. Emphasize keeping ISRs short, avoiding blocking calls, and using volatile for shared variables.
- 4
What is the purpose of a watchdog timer in an embedded system for a manufacturing environment?
Describe how it resets the system if firmware hangs, improving reliability in unattended industrial equipment. Mention windowed watchdogs and proper servicing.
Practical Scenarios and Debugging
- 5
Your embedded device resets randomly in the field. How would you debug this?
Outline a systematic approach: check power supply, brown-out, watchdog, stack overflow, and EMI. Mention using a scope, logging, and reviewing recent code changes.
- 6
You need to interface a new temperature sensor to an existing microcontroller. Walk through your steps from datasheet to working code.
Cover reading the datasheet for voltage levels, protocol, and timing; checking hardware connections; writing a driver; and testing with a known reference.
- 7
How would you reduce power consumption in a battery-operated sensor node for an industrial monitoring system?
Discuss sleep modes, disabling unused peripherals, lowering clock speed, and using interrupts to wake up. Mention duty cycling and choosing low-power components.
- 8
Explain how you would implement PWM to control a motor speed in a fan or pump. What parameters matter?
Describe timer configuration, frequency selection to avoid audible noise, duty cycle control, and dead-time for H-bridge drivers. Mention feedback from tachometer or current sensing.
Projects and Problem Solving
- 9
Describe your final-year project. What microcontroller did you use and what was the most challenging part?
Be specific about your role, the hardware and software stack, and a concrete problem you solved. Avoid vague descriptions; highlight debugging or optimization.
- 10
Have you ever used an RTOS? If yes, explain how you assigned priorities to tasks. If no, how would you structure a bare-metal program with multiple periodic tasks?
For RTOS, discuss rate-monotonic or priority-based scheduling and avoiding priority inversion. For bare-metal, mention a timer-based scheduler or state machine.
- 11
Tell me about a time your embedded code did not work as expected. How did you find the root cause?
Use the STAR method. Focus on your debugging process, tools used, and what you learned. Show persistence and methodical thinking.
- 12
How do you ensure your code is reliable and maintainable for a product that will be manufactured in thousands of units?
Mention coding standards like MISRA C, code reviews, unit testing, version control, and static analysis. Relate to safety and quality requirements in manufacturing.
Behavioural and HR Questions
- 13
Why do you want to work as an embedded engineer in the manufacturing and automobile sector?
Show genuine interest in physical products, reliability, and the impact of embedded systems in everyday appliances or vehicles. Connect to your projects or coursework.
- 14
Describe a time you worked in a team to complete a hardware or software project. What was your contribution?
Highlight collaboration, communication, and handling disagreements. Mention specific tools like Git or shared documentation.
- 15
How do you keep your technical skills updated? Give an example of something you learned recently.
Mention online courses, datasheets, open-source projects, or hobby electronics. Show curiosity and self-learning beyond the syllabus.
- 16
Where do you see yourself in three years in this role?
Align your growth with deepening embedded expertise, taking ownership of modules, and contributing to product quality. Avoid saying you want to move to management immediately.
Coding round
Embedded Engineer interviews usually include a coding round. Practise planning the solution out loud, then review code the AI writes from your plan, in Python, Java, C++, C or JavaScript.
Ready to try it for real?
Take a timed test or talk through a mock interview for this role, then see your scores.
This is practice material for Embedded Engineer roles, written with AI. It is not a list of questions Havells India or any other company has asked.