Need help? Reach out to us
Back to library

Manufacturing, automobile and engineering

Legrand India Embedded Engineer Interview: Rounds, Questions and Preparation

For Embedded Engineer roles at companies like Legrand India

Share with friends

Preparing together? Send them this role's questions.

https://www.cynchrony.in/library/legrand-india-embedded-engineer

What the job involves

An Embedded Engineer in manufacturing, automobile, and engineering companies designs, develops, and tests firmware for microcontroller-based products such as smart switches, motor controllers, sensors, and industrial automation devices. The day-to-day work involves writing C code, debugging with oscilloscopes and logic analyzers, reading datasheets and schematics, and collaborating with hardware and testing teams to ensure reliable operation in harsh electrical environments.

Role and Technical Knowledge

  1. 1

    Explain the difference between a microcontroller and a microprocessor. Where would you use each in a manufacturing product?

    A strong answer highlights that microcontrollers have integrated peripherals and are used for dedicated control tasks like motor control or sensor reading, while microprocessors need external components and are used for high-compute tasks like HMI panels or gateways.

  2. 2

    What is the purpose of a watchdog timer in an embedded system? Give an example from an industrial or automotive application.

    Cover that it resets the system if the software hangs, and give an example like a motor controller that must not freeze during operation, or an automotive ECU that needs fail-safe recovery.

  3. 3

    How does an interrupt differ from polling? When would you choose one over the other in a real-time embedded product?

    Explain that interrupts are event-driven and save CPU cycles, while polling is simpler but wastes cycles. Choose interrupts for time-critical events like encoder pulses or UART receive, and polling for low-frequency status checks.

  4. 4

    Describe the I2C communication protocol. How would you debug a situation where an I2C sensor is not responding?

    Mention start/stop conditions, addressing, ACK/NACK, and clock stretching. For debugging, check pull-up resistors, bus voltage levels, device address, and use a logic analyzer to capture the waveform.

Practical Scenarios and Debugging

  1. 5

    Your embedded board resets randomly when a nearby motor turns on. How would you approach this problem?

    A strong answer considers electrical noise, inadequate decoupling capacitors, ground loops, and watchdog resets. Suggest checking power supply ripple with an oscilloscope, adding filtering, and reviewing PCB layout for noise coupling.

  2. 6

    You need to read an analog temperature sensor and send the data over UART every 100 ms. Outline your firmware structure.

    Cover using ADC with interrupt or DMA, a timer interrupt for the 100 ms period, and a UART transmit function. Mention avoiding blocking delays and ensuring data consistency.

  3. 7

    A device works fine on the bench but fails in the field after a few hours. What could be the cause and how would you investigate?

    Discuss thermal issues, memory leaks, stack overflow, power supply drift, and EMI. Suggest adding logging, using a debugger in situ, and testing over extended periods with environmental stress.

  4. 8

    How would you implement debouncing for a mechanical switch in firmware? Write a simple logic outline.

    Explain that you sample the switch at regular intervals (e.g., every 10 ms) and only accept a state change after it remains stable for a few consecutive samples. Mention using a timer interrupt or a simple counter.

Embedded C and Programming Concepts

  1. 9

    What is the difference between a macro and an inline function in C? Which would you prefer for register access in embedded code?

    Macros are textual replacements with no type checking, while inline functions are type-safe and debuggable. For register access, macros are common but inline functions with volatile pointers can be safer.

  2. 10

    Explain the use of the volatile keyword in embedded C. Give an example where omitting it causes a bug.

    volatile tells the compiler not to optimize away reads/writes, essential for hardware registers and variables modified by interrupts. Example: a flag set in an ISR and polled in main without volatile may never update.

  3. 11

    How do you manage memory in a microcontroller with only 2 KB of RAM? What techniques do you use to reduce RAM usage?

    Discuss static allocation, avoiding dynamic memory, using smaller data types, reusing buffers, and placing constant data in flash (const). Mention stack size monitoring and avoiding large local arrays.

  4. 12

    Write a C function to set, clear, and toggle a specific bit in a register without affecting other bits.

    Show using bitwise operators: set with OR (|=), clear with AND and NOT (&= ~), toggle with XOR (^=). Emphasize using a mask and not hardcoding the bit position.

Behavioural and HR Questions

  1. 13

    Tell me about a project where you had to learn a new microcontroller or tool quickly. How did you manage?

    Use the STAR method: describe the situation, the task, the actions you took (datasheets, online tutorials, small test programs), and the result. Highlight self-learning and persistence.

  2. 14

    Describe a time you faced a difficult bug in a team project. How did you handle it?

    Focus on systematic debugging, collaboration with teammates, and communication. Show that you stayed calm, used tools like logic analyzers or debuggers, and documented the solution.

  3. 15

    Why do you want to work in the manufacturing and automobile sector as an embedded engineer?

    Connect your interest to tangible products, reliability requirements, and the impact of embedded systems in automation and safety. Mention willingness to work in a lab or factory environment.

  4. 16

    Where do you see yourself in three years in this role?

    Show ambition to grow into a senior embedded engineer or technical lead, with deeper expertise in real-time systems, communication protocols, and product ownership. Emphasize continuous learning.

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 Legrand India or any other company has asked.