Skip to content

🔧 Kirloskar Interview Experience

⬅️ Back Role: System Engineer
Mode: Online
Rounds: 2 Technical + 1 HR

🧪 Technical Round 1: Fundamentals + Domain Awareness

Topics Touched: - System architecture understanding - Microcontroller basics - Engine control concepts - Requirement analysis

Sample Questions:

  1. How would you define a system requirement vs a software requirement?
    (They expected clarity in boundary understanding between system & software layers.)

  2. Explain how you would represent an engine ECU system using block or architecture diagrams.

  3. What’s your experience with 16-bit or 32-bit microcontrollers? Which ones have you worked with?

  4. What type of inputs and outputs would you expect in a typical engine control ECU?
    (They hinted at analog sensors, actuators, ignition systems, crank position, etc.)

  5. If given a high-level customer requirement, how would you convert it into a system-level requirement?
    (They expected you to describe how you'd decompose or refine a vague statement into something testable and implementable.)

  6. What tools have you used for writing and managing system requirements? (They were expecting knowledge of tools like DOORS, Jama, Polarion, etc.)

🔬 Technical Round 2: Problem Solving & System Integration

Topics Touched: - Real-world validation strategies - ECU functionality - Engine-related subsystems - Requirement traceability and change impact analysis

Sample Questions:

  1. Explain the key components involved in engine start/stop control and how a system engineer ensures safe operation.

  2. How would you test and validate whether a system-level requirement related to fuel injection timing is met?

  3. If a requirement is changed late in the development phase, how would you manage its impact across the system?

  4. What do you understand by ‘requirement traceability’? Why is it critical in automotive system development?

  5. You’re assigned to create system-level requirements for an ECU controlling engine RPM limits. What inputs do you need, and how would you approach writing that requirement?

  6. Have you worked with any simulation or modeling tools to validate engine ECU behavior before hardware is ready? (They were hinting at tools like Simulink, TargetLink, or virtual ECU setups.)

HR Round

  • General discussion about relocation and career goals.

📝 Final Notes:

  • These rounds focused heavily on how you think, define, and validate systems — especially in safety- and performance-critical domains like engine ECUs.
  • Familiarity with real-world engine components (TPS, MAP, crankshaft sensors) added extra weight.
  • Understanding how to write, trace, validate, and modify requirements showed maturity in system-level roles.
  • Very technical panel. Be confident with practical project exposure.