Controller Modelling Developer – Virtual Prototyping at General Motors

📍 Job Overview

Job Title: Controller Modelling Developer – Virtual Prototyping

Company: General Motors

Location: Markham, Ontario, Canada

Job Type: FULL_TIME

Category: Automotive Software Engineering / Virtual Prototyping

Date Posted: 2025-06-11T00:00:00

Experience Level: 10+ years

Remote Status: Hybrid

🎨 Role Summary

Develop and integrate Level 4 Virtual ECUs (vECUs) using SystemC TLM 2.0 models for real-time virtual prototyping of embedded control systems in the automotive domain.
Create sophisticated SystemC TLM2.0 models for microcontrollers, ASICs, drivers, and various peripherals crucial for automotive electronic control units.
Collaborate extensively with Design Release Engineers, Tier 1 suppliers, and software engineers to build and validate vECUs, ensuring they accurately execute unmodified production code.
Support the integration of vECUs into complex virtual validation environments, enabling early-stage software development and testing without physical hardware.

📝 Enhancement Note: This role, while deeply technical in software and modeling, is critical to the design and validation lifecycle of automotive embedded systems. The ability to understand hardware architecture and translate it into functional virtual models directly impacts the efficiency and quality of the overall vehicle design process, particularly in software-defined vehicles. The emphasis on SystemC and TLM 2.0 highlights a focus on high-level abstraction for performance in simulation, which is a key design consideration in virtual prototyping.

🖼️ Primary Responsibilities

Design, implement, and validate SystemC TLM2.0 models for a wide range of automotive microcontroller components and peripherals, including timers, switches, and transceivers, ensuring accuracy and performance.
Perform comprehensive integration of newly developed microcontroller and peripheral models into complete Level 4 virtual ECUs, managing complex dependencies and configurations.
Conduct rigorous debugging of both individual models and integrated vECUs to identify and resolve functional issues, performance bottlenecks, and integration conflicts.
Engage in cross-functional collaboration with hardware engineers, software developers, and external suppliers to align model development with physical ECU specifications and software requirements.
Integrate production-level embedded software into vECUs, ensuring seamless execution and accurate representation of real-world behavior.
Develop and execute validation and verification strategies for vECUs to confirm they meet functional requirements and execute production software as intended, using co-simulation techniques.
Collaborate with software development teams to diagnose and resolve low-level software and application issues within the virtual environment, providing expert insight into vECU behavior.
Create and maintain script-based workarounds and test harnesses to address virtual model limitations and facilitate efficient testing and debugging cycles.
Support Simulation Integration Engineers by providing robust and well-documented vECUs for integration into larger virtual vehicle environments, ensuring compatibility and performance.

📝 Enhancement Note: The responsibilities clearly indicate a role that bridges hardware and software, requiring a deep understanding of both embedded systems and virtual modeling. The emphasis on debugging and cross-functional collaboration is crucial in a complex automotive development environment. The need to integrate production code into virtual environments underscores the criticality of accurate modeling for early validation in the design process.

🎓 Skills & Qualifications

Education: While not strictly required, a Bachelor’s or Master’s degree in Electrical Engineering, Computer Engineering, Software Engineering, Computer Science, or a similar field is preferred and provides a strong foundation for understanding embedded systems and software development relevant to virtual prototyping. Equivalent practical experience demonstrating deep technical knowledge is also valued.

Experience: A minimum of 10+ years of relevant professional engineering experience is required, with a significant portion focused on embedded systems, microcontroller modeling, and virtual prototyping, preferably within the automotive or a related industry. A strong portfolio of past projects demonstrating expertise in SystemC/TLM 2.0 and vECU development will be highly beneficial.

Required Skills:

Expert-level proficiency in SystemC and Transaction Level Modeling (TLM 2.0), including practical experience in creating complex, high-fidelity models of hardware components.
Demonstrated expertise in the creation and integration of Level 4 Virtual ECU (vECU) prototypes, capable of executing unmodified production embedded software.
Proficiency with industry-standard Electronic Design Automation (EDA) toolchains specifically used for virtual prototyping, such as Synopsys Virtualizer and ASTC vLAB.
Strong expertise in multiple programming languages essential for embedded development and modeling, including C, C++, and Python.
Deep expertise in low-level input/output (I/O) driver development, debugging, and understanding the interaction between software and hardware at the register level.
Comprehensive knowledge of electronic control modules (ECMs) and the architecture and principles of embedded control systems in automotive applications.
Detailed knowledge of ARM-based microcontrollers, including their architecture, peripherals, and programming models, which are prevalent in automotive ECUs.
Expertise in software integration processes, including a strong understanding of compiler and linker functionalities and their impact on embedded software execution.

