Embedded Software and Cybersecurity Engineer, Ford Energy
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. Remove boilerplate, duplicated lines, application instructions. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". Pay/Schedule/Benefits only if posting actually states them.
We need to extract content: The posting includes:
- Intro about Ford Energy (About the role? maybe "About the role" or "About the company"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate sections based on content.
We have:
- "Why Ford Energy?" includes description of backing, competitive compensation package including performance-based bonuses, Ford vehicle discounts, opportunity to shape energy strategy. That's maybe Benefits.
- "In this position..." description of role: Embedded Software & Cybersecurity Engineer will design, develop, and secure embedded firmware... That's maybe About the role.
- Responsibilities: bullet list under "What you'll do..." with many items.
- Qualifications: "You'll have..." list.
- "Even better, you may have ..." list of nice-to-have.
- Location & Travel: location Dearborn, MI, hybrid-friendly, occasional travel.
- Benefits: list after "No matter what you choose, we offer a work life that works for you, including:" then bullet list of benefits.
- Pay: "This position is a salary grade 8 and ranges from $99,100–166,200."
- Schedule: Not explicitly given; maybe hybrid schedule? Not explicit schedule like full-time, part-time. There's mention of hybrid-friendly, occasional travel. Not a clear schedule. Probably we should not include Schedule unless explicit.
- Skills: Could be derived from qualifications but we have Qualifications section. The instruction says we can have Skills section separate if there is specific content. The posting includes qualifications and also "Even better, you may have ..." which could be considered Skills or Preferred Qualifications. We could combine into Qualifications and maybe Skills. But we need to follow instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content.
We have:
- About the role: description of role (the "In this position..." paragraph). Could be About the role.
- Responsibilities: bullet list under "What you'll do..."
- Requirements: Could be Qualifications (mandatory). Could treat as Requirements.
- Qualifications: maybe separate from Requirements? The posting has "Qualifications You'll have..." (mandatory) and "Even better, you may have ..." (preferred). Could map Requirements to mandatory qualifications, Skills to preferred? Or we could have Qualifications (mandatory) and Skills (preferred). But we need to avoid duplication.
Better: Use sections:
- About the role (h3) with paragraph describing role.
- Responsibilities (h3) with ul list of duties.
- Requirements (h3) with ul list of mandatory qualifications.
- Skills (h3) with ul list of preferred qualifications/nice-to-have.
- Benefits (h3) with ul list of benefits.
- Pay (h3) with p containing salary range.
- Possibly Location & Travel could be part of About the role or separate? Not in list of headings; we could omit or fold into About the role as a p.
We must not include sections with filler. Ensure we preserve all substantive information.
We need to remove boilerplate: EEO, visa sponsorship, legal, application instructions, etc. Also remove duplicated lines.
Let's extract content.
First, About the role paragraph:
From "In this position... The Embedded Software & Cybersecurity Engineer will design, develop, and secure the embedded firmware that powers Ford Energy's battery management and monitoring systems. You will own the software architecture running on microcontrollers and embedded processors within the BESS environment — writing and hardening the low-level code that reads sensors, manages state-of-charge logic, communicates over vehicle- and grid-grade protocols, and defends against sophisticated threats. Working in close coordination with Ford Auto Engineering and Ford Energy technical teams, this is a hands-on engineering role at the intersection of firmware development and cybersecurity, ensuring safe, reliable, and secure operation of safety-critical infrastructure."
That's the role description.
Now Responsibilities bullet list:
From "What you'll do..." after Responsibilities heading.
List items:
- Embedded Firmware Development & Architecture
- Design, develop, and maintain embedded C/C++ firmware for BMS controllers and battery monitoring electronics, including drivers, RTOS tasks, and control logic.
- Develop and maintain higher level applications that utilize Python, C#, Java.
- Architect secure-by-design firmware structures, including memory partitioning, secure bootloaders, and modular software layers that support both functional and security requirements.
- Implement Hardware Root of Trust, secure boot chains, code signing pipelines, and cryptographic key lifecycle management directly within embedded software.
- Develop and maintain low-level drivers and middleware for microcontroller peripherals (ADC, UART, SPI, CAN controllers) used in battery sensing and monitoring.
- Cybersecurity Architecture & Risk Management
- Lead cybersecurity architecture and TARA (Threat Analysis and Risk Assessment) for battery monitoring electronics and their firmware.
- Focus on mitigating risks related to sensor spoofing, unauthorized SOC manipulation, malicious commands, remote access, and firmware compromise through robust software design.
- Define and maintain testable cybersecurity requirements for BMS and monitoring functions, ensuring traceability from concept to release, and implement them directly in embedded code.
- Communication Stack & Secure Update Software
- Develop and secure embedded communication stacks, including CAN, SPI, Ethernet, and Modbus TCP protocol implementations.
- Design and implement secure OTA (Over-the-Air) and field update firmware, including bootloader-level authentication, anti-rollback protection, and fail-safe recovery/rollback logic.
- Design and implement algorithms for state of charge (SOC) and state of health (SOH), thermal management, and fault detection.
- Build and integrate embedded intrusion/anomaly detection routines into firmware for real-time attack awareness at the edge.
- Validation, Testing & Response
- Write and execute unit, integration, and hardware-in-the-loop (HIL) tests for embedded firmware; support vulnerability analysis, penetration testing, and fuzz testing on battery monitoring and connected interfaces.
- Debug firmware issues using JTAG/SWD, logic analyzers, and oscilloscopes; lead issue remediation planning and establish response processes for product vulnerabilities and field issues.
- Develop technical security case materials and evidence for design gates, audits, and compliance reviews.
- Cross-Functional Co-Engineering
- Collaborate with software, controls, and safety teams to ensure embedded security controls are compatible with functional safety and safe-state behavior.
- Align with Ford Energy Engineering and global suppliers on shared firmware architecture, release, and implementation standards.
- Communicate technical security risks, tradeoffs, and firmware design decisions to executive-level stakeholders.
We need to flatten into ul li items. Could keep sub-bullets? Probably just a flat list; but we can keep nested ul? The instruction says use
- for any list of duties/requirements/benefits. It doesn't forbid nested lists, but we can keep simple.
We'll produce a
with each bullet as - . Might be long but okay.
Now Requirements (mandatory qualifications):
From "Qualifications You'll have..." list:
- Bachelor's degree in Electrical, Computer, or Systems Engineering, Computer Science, or Cybersecurity or equivalent experience.
- 5+ years of embedded software/firmware development experience (C/C++, RTOS, microcontrollers) in BMS or battery electronics.
- Experience in embedded software, controls, or firmware development, preferably in energy storage, power electronics, EV, or renewable energy systems.
- Practical experience in TARA, cybersecurity architecture, and authoring technical security requirements implemented at the software level.
- Demonstrated experience with secure embedded design (Secure Boot, cryptographic implementation, bootloader development).
- Hands-on experience with embedded debugging tools (JTAG/SWD, oscilloscopes, logic analyzers) and unit/HIL test frameworks.
- Strong communication skills with the ability to navigate cross-functional engineering teams.
Now Skills (preferred/nice-to-have):
From "Even better, you may have ..." list:
- Master's degree in a relevant technical field.
- Experience with AUTOSAR, embedded Linux, or other software platforms.
- Direct experience with IEC 61508/62443, NERC CIP, or NIST SP 800-82 frameworks.
- Familiarity with functional safety (ISO 26262) and the co-engineering of safety and security in embedded systems.
- Experience developing secure OTA update mechanisms and vulnerability response firmware in a utility-scale environment.
- Deep knowledge of communication protocol stacks such as Modbus TCP, Ethernet, and CAN-FD at the driver/software level.
- Security-Minded Firmware Architect who views cybersecurity as a fundamental pillar of embedded software design, grid-scale safety, and reliability.
- Collaborative Technical Lead capable of bridging embedded software practices with industrial energy requirements.
- Analytical Problem Solver who can anticipate emerging threats and translate them into actionable firmware and architecture requirements.
- Strategic Gatekeeper dedicated to ensuring the integrity of data and commands across the entire BESS software lifecycle.
Now Benefits:
From after "No matter what you choose, we offer a work life that works for you, including:" list:
- Immediate medical, dental, vision and prescription drug coverage
- Flexible family care days, paid parental leave, new parent ramp-up programs, subsidized back-up child care and more
- Family building benefits including adoption and surrogacy expense reimbursement, fertility treatments, and more
- Vehicle discount program for employees and family members
- Tuition assistance
- Established and active employee resource groups
- Paid time off for individual and team community service
- A generous schedule of paid holidays, including the week between Christmas and New Year’s Day
- Paid time off and the option to purchase additional vacation time
Also earlier "Why Ford Energy?" mentions competitive compensation package including performance-based bonuses, Ford vehicle discounts, and opportunity to shape energy strategy. That's also benefits but we already have vehicle discount etc. Could incorporate but not duplicate.
We should not duplicate. We'll include the benefits list as above.
Pay:
- "This position is a salary grade 8 and ranges from $99,100–166,200. Final determination of salary grade will be based on candidate's skills and experience, and base salary will be set within the applicable range according to job scope, responsibility and competitive market value."
We can put that in a
under Pay heading.
Schedule: Not explicit; we have hybrid-friendly, occasional travel. Not a schedule like full-time/part-time. Probably we should not include Schedule section.
Location & Travel: Not in headings list; we could fold into About the role as a paragraph.
We need to preserve all substantive information; we can include location and travel details in About the role or maybe a separate section not in headings list? The instruction says use headings for those specific sections; we can add other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for sections; we could also add other headings if needed but better to stick to those. We can include location/travel details in About the role paragraph.
Thus About the role paragraph will include description plus location/hybrid/travel.
Let's craft About the role paragraph:
"Ford Energy is a newly formed, wholly owned subsidiary of Ford Motor Company dedicated to accelerating US energy independence. Leveraging Ford’s century of manufacturing excellence and world-class battery
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, duplicated lines, application instructions. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". Pay/Schedule/Benefits only if posting actually states them. We need to extract content: The posting includes: - Intro about Ford Energy (About the role? maybe "About the role" or "About the company"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate sections based on content. We have: - "Why Ford Energy?" includes description of backing, competitive compensation package including performance-based bonuses, Ford vehicle discounts, opportunity to shape energy strategy. That's maybe Benefits. - "In this position..." description of role: Embedded Software & Cybersecurity Engineer will design, develop, and secure embedded firmware... That's maybe About the role. - Responsibilities: bullet list under "What you'll do..." with many items. - Qualifications: "You'll have..." list. - "Even better, you may have ..." list of nice-to-have. - Location & Travel: location Dearborn, MI, hybrid-friendly, occasional travel. - Benefits: list after "No matter what you choose, we offer a work life that works for you, including:" then bullet list of benefits. - Pay: "This position is a salary grade 8 and ranges from $99,100–166,200." - Schedule: Not explicitly given; maybe hybrid schedule? Not explicit schedule like full-time, part-time. There's mention of hybrid-friendly, occasional travel. Not a clear schedule. Probably we should not include Schedule unless explicit. - Skills: Could be derived from qualifications but we have Qualifications section. The instruction says we can have Skills section separate if there is specific content. The posting includes qualifications and also "Even better, you may have ..." which could be considered Skills or Preferred Qualifications. We could combine into Qualifications and maybe Skills. But we need to follow instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have: - About the role: description of role (the "In this position..." paragraph). Could be About the role. - Responsibilities: bullet list under "What you'll do..." - Requirements: Could be Qualifications (mandatory). Could treat as Requirements. - Qualifications: maybe separate from Requirements? The posting has "Qualifications You'll have..." (mandatory) and "Even better, you may have ..." (preferred). Could map Requirements to mandatory qualifications, Skills to preferred? Or we could have Qualifications (mandatory) and Skills (preferred). But we need to avoid duplication. Better: Use sections: - About the role (h3) with paragraph describing role. - Responsibilities (h3) with ul list of duties. - Requirements (h3) with ul list of mandatory qualifications. - Skills (h3) with ul list of preferred qualifications/nice-to-have. - Benefits (h3) with ul list of benefits. - Pay (h3) with p containing salary range. - Possibly Location & Travel could be part of About the role or separate? Not in list of headings; we could omit or fold into About the role as a p. We must not include sections with filler. Ensure we preserve all substantive information. We need to remove boilerplate: EEO, visa sponsorship, legal, application instructions, etc. Also remove duplicated lines. Let's extract content. First, About the role paragraph: From "In this position... The Embedded Software & Cybersecurity Engineer will design, develop, and secure the embedded firmware that powers Ford Energy's battery management and monitoring systems. You will own the software architecture running on microcontrollers and embedded processors within the BESS environment — writing and hardening the low-level code that reads sensors, manages state-of-charge logic, communicates over vehicle- and grid-grade protocols, and defends against sophisticated threats. Working in close coordination with Ford Auto Engineering and Ford Energy technical teams, this is a hands-on engineering role at the intersection of firmware development and cybersecurity, ensuring safe, reliable, and secure operation of safety-critical infrastructure." That's the role description. Now Responsibilities bullet list: From "What you'll do..." after Responsibilities heading. List items: - Embedded Firmware Development & Architecture - Design, develop, and maintain embedded C/C++ firmware for BMS controllers and battery monitoring electronics, including drivers, RTOS tasks, and control logic. - Develop and maintain higher level applications that utilize Python, C#, Java. - Architect secure-by-design firmware structures, including memory partitioning, secure bootloaders, and modular software layers that support both functional and security requirements. - Implement Hardware Root of Trust, secure boot chains, code signing pipelines, and cryptographic key lifecycle management directly within embedded software. - Develop and maintain low-level drivers and middleware for microcontroller peripherals (ADC, UART, SPI, CAN controllers) used in battery sensing and monitoring. - Cybersecurity Architecture & Risk Management - Lead cybersecurity architecture and TARA (Threat Analysis and Risk Assessment) for battery monitoring electronics and their firmware. - Focus on mitigating risks related to sensor spoofing, unauthorized SOC manipulation, malicious commands, remote access, and firmware compromise through robust software design. - Define and maintain testable cybersecurity requirements for BMS and monitoring functions, ensuring traceability from concept to release, and implement them directly in embedded code. - Communication Stack & Secure Update Software - Develop and secure embedded communication stacks, including CAN, SPI, Ethernet, and Modbus TCP protocol implementations. - Design and implement secure OTA (Over-the-Air) and field update firmware, including bootloader-level authentication, anti-rollback protection, and fail-safe recovery/rollback logic. - Design and implement algorithms for state of charge (SOC) and state of health (SOH), thermal management, and fault detection. - Build and integrate embedded intrusion/anomaly detection routines into firmware for real-time attack awareness at the edge. - Validation, Testing & Response - Write and execute unit, integration, and hardware-in-the-loop (HIL) tests for embedded firmware; support vulnerability analysis, penetration testing, and fuzz testing on battery monitoring and connected interfaces. - Debug firmware issues using JTAG/SWD, logic analyzers, and oscilloscopes; lead issue remediation planning and establish response processes for product vulnerabilities and field issues. - Develop technical security case materials and evidence for design gates, audits, and compliance reviews. - Cross-Functional Co-Engineering - Collaborate with software, controls, and safety teams to ensure embedded security controls are compatible with functional safety and safe-state behavior. - Align with Ford Energy Engineering and global suppliers on shared firmware architecture, release, and implementation standards. - Communicate technical security risks, tradeoffs, and firmware design decisions to executive-level stakeholders. We need to flatten into ul li items. Could keep sub-bullets? Probably just a flat list; but we can keep nested ul? The instruction says use
- for any list of duties/requirements/benefits. It doesn't forbid nested lists, but we can keep simple.
We'll produce a
- with each bullet as
- . Might be long but okay.
Now Requirements (mandatory qualifications):
From "Qualifications You'll have..." list:
- Bachelor's degree in Electrical, Computer, or Systems Engineering, Computer Science, or Cybersecurity or equivalent experience.
- 5+ years of embedded software/firmware development experience (C/C++, RTOS, microcontrollers) in BMS or battery electronics.
- Experience in embedded software, controls, or firmware development, preferably in energy storage, power electronics, EV, or renewable energy systems.
- Practical experience in TARA, cybersecurity architecture, and authoring technical security requirements implemented at the software level.
- Demonstrated experience with secure embedded design (Secure Boot, cryptographic implementation, bootloader development).
- Hands-on experience with embedded debugging tools (JTAG/SWD, oscilloscopes, logic analyzers) and unit/HIL test frameworks.
- Strong communication skills with the ability to navigate cross-functional engineering teams.
Now Skills (preferred/nice-to-have):
From "Even better, you may have ..." list:
- Master's degree in a relevant technical field.
- Experience with AUTOSAR, embedded Linux, or other software platforms.
- Direct experience with IEC 61508/62443, NERC CIP, or NIST SP 800-82 frameworks.
- Familiarity with functional safety (ISO 26262) and the co-engineering of safety and security in embedded systems.
- Experience developing secure OTA update mechanisms and vulnerability response firmware in a utility-scale environment.
- Deep knowledge of communication protocol stacks such as Modbus TCP, Ethernet, and CAN-FD at the driver/software level.
- Security-Minded Firmware Architect who views cybersecurity as a fundamental pillar of embedded software design, grid-scale safety, and reliability.
- Collaborative Technical Lead capable of bridging embedded software practices with industrial energy requirements.
- Analytical Problem Solver who can anticipate emerging threats and translate them into actionable firmware and architecture requirements.
- Strategic Gatekeeper dedicated to ensuring the integrity of data and commands across the entire BESS software lifecycle.
Now Benefits:
From after "No matter what you choose, we offer a work life that works for you, including:" list:
- Immediate medical, dental, vision and prescription drug coverage
- Flexible family care days, paid parental leave, new parent ramp-up programs, subsidized back-up child care and more
- Family building benefits including adoption and surrogacy expense reimbursement, fertility treatments, and more
- Vehicle discount program for employees and family members
- Tuition assistance
- Established and active employee resource groups
- Paid time off for individual and team community service
- A generous schedule of paid holidays, including the week between Christmas and New Year’s Day
- Paid time off and the option to purchase additional vacation time
Also earlier "Why Ford Energy?" mentions competitive compensation package including performance-based bonuses, Ford vehicle discounts, and opportunity to shape energy strategy. That's also benefits but we already have vehicle discount etc. Could incorporate but not duplicate.
We should not duplicate. We'll include the benefits list as above.
Pay:
- "This position is a salary grade 8 and ranges from $99,100–166,200. Final determination of salary grade will be based on candidate's skills and experience, and base salary will be set within the applicable range according to job scope, responsibility and competitive market value."
We can put that in a
under Pay heading. Schedule: Not explicit; we have hybrid-friendly, occasional travel. Not a schedule like full-time/part-time. Probably we should not include Schedule section. Location & Travel: Not in headings list; we could fold into About the role as a paragraph. We need to preserve all substantive information; we can include location and travel details in About the role or maybe a separate section not in headings list? The instruction says use headings for those specific sections; we can add other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for sections; we could also add other headings if needed but better to stick to those. We can include location/travel details in About the role paragraph. Thus About the role paragraph will include description plus location/hybrid/travel. Let's craft About the role paragraph: "Ford Energy is a newly formed, wholly owned subsidiary of Ford Motor Company dedicated to accelerating US energy independence. Leveraging Ford’s century of manufacturing excellence and world-class battery
- . Might be long but okay.
Now Requirements (mandatory qualifications):
From "Qualifications You'll have..." list:
- Bachelor's degree in Electrical, Computer, or Systems Engineering, Computer Science, or Cybersecurity or equivalent experience.
- 5+ years of embedded software/firmware development experience (C/C++, RTOS, microcontrollers) in BMS or battery electronics.
- Experience in embedded software, controls, or firmware development, preferably in energy storage, power electronics, EV, or renewable energy systems.
- Practical experience in TARA, cybersecurity architecture, and authoring technical security requirements implemented at the software level.
- Demonstrated experience with secure embedded design (Secure Boot, cryptographic implementation, bootloader development).
- Hands-on experience with embedded debugging tools (JTAG/SWD, oscilloscopes, logic analyzers) and unit/HIL test frameworks.
- Strong communication skills with the ability to navigate cross-functional engineering teams.
Now Skills (preferred/nice-to-have):
From "Even better, you may have ..." list:
- Master's degree in a relevant technical field.
- Experience with AUTOSAR, embedded Linux, or other software platforms.
- Direct experience with IEC 61508/62443, NERC CIP, or NIST SP 800-82 frameworks.
- Familiarity with functional safety (ISO 26262) and the co-engineering of safety and security in embedded systems.
- Experience developing secure OTA update mechanisms and vulnerability response firmware in a utility-scale environment.
- Deep knowledge of communication protocol stacks such as Modbus TCP, Ethernet, and CAN-FD at the driver/software level.
- Security-Minded Firmware Architect who views cybersecurity as a fundamental pillar of embedded software design, grid-scale safety, and reliability.
- Collaborative Technical Lead capable of bridging embedded software practices with industrial energy requirements.
- Analytical Problem Solver who can anticipate emerging threats and translate them into actionable firmware and architecture requirements.
- Strategic Gatekeeper dedicated to ensuring the integrity of data and commands across the entire BESS software lifecycle.
Now Benefits:
From after "No matter what you choose, we offer a work life that works for you, including:" list:
- Immediate medical, dental, vision and prescription drug coverage
- Flexible family care days, paid parental leave, new parent ramp-up programs, subsidized back-up child care and more
- Family building benefits including adoption and surrogacy expense reimbursement, fertility treatments, and more
- Vehicle discount program for employees and family members
- Tuition assistance
- Established and active employee resource groups
- Paid time off for individual and team community service
- A generous schedule of paid holidays, including the week between Christmas and New Year’s Day
- Paid time off and the option to purchase additional vacation time
Also earlier "Why Ford Energy?" mentions competitive compensation package including performance-based bonuses, Ford vehicle discounts, and opportunity to shape energy strategy. That's also benefits but we already have vehicle discount etc. Could incorporate but not duplicate.
We should not duplicate. We'll include the benefits list as above.
Pay:
- "This position is a salary grade 8 and ranges from $99,100–166,200. Final determination of salary grade will be based on candidate's skills and experience, and base salary will be set within the applicable range according to job scope, responsibility and competitive market value."
We can put that in a