Sr. Director – Software, Controls & Vehicle Systems

We need to output HTML fragment with sections only if content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting includes description, responsibilities, requirements, qualifications, skills etc. We need to parse. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO statement. Also remove application instructions (none present). Keep all substantive info. We need to decide sections: The posting includes description (overview), responsibilities (list of duties), requirements (education/experience), qualifications (maybe same as requirements), skills (maybe technical skills). Benefits, Pay, Schedule not present, so omit those sections. We must not create sections with filler like "commensurate with experience". So only include sections where we have real content. We need to use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to embed the content accordingly. Let's extract sections: - About the role: Could be the introductory paragraph(s) describing role. The description: "The Senior Director of Software, Controls & Vehicle Systems will lead the strategy, organization, architecture, development, integration, and validation of vehicle software and controls across Workhorse's current and future commercial vehicle platforms. Workhorse was formed through the merger of Workhorse Group and Motiv Electric Trucks. This leader will have an immediate organizational mandate to integrate the legacy Workhorse and Motiv Software & Controls teams into a single, high-performing organization with common processes, tools, architectures, technical standards, and accountability. The Senior Director will establish a scalable organizational structure that preserves the technical strengths and product knowledge of both legacy teams while creating a unified approach to future vehicle development. The role will also lead the transformation of Workhorse's software and controls capabilities to support next-generation electric and autonomous commercial vehicles. This includes establishing an AUTOSAR-based development strategy, strengthening functional safety and automotive cybersecurity capabilities, advancing model-based development and automated validation, and defining the vehicle-control architecture and interfaces necessary to support advanced ADAS and autonomous-driving systems. This position requires a leader who combines deep technical credibility with strong organizational leadership. The successful candidate must be capable of challenging technical decisions while creating an environment where engineers and cross-functional teams can openly debate alternatives, make decisions, and collectively own vehicle-level outcomes." That's a good prose for About the role. - Responsibilities: The bullet points under "Organizational Leadership & Team Integration", "Software & Controls Strategy and Architecture", "Autonomous Vehicle & Advanced Controls Development", "Functional Safety & Cybersecurity", "Software Development Process & Quality", "Current Product & Customer Support", "Supplier & Technology Partner Leadership". Those are responsibilities. We need to list them as

  • . Each bullet is a sentence or multiple sentences. We'll preserve content. - Requirements: The "Requirements" section includes bullet list of education/experience etc. We'll treat as Requirements. - Qualifications: Might be same as Requirements? The posting has "Requirements" then later "Highly Desired". Could treat "Requirements" as mandatory qualifications, and "Highly Desired" as preferred qualifications/skills. But we have headings: Qualifications, Skills. We could put mandatory requirements under Qualifications, and desired under Skills. Or we could put Requirements under Requirements heading, and Skills under Skills heading. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have separate headings for Requirements and Qualifications and Skills. We need to decide mapping. The posting has "Requirements" bullet list (education, experience). Then "Highly Desired Experience" bullet list. Could treat "Requirements" as Requirements section, and "Highly Desired" as Skills or Qualifications. Since Qualifications often refer to education/degrees, but we already have that in Requirements. Skills could be technical skills like AUTOSAR, functional safety, etc. The Highly Desired list includes many specific experiences: developing vehicle platforms for Level 2+ autonomy, defining vehicle-control interfaces, redundant/fail-operational controls, commercial vehicles, EV propulsion, telematics, managing globally distributed organizations, leading through mergers. Those are more like desired qualifications/skills. Thus we can put: - Requirements: Bachelor's degree ... 15+ years ... Significant leadership experience ... Demonstrated success integrating ... Deep experience with embedded automotive software ... Strong experience with AUTOSAR ... Demonstrated experience with automotive functional safety ... Strong automotive cybersecurity experience ... Experience developing or integrating safety-critical vehicle-control systems ... Experience with model-based development ... Strong understanding of automotive communications ... Demonstrated ability to lead effectively across organizational and functional boundaries. - Qualifications: maybe we could treat as same as Requirements? But we need to avoid duplication. Could omit Qualifications if content same as Requirements? But we need to include only when posting has real specific content. The posting does not have a separate "Qualifications" section besides Requirements. So we should not create a Qualifications heading with filler. So we omit Qualifications. - Skills: Could be the Highly Desired list. Or we could treat Skills as technical skills like AUTOSAR, functional safety, cybersecurity, model-based development, etc. But those are already in Requirements. However we can still list them under Skills if we want. But we must not duplicate content? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid redundancy. We could place the Highly Desired list under Skills, as they are desired skills/experience. That seems appropriate. Thus: - About the role: prose paragraph(s) as above. - Responsibilities: list of duties from the sections. - Requirements: list of mandatory requirements. - Skills: list of highly desired experience. We must not include Benefits, Pay, Schedule. Now we need to format. We need to wrap each section with

    heading then content. For About the role: use

    for prose. For Responsibilities: use

    • each duty. For Requirements: use
      • each bullet. For Skills: use
        • each bullet. We must preserve all substantive information; do not omit any detail. Let's extract responsibilities precisely. From the posting: Organizational Leadership & Team Integration: - Integrate the legacy Workhorse and Motiv Software & Controls organizations into one cohesive engineering team with clearly defined roles, responsibilities, technical ownership, and decision authority. - Develop and implement the future organizational structure for Software & Controls Engineering, including leadership roles, technical disciplines, staffing requirements, and capability-development plans. - Establish a culture of collaboration, technical rigor, accountability, constructive challenge, and vehicle-level ownership that operates around company and vehicle objectives rather than legacy organizational or functional boundaries - Develop managers and technical leaders who can make decisions and lead teams independently while maintaining appropriate architectural and technical governance. - Recruit and develop talent in embedded software, controls, AUTOSAR, cybersecurity, functional safety, diagnostics, telematics/cloud connectivity, vehicle integration, and automated validation. - Create effective working relationships across Electrical Engineering, Mechanical Engineering, Battery Systems, Test & Validation, Manufacturing, Field Service, Procurement, Program Management, and external technology partners. Software & Controls Strategy and Architecture: - Own the software and controls strategy for current and future Workhorse vehicle platforms. - Define a scalable vehicle software and controls architecture supporting multiple commercial vehicle platforms and configurations. - Establish clear ownership and governance for embedded software, vehicle controls, body controls, propulsion controls, diagnostics, communications, telematics, cloud interfaces, OTA capabilities, and vehicle-level supervisory controls. - Lead the transition toward an AUTOSAR-compliant software architecture and development environment, including appropriate application of Classic and Adaptive AUTOSAR. - Define standardized software interfaces and abstraction layers that reduce dependency on specific hardware suppliers and improve reuse across vehicle platforms. - Establish architectural standards for CAN/CAN-FD, Ethernet and other vehicle networks, diagnostics, communication protocols, and vehicle-level interfaces. - Drive software reuse, modularity, configurability, and commonality across vehicle programs to reduce development time, cost, and complexity. Autonomous Vehicle & Advanced Controls Development: - Lead Software & Controls activities supporting development of autonomous commercial vehicle platforms. - Define the vehicle-control architecture required to safely interface with ADAS and Level 4 autonomous-driving systems. - Establish standardized, secure vehicle-control interfaces/APIs for steering, braking, propulsion, gear selection, body controls, vehicle state, diagnostics, and other systems required by autonomy partners. - Lead development and integration of drive-by-wire and other safety-critical vehicle-control capabilities required for autonomous operation. - Establish clear interface ownership between Workhorse vehicle controls and third-party autonomy technology providers. - Ensure vehicle architecture supports appropriate redundancy, fault detection, degraded operating modes, safe-state behavior, diagnostics, and system health monitoring. - Work closely with autonomy development partners, suppliers, customers, and internal engineering teams to translate autonomous-driving requirements into production-capable vehicle systems. Functional Safety & Cybersecurity: - Establish and lead the company's automotive functional safety strategy and engineering processes consistent with ISO 26262. - Establish automotive cybersecurity engineering processes aligned with ISO/SAE 21434 and applicable regulatory requirements. - Integrate functional safety and cybersecurity activities into the complete product-development lifecycle, from concept and requirements through architecture, implementation, validation, production, and field support. - Establish processes for hazard analysis and risk assessment, functional and technical safety concepts, FMEA/FMEDA, safety requirements, safety cases, and verification and validation. - Establish cybersecurity risk assessment, threat analysis, secure communications, authentication, secure boot, software update, key management, vulnerability management, and incident-response strategies. - Ensure safety and cybersecurity requirements are incorporated into supplier requirements and technical agreements. Software Development Process & Quality: - Establish a common Software Development Lifecycle across the combined organization, including requirements management, architecture, design reviews, coding standards, configuration management, integration, verification, validation, and release. - Improve requirements traceability from vehicle-level requirements through system, software, and validation requirements. - Establish disciplined software release and configuration-management processes across all vehicle platforms. - Expand model-based software and controls development where appropriate. - Advance CI/CD practices, automated builds, automated testing, static analysis, code quality, and software metrics. - Expand SIL, MIL and HIL/HWIL capabilities and automated regression testing to improve test coverage and release confidence. - Partner with Test & Validation to establish integrated software and vehicle validation strategies and objective release criteria. - Establish metrics for software quality, requirements coverage, test coverage, defect escape, release performance, technical debt, and field reliability. Current Product & Customer Support: - Maintain strong engineering ownership of software and controls for existing Workhorse and legacy Motiv products while transforming the organization for future platforms. - Ensure customer, field, and manufacturing concerns receive appropriate priority and disciplined root-cause analysis. - Establish a vehicle-level problem-solving culture in which issues are investigated collaboratively before functional ownership is determined. - Improve closed-loop learning from field issues so that lessons learned are incorporated into requirements, architectures, design standards, and validation processes for future products. - Manage component obsolescence, supplier changes, software updates, and continuous product improvement for production vehicle platforms. Supplier & Technology Partner Leadership: - Provide technical leadership in the selection and management of software, controls, ECU, connectivity, cybersecurity, ADAS, and autonomy technology suppliers. - Establish software and controls requirements, interface-control documents, development expectations, validation requirements, and technical acceptance criteria for suppliers. - Evaluate build-versus-buy decisions and determine which software and controls capabilities represent strategic Workhorse intellectual property. - Manage technical relationships with external development partners while maintaining Workhorse ownership of vehicle architecture, integration, safety, and overall vehicle performance. Now Requirements bullet list: - Bachelor's degree in Electrical Engineering, Computer Engineering, Computer Science, Mechanical Engineering, or related technical discipline; advanced degree preferred. - 15+ years of progressively responsible automotive, commercial vehicle, or similar safety-critical embedded systems experience. - Significant leadership experience managing multidisciplinary software and controls engineering organizations. - Demonstrated success integrating, restructuring, or significantly scaling engineering teams. - Deep experience with embedded automotive software and vehicle-control systems.