Preferred Skills:

Knowledge of AUTOSAR (Automotive Open System Architecture) and its relevance to embedded software development and integration in automotive systems.
Familiarity with Automotive Cyber Security concepts and how they apply to embedded systems and virtual prototyping environments.
Knowledge of various automotive communication protocols, including CAN, LIN, SPI, I2C, and UART, and their modeling in virtual environments.
Experience with Co-Simulation techniques for integrating and validating Level 4 VECUs with other simulation models and environments.
Expertise in the use of professional software debugging tools commonly used in embedded development, such as Lauterbach and Green Hills Multi IDE.
Expertise in automotive network analysis tools like Intrepid Vehicle Spy and Vector CANoe for monitoring and debugging automotive communication buses.
Experience with software test automation frameworks and methodologies applicable to embedded systems and virtual validation.
Expertise in the development of software tools to support the virtual prototyping workflow, including scripting, automation, and data analysis.
Strong expertise in embedded control system design principles and best practices.
Experience in executing production vehicle programs, providing practical insight into the automotive development lifecycle.
Development experience in both Windows and Linux operating environments.
Familiarity with modern software development build processes and associated tools (e.g., Gerrit, Jenkins, Git) for version control and continuous integration.
Familiarity with scalable simulation deployment methodologies leveraging containerization technologies (e.g., Docker, Singularity) for managing virtual environments.
Familiarity with synchronous and asynchronous event-driven simulation paradigms.

📝 Enhancement Note: The required skills list is highly specific to embedded software, hardware modeling, and virtual prototyping, aligning with the technical nature of the role. The preferred skills add significant value by indicating a desire for candidates with automotive domain knowledge, familiarity with industry-standard tools and methodologies, and experience in production environments. This suggests a need for candidates who can not only build models but also understand the context and application within automotive development.

🎨 Portfolio & Creative Requirements

Portfolio Essentials:

While not a traditional design portfolio, candidates should prepare a technical portfolio or project summaries demonstrating their expertise in SystemC/TLM 2.0 modeling and virtual ECU development.
Include detailed case studies of past projects where you successfully modeled complex microcontroller peripherals or integrated multiple models into a functional virtual prototype.
Showcase your approach to debugging complex embedded software running on virtual hardware, illustrating your problem-solving process and use of debugging tools.
Present examples of how you validated and verified virtual ECUs against specifications or real-world behavior, highlighting your methodology and results.

Process Documentation:

Document your process for creating SystemC models, from understanding hardware specifications and datasheets to implementing and verifying the model's accuracy.
Detail your approach to integrating different models and production software into a cohesive virtual ECU, including how you handle dependencies and configurations.
Explain your strategies for debugging issues that arise in the virtual environment, including how you isolate problems between the model, the software, and the integration layer.

📝 Enhancement Note: Given this is not a traditional visual design role, the concept of a "portfolio" is adapted to a technical portfolio showcasing modeling and development expertise. The focus shifts to demonstrating technical process, problem-solving skills, and the ability to translate hardware concepts into functional virtual representations, which are the "creative" aspects of this specific technical domain.

💵 Compensation & Benefits

Salary Range: Based on extensive market research for similar highly specialized engineering roles with over 10 years of experience in the automotive and embedded systems domain within the Markham/Toronto area of Ontario, Canada, the estimated salary range for this position is likely between CAD $120,000 and $160,000 annually. This estimate considers the high level of technical expertise required (SystemC, TLM 2.0, embedded systems), the automotive industry context, the experience level (10+ years), and the cost of living in the Greater Toronto Area. Specific compensation within this range would depend on the candidate's exact qualifications, experience, and interview performance. Data sources include publicly available salary data from job boards, industry reports focusing on engineering compensation in Canada, and comparisons with similar roles at major automotive or technology companies in the region.

Benefits:

Paid Time Off: Includes vacation days, company holidays, and supplemental benefits for pregnancy, parental, and adoption leave, providing flexibility and support for work-life balance.
Healthcare, Dental, and Vision Benefits: Comprehensive health coverage to support the well-being of employees and their families.
Life Insurance: Plans to provide financial security for employees and their dependents.
Pension Plan: Company and matching contributions to a Defined Contribution Pension plan to assist employees in saving for retirement.
GM Vehicle Purchase Plan: Exclusive discounts on GM vehicles for employees, their family, and friends.

