Sr. Technical Program Manager, Controls
Lucid Motors · Southfield, MI · 3 wk ago
Information TechnologyFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title. Use for each heading. Use
for each heading. Use - for lists. Use
for prose. Remove boilerplate: EEO, etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. Keep substantive info.
Let's parse the posting.
First paragraph: About Lucid (company description). This could be "About the role"? Actually "About Lucid" is company overview. The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading, but the content is about Lucid and the role. The posting says: "We are seeking a Senior Technical Program Manager, Controls Software to lead the development and delivery of vehicle controls software across current and future Lucid platforms." That's role description. So we can put that under About the role.
Then "Role" bullet list of responsibilities. That's responsibilities.
Then "Qualifications" list.
Then "Preferred" list (maybe under Skills? Actually "Preferred" includes specific experiences; could be under Skills or Qualifications. We'll treat as Skills.
Then "Education" maybe part of Qualifications? Could be under Qualifications as well.
Then "Compensation & Benefits:" includes benefits details. So Benefits section.
Pay: Not specified explicitly; they mention compensation package but not specific salary. So we should NOT create Pay section unless posting actually states them. It does not give a number or range, just says comprehensive benefits. So we should not include Pay.
Schedule: Not mentioned. So omit.
We also need to include maybe "About Lucid" as part of About the role. We'll include description.
We must remove boilerplate: EEO statements, accessibility, candidate data privacy, agency stuff, etc.
Also remove duplicated lines: there are two EEO paragraphs; remove both.
Also remove "Compensation & Benefits:" heading? We'll create Benefits section with Benefits
and then list.
We need to preserve all substantive information: company mission, role purpose, responsibilities list, qualifications list, preferred experience, education, benefits details.
Let's extract.
About Lucid paragraph: "At Lucid, we are creating exceptional mobility experiences through innovation to drive the world forward. Built on Lucid’s proprietary technology and software-defined vehicle architecture, our award-winning vehicles bring our “Compromise Nothing™” approach to the global automotive market. That means refusing to choose between performance and sustainability, design and engineering, ambition and integrity. In Lucid Air and Lucid Gravity, we have designed and built vehicles that have redefined their segments, combining exceptional range, performance, design, and expansive space in a single experience. We achieve this through deep vertical integration, with design, engineering, and production happening in-house across our global offices and manufacturing facilities. Our teams come from industries around the world, united by a shared commitment to excellence. By refusing to settle, you can help redefine what’s possible and shape the future of mobility. Lucid's mission is to inspire the adoption of sustainable energy through the creation of the world's most captivating luxury electric vehicles."
Then role statement: "We are seeking a Senior Technical Program Manager, Controls Software to lead the development and delivery of vehicle controls software across current and future Lucid platforms. This role will drive cross-functional execution across Controls Engineering, Systems Engineering, ECU Owners, Software Platform teams, Validation, Manufacturing, Vehicle Integration, and suppliers to ensure successful delivery from concept through production launch and series support. The ideal candidate combines strong technical acumen in automotive embedded software and systems with exceptional program leadership, risk management, and execution skills"
We can combine these into About the role.
Responsibilities: bullet list under "Role" heading:
- Lead end-to-end delivery of controls software features and functions across multiple vehicle programs.
- Drive program planning, execution, and launch readiness from requirements definition through production support.
- Manage technical risks, dependencies, issue resolution, and critical path activities across cross-functional teams.
- Partner with Controls Engineers, Systems Engineers, ECU Owners, Vehicle Feature Owners, and suppliers to ensure successful integration and delivery.
- Coordinate software development, integration, release planning, validation, and deployment activities.
- Drive vehicle-level system integration, interface management, and feature readiness reviews.
- Support software architecture discussions and technical tradeoff decisions to enable scalable and maintainable solutions.
- Coordinate verification and validation activities, defect resolution, and readiness assessments.
- Support manufacturing and end-of-line (EOL) software readiness, vehicle bring-up and launch activities.
- Drive continuous improvement of systems engineering, software development, and program management processes.
- Communicate program status, risks, and mitigation plans to leadership and executive stakeholders.
Qualifications (required):
- 8+ years of experience in automotive software, embedded systems, systems engineering, product development, or technical program management.
- 5+ years leading complex cross-functional software and hardware development programs.
- Proven track record delivering automotive embedded software systems from concept through production.
- Strong understanding of automotive software development, system integration, and product development lifecycles.
- Experience driving execution across organizations without direct authority.
- Experience in managing technical risks, schedules, dependencies, and supplier deliverables.
- Experience with Agile development methodologies, sprint planning, backlog management, and release planning.
- Strong communication and stakeholder management skills.
Preferred (maybe Skills):
- Automotive embedded software development experience.
- Experience with Software Defined Vehicle (SDV) architectures and vehicle software platforms.
- Experience with vehicle-level software integration and release management.
- Experience with Jama, 3DX, Jira, Confluence, or similar tools.
- Experience managing Tier-1 supplier software development and integration.
- Working knowledge of ISO 26262 Functional Safety.
- Experience working within ASPICE-compliant development processes.
Education:
- BS in Computer Engineering, Electrical Engineering, Computer Science, or related field.
- MS preferred.
- PMP, ASPICE, or ISO 26262 certifications are a plus.
We could put Education under Qualifications or separate. Since Qualifications heading is allowed, we could include education there. But we have Qualifications already; we could add education as part of Qualifications. However the instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list Education separately; we could put education under Qualifications. Or we could create a separate "Qualifications" heading for required qualifications and a "Skills" heading for preferred/experience. Education could be under Qualifications as well.
We'll do:
About the role
with paragraphs.
Responsibilities
with - ...
Qualifications
with required qualifications list plus education bullet points? Might be okay.
Skills
with preferred experience list.
Benefits
with benefits description.
We must not include Pay or Schedule.
Now format.
We need to ensure we don't include any boilerplate like "At Lucid, we don’t just welcome diversity - we celebrate it!" etc. Remove all EEO lines.
Also remove "Compensation & Benefits:" line but we will use Benefits heading.
Now produce HTML.
Let's craft.
About the role: combine company description and role statement into maybe two paragraphs.
Paragraph 1: company description.
Paragraph 2: role statement.
We'll output:
About the role
At Lucid, we are creating exceptional mobility experiences through innovation to drive the world forward. Built on Lucid’s proprietary technology and software-defined vehicle architecture, our award-winning vehicles bring our “Compromise Nothing™” approach to the global automotive market. That means refusing to choose between performance and sustainability, design and engineering, ambition and integrity. In Lucid Air and Lucid Gravity, we have designed and built vehicles that have redefined their segments, combining exceptional range, performance, design, and expansive space in a single experience. We achieve this through deep vertical integration, with design, engineering, and production happening in-house across our global offices and manufacturing facilities. Our teams come from industries around the world, united by a shared commitment to excellence. By refusing to settle, you can help redefine what’s possible and shape the future of mobility. Lucid's mission is to inspire the adoption of sustainable energy through the creation of the world's most captivating luxury electric vehicles.
We are seeking a Senior Technical Program Manager, Controls Software to lead the development and delivery of vehicle controls software across current and future Lucid platforms. This role will drive cross-functional execution across Controls Engineering, Systems Engineering, ECU Owners, Software Platform teams, Validation, Manufacturing, Vehicle Integration, and suppliers to ensure successful delivery from concept through production launch and series support. The ideal candidate combines strong technical acumen in automotive embedded software and systems with exceptional program leadership, risk management, and execution skills.
Then Responsibilities.
Responsibilities
- Lead end-to-end delivery of controls software features and functions across multiple vehicle programs.
- Drive program planning, execution, and launch readiness from requirements definition through production support.
- Manage technical risks, dependencies, issue resolution, and critical path activities across cross-functional teams.
- Partner with Controls Engineers, Systems Engineers, ECU Owners, Vehicle Feature Owners, and suppliers to ensure successful integration and delivery.
- Coordinate software development, integration, release planning, validation, and deployment activities.
- Drive vehicle-level system integration, interface management, and feature readiness reviews.
- Support software architecture discussions and technical tradeoff decisions to enable scalable and maintainable solutions.
- Coordinate verification and validation activities, defect resolution, and readiness assessments.
- Support manufacturing and end-of-line (EOL) software readiness, vehicle bring-up and launch activities.
- Drive continuous improvement of systems engineering, software development, and program management processes.
- Communicate program status, risks, and mitigation plans to leadership and executive stakeholders.
Qualifications:
Qualifications
- 8+ years of experience in automotive software, embedded systems, systems engineering, product development, or technical program management.
- 5+ years leading complex cross-functional software and hardware development programs.
- Proven track record delivering automotive embedded software systems from concept through production.
- Strong understanding of automotive software development, system integration, and product development lifecycles.
- Experience driving execution across organizations without direct authority.
- Experience in managing technical risks, schedules, dependencies, and supplier deliverables.
- Experience with Agile development methodologies, sprint planning, backlog management, and release planning.
- Strong communication and stakeholder management skills.
- BS in Computer Engineering, Electrical Engineering, Computer Science, or related field.
- MS preferred.
- PMP, ASPICE, or ISO 26262 certifications are a plus.
Skills:
Skills
- Automotive embedded software development experience.
- Experience with Software Defined Vehicle (SDV) architectures and vehicle software platforms.
- Experience with vehicle-level software integration and release management.
- Experience with Jama, 3DX, Jira, Confluence, or similar tools.
- Experience managing Tier-1 supplier software development and integration.
- Working knowledge of ISO 26262 Functional Safety.
- Experience working within ASPICE-compliant development processes.
Benefits:
Benefits
Lucid offers a comprehensive and competitive benefits package including medical, dental, and vision insurance; life and disability coverage; paid time off; paid holidays, paid sick leave; and a 401(k) retirement plan. Hourly/non-exempt employees accrue
for prose. Remove boilerplate: EEO, etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. Keep substantive info. Let's parse the posting. First paragraph: About Lucid (company description). This could be "About the role"? Actually "About Lucid" is company overview. The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading, but the content is about Lucid and the role. The posting says: "We are seeking a Senior Technical Program Manager, Controls Software to lead the development and delivery of vehicle controls software across current and future Lucid platforms." That's role description. So we can put that under About the role.
Then "Role" bullet list of responsibilities. That's responsibilities.
Then "Qualifications" list.
Then "Preferred" list (maybe under Skills? Actually "Preferred" includes specific experiences; could be under Skills or Qualifications. We'll treat as Skills.
Then "Education" maybe part of Qualifications? Could be under Qualifications as well.
Then "Compensation & Benefits:" includes benefits details. So Benefits section.
Pay: Not specified explicitly; they mention compensation package but not specific salary. So we should NOT create Pay section unless posting actually states them. It does not give a number or range, just says comprehensive benefits. So we should not include Pay.
Schedule: Not mentioned. So omit.
We also need to include maybe "About Lucid" as part of About the role. We'll include description.
We must remove boilerplate: EEO statements, accessibility, candidate data privacy, agency stuff, etc.
Also remove duplicated lines: there are two EEO paragraphs; remove both.
Also remove "Compensation & Benefits:" heading? We'll create Benefits section with Benefits
and then list.
We need to preserve all substantive information: company mission, role purpose, responsibilities list, qualifications list, preferred experience, education, benefits details.
Let's extract.
About Lucid paragraph: "At Lucid, we are creating exceptional mobility experiences through innovation to drive the world forward. Built on Lucid’s proprietary technology and software-defined vehicle architecture, our award-winning vehicles bring our “Compromise Nothing™” approach to the global automotive market. That means refusing to choose between performance and sustainability, design and engineering, ambition and integrity. In Lucid Air and Lucid Gravity, we have designed and built vehicles that have redefined their segments, combining exceptional range, performance, design, and expansive space in a single experience. We achieve this through deep vertical integration, with design, engineering, and production happening in-house across our global offices and manufacturing facilities. Our teams come from industries around the world, united by a shared commitment to excellence. By refusing to settle, you can help redefine what’s possible and shape the future of mobility. Lucid's mission is to inspire the adoption of sustainable energy through the creation of the world's most captivating luxury electric vehicles."
Then role statement: "We are seeking a Senior Technical Program Manager, Controls Software to lead the development and delivery of vehicle controls software across current and future Lucid platforms. This role will drive cross-functional execution across Controls Engineering, Systems Engineering, ECU Owners, Software Platform teams, Validation, Manufacturing, Vehicle Integration, and suppliers to ensure successful delivery from concept through production launch and series support. The ideal candidate combines strong technical acumen in automotive embedded software and systems with exceptional program leadership, risk management, and execution skills"
We can combine these into About the role.
Responsibilities: bullet list under "Role" heading:
- Lead end-to-end delivery of controls software features and functions across multiple vehicle programs.
- Drive program planning, execution, and launch readiness from requirements definition through production support.
- Manage technical risks, dependencies, issue resolution, and critical path activities across cross-functional teams.
- Partner with Controls Engineers, Systems Engineers, ECU Owners, Vehicle Feature Owners, and suppliers to ensure successful integration and delivery.
- Coordinate software development, integration, release planning, validation, and deployment activities.
- Drive vehicle-level system integration, interface management, and feature readiness reviews.
- Support software architecture discussions and technical tradeoff decisions to enable scalable and maintainable solutions.
- Coordinate verification and validation activities, defect resolution, and readiness assessments.
- Support manufacturing and end-of-line (EOL) software readiness, vehicle bring-up and launch activities.
- Drive continuous improvement of systems engineering, software development, and program management processes.
- Communicate program status, risks, and mitigation plans to leadership and executive stakeholders.
Qualifications (required):
- 8+ years of experience in automotive software, embedded systems, systems engineering, product development, or technical program management.
- 5+ years leading complex cross-functional software and hardware development programs.
- Proven track record delivering automotive embedded software systems from concept through production.
- Strong understanding of automotive software development, system integration, and product development lifecycles.
- Experience driving execution across organizations without direct authority.
- Experience in managing technical risks, schedules, dependencies, and supplier deliverables.
- Experience with Agile development methodologies, sprint planning, backlog management, and release planning.
- Strong communication and stakeholder management skills.
Preferred (maybe Skills):
- Automotive embedded software development experience.
- Experience with Software Defined Vehicle (SDV) architectures and vehicle software platforms.
- Experience with vehicle-level software integration and release management.
- Experience with Jama, 3DX, Jira, Confluence, or similar tools.
- Experience managing Tier-1 supplier software development and integration.
- Working knowledge of ISO 26262 Functional Safety.
- Experience working within ASPICE-compliant development processes.
Education:
- BS in Computer Engineering, Electrical Engineering, Computer Science, or related field.
- MS preferred.
- PMP, ASPICE, or ISO 26262 certifications are a plus.
We could put Education under Qualifications or separate. Since Qualifications heading is allowed, we could include education there. But we have Qualifications already; we could add education as part of Qualifications. However the instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list Education separately; we could put education under Qualifications. Or we could create a separate "Qualifications" heading for required qualifications and a "Skills" heading for preferred/experience. Education could be under Qualifications as well.
We'll do:
About the role
with paragraphs.
Responsibilities
with - ...
Qualifications
with required qualifications list plus education bullet points? Might be okay.
Skills
with preferred experience list.
Benefits
with benefits description.
We must not include Pay or Schedule.
Now format.
We need to ensure we don't include any boilerplate like "At Lucid, we don’t just welcome diversity - we celebrate it!" etc. Remove all EEO lines.
Also remove "Compensation & Benefits:" line but we will use Benefits heading.
Now produce HTML.
Let's craft.
About the role: combine company description and role statement into maybe two paragraphs.
Paragraph 1: company description.
Paragraph 2: role statement.
We'll output:
About the role
At Lucid, we are creating exceptional mobility experiences through innovation to drive the world forward. Built on Lucid’s proprietary technology and software-defined vehicle architecture, our award-winning vehicles bring our “Compromise Nothing™” approach to the global automotive market. That means refusing to choose between performance and sustainability, design and engineering, ambition and integrity. In Lucid Air and Lucid Gravity, we have designed and built vehicles that have redefined their segments, combining exceptional range, performance, design, and expansive space in a single experience. We achieve this through deep vertical integration, with design, engineering, and production happening in-house across our global offices and manufacturing facilities. Our teams come from industries around the world, united by a shared commitment to excellence. By refusing to settle, you can help redefine what’s possible and shape the future of mobility. Lucid's mission is to inspire the adoption of sustainable energy through the creation of the world's most captivating luxury electric vehicles.
We are seeking a Senior Technical Program Manager, Controls Software to lead the development and delivery of vehicle controls software across current and future Lucid platforms. This role will drive cross-functional execution across Controls Engineering, Systems Engineering, ECU Owners, Software Platform teams, Validation, Manufacturing, Vehicle Integration, and suppliers to ensure successful delivery from concept through production launch and series support. The ideal candidate combines strong technical acumen in automotive embedded software and systems with exceptional program leadership, risk management, and execution skills.
Then Responsibilities.
Responsibilities
- Lead end-to-end delivery of controls software features and functions across multiple vehicle programs.
- Drive program planning, execution, and launch readiness from requirements definition through production support.
- Manage technical risks, dependencies, issue resolution, and critical path activities across cross-functional teams.
- Partner with Controls Engineers, Systems Engineers, ECU Owners, Vehicle Feature Owners, and suppliers to ensure successful integration and delivery.
- Coordinate software development, integration, release planning, validation, and deployment activities.
- Drive vehicle-level system integration, interface management, and feature readiness reviews.
- Support software architecture discussions and technical tradeoff decisions to enable scalable and maintainable solutions.
- Coordinate verification and validation activities, defect resolution, and readiness assessments.
- Support manufacturing and end-of-line (EOL) software readiness, vehicle bring-up and launch activities.
- Drive continuous improvement of systems engineering, software development, and program management processes.
- Communicate program status, risks, and mitigation plans to leadership and executive stakeholders.
Qualifications:
Qualifications
- 8+ years of experience in automotive software, embedded systems, systems engineering, product development, or technical program management.
- 5+ years leading complex cross-functional software and hardware development programs.
- Proven track record delivering automotive embedded software systems from concept through production.
- Strong understanding of automotive software development, system integration, and product development lifecycles.
- Experience driving execution across organizations without direct authority.
- Experience in managing technical risks, schedules, dependencies, and supplier deliverables.
- Experience with Agile development methodologies, sprint planning, backlog management, and release planning.
- Strong communication and stakeholder management skills.
- BS in Computer Engineering, Electrical Engineering, Computer Science, or related field.
- MS preferred.
- PMP, ASPICE, or ISO 26262 certifications are a plus.
Skills:
Skills
- Automotive embedded software development experience.
- Experience with Software Defined Vehicle (SDV) architectures and vehicle software platforms.
- Experience with vehicle-level software integration and release management.
- Experience with Jama, 3DX, Jira, Confluence, or similar tools.
- Experience managing Tier-1 supplier software development and integration.
- Working knowledge of ISO 26262 Functional Safety.
- Experience working within ASPICE-compliant development processes.
Benefits:
Benefits
Lucid offers a comprehensive and competitive benefits package including medical, dental, and vision insurance; life and disability coverage; paid time off; paid holidays, paid sick leave; and a 401(k) retirement plan. Hourly/non-exempt employees accrue
Qualifications
with required qualifications list plus education bullet points? Might be okay.Skills
with preferred experience list.Benefits
with benefits description. We must not include Pay or Schedule. Now format. We need to ensure we don't include any boilerplate like "At Lucid, we don’t just welcome diversity - we celebrate it!" etc. Remove all EEO lines. Also remove "Compensation & Benefits:" line but we will use Benefits heading. Now produce HTML. Let's craft. About the role: combine company description and role statement into maybe two paragraphs. Paragraph 1: company description. Paragraph 2: role statement. We'll output:About the role
At Lucid, we are creating exceptional mobility experiences through innovation to drive the world forward. Built on Lucid’s proprietary technology and software-defined vehicle architecture, our award-winning vehicles bring our “Compromise Nothing™” approach to the global automotive market. That means refusing to choose between performance and sustainability, design and engineering, ambition and integrity. In Lucid Air and Lucid Gravity, we have designed and built vehicles that have redefined their segments, combining exceptional range, performance, design, and expansive space in a single experience. We achieve this through deep vertical integration, with design, engineering, and production happening in-house across our global offices and manufacturing facilities. Our teams come from industries around the world, united by a shared commitment to excellence. By refusing to settle, you can help redefine what’s possible and shape the future of mobility. Lucid's mission is to inspire the adoption of sustainable energy through the creation of the world's most captivating luxury electric vehicles.
We are seeking a Senior Technical Program Manager, Controls Software to lead the development and delivery of vehicle controls software across current and future Lucid platforms. This role will drive cross-functional execution across Controls Engineering, Systems Engineering, ECU Owners, Software Platform teams, Validation, Manufacturing, Vehicle Integration, and suppliers to ensure successful delivery from concept through production launch and series support. The ideal candidate combines strong technical acumen in automotive embedded software and systems with exceptional program leadership, risk management, and execution skills.
Then Responsibilities.Responsibilities
- Lead end-to-end delivery of controls software features and functions across multiple vehicle programs.
- Drive program planning, execution, and launch readiness from requirements definition through production support.
- Manage technical risks, dependencies, issue resolution, and critical path activities across cross-functional teams.
- Partner with Controls Engineers, Systems Engineers, ECU Owners, Vehicle Feature Owners, and suppliers to ensure successful integration and delivery.
- Coordinate software development, integration, release planning, validation, and deployment activities.
- Drive vehicle-level system integration, interface management, and feature readiness reviews.
- Support software architecture discussions and technical tradeoff decisions to enable scalable and maintainable solutions.
- Coordinate verification and validation activities, defect resolution, and readiness assessments.
- Support manufacturing and end-of-line (EOL) software readiness, vehicle bring-up and launch activities.
- Drive continuous improvement of systems engineering, software development, and program management processes.
- Communicate program status, risks, and mitigation plans to leadership and executive stakeholders.
Qualifications
- 8+ years of experience in automotive software, embedded systems, systems engineering, product development, or technical program management.
- 5+ years leading complex cross-functional software and hardware development programs.
- Proven track record delivering automotive embedded software systems from concept through production.
- Strong understanding of automotive software development, system integration, and product development lifecycles.
- Experience driving execution across organizations without direct authority.
- Experience in managing technical risks, schedules, dependencies, and supplier deliverables.
- Experience with Agile development methodologies, sprint planning, backlog management, and release planning.
- Strong communication and stakeholder management skills.
- BS in Computer Engineering, Electrical Engineering, Computer Science, or related field.
- MS preferred.
- PMP, ASPICE, or ISO 26262 certifications are a plus.
Skills
- Automotive embedded software development experience.
- Experience with Software Defined Vehicle (SDV) architectures and vehicle software platforms.
- Experience with vehicle-level software integration and release management.
- Experience with Jama, 3DX, Jira, Confluence, or similar tools.
- Experience managing Tier-1 supplier software development and integration.
- Working knowledge of ISO 26262 Functional Safety.
- Experience working within ASPICE-compliant development processes.
Benefits
Lucid offers a comprehensive and competitive benefits package including medical, dental, and vision insurance; life and disability coverage; paid time off; paid holidays, paid sick leave; and a 401(k) retirement plan. Hourly/non-exempt employees accrue