**Please strictly adhere to the following resume naming convention:
ALL CAPS, NO SPACES B/T UNDERSCORES
: -
PTN_US_GBAMSREQID_CandidateBeelineID
i.e. PTN_US_9999999_SKIPJOHNSON0413
MSP Owner: Patrice Patrick
Location: Dearborn, Michigan 48124 (Hybrid - 4 days in office)
Duration: 6 months
skill id: 10815777
Experience Required: 4-8
Role: Model-Based Software Development & Validation Engineer
Must Have Skills:
• Must have strong fundamentals and experience in model-based feature software development for automotive systems using MATLAB/Simulink/State flow. Strong understanding of solver configurations, sample time settings, and data dictionary management.
• Expertise in Test Case Development and Execution using MIL and SIL. Experience using BTC and Simulink Test for automated test generation, executing back-to-back testing (MIL vs. SIL), measuring structural coverage (MC/DC), and utilizing formal verification methods to mathematically prove the safety and correctness of the control logic
• Good analytical, debugging, and technical documentation skills
• Experience creating Simulink Test setups and writing functional/system test cases and scripting for automated execution
• Exposure to model-based design workflows and continuous integration environments
• Exposure to Automotive ADAS domain knowledge
Roles & Responsibilities
1. Requirements Engineering & Interface Design
o Translate vehicle-level requirements into software specifications and define ECU interfaces (I/O, calibrations, and network signals).
2. Model-Based Algorithm Development
o Design and prototype control algorithms and state-machine logic using MATLAB/Simulink and Stateflow.
3. Model-in-the-Loop (MIL) Verification
o Run closed-loop simulations with plant models, authoring functional tests in SimulinkTest and using BTC EmbeddedTester to generate automated test vectors and analyze model coverage (MC/DC).
4. Automated Code Generation & ECU Integration
o Generate production-grade C/C++ code from models using Embedded Coder, ensuring AUTOSAR architecture compliance and supporting integration into base software (BSW).
5. Software Verification, Validation & Testing
o Conduct back-to-back MIL vs. SIL equivalence testing and code coverage analysis using BTC and Simulink Test, owning the triage and resolution of model-level bugs.
6. Functional Safety & Standards Compliance
o Design software to comply with ISO 26262 (ASIL) and MISRA C, maintaining strict bidirectional traceability from requirements to test cases.
7. Configuration & Lifecycle Management
o Manage models, data dictionaries (.sldd), and code in version control, packaging verified software increments for program milestones
Stakeholder Collaboration
• With Systems Engineering:
o Requirement & Interface Alignment: Review high-level requirements for software feasibility, align on interface/signal databases, and map safety requirements to the software model.
o Change Management: Conduct impact analyses on existing models and code when system-level change requests are proposed.
• With Verification & Validation (V&V):
o Test Strategy & Sharing: Define virtual (MIL/SIL) vs. physical (HIL/Vehicle) test boundaries and share reusable test vectors/assessments from Simulink Test and BTC.
o Joint Debugging: Lead the root-cause analysis of HIL or vehicle test failures to isolate and patch software bugs in the model.
Managerial Skills:
• Highly proactive, ownership-driven, and technically hands-on.
• Excellent communication and cross-functional collaboration skills.
• Focused on continuous improvement and innovation in testing practices.
• Work with offshore engineers to deliver models with test suits etc.
• Participate in root cause analysis for software quality problems and software defects
Pre-Screening Questionnaire
Q1. Explain Model Based design approach and which major advantage it provide over conventional software development cycle?
Ans: Model Based design is an approach where the entire development and test cycle is around a functional/mathematical model rather than a textual document.
The requirements are implemented in an executable model form which can be simulated to prove the behavior expected out of the requirements.
ALL CAPS, NO SPACES B/T UNDERSCORES
: -
PTN_US_GBAMSREQID_CandidateBeelineID
i.e. PTN_US_9999999_SKIPJOHNSON0413
MSP Owner: Patrice Patrick
Location: Dearborn, Michigan 48124 (Hybrid - 4 days in office)
Duration: 6 months
skill id: 10815777
Experience Required: 4-8
Role: Model-Based Software Development & Validation Engineer
Must Have Skills:
• Must have strong fundamentals and experience in model-based feature software development for automotive systems using MATLAB/Simulink/State flow. Strong understanding of solver configurations, sample time settings, and data dictionary management.
• Expertise in Test Case Development and Execution using MIL and SIL. Experience using BTC and Simulink Test for automated test generation, executing back-to-back testing (MIL vs. SIL), measuring structural coverage (MC/DC), and utilizing formal verification methods to mathematically prove the safety and correctness of the control logic
• Good analytical, debugging, and technical documentation skills
• Experience creating Simulink Test setups and writing functional/system test cases and scripting for automated execution
• Exposure to model-based design workflows and continuous integration environments
• Exposure to Automotive ADAS domain knowledge
Roles & Responsibilities
1. Requirements Engineering & Interface Design
o Translate vehicle-level requirements into software specifications and define ECU interfaces (I/O, calibrations, and network signals).
2. Model-Based Algorithm Development
o Design and prototype control algorithms and state-machine logic using MATLAB/Simulink and Stateflow.
3. Model-in-the-Loop (MIL) Verification
o Run closed-loop simulations with plant models, authoring functional tests in SimulinkTest and using BTC EmbeddedTester to generate automated test vectors and analyze model coverage (MC/DC).
4. Automated Code Generation & ECU Integration
o Generate production-grade C/C++ code from models using Embedded Coder, ensuring AUTOSAR architecture compliance and supporting integration into base software (BSW).
5. Software Verification, Validation & Testing
o Conduct back-to-back MIL vs. SIL equivalence testing and code coverage analysis using BTC and Simulink Test, owning the triage and resolution of model-level bugs.
6. Functional Safety & Standards Compliance
o Design software to comply with ISO 26262 (ASIL) and MISRA C, maintaining strict bidirectional traceability from requirements to test cases.
7. Configuration & Lifecycle Management
o Manage models, data dictionaries (.sldd), and code in version control, packaging verified software increments for program milestones
Stakeholder Collaboration
• With Systems Engineering:
o Requirement & Interface Alignment: Review high-level requirements for software feasibility, align on interface/signal databases, and map safety requirements to the software model.
o Change Management: Conduct impact analyses on existing models and code when system-level change requests are proposed.
• With Verification & Validation (V&V):
o Test Strategy & Sharing: Define virtual (MIL/SIL) vs. physical (HIL/Vehicle) test boundaries and share reusable test vectors/assessments from Simulink Test and BTC.
o Joint Debugging: Lead the root-cause analysis of HIL or vehicle test failures to isolate and patch software bugs in the model.
Managerial Skills:
• Highly proactive, ownership-driven, and technically hands-on.
• Excellent communication and cross-functional collaboration skills.
• Focused on continuous improvement and innovation in testing practices.
• Work with offshore engineers to deliver models with test suits etc.
• Participate in root cause analysis for software quality problems and software defects
Pre-Screening Questionnaire
Q1. Explain Model Based design approach and which major advantage it provide over conventional software development cycle?
Ans: Model Based design is an approach where the entire development and test cycle is around a functional/mathematical model rather than a textual document.
The requirements are implemented in an executable model form which can be simulated to prove the behavior expected out of the requirements.