Working Hours: This is a full-time role, typically involving a standard 40-hour work week. As a hybrid role, flexibility may exist around specific daily hours, but core hours for team collaboration and meetings will likely be required. The nature of embedded systems development and debugging may occasionally require flexibility beyond standard hours depending on project phases and critical deadlines.

📝 Enhancement Note: The salary estimate is based on regional data for highly specialized engineering roles, taking into account the specific technical skills (SystemC, TLM), industry (automotive), and experience level (10+ years). The benefits listed are standard for a large corporation like GM in Canada, providing a comprehensive package for employee well-being and financial planning. The hybrid work arrangement offers a degree of flexibility common in modern engineering roles.

🎯Team & Company Context

🏢 Company & Design Culture

Industry: Motor Vehicle Manufacturing. General Motors is a global automotive leader undergoing a significant transformation towards electric vehicles, autonomous driving, and software-defined vehicles. This role is at the forefront of enabling this transformation by developing virtual prototyping capabilities, which are crucial for accelerating the development cycle of complex electronic systems in modern vehicles.

Company Size: 10,001+ employees globally. As a large, established corporation, GM offers extensive resources, global reach, and opportunities for complex, large-scale projects. This size implies structured processes, potentially specialized teams, and opportunities for collaborating with a wide range of experts across different engineering disciplines.

Founded: General Motors was founded in 1908. With over a century of history, GM has a deep legacy in automotive engineering. The current focus on virtual prototyping indicates a commitment to adopting cutting-edge technologies and modern development methodologies to stay competitive in a rapidly evolving industry.

Team Structure:

This role is within the Virtualization and SIL Integration team, which is described as highly technical and focused on organizational transformation.
The team is expanding its capabilities, suggesting growth and investment in this area.
Collaboration is explicitly mentioned with Design Release Engineers, Tier 1 suppliers, and software engineers, indicating a cross-functional and collaborative environment.

Methodology:

The core methodology involves creating Level 4 Virtual ECUs (vECUs) that execute unmodified production code, indicating a focus on high-fidelity simulation.
The use of SystemC and TLM 2.0 points to a transaction-level modeling approach for virtual prototyping, balancing simulation speed with sufficient detail for software execution.
The emphasis on integration, debugging, validation, and verification highlights a rigorous engineering process for ensuring the accuracy and reliability of the virtual environment.

Company Website: http://www.gm.com

📝 Enhancement Note: The company context highlights GM's strategic shift towards software-defined vehicles and the importance of this role in supporting that transformation through advanced virtual prototyping. The size and history of GM indicate a mature organization with established processes, while the focus on virtualization suggests a forward-thinking approach to engineering challenges. The team structure and methodology description provide insight into the daily work environment and technical approach.

📈 Career & Growth Analysis

Design Career Level: This role is positioned as a senior-level engineering position, requiring a minimum of 10 years of experience. The responsibilities involve significant technical expertise, problem-solving, and likely a degree of technical leadership or mentoring within the team. It's a specialist role focused on a critical and growing area of automotive development.

Reporting Structure: While not explicitly stated, given the team's focus on organizational transformation and its expansion, this role likely reports to an engineering manager overseeing the Virtualization and SIL Integration efforts. Collaboration with various engineering disciplines and external partners suggests a matrixed or project-based reporting dimension as well.

Design Impact: The "design" impact in this context is on the design and validation process of automotive embedded systems. By enabling early and comprehensive testing of production software on virtual hardware, this role directly influences the quality, reliability, and development speed of vehicle electronic control units, which are fundamental to vehicle functionality and performance.

Growth Opportunities:

Technical Specialization: Deepen expertise in SystemC/TLM 2.0, advanced modeling techniques, and specific automotive domains (e.g., electrification, ADAS) to become a recognized subject matter expert within GM and the industry.
Technical Leadership: Lead complex modeling projects, mentor junior engineers, and contribute to defining best practices and technical standards for virtual prototyping within the organization.
Cross-Functional Influence: Expand influence by working closely with hardware design teams to ensure models accurately reflect future silicon and with software teams to optimize code for virtual environments.

📝 Enhancement Note: The career analysis focuses on the technical growth paths available within a large automotive engineering organization for a specialist role. The impact is clearly defined in terms of enabling the broader embedded system development and validation process. Growth opportunities are framed around increasing technical depth, leadership responsibilities, and cross-functional influence within the engineering domain.

