Godrej Aerospace Embedded Engineer Interview: Rounds, Questions and Preparation

What the job involves

Embedded engineers in manufacturing and aerospace companies design, code, and test firmware that runs on microcontrollers inside machines, test rigs, and control systems. Day to day work includes writing C code, debugging hardware with oscilloscopes and logic analysers, and ensuring real time performance and reliability under strict quality standards. You may work on motor control, sensor interfaces, communication protocols, or safety critical subsystems for aircraft and industrial equipment.

Role and technical knowledge

1. 1

   Explain the difference between a microcontroller and a microprocessor. Where would you use each in an aerospace or manufacturing context?

   Cover integration (MCU has RAM, ROM, peripherals on chip), power, cost, and real time determinism. Give examples like using an MCU for a sensor node and a microprocessor for a complex flight computer.

2. 2

   What is the role of the volatile keyword in embedded C? Give a scenario where omitting it causes a bug.

   Explain that volatile tells the compiler the variable can change unexpectedly, such as a hardware register or a variable modified in an ISR. Mention that without it, the compiler may optimise away reads and cause stale data.

3. 3

   How does an interrupt work? What happens to the stack and program counter when an interrupt occurs?

   Describe the CPU finishing the current instruction, saving context (PC, registers) on the stack, jumping to the ISR, and restoring context on return. Mention the importance of keeping ISRs short.

4. 4

   What are the key differences between UART, SPI, and I2C? When would you choose one over the other for connecting sensors in a machine?

   Compare speed, number of wires, addressing, and multi master capability. For example, SPI for high speed short distance, I2C for multiple low speed sensors, UART for point to point communication.

Practical scenarios and debugging

1. 5

   Your embedded system resets randomly after running for a few hours. How would you debug this?

   Mention checking power supply noise, watchdog timer, stack overflow, memory corruption, and temperature effects. Suggest using a scope to monitor Vcc and a debugger to check for hard faults.

2. 6

   You need to read a temperature sensor every 10 ms and send data over CAN bus every 100 ms. How would you structure your code without an RTOS?

   Propose a timer based scheduler with flags, or a simple state machine. Explain using a hardware timer for the 10 ms tick and counting ticks for the 100 ms task, keeping ISRs minimal.

3. 7

   A motor controlled by your firmware starts vibrating at certain speeds. What could be the cause and how would you investigate?

   Consider control loop timing, PWM frequency, sensor feedback noise, and mechanical resonance. Suggest checking ADC sampling, PID tuning, and using a scope to look at the PWM and feedback signals.

4. 8

   How would you test a firmware update for a safety critical system before deploying it to the field?

   Mention unit tests, hardware in loop simulation, boundary tests, and long duration stress tests. Emphasise following a formal test plan and having a rollback mechanism.

Behavioural and teamwork

1. 9

   Tell me about a time you had to learn a new tool or technology quickly for a project. How did you approach it?

   Use STAR format. Show initiative, resourcefulness (datasheets, online forums, seniors), and a concrete outcome like finishing the project on time.

2. 10

   Describe a situation where your code had a bug that you could not find for hours. What did you do?

   Highlight systematic debugging, asking for help when stuck, and learning from the mistake. Show persistence and a methodical approach rather than panic.

3. 11

   In a manufacturing environment, deadlines and quality are both critical. How would you handle a situation where you are asked to skip a test to meet a deadline?

   Emphasise safety and quality first, especially in aerospace. Suggest communicating risks to the supervisor and finding a way to do a reduced but meaningful test, never skipping critical checks.

4. 12

   Why do you want to work in embedded systems in the manufacturing and aerospace sector, and what do you know about our company?

   Show genuine interest in hardware, real time systems, and reliability. Mention specific products or technologies the company works on, and connect your skills to their needs.

HR and career fit

1. 13

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

   Show a growth path from embedded engineer to senior or lead, with deeper expertise in real time systems or safety standards. Avoid saying you want to move to management too soon.

2. 14

   Are you comfortable working on site in a factory or lab environment, sometimes with strict safety protocols?

   Answer positively and give an example of hands on work from college projects or internships. Show awareness of safety and discipline in aerospace manufacturing.

3. 15

   How do you handle working under pressure when a production line is down and you need to fix firmware quickly?

   Describe staying calm, following a checklist, communicating clearly with the team, and prioritising a quick but safe fix. Mention documenting the issue for future prevention.