Skip to content

💼 Interview Experiences – Overview

⬅️ Back Over the years, I’ve appeared for interviews with multiple top-tier automotive companies for roles including Model-Based Development Engineer, Embedded Software Developer, and AUTOSAR Developer. These interviews were with both product-based companies and Tier-1 suppliers. This section shares those real-life interview experiences in a client-wise manner.

🧭 Typical Interview Flow

Most of the interviews I’ve attended follow a consistent structure, usually consisting of 2 to 3 technical rounds. Here's how they generally go:

1. 🗣️ Introduction & Company Briefing

The interviewer usually starts by asking me to introduce myself. Once that’s done, they explain the company background and details about the end client or project the role is associated with.

2. 💡 Technical Deep Dive

After introductions, we jump into technical discussions. The questions are typically tailored to the job description and role requirements.

  • They test your understanding of core topics like Simulink modeling, Stateflow logic, AUTOSAR architecture, TLC files, or Embedded C depending on the role.
  • Most importantly, they expect not just the right answer, but a confident explanation behind your answers.

3. 🤝 Attitude Over Perfection

Even if you’re unable to answer a few questions perfectly, what really matters is your confidence, problem-solving mindset, and clarity of thought. Interviewers often judge whether the candidate has the right attitude to learn and grow with the team.

If you can demonstrate that you're quick to understand, open to feedback, and curious, it leaves a strong impression — even more than perfect technical accuracy.

4. ❓ Questions From Your Side

At the end, they usually ask “Do you have any questions for us?”
Regardless of how the interview went, always ask for feedback on your performance. This helps you understand: - What went well - Where you lagged - What you need to improve

This section highlights the most commonly asked questions for both Level 1 (L1) and Level 2 (L2) technical interviews across companies in the automotive domain. These questions often assess:

  • Core understanding of Simulink blocks and behavior
  • Signal propagation and control flow
  • Model architecture and hierarchy (Libraries, Referenced Models)
  • Stateflow vs Simulink usage
  • Code generation optimization
  • Simulink requirement linking and traceability
  • Tool usage like Requirements Toolbox and Simulink Test

🧠 Typical L1 Topics:

  • Basic model creation, hierarchy, atomic vs virtual subsystems
  • Triggered and enabled subsystems
  • Understanding of sample time and solver settings
  • Bus creator, selector, switch/mux vs merge logic
  • Basics of Data Dictionary and initialization
  • Forward and backward traceability with Simulink Requirements

💡 Typical L2 Topics:

  • TLC customization questions
  • Handling model variants and configuration sets
  • Model referencing vs subsystem tradeoffs
  • Writing custom blocks with S-Function Builder
  • Configuring Polyspace for static analysis
  • Understanding and resolving MISRA C and other compliance issues
  • Linking Simulink Requirements and setting pass/fail criteria for test harness

✅ This section is designed to help prepare effectively for both beginner and mid-senior level technical discussions.

🔗 Client-wise Interview Logs

Here you’ll find my detailed interview experiences, categorized by company:

🧠 What You’ll Gain

  • Real technical questions from real interviews
  • Strategies to tackle interviews even when you’re unsure
  • Clarity on what recruiters are actually looking for
  • A mental framework to prepare with confidence and purpose

💬 Note: These experiences are based on my memory and personal reflection. Actual experiences may vary depending on team, region, and interview panel.