🌐 Work Environment

Studio Type: This is a hybrid role, requiring a minimum of three days per week in office, specifically at the Markham Elevation Centre or potentially the Oshawa location in Ontario, Canada. This suggests a blend of in-office collaboration for complex technical work and modeling, with the flexibility of remote work for focused tasks.

Office Location(s): Markham Elevation Centre - Markham, Ontario, Canada, and potentially Oshawa, Ontario, Canada. These locations are key engineering and R&D hubs for General Motors in Canada, providing access to necessary infrastructure, labs, and collaboration spaces.

Design Workspace Context:

The hybrid model suggests dedicated workspace is available in the office for collaborative activities, technical discussions, and access to specialized hardware or simulation infrastructure.
The work will involve significant time spent on high-performance computing resources for running complex simulations and debugging virtual environments.
Interaction with physical hardware setups (e.g., Hardware-in-the-Loop systems) may be part of the validation process, requiring access to lab facilities.

Work Schedule: Full-time, with a minimum of three days per week required in the office. The specific in-office days may be flexible or set by the team to optimize collaboration. The nature of the work may require occasional adjustments to the schedule for critical project milestones or debugging sessions.

📝 Enhancement Note: The work environment description clarifies the hybrid nature of the role and the importance of physical presence for collaboration and access to specialized resources. The locations in Ontario are significant R&D centers, implying a concentration of engineering talent and infrastructure relevant to this role. The workspace context highlights the blend of individual technical work and collaborative problem-solving inherent in embedded systems development and virtual prototyping.

📄 Application & Portfolio Review Process

Design Interview Process:

Initial Screening: Expect a recruiter screen to assess basic qualifications, experience, and fit for the role and company culture.
Technical Interview(s): Multiple rounds with engineering team members and potentially the hiring manager. These interviews will heavily focus on your technical expertise in SystemC, TLM 2.0, embedded systems, microcontroller architecture, and debugging skills. Be prepared to discuss your experience in detail, including specific projects and challenges you've faced.
Case Study / Technical Deep Dive: You may be asked to present a detailed case study of a complex modeling or integration project from your past, walking through your process, challenges, and solutions. Alternatively, a technical deep dive into a specific area of your expertise (e.g., modeling a particular peripheral, debugging a complex issue) may be required.
Behavioral Interview: Assess your collaboration skills, problem-solving approach, ability to handle ambiguity, and alignment with GM's leadership behaviors and values.
Final Interview(s): Potentially with higher-level management or key stakeholders involved in the virtual prototyping initiative.

Portfolio Review Tips:

Structure your technical portfolio or project summaries clearly, focusing on projects most relevant to SystemC/TLM 2.0 modeling and virtual ECU development.
For each project, clearly state the problem you were solving, your role, the technologies used (specifically SystemC, TLM 2.0, EDA tools), your approach, the technical challenges encountered, and the outcomes or impact of your work.
Highlight your process for understanding hardware specifications and translating them into accurate and performant virtual models.
Showcase your debugging skills by describing specific instances where you identified and resolved complex issues in virtual environments or embedded software running on vECUs.

Challenge Preparation:

Be prepared for questions or a potential exercise related to modeling a simplified hardware component using SystemC and TLM 2.0.
Practice explaining complex technical concepts clearly and concisely, particularly regarding microcontroller architecture, memory mapping, and peripheral interactions.
Review common debugging scenarios in embedded systems and be ready to discuss your systematic approach to root cause analysis.

ATS Keywords: SystemC, TLM 2.0, Virtual Prototyping, vECU, Embedded Systems, Microcontroller Modeling, EDA Toolchains (Synopsys Virtualizer, ASTC vLAB), C, C++, Python, Driver Development, Low-Level Programming, AUTOSAR, Automotive Cyber Security, CAN, LIN, SPI, I2C, UART, Co-Simulation, Debugging Tools (Lauterbach, Green Hills Multi IDE), Intrepid Vehicle Spy, Vector CANoe, Software Integration, Compiler, Linker, Hardware Architecture, Micro-architecture, Software Test Automation, Software Tools Development, Embedded Control System Design, Production Vehicle Programs, Windows, Linux, Gerrit, Jenkins, Git, Docker, Singularity, Event-Driven Simulation, Transaction Level Modeling, Hardware/Software Co-design, Automotive Engineering, Vehicle Electrification, ADAS, Model-Based Design, Simulation, Validation, Verification, Debugging, Problem Solving, Collaboration, Communication, Technical Leadership.

