Electrical Engineer - Vehicle Systems
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no invented details. Remove boilerplate like EEO, legal, etc. Also remove duplicated lines, application instructions. Must not include sections with filler like "commensurate with experience" etc. So we need to parse the posting. Let's extract content: Company Information: description of PACCAR and Peterbilt. Could be "About the role"? Actually "Company Information" is about the employer, not role. The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - Requisition Summary: "This position is available for an experienced electrical engineer designing vehicle systems. Hiring level will commensurate with experience and skills." This is vague; "Hiring level will commensurate with experience and skills" is filler (commensurate with experience). Should we include? The instruction says do NOT emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should not include a section if content is just that. The Requisition Summary includes also "This position is available for an experienced electrical engineer designing vehicle systems." That's substantive. Could be part of About the role? Possibly. - Job Responsibilities: list of responsibilities bullet points. - Required Qualifications: list. - Preferred Qualifications: list. - General Description Of All Benefits: list of benefits. - Additional Job Information: includes EEO etc (boilerplate) and diversity groups. The diversity groups maybe could be considered part of Benefits? But it's more about company culture. Might be considered as part of "About the role"? Not sure. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The diversity groups might be considered not boilerplate but still maybe not needed. However they are part of "Additional Job Information". Might be considered substantive? It's about diversity and inclusion groups. Could be considered part of "Benefits"? Not exactly. The instruction says only include sections when posting has real, specific content for it. The diversity groups are specific content. But the heading list does not include a "Diversity" heading. We could possibly put under "About the role" or maybe under "Benefits"? Not ideal. Perhaps we can omit that part as it's not covered by headings. The instruction says we should only use those headings; we can omit content that doesn't fit? But we must preserve ALL substantive information. However we cannot invent headings. If we cannot fit diversity info under any of the allowed headings, maybe we can include it under "About the role" as a paragraph describing company culture. That seems acceptable. Also "General Description Of All Benefits" is clearly Benefits. Pay and Schedule: not mentioned. So we should not include Pay or Schedule sections. Skills: we could extract from Required/Preferred Qualifications maybe as Skills section. But we already have Requirements and Qualifications headings. The instruction list includes both Requirements and Qualifications as separate headings. We need to decide what goes where. Typically Requirements = required qualifications; Qualifications = preferred qualifications? Or Skills = skills. We have both Required Qualifications and Preferred Qualifications. We could map Required Qualifications to "Requirements" heading, and Preferred Qualifications to "Qualifications" heading. Skills could be maybe derived from both but we might not need a separate Skills section if content is covered. However we must not create thin sections. If we have both Requirements and Qualifications, we can include them. Skills maybe not needed. About the role: we can include company overview and position summary. Thus sections: - About the role: include company information (PACCAR, Peterbilt) and the position summary: "This position is available for an experienced electrical engineer designing vehicle systems." - Responsibilities: list from Job Responsibilities. - Requirements: list from Required Qualifications. - Qualifications: list from Preferred Qualifications. - Benefits: list from General Description Of All Benefits. We should not include Pay or Schedule. We must not repeat job title. Not include Job ID etc. We must preserve all substantive information: ensure we include all bullet points from responsibilities, required quals, preferred quals, benefits. Also include company overview text. We must not include boilerplate like EEO, legal, etc. Also remove duplicated lines. Check for duplicates: The responsibilities list includes multiple lines; ensure we keep each. Let's extract bullet points exactly. Job Responsibilities (as given): - Responsible for engineering definition, development, design, validation, release, and production support of vehicle electrical systems and components, with emphasis on wiring harnesses and system integration. - Apply standard electrical engineering practices to support product development, problem resolution, validation activities, and production issues across multiple vehicle platforms. - Define, integrate, and support the placement of electrical and electronic components, harnesses, system interfaces, and harness routings across low‑voltage and high‑voltage architectures, including Battery Electric Vehicle (BEV) systems such as high‑voltage power distribution, equip bonding, grounding, and related safety components. - Support electrical system implementation for production builds, including documentation, design releases, and change management activities across vehicle programs. - Own assigned electrical components or subsystems, including requirements definition, interface coordination, validation planning, and maintenance of design documentation across the product lifecycle. - Must be able to work with a diverse set of stakeholders (PACCAR Divisions, Suppliers & Customers) and manage multiple tasks concurrently. - Up to 10 % travel can be expected We should keep these as
tags. Position summary: "This position is available for an experienced electrical engineer designing vehicle systems." We should not include the "Hiring level will commensurate with experience and skills." as filler. Thus About the role could have two
elements: one for company overview, one for position summary. Now ensure we don't include any boilerplate like EEO etc. The Additional Job Information includes EEO statement and diversity groups. We should remove EEO boilerplate. The diversity groups maybe could be considered part of About the role? But we already have company overview; we could add a sentence about diversity and inclusion groups as part of company overview. However the instruction says remove EEO/equal-opportunity/scam-warning boilerplate. Diversity groups are not exactly EEO boilerplate but they are part of diversity and inclusion initiatives. Might be considered substantive. But we have no heading for it; we could incorporate into About the role as an extra sentence. However we must be careful not to include the EEO statement line: "PACCAR is an Equal Opportunity Employer/Protected Veteran/Disability corporation." That's boilerplate; remove. The diversity council etc lines: "Peterbilt promotes Diversity and Inclusion through mentorship, events, and affinity support groups – The Diversity Council, Peterbilt Women’s Initiative (PBWIN), Veterans Group, Peterbilt Black Organization for Leadership and Development (B.O.L.D), and ADVOCATE (An LGBTQ support group)." This is substantive about company culture. We could include it in About the role as an additional paragraph. Thus About the role will have maybe three paragraphs: company overview, position summary, diversity and inclusion. Now check for any duplicated lines: none. Now produce HTML fragment:
About the role
...company overview...
...position summary...
...diversity and inclusion...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
- ... ...