Safety Investigations Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Remove boilerplate like EEO, legal, scam warning, application instructions, etc. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About the role: The first paragraph: "The Ford Motor Credit Company team helps put people behind the wheels of great Ford and Lincoln vehicles. By partnering with dealerships, we provide financing, personalized service and professional expertise to thousands of dealers and millions of customers in over one hundred countries around the world." That's about the role/company. - Responsibilities: The "What You'll Do..." bullet list (though not bullet but sentences). It includes: Prepare presentations and reports, including engineering analysis and the coordination of special vehicle/component demonstrations, to be used in both technical and non-technical discussions with all levels of leadership. Work proactively with NHTSA and TC on government investigations and compliance audits. Collaborate with facing organizations in the development of service solutions for potential field issues. Create and maintain investigation documentation in accordance with document retention guidelines and submit regulatory documentation as necessary. Identify potential lessons-learned opportunities in support of the company's efforts to prevent future potential recalls through involvement in stop ships, Prevent Action Closures, Campaign Trends Task Force meetings, SDS development, and other initiatives. Also later there is a repeated list under "You'll have..." which seems like responsibilities again: Act as the lead technical investigator for internal and external safety defect and compliance investigations. Partner with cross-functional teams (Product Development, Manufacturing, Customer Service, Suppliers) to design special tests, conduct field surveys, and gather the facts necessary to evaluate potential safety and compliance risks. Establish and document Ford’s engineering positions using rigorous data analysis. Prepare comprehensive reports, presentations, and vehicle demonstrations for technical and non-technical audiences, including executive leadership. Work proactively with government agencies (e.g., NHTSA, Transport Canada) on investigations and compliance audits. Provide crucial technical assistance to the Office of General Counsel (OGC) and outside law firms. Identify global trends and "lessons learned" from field issues. Inject these insights back into the product development cycle (via stop ships, Task Forces, and design updates) to proactively prevent future recalls. Work seamlessly with regional peers and global teams to resolve complex, worldwide vehicle concerns. Create & maintain investigation documentation in accordance with document retention guidelines and submit regulatory documentation as necessary. Identify potential lessons-learned opportunities in support of the company’s efforts to prevent future potential recalls through involvement in stop ships, Prevent Action Closures, Campaign Trends Task Force meetings, SDS development, and other initiatives. Provide technical assistance to the OGC, Design Analysis, PD activities, and outside law firms as appropriate. We need to combine responsibilities without duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep all content, but we can combine similar sentences? Might be considered summarizing away detail if we merge duplicates. Safer to keep both sets as separate bullet points, even if overlapping. But we need to avoid duplication? The instruction says remove duplicated lines. So we should remove duplicated lines. So we need to deduplicate identical sentences. Many lines repeat. Let's identify unique responsibilities. List from first "What You'll Do...": 1. Prepare presentations and reports, including engineering analysis and the coordination of special vehicle/component demonstrations, to be used in both technical and non-technical discussions with all levels of leadership. 2. Work proactively with NHTSA and TC on government investigations and compliance audits. 3. Collaborate with facing organizations in the development of service solutions for potential field issues. 4. Create and maintain investigation documentation in accordance with document retention guidelines and submit regulatory documentation as necessary. 5. Identify potential lessons-learned opportunities in support of the company's efforts to prevent future potential recalls through involvement in stop ships, Prevent Action Closures, Campaign Trends Task Force meetings, SDS development, and other initiatives. Second list "You'll have..." (actually responsibilities again): - Act as the lead technical investigator for internal and external safety defect and compliance investigations. - Partner with cross-functional teams (Product Development, Manufacturing, Customer Service, Suppliers) to design special tests, conduct field surveys, and gather the facts necessary to evaluate potential safety and compliance risks. - Establish and document Ford’s engineering positions using rigorous data analysis. - Prepare comprehensive reports, presentations, and vehicle demonstrations for technical and non-technical audiences, including executive leadership. - Work proactively with government agencies (e.g., NHTSA, Transport Canada) on investigations and compliance audits. - Provide crucial technical assistance to the Office of General Counsel (OGC) and outside law firms. - Identify global trends and "lessons learned" from field issues. - Inject these insights back into the product development cycle (via stop ships, Task Forces, and design updates) to proactively prevent future recalls. - Work seamlessly with regional peers and global teams to resolve complex, worldwide vehicle concerns. - Create & maintain investigation documentation in accordance with document retention guidelines and submit regulatory documentation as necessary. - Identify potential lessons-learned opportunities in support of the company’s efforts to prevent future potential recalls through involvement in stop ships, Prevent Action Closures, Campaign Trends Task Force meetings, SDS development, and other initiatives. - Provide technical assistance to the OGC, Design Analysis, PD activities, and outside law firms as appropriate. Now we need to deduplicate identical lines. Some lines are similar but not identical: e.g., "Prepare presentations and reports, including engineering analysis and the coordination of special vehicle/component demonstrations, to be used in both technical and non-technical discussions with all levels of leadership." vs "Prepare comprehensive reports, presentations, and vehicle demonstrations for technical and non-technical audiences, including executive leadership." Not identical, keep both. "Work proactively with NHTSA and TC on government investigations and compliance audits." vs "Work proactively with government agencies (e.g., NHTSA, Transport Canada) on investigations and compliance audits." Slightly different; keep both. "Create and maintain investigation documentation in accordance with document retention guidelines and submit regulatory documentation as necessary." appears twice identical? First: "Create and maintain investigation documentation in accordance with document retention guidelines and submit regulatory documentation as necessary." Second: "Create & maintain investigation documentation in accordance with document retention guidelines and submit regulatory documentation as necessary." Slight difference: "&" vs "and". Not identical but essentially same. Might consider duplicate? The instruction says remove duplicated lines. Since they are not exactly same string, we might keep both? Safer to keep both? But they convey same meaning; removing one could be considered summarizing away detail? It's duplicate in meaning. I'd keep one to avoid redundancy. Choose one version. "Identify potential lessons-learned opportunities in support of the company's efforts to prevent future potential recalls through involvement in stop ships, Prevent Action Closures, Campaign Trends Task Force meetings, SDS development, and other initiatives." appears twice with slight variation: first says "company's efforts", second "company’s efforts". Essentially same. Keep one. Now responsibilities list should include all unique items. Now Requirements/Qualifications/Skills sections. We have "You'll have..." after responsibilities? Actually after "You'll have..." we have list of qualifications: Bachelor of Science Degree in Mechanical, Electrical Engineering, Software Engineering, Systems Engineering, or a related technical field. 5+ years of experience in engineering, quality assurance, systems safety, or defect investigation within complex hardware/software environments. Strong working knowledge of modern vehicle systems, electronic control units (ECUs), and system architecture. Exceptional analytical and problem-solving skills, with a proven ability to conduct rigorous root-cause analysis on highly complex technical issues. Outstanding communication skills; you must be able to translate dense engineering data into clear, defensible, and articulate arguments for executive and legal audiences. Ability to interface effectively with all levels of management. Then "Even better, you may have..." list: High emotional intelligence and interpersonal skills to effectively navigate high-pressure situations with diverse, cross-functional global teams. Even Better Hands-on experience in Software Development, Software Quality, or Advanced Driver Assistance Systems (ADAS) engineering. Prior experience interacting directly with regulatory bodies (NHTSA, Transport Canada, FAA, FDA) or managing government compliance audits. A strong understanding of automotive OEM product development lifecycles and manufacturing processes (Ford-specific experience is a plus, but not required). Experience providing technical assistance to legal teams, participating in legal investigations, or drafting regulatory documentation. Familiarity with functional safety standards such as ISO 26262. Then "You may not check every box..." is encouragement, not a section. Thus we can categorize: - Qualifications: Education and experience requirements (Bachelor degree, 5+ years experience, knowledge of vehicle systems, ECUs, architecture). Could be under "Qualifications". - Skills: Analytical, problem-solving, communication, ability to interface with management. Could be under "Skills". - Preferred qualifications / "Even better": Additional desirable skills/experience. Could be under "Skills" as well, or separate "Preferred Qualifications". But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use Qualifications for education/experience, Skills for abilities and preferred. We need to avoid filler like "commensurate with experience". Not present. Now Benefits: The paragraph after "As an established global company, we offer the benefit of choice..." includes list of benefits: 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 and management leases. 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 mention: "This position is leadership level 6 and ranges from $115,500-$218,100." That's Pay. Also schedule: "This position is hybrid with a requirement to be onsite four or more days per week." That's Schedule. Also note: "Visa sponsorship is not available for this position." That's maybe not a section; could be included in a short p under Requirements? But it's not a heading; we can include as a paragraph under maybe "Requirements" or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Visa sponsorship is minor metadata; we can fold into a short p maybe under Requirements or at end. But we need to preserve all substantive information; we can include a paragraph after sections maybe. Also: "Candidates for positions with Ford Motor Company must be legally authorized to work in the United States. Verification of employment eligibility will be required at the time of hire." Also minor metadata. Also EEO boilerplate: remove. Also "For more information on salary and benefits, click here: https://fordcareers.co/LL6" - that's application instruction? It's a link for more info; maybe considered application instructions; we should remove. Also "Internal applicants: moving into this role may result in an adjustment to your current compensation based on the posted pay range for this role, taking into consideration your qualifications and other relevant factors." That's about pay; could be included in Pay section. Now we need to output HTML fragment with sections. We'll decide sections: -

About the role

...

-

Responsibilities

• ... each responsibility

-

Qualifications

• ... education and experience requirements

-

Skills

• ... core skills and preferred qualifications