📝 Enhancement Note: The application process and interview preparation section are tailored to a highly technical engineering role, emphasizing the need to demonstrate deep expertise in specific tools and methodologies (SystemC, TLM 2.0, EDA tools). The "portfolio" guidance is adapted to a technical context, focusing on project case studies and process documentation rather than visual design. The keyword list is comprehensive and covers the key technical skills and concepts mentioned in the job description, aiding candidates in optimizing their resumes.

🛠 Tools & Technology Stack

Primary Design Tools: (Note: "Design" here refers to the design of virtual models and systems, not visual design.)

SystemC: Essential C++ class library for discrete-event simulation, used for modeling hardware at various levels of abstraction, with expertise required in high-level modeling.
Transaction Level Modeling (TLM 2.0): Key methodology for modeling communication between components in SystemC, crucial for building efficient and accurate virtual prototypes of ECUs. Expertise in implementing TLM 2.0 compliant models and understanding transaction-based communication is required.
Synopsys Virtualizer / ASTC vLAB: Industry-standard EDA toolchains specifically designed for creating and integrating virtual prototypes of embedded systems. Proficiency in using these tools for model development, integration, and simulation is critical.

Collaboration & Handoff:

Git: Version control system for managing source code for SystemC models, scripts, and related files. Familiarity with branching, merging, and collaborative workflows is expected.
Gerrit: Code review tool often used in conjunction with Git for collaborative code development and quality control.
Jenkins: Automation server for continuous integration and potentially automated testing of virtual ECU builds and simulations.

Research & Testing:

Lauterbach / Green Hills Multi IDE: Professional hardware and software debugging tools. While the focus is on virtual environments, experience with these tools provides valuable insight into embedded system behavior and debugging techniques applicable to vECUs.
Intrepid Vehicle Spy / Vector CANoe: Tools for analyzing and interacting with automotive communication buses (CAN, LIN, etc.). Knowledge of these tools is beneficial for understanding real-world automotive communication and validating virtual models of communication peripherals.
Python: Widely used for scripting, test automation, data analysis, and developing engineering workarounds to support the virtual prototyping workflow.

📝 Enhancement Note: The tools and technology stack is highly specific to embedded systems development and virtual prototyping, reinforcing the technical nature of the role. The inclusion of collaboration and testing tools highlights the integrated nature of the work within a larger engineering process. The emphasis on SystemC, TLM 2.0, and specific EDA tools underscores the core technical requirements for this position.

👥 Team Culture & Values

Design Values: (Note: "Design Values" are interpreted here in the context of engineering design and the principles guiding the virtual prototyping process.)

Accuracy and Fidelity: A strong emphasis on creating virtual models that accurately reflect the behavior of physical hardware to ensure reliable software execution and validation.
Innovation and Transformation: Being part of a team focused on "organizational transformation" implies a culture that values finding cutting-edge solutions and challenging traditional hardware-dependent development processes.
Collaboration: The requirement to work cross-functionally with various engineering teams and external suppliers indicates a collaborative environment where sharing knowledge and working together to achieve common goals is essential.
Problem-Solving and Debugging: Given the complexity of embedded systems and virtual environments, a culture that encourages rigorous problem-solving, systematic debugging, and attention to detail is likely fostered.

Collaboration Style:

Cross-functional collaboration with Design Release Engineers (DREs) and software engineers to align virtual models with hardware specifications and software requirements.
Collaboration with Tier 1 suppliers who may provide models or technical information about components.
Internal team collaboration for code reviews (potentially using Gerrit), technical discussions, and knowledge sharing on modeling techniques and best practices.

📝 Enhancement Note: The "Design Values" are interpreted through the lens of engineering design and the specific goals of the virtual prototyping team at GM. The emphasis on accuracy, innovation, and collaboration aligns with the technical and transformative nature of the role. The collaboration style description provides specific examples of how the team interacts internally and externally.

⚡ Challenges & Growth Opportunities

Design Challenges: (Note: "Design Challenges" refer to the technical and process challenges in virtual prototyping.)

