Principal BMS Engineer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info; remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section only when posting has real specific content for it; never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the job description.
Key sections:
- About the role: The description starts with "Principal Battery Management System (BMS) Engineer provides technical leadership..." That's about the role. Could be "About the role" heading.
- Responsibilities: List of responsibilities bullet points.
- Essential Skills: Could be "Qualifications" or "Skills". The posting includes "Essential Skills" and "Additional Skills & Qualifications". Could combine into "Qualifications" or "Skills". We need to decide.
- Work Environment: Could be "Work Environment" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings.
We have:
- About the role: description of role.
- Responsibilities: bullet list.
- Requirements: maybe essential skills? Could be "Requirements" heading for essential skills (education, years experience). Or "Qualifications". The allowed headings include both Requirements and Qualifications and Skills. We need to decide which to use.
We have "Essential Skills" (education, years experience, expertise). Also "Additional Skills & Qualifications". Could combine into "Qualifications" or "Skills". Since we have both headings allowed, we could use "Qualifications" for education/experience requirements, and "Skills" for technical skills list.
But we must not create sections with filler. Ensure each section has substantive content.
We also have "Work Environment" description; not in allowed headings, but we could incorporate into "About the role" or maybe omit? The instruction: "Prefer a few substantive sections over many thin ones." We could incorporate work environment into About the role or Responsibilities? Probably better to include in About the role as additional prose.
We have "Pay And Benefits": includes pay range and benefits details. So we need Pay and Benefits sections. Pay: we have pay range. Benefits: list of benefits.
We have "Work Type": fully onsite. Could be Schedule? Not exactly. Schedule heading is for work schedule (e.g., full-time, shift). Not present. Could omit Schedule.
We have "Job Type & Location": Permanent position based out of Plymouth, MI. Could be included in About the role or maybe as a short paragraph under About the role. Not a heading.
We have "Application Deadline": anticipated to close on Sep 25, 2026. That's application instruction; we should remove application instructions per rule: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should drop Application Deadline.
We have boilerplate about Actalent, EEO, etc. Remove.
We have "Work Environment" paragraph; we can keep as prose under About the role or maybe as its own section if we map to "About the role". Probably incorporate.
We have "Work Type" (fully onsite) maybe incorporate.
We have "Pay And Benefits": we need Pay and Benefits sections.
We need to use
for section headings.
We need to use - for any list of duties/requirements/benefits.
We need to use
for prose.
We must not repeat job title as heading.
We must not put Job ID/requisition numbers as headings (none present).
We must preserve all substantive information; do not invent or summarize away detail.
We must remove boilerplate etc.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract substantive content:
About the role: The role description paragraph(s):
"Principal Battery Management System (BMS) Engineer provides technical leadership, architectural ownership, and long-term stewardship of advanced battery management solutions. In this role, you define system-level technical direction, own key architecture decisions, and ensure regulatory and functional safety compliance while serving as the subject-matter expert across firmware, electronics, algorithms, and system integration. You will lead the evolution of multi-generation BMS platforms, guide cross-functional architectural decisions, and ensure solutions are robust, scalable, and aligned with current and future product roadmaps."
Also maybe include work environment: "This role focuses on advanced Battery Management System engineering within an embedded systems and electronics environment. You will work with technologies such as embedded firmware, real-time systems, communication protocols (SPI, I2C, CAN, CANOpen, J1939, UDS), and safety and compliance frameworks (UL, IEC, ISO, functional safety guidance). The position involves close collaboration with cross-functional engineering teams, participation in design reviews and risk assessments, and engagement with manufacturing and test engineering to ensure designs are manufacturable, testable, and serviceable at scale. Work is primarily performed in an office and laboratory setting with access to development tools, diagnostic equipment, and test systems for batteries and power electronics."
Also job type/location: "This is a Permanent position based out of Plymouth, MI." Could be included.
We could combine all into About the role.
Responsibilities: list bullet points from "Responsibilities" section.
Let's extract each responsibility line:
- Serve as the technical authority for BMS architecture, covering firmware, electronics, sensing, controls, and system integration.
- Define and maintain system-level BMS architecture, design patterns, and technical standards across multiple product lines.
- Lead technical trade studies that balance safety, performance, cost, manufacturability, and long-term maintainability.
- Establish best practices for embedded firmware architecture, hardware abstraction, diagnostics, and fault handling.
- Provide expert-level guidance on embedded firmware design, real-time systems, and safety-critical software.
- Lead the development and review of core BMS algorithms, including state of charge (SOC), state of health (SOH), state of energy (SOE), cell balancing, protection, diagnostics, and degradation monitoring.
- Own the interpretation and application of relevant safety and compliance standards such as UL, IEC, ISO, and functional safety guidance as they relate to BMS design.
- Drive system-level requirements decomposition, traceability, and verification strategies to ensure complete coverage and robust performance.
- Lead DFMEA, fault tree analysis (FTA), and system-level risk assessments, ensuring mitigation strategies are implemented, verified, and maintained.
- Guide the development of end-of-line test strategies, diagnostic coverage, and service tools to support manufacturing and field service.
- Ensure BMS designs are manufacturable, testable, and serviceable at scale for long-term product success.
- Support long-term sustainment activities, reliability improvements, and continuous improvement initiatives across BMS platforms.
- Perform other engineering and technical duties as needed to support product development and lifecycle management.
We need to keep all.
Requirements: Could be "Essential Skills" which includes education and experience.
Essential Skills bullet list:
- Master’s degree in Electrical Engineering, Computer Science, or Computer Engineering preferred, or a Bachelor’s degree in a related field with relevant certifications or graduate-level coursework.
- 15+ years of embedded systems work experience.
- 7+ years of experience working with battery or relevant energy systems preferred.
- Recognized expertise in BMS firmware, electronics, and system-level design.
- Deep understanding of lithium-ion battery behavior, protection strategies, and safety mechanisms.
- Proven ability to define and evolve system architectures across multiple product generations.
- Advanced proficiency with embedded communication protocols, including SPI, I2C, CAN, CANOpen, J1939, and UDS.
- Strong experience with verification, validation, and compliance in regulated or safety-critical environments.
- Exceptional analytical and problem-solving skills, including root-cause analysis of complex system issues.
- Hands-on experience with battery management systems, algorithm development, system integration, and embedded controls.
- Strong experience in embedded systems and systems architecture.
- Experience with DFMEA and related system-level risk assessment methodologies.
We could treat these as Requirements.
Additional Skills & Qualifications list:
- Graduate-level coursework or relevant certifications in embedded systems, controls, or safety-critical software development.
- Experience defining and maintaining technical standards and design patterns across multiple product lines.
- experience in functional safety frameworks and their application to BMS design.
- Experience guiding cross-functional teams in system integration and architectural decision-making.
- Strong communication skills to articulate complex technical concepts to diverse stakeholders.
- Ability to mentor and influence engineering teams in best practices for firmware, hardware abstraction, diagnostics, and fault handling.
We could merge with Requirements or Skills. Since we have both Requirements and Skills headings allowed, we could put the essential skills under Requirements, and additional skills under Skills. Or we could combine all under Skills. But we need to avoid thin sections. Perhaps better to have Requirements (education/experience) and Skills (technical skills). However the essential skills list includes both education/experience and technical skills. Could split: Requirements: education and years experience; Skills: technical expertise list.
But we must preserve all substantive info; we can split.
Let's define:
- Requirements: education and experience (Master's/Bachelor's preferred, 15+ years embedded, 7+ years battery, etc). Also maybe include "Recognized expertise in BMS firmware, electronics, and system-level design." That's more skill. Hmm.
Better to follow typical pattern: Requirements = mandatory qualifications (education, years experience). Skills = technical skills.
Thus:
Requirements (
Requirements
):
- Master’s degree in Electrical Engineering, Computer Science, or Computer Engineering preferred, or a Bachelor’s degree in a related field with relevant certifications or graduate-level coursework.
- 15+ years of embedded systems work experience.
- 7+ years of experience working with battery or relevant energy systems preferred.
Skills (Skills
):
List all technical expertise items: Recognized expertise in BMS firmware, electronics, and system-level design; Deep understanding of lithium-ion battery behavior, protection strategies, and safety mechanisms; Proven ability to define and evolve system architectures across multiple product generations; Advanced proficiency with embedded communication protocols, including SPI, I2C, CAN, CANOpen, J1939, and UDS; Strong experience with verification, validation, and compliance in regulated or safety-critical environments; Exceptional analytical and problem-solving skills, including root-cause analysis of complex system issues; Hands-on experience with battery management systems, algorithm development, system integration, and embedded controls; Strong experience in embedded systems and systems architecture; Experience with DFMEA and related system-level risk assessment methodologies; Graduate-level coursework or relevant certifications in embedded systems, controls, or safety-critical software development; Experience defining and maintaining technical standards and design patterns across multiple product lines; experience in functional safety frameworks and their application to BMS design; Experience guiding cross-functional teams in system integration and architectural decision-making; Strong communication skills to articulate complex technical concepts to diverse stakeholders; Ability to mentor and influence engineering teams in best practices for firmware, hardware abstraction, diagnostics, and fault handling.
We could also include "Strong experience in embedded systems and systems architecture" (already). Ensure we don't duplicate.
Now Benefits: list from "Health & Insurance Benefits", "Retirement & Financial Perks", "Time Off & Professional Growth". Let's extract:
Health & Insurance Benefits:
- Comprehensive medical, dental, and vision care
- Flexible Spending Accounts (FSA) for tax savings
- Life insurance and Accidental Death & Dismemberment (AD&D) coverage
Retirement & Financial Perks:
- Employer-matched 401(k) retirement plan contributions
- Employee referral bonuses
- Salary continuance for jury duty service
Time Off & Professional Growth:
- Generous paid time off (PTO) or flexible/unlimited PTO policies
- Paid federal
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info; remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section only when posting has real specific content for it; never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the job description. Key sections: - About the role: The description starts with "Principal Battery Management System (BMS) Engineer provides technical leadership..." That's about the role. Could be "About the role" heading. - Responsibilities: List of responsibilities bullet points. - Essential Skills: Could be "Qualifications" or "Skills". The posting includes "Essential Skills" and "Additional Skills & Qualifications". Could combine into "Qualifications" or "Skills". We need to decide. - Work Environment: Could be "Work Environment" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings. We have: - About the role: description of role. - Responsibilities: bullet list. - Requirements: maybe essential skills? Could be "Requirements" heading for essential skills (education, years experience). Or "Qualifications". The allowed headings include both Requirements and Qualifications and Skills. We need to decide which to use. We have "Essential Skills" (education, years experience, expertise). Also "Additional Skills & Qualifications". Could combine into "Qualifications" or "Skills". Since we have both headings allowed, we could use "Qualifications" for education/experience requirements, and "Skills" for technical skills list. But we must not create sections with filler. Ensure each section has substantive content. We also have "Work Environment" description; not in allowed headings, but we could incorporate into "About the role" or maybe omit? The instruction: "Prefer a few substantive sections over many thin ones." We could incorporate work environment into About the role or Responsibilities? Probably better to include in About the role as additional prose. We have "Pay And Benefits": includes pay range and benefits details. So we need Pay and Benefits sections. Pay: we have pay range. Benefits: list of benefits. We have "Work Type": fully onsite. Could be Schedule? Not exactly. Schedule heading is for work schedule (e.g., full-time, shift). Not present. Could omit Schedule. We have "Job Type & Location": Permanent position based out of Plymouth, MI. Could be included in About the role or maybe as a short paragraph under About the role. Not a heading. We have "Application Deadline": anticipated to close on Sep 25, 2026. That's application instruction; we should remove application instructions per rule: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should drop Application Deadline. We have boilerplate about Actalent, EEO, etc. Remove. We have "Work Environment" paragraph; we can keep as prose under About the role or maybe as its own section if we map to "About the role". Probably incorporate. We have "Work Type" (fully onsite) maybe incorporate. We have "Pay And Benefits": we need Pay and Benefits sections. We need to use
for section headings.
We need to use - for any list of duties/requirements/benefits.
We need to use
for prose.
We must not repeat job title as heading.
We must not put Job ID/requisition numbers as headings (none present).
We must preserve all substantive information; do not invent or summarize away detail.
We must remove boilerplate etc.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract substantive content:
About the role: The role description paragraph(s):
"Principal Battery Management System (BMS) Engineer provides technical leadership, architectural ownership, and long-term stewardship of advanced battery management solutions. In this role, you define system-level technical direction, own key architecture decisions, and ensure regulatory and functional safety compliance while serving as the subject-matter expert across firmware, electronics, algorithms, and system integration. You will lead the evolution of multi-generation BMS platforms, guide cross-functional architectural decisions, and ensure solutions are robust, scalable, and aligned with current and future product roadmaps."
Also maybe include work environment: "This role focuses on advanced Battery Management System engineering within an embedded systems and electronics environment. You will work with technologies such as embedded firmware, real-time systems, communication protocols (SPI, I2C, CAN, CANOpen, J1939, UDS), and safety and compliance frameworks (UL, IEC, ISO, functional safety guidance). The position involves close collaboration with cross-functional engineering teams, participation in design reviews and risk assessments, and engagement with manufacturing and test engineering to ensure designs are manufacturable, testable, and serviceable at scale. Work is primarily performed in an office and laboratory setting with access to development tools, diagnostic equipment, and test systems for batteries and power electronics."
Also job type/location: "This is a Permanent position based out of Plymouth, MI." Could be included.
We could combine all into About the role.
Responsibilities: list bullet points from "Responsibilities" section.
Let's extract each responsibility line:
- Serve as the technical authority for BMS architecture, covering firmware, electronics, sensing, controls, and system integration.
- Define and maintain system-level BMS architecture, design patterns, and technical standards across multiple product lines.
- Lead technical trade studies that balance safety, performance, cost, manufacturability, and long-term maintainability.
- Establish best practices for embedded firmware architecture, hardware abstraction, diagnostics, and fault handling.
- Provide expert-level guidance on embedded firmware design, real-time systems, and safety-critical software.
- Lead the development and review of core BMS algorithms, including state of charge (SOC), state of health (SOH), state of energy (SOE), cell balancing, protection, diagnostics, and degradation monitoring.
- Own the interpretation and application of relevant safety and compliance standards such as UL, IEC, ISO, and functional safety guidance as they relate to BMS design.
- Drive system-level requirements decomposition, traceability, and verification strategies to ensure complete coverage and robust performance.
- Lead DFMEA, fault tree analysis (FTA), and system-level risk assessments, ensuring mitigation strategies are implemented, verified, and maintained.
- Guide the development of end-of-line test strategies, diagnostic coverage, and service tools to support manufacturing and field service.
- Ensure BMS designs are manufacturable, testable, and serviceable at scale for long-term product success.
- Support long-term sustainment activities, reliability improvements, and continuous improvement initiatives across BMS platforms.
- Perform other engineering and technical duties as needed to support product development and lifecycle management.
We need to keep all.
Requirements: Could be "Essential Skills" which includes education and experience.
Essential Skills bullet list:
- Master’s degree in Electrical Engineering, Computer Science, or Computer Engineering preferred, or a Bachelor’s degree in a related field with relevant certifications or graduate-level coursework.
- 15+ years of embedded systems work experience.
- 7+ years of experience working with battery or relevant energy systems preferred.
- Recognized expertise in BMS firmware, electronics, and system-level design.
- Deep understanding of lithium-ion battery behavior, protection strategies, and safety mechanisms.
- Proven ability to define and evolve system architectures across multiple product generations.
- Advanced proficiency with embedded communication protocols, including SPI, I2C, CAN, CANOpen, J1939, and UDS.
- Strong experience with verification, validation, and compliance in regulated or safety-critical environments.
- Exceptional analytical and problem-solving skills, including root-cause analysis of complex system issues.
- Hands-on experience with battery management systems, algorithm development, system integration, and embedded controls.
- Strong experience in embedded systems and systems architecture.
- Experience with DFMEA and related system-level risk assessment methodologies.
We could treat these as Requirements.
Additional Skills & Qualifications list:
- Graduate-level coursework or relevant certifications in embedded systems, controls, or safety-critical software development.
- Experience defining and maintaining technical standards and design patterns across multiple product lines.
- experience in functional safety frameworks and their application to BMS design.
- Experience guiding cross-functional teams in system integration and architectural decision-making.
- Strong communication skills to articulate complex technical concepts to diverse stakeholders.
- Ability to mentor and influence engineering teams in best practices for firmware, hardware abstraction, diagnostics, and fault handling.
We could merge with Requirements or Skills. Since we have both Requirements and Skills headings allowed, we could put the essential skills under Requirements, and additional skills under Skills. Or we could combine all under Skills. But we need to avoid thin sections. Perhaps better to have Requirements (education/experience) and Skills (technical skills). However the essential skills list includes both education/experience and technical skills. Could split: Requirements: education and years experience; Skills: technical expertise list.
But we must preserve all substantive info; we can split.
Let's define:
- Requirements: education and experience (Master's/Bachelor's preferred, 15+ years embedded, 7+ years battery, etc). Also maybe include "Recognized expertise in BMS firmware, electronics, and system-level design." That's more skill. Hmm.
Better to follow typical pattern: Requirements = mandatory qualifications (education, years experience). Skills = technical skills.
Thus:
Requirements (
Requirements
):
- Master’s degree in Electrical Engineering, Computer Science, or Computer Engineering preferred, or a Bachelor’s degree in a related field with relevant certifications or graduate-level coursework.
- 15+ years of embedded systems work experience.
- 7+ years of experience working with battery or relevant energy systems preferred.
Skills (Skills
):
List all technical expertise items: Recognized expertise in BMS firmware, electronics, and system-level design; Deep understanding of lithium-ion battery behavior, protection strategies, and safety mechanisms; Proven ability to define and evolve system architectures across multiple product generations; Advanced proficiency with embedded communication protocols, including SPI, I2C, CAN, CANOpen, J1939, and UDS; Strong experience with verification, validation, and compliance in regulated or safety-critical environments; Exceptional analytical and problem-solving skills, including root-cause analysis of complex system issues; Hands-on experience with battery management systems, algorithm development, system integration, and embedded controls; Strong experience in embedded systems and systems architecture; Experience with DFMEA and related system-level risk assessment methodologies; Graduate-level coursework or relevant certifications in embedded systems, controls, or safety-critical software development; Experience defining and maintaining technical standards and design patterns across multiple product lines; experience in functional safety frameworks and their application to BMS design; Experience guiding cross-functional teams in system integration and architectural decision-making; Strong communication skills to articulate complex technical concepts to diverse stakeholders; Ability to mentor and influence engineering teams in best practices for firmware, hardware abstraction, diagnostics, and fault handling.
We could also include "Strong experience in embedded systems and systems architecture" (already). Ensure we don't duplicate.
Now Benefits: list from "Health & Insurance Benefits", "Retirement & Financial Perks", "Time Off & Professional Growth". Let's extract:
Health & Insurance Benefits:
- Comprehensive medical, dental, and vision care
- Flexible Spending Accounts (FSA) for tax savings
- Life insurance and Accidental Death & Dismemberment (AD&D) coverage
Retirement & Financial Perks:
- Employer-matched 401(k) retirement plan contributions
- Employee referral bonuses
- Salary continuance for jury duty service
Time Off & Professional Growth:
- Generous paid time off (PTO) or flexible/unlimited PTO policies
- Paid federal
for prose. We must not repeat job title as heading. We must not put Job ID/requisition numbers as headings (none present). We must preserve all substantive information; do not invent or summarize away detail. We must remove boilerplate etc. We need to output only HTML fragment, no /, no markdown fences. Let's extract substantive content: About the role: The role description paragraph(s): "Principal Battery Management System (BMS) Engineer provides technical leadership, architectural ownership, and long-term stewardship of advanced battery management solutions. In this role, you define system-level technical direction, own key architecture decisions, and ensure regulatory and functional safety compliance while serving as the subject-matter expert across firmware, electronics, algorithms, and system integration. You will lead the evolution of multi-generation BMS platforms, guide cross-functional architectural decisions, and ensure solutions are robust, scalable, and aligned with current and future product roadmaps." Also maybe include work environment: "This role focuses on advanced Battery Management System engineering within an embedded systems and electronics environment. You will work with technologies such as embedded firmware, real-time systems, communication protocols (SPI, I2C, CAN, CANOpen, J1939, UDS), and safety and compliance frameworks (UL, IEC, ISO, functional safety guidance). The position involves close collaboration with cross-functional engineering teams, participation in design reviews and risk assessments, and engagement with manufacturing and test engineering to ensure designs are manufacturable, testable, and serviceable at scale. Work is primarily performed in an office and laboratory setting with access to development tools, diagnostic equipment, and test systems for batteries and power electronics." Also job type/location: "This is a Permanent position based out of Plymouth, MI." Could be included. We could combine all into About the role. Responsibilities: list bullet points from "Responsibilities" section. Let's extract each responsibility line: - Serve as the technical authority for BMS architecture, covering firmware, electronics, sensing, controls, and system integration. - Define and maintain system-level BMS architecture, design patterns, and technical standards across multiple product lines. - Lead technical trade studies that balance safety, performance, cost, manufacturability, and long-term maintainability. - Establish best practices for embedded firmware architecture, hardware abstraction, diagnostics, and fault handling. - Provide expert-level guidance on embedded firmware design, real-time systems, and safety-critical software. - Lead the development and review of core BMS algorithms, including state of charge (SOC), state of health (SOH), state of energy (SOE), cell balancing, protection, diagnostics, and degradation monitoring. - Own the interpretation and application of relevant safety and compliance standards such as UL, IEC, ISO, and functional safety guidance as they relate to BMS design. - Drive system-level requirements decomposition, traceability, and verification strategies to ensure complete coverage and robust performance. - Lead DFMEA, fault tree analysis (FTA), and system-level risk assessments, ensuring mitigation strategies are implemented, verified, and maintained. - Guide the development of end-of-line test strategies, diagnostic coverage, and service tools to support manufacturing and field service. - Ensure BMS designs are manufacturable, testable, and serviceable at scale for long-term product success. - Support long-term sustainment activities, reliability improvements, and continuous improvement initiatives across BMS platforms. - Perform other engineering and technical duties as needed to support product development and lifecycle management. We need to keep all. Requirements: Could be "Essential Skills" which includes education and experience. Essential Skills bullet list: - Master’s degree in Electrical Engineering, Computer Science, or Computer Engineering preferred, or a Bachelor’s degree in a related field with relevant certifications or graduate-level coursework. - 15+ years of embedded systems work experience. - 7+ years of experience working with battery or relevant energy systems preferred. - Recognized expertise in BMS firmware, electronics, and system-level design. - Deep understanding of lithium-ion battery behavior, protection strategies, and safety mechanisms. - Proven ability to define and evolve system architectures across multiple product generations. - Advanced proficiency with embedded communication protocols, including SPI, I2C, CAN, CANOpen, J1939, and UDS. - Strong experience with verification, validation, and compliance in regulated or safety-critical environments. - Exceptional analytical and problem-solving skills, including root-cause analysis of complex system issues. - Hands-on experience with battery management systems, algorithm development, system integration, and embedded controls. - Strong experience in embedded systems and systems architecture. - Experience with DFMEA and related system-level risk assessment methodologies. We could treat these as Requirements. Additional Skills & Qualifications list: - Graduate-level coursework or relevant certifications in embedded systems, controls, or safety-critical software development. - Experience defining and maintaining technical standards and design patterns across multiple product lines. - experience in functional safety frameworks and their application to BMS design. - Experience guiding cross-functional teams in system integration and architectural decision-making. - Strong communication skills to articulate complex technical concepts to diverse stakeholders. - Ability to mentor and influence engineering teams in best practices for firmware, hardware abstraction, diagnostics, and fault handling. We could merge with Requirements or Skills. Since we have both Requirements and Skills headings allowed, we could put the essential skills under Requirements, and additional skills under Skills. Or we could combine all under Skills. But we need to avoid thin sections. Perhaps better to have Requirements (education/experience) and Skills (technical skills). However the essential skills list includes both education/experience and technical skills. Could split: Requirements: education and years experience; Skills: technical expertise list. But we must preserve all substantive info; we can split. Let's define: - Requirements: education and experience (Master's/Bachelor's preferred, 15+ years embedded, 7+ years battery, etc). Also maybe include "Recognized expertise in BMS firmware, electronics, and system-level design." That's more skill. Hmm. Better to follow typical pattern: Requirements = mandatory qualifications (education, years experience). Skills = technical skills. Thus: Requirements (