Model Accuracy and Performance: Balancing the need for high-fidelity models that accurately represent hardware behavior with the performance requirements for real-time simulation. This requires deep understanding of both hardware and software.
Integration Complexity: Integrating numerous individual component models and production software into a single, functional virtual ECU, managing dependencies and ensuring seamless interaction.
Debugging in Virtual Environments: Diagnosing and resolving complex issues that can arise from interactions between the virtual model, the embedded software, and the simulation environment itself.
Keeping Pace with Hardware Evolution: Continuously updating virtual models to reflect changes in hardware designs and new microcontroller features, requiring ongoing learning and adaptation.

Learning & Development Opportunities:

Deep Technical Specialization: Become an expert in specific areas of microcontroller architecture modeling, advanced SystemC/TLM 2.0 techniques, or specialized automotive domains like functional safety or automotive cyber security in virtual contexts.
Toolchain Mastery: Gain deep expertise in using and potentially extending industry-leading EDA toolchains for virtual prototyping.
Cross-Domain Knowledge: Expand knowledge of related areas such as hardware design, embedded software development best practices, and automotive functional safety standards.

📝 Enhancement Note: The challenges listed are inherent to the domain of virtual prototyping of embedded systems, highlighting the technical complexity and problem-solving required. The growth opportunities are directly tied to overcoming these challenges and deepening expertise in relevant technical areas, offering a clear path for professional development within this specialized field.

💡 Interview Preparation

Design Process Questions: (Note: "Design Process" refers to the virtual modeling and development process.)

"Describe your process for creating a SystemC TLM 2.0 model of a complex microcontroller peripheral (e.g., a CAN controller or a timer). How do you ensure accuracy and performance?" Prepare by reviewing your past projects and outlining your step-by-step approach, including how you interpret datasheets, implement logic, and verify behavior.
"Walk me through a time you debugged a complex issue in a virtual embedded system. How did you isolate the problem between the model, the software, and the simulation environment?" Be ready to discuss specific examples, detailing your debugging methodology, the tools you used, and how you arrived at the solution.
"How do you approach integrating production embedded software into a virtual ECU? What are the key challenges, and how do you address them?" Discuss your experience with compiler/linker configurations, memory mapping, and handling software dependencies in a virtual environment.

Company Culture Questions:

"How do you approach collaboration with hardware design engineers and software developers when building virtual models?" Prepare examples of successful cross-functional collaboration, highlighting how you communicate technical information and resolve disagreements.
"Describe your experience working with external suppliers (e.g., Tier 1 suppliers or EDA tool vendors). How do you manage technical communication and dependencies?" Discuss instances where you've worked with external partners to acquire information, models, or support.
"Given GM's focus on transformation, how do you stay updated on the latest advancements in virtual prototyping techniques and tools?" Discuss your approach to continuous learning, including conferences, online resources, and experimentation.

Portfolio Presentation Strategy:

Select 2-3 key projects that best showcase your expertise in SystemC/TLM 2.0 modeling and virtual ECU development.
For each project, structure your presentation as a case study: briefly introduce the project goal, describe the technical challenge you addressed, explain your approach using specific tools and methodologies (SystemC, TLM 2.0, EDA tools), detail the results or impact of your work, and highlight key lessons learned.
Be prepared to deep dive into the technical details of your models, including architectural decisions, implementation choices, and verification strategies.

📝 Enhancement Note: The interview preparation section provides targeted advice based on the technical requirements and likely focus areas of the interview process. The sample questions are specific to the role's technical domain and encourage candidates to provide concrete examples from their experience. The portfolio presentation strategy is adapted for a technical portfolio, emphasizing the demonstration of process, problem-solving, and technical depth.

📌 Application Steps

To apply for this design position:

Submit your application through this link
Prepare a technical portfolio or summary of key projects that demonstrate your expertise in SystemC/TLM 2.0 modeling, virtual ECU development, and embedded systems debugging. Focus on projects relevant to automotive or similar complex embedded domains.
Optimize your resume to include relevant keywords and highlight your experience with SystemC, TLM 2.0, EDA toolchains (Synopsys Virtualizer, ASTC vLAB), C, C++, Python, and automotive communication protocols. Quantify your achievements where possible.
Practice articulating your technical process for modeling and debugging, preparing to discuss specific challenges and solutions from your past projects. Rehearse presenting your technical case studies clearly and concisely.
Research General Motors' recent work in electrification, software-defined vehicles, and virtual validation to understand how this role fits into the company's broader strategy. Familiarize yourself with GM's values and leadership behaviors.

⚠️ Important Notice: This enhanced job description includes AI-generated insights and design industry-standard assumptions. All details should be verified directly with the hiring organization before making application decisions.

Controller Modelling Developer – Virtual Prototyping