Principal Engineer - Controls
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include details from the posting.
We need to avoid repeating job title as heading; we won't.
We need to drop Job ID/requisition numbers (none present). Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to strip out the EEO statement, accommodation contact, etc. Also remove "Oshkosh is committed to working with..." etc. Also remove "Certain positions..." etc. Also remove "Beyond offering a competitive total rewards package..." maybe that's not specific benefit, but it's a statement about benefits; but we cannot create Benefits section unless specific. However we could include that sentence in About the role? It's not about role. Might be considered boilerplate? It's a generic statement about total rewards. Might be considered boilerplate; but it's not EEO. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This statement is not exactly those categories, but it's a generic benefits statement. Since we are not creating Benefits section, we could either omit it or include it somewhere else? The rule: Preserve ALL substantive information; do NOT invent or summarize away detail. If we omit that sentence, we lose substantive info about benefits. However we are not allowed to create Benefits section unless posting actually states them. It does state "Beyond offering a competitive total rewards package, we prioritize a people-first culture and offer various opportunities to support team member growth and success." That's a statement about benefits/culture. Could we put that under About the role? Not really. Could we create a Benefits section with that content? The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state a competitive total rewards package and opportunities for growth. That is somewhat specific? It's vague but still a statement. I'd argue we can include a Benefits section with that sentence. However the rule also says: Prefer a few substantive sections over many thin ones. So maybe we can incorporate that into About the role or another section. But About the role is about the role, not benefits. Could we create a "Benefits" section with that sentence? It's not a list, just prose. Use
. That seems okay.
But we need to check if the posting actually states benefits: It says "Beyond offering a competitive total rewards package, we prioritize a people-first culture and offer various opportunities to support team member growth and success." That's a benefit statement. So we can include Benefits section with that sentence.
Now we need to ensure we don't include filler like "commensurate with experience". Not present.
Now we need to structure.
Sections:
- About the role: paragraph describing the role: "The Principal Engineer – Controls works within engineering groups to lead the exploration of applicable technologies and systems and methods for vehicle control strategies. Develops and implements advanced strategies and system level requirements for vehicle control systems. Controls work encompassing control strategy development and verification for engine, hybrid, and electric vehicles, for components (electronic control modules, motors, drives, engines, generators, energy storage cells, sensors, etc.), and for autonomous vehicle systems, suspensions systems, material handling systems, and other auxiliary systems for on-road and off-road applications."
That's a block of prose; we can put in
.
- Responsibilities: list of duties from "Your Impact" and other duties. Let's extract bullet points:
Your Impact:
- Responsible for the technical completion of a project or part of a project of moderate complexity and managing the controls schedule for the project.
- May be responsible for managing multiple priorities.
- Performs more complex engineering calculations, investigations, and tasks.
- Deliver results according to Oshkosh and general industry engineering standards and processes.
- Responsible for preparation and delivery of plans, designs, computation methods, and/or reporting.
- Work in collaboration with software engineering, and other engineering groups or business support disciplines as well as external component suppliers.
- May have exposure to external customers and/or industry organizations.
- Provide guidance or mentorship to entry level engineers working on common projects.
- Research, create, and update standard engineering methodology and procedures - best practices, etc.
- Responsible for vehicle system controls research, development, verification and validation, testing and production implementation.
- Establish requirements (resources, equipment, estimates, test plans, and milestones) according to the needs of a project.
- Responsible for developing control strategies in a virtual simulation environment using modeling tools (such as ADAMS, Matlab/Simulink/State flow, AMEsim, etc.) or hardware-in-the-loop simulators and transferring simulated strategies to vehicle testing and eventual production implementation.
- Work with internal and external (industry consortiums, universities...) project teams on advanced control development efforts and on component development efforts
- Assist feasibility studies and project estimates (manpower, budget development, timelines) on proposed projects.
- Support proposal development with regards to acquiring appropriate funding for various advanced control development efforts.
- Other duties as assigned.
- Regular attendance is required.
We need to put these as
- items.
- Requirements: Minimum Qualifications: "Accredited Bachelor's degree in mechnical/electrical Engineering or related field with five (5) or more years of related experience." Note typo "mechnical". Keep as is.
- Qualifications: Standout Qualifications: list:
- Bachelor's degree in mechanical or electrical Engineering and eight (8) or more years of related experience
- Master’s degree in mechanical or electrical Engineering and five (5) or more years of related experience
- Ph.D. degree in mechanical or electrical Engineering with two (2) or more years of related experience
- Automotive or heavy-duty vehicle background with vehicle control system experience.
- Work experience in automotive or heavy-duty vehicle CAN bus and architecture.
- Work experience in Mathworks, dSPACE or Vector tools and Autosar.
- Embedded software development experiences using C/C++/C# or Python a plus.
We need to preserve exactly.
- Skills: Core Competencies: This is a long list broken into categories: Internal Contacts, External Contacts, Communication Skills, Decision-Making, Complexity, Judgment and Problem Solving, Supervisory/Managerial, Working Conditions (Physical Demands, Non-Physical Demands, Environmental Demands), Demands/Deadlines.
We need to decide if we treat Core Competencies as Skills section. The heading "Skills" is allowed. We'll put the core competencies content under Skills.
We need to format as
- for any list. The core competencies includes paragraphs with bullet-like sentences but not explicit list. We could convert each sentence into a list item. However the instruction: Use
- for any list of duties/requirements/benefits. For prose, use
. The core competencies is not a list but a set of categories with descriptions. Could be considered prose. But we could break into
for each category. However to preserve all detail, we could keep as
with the whole block. But that might be long. The instruction: Prefer a few substantive sections over many thin ones. So we could keep as a single
containing the whole core competencies text.
But we need to ensure we don't lose any detail. We'll include the whole block as a
.
- Benefits: we have statement: "Beyond offering a competitive total rewards package, we prioritize a people-first culture and offer various opportunities to support team member growth and success." We'll put as
.
- Pay: Pay Range $91,500.00 - $148,100.00 plus explanation: "The above pay range reflects the minimum and maximum target pay for the position across all U.S. locations. Within this range, individual pay is determined by various factors, including the scope and responsibilities of the role, the candidate's experience, education and skills, as well as the equity of pay among team members in similar positions." We'll put as
.
- Schedule: Work Schedule: Routine shift hours. Infrequent overtime, weekend, or shift rotation. Also Demands/Deadlines: "High volume and variable work demands and deadlines impose strain on routine basis or considerable stress intermittently; OR regular direct contacts with distressed individuals within the immediate work environment; and/or exposure to demands and pressures from persons other than immediate supervisor." This is part of Working Conditions but maybe we can include under Schedule? Actually schedule section should contain work schedule info. The Demands/Deadlines is more about working conditions. But we have no separate heading for Working Conditions. Could we incorporate Demands/Deadlines into Schedule? Might be odd. Better to include Demands/Deadlines under Schedule? The instruction: include a section ONLY when the posting has real, specific content for it. We have specific content for Work Schedule and also for Demands/Deadlines. But we don't have a heading for Demands/Deadlines. Could we treat Demands/Deadlines as part of Schedule? Not ideal. Could we create a separate section like "Working Conditions"? Not in allowed headings. The allowed headings are limited to those listed. So we must fit content into those headings. We could put Demands/Deadlines under Schedule as additional info, but that may be mixing. However the instruction says prefer a few substantive sections over many thin ones. So we could combine schedule and demands into Schedule section.
Thus Schedule section will include both Work Schedule and Demands/Deadlines.
Now we need to ensure we don't include boilerplate like EEO statements, accommodation contact, etc. Remove those.
Now produce HTML fragment.
Structure:
About the role
...
Responsibilities
- ...
...
Requirements
Accredited Bachelor's degree in mechnical/electrical Engineering or related field with five (5) or more years of related experience.
Qualifications
for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include details from the posting. We need to avoid repeating job title as heading; we won't. We need to drop Job ID/requisition numbers (none present). Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to strip out the EEO statement, accommodation contact, etc. Also remove "Oshkosh is committed to working with..." etc. Also remove "Certain positions..." etc. Also remove "Beyond offering a competitive total rewards package..." maybe that's not specific benefit, but it's a statement about benefits; but we cannot create Benefits section unless specific. However we could include that sentence in About the role? It's not about role. Might be considered boilerplate? It's a generic statement about total rewards. Might be considered boilerplate; but it's not EEO. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This statement is not exactly those categories, but it's a generic benefits statement. Since we are not creating Benefits section, we could either omit it or include it somewhere else? The rule: Preserve ALL substantive information; do NOT invent or summarize away detail. If we omit that sentence, we lose substantive info about benefits. However we are not allowed to create Benefits section unless posting actually states them. It does state "Beyond offering a competitive total rewards package, we prioritize a people-first culture and offer various opportunities to support team member growth and success." That's a statement about benefits/culture. Could we put that under About the role? Not really. Could we create a Benefits section with that content? The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state a competitive total rewards package and opportunities for growth. That is somewhat specific? It's vague but still a statement. I'd argue we can include a Benefits section with that sentence. However the rule also says: Prefer a few substantive sections over many thin ones. So maybe we can incorporate that into About the role or another section. But About the role is about the role, not benefits. Could we create a "Benefits" section with that sentence? It's not a list, just prose. Use
. That seems okay. But we need to check if the posting actually states benefits: It says "Beyond offering a competitive total rewards package, we prioritize a people-first culture and offer various opportunities to support team member growth and success." That's a benefit statement. So we can include Benefits section with that sentence. Now we need to ensure we don't include filler like "commensurate with experience". Not present. Now we need to structure. Sections: - About the role: paragraph describing the role: "The Principal Engineer – Controls works within engineering groups to lead the exploration of applicable technologies and systems and methods for vehicle control strategies. Develops and implements advanced strategies and system level requirements for vehicle control systems. Controls work encompassing control strategy development and verification for engine, hybrid, and electric vehicles, for components (electronic control modules, motors, drives, engines, generators, energy storage cells, sensors, etc.), and for autonomous vehicle systems, suspensions systems, material handling systems, and other auxiliary systems for on-road and off-road applications." That's a block of prose; we can put in
. - Responsibilities: list of duties from "Your Impact" and other duties. Let's extract bullet points: Your Impact: - Responsible for the technical completion of a project or part of a project of moderate complexity and managing the controls schedule for the project. - May be responsible for managing multiple priorities. - Performs more complex engineering calculations, investigations, and tasks. - Deliver results according to Oshkosh and general industry engineering standards and processes. - Responsible for preparation and delivery of plans, designs, computation methods, and/or reporting. - Work in collaboration with software engineering, and other engineering groups or business support disciplines as well as external component suppliers. - May have exposure to external customers and/or industry organizations. - Provide guidance or mentorship to entry level engineers working on common projects. - Research, create, and update standard engineering methodology and procedures - best practices, etc. - Responsible for vehicle system controls research, development, verification and validation, testing and production implementation. - Establish requirements (resources, equipment, estimates, test plans, and milestones) according to the needs of a project. - Responsible for developing control strategies in a virtual simulation environment using modeling tools (such as ADAMS, Matlab/Simulink/State flow, AMEsim, etc.) or hardware-in-the-loop simulators and transferring simulated strategies to vehicle testing and eventual production implementation. - Work with internal and external (industry consortiums, universities...) project teams on advanced control development efforts and on component development efforts - Assist feasibility studies and project estimates (manpower, budget development, timelines) on proposed projects. - Support proposal development with regards to acquiring appropriate funding for various advanced control development efforts. - Other duties as assigned. - Regular attendance is required. We need to put these as
- items.
- Requirements: Minimum Qualifications: "Accredited Bachelor's degree in mechnical/electrical Engineering or related field with five (5) or more years of related experience." Note typo "mechnical". Keep as is.
- Qualifications: Standout Qualifications: list:
- Bachelor's degree in mechanical or electrical Engineering and eight (8) or more years of related experience
- Master’s degree in mechanical or electrical Engineering and five (5) or more years of related experience
- Ph.D. degree in mechanical or electrical Engineering with two (2) or more years of related experience
- Automotive or heavy-duty vehicle background with vehicle control system experience.
- Work experience in automotive or heavy-duty vehicle CAN bus and architecture.
- Work experience in Mathworks, dSPACE or Vector tools and Autosar.
- Embedded software development experiences using C/C++/C# or Python a plus.
We need to preserve exactly.
- Skills: Core Competencies: This is a long list broken into categories: Internal Contacts, External Contacts, Communication Skills, Decision-Making, Complexity, Judgment and Problem Solving, Supervisory/Managerial, Working Conditions (Physical Demands, Non-Physical Demands, Environmental Demands), Demands/Deadlines.
We need to decide if we treat Core Competencies as Skills section. The heading "Skills" is allowed. We'll put the core competencies content under Skills.
We need to format as
- for any list. The core competencies includes paragraphs with bullet-like sentences but not explicit list. We could convert each sentence into a list item. However the instruction: Use
- for any list of duties/requirements/benefits. For prose, use
. The core competencies is not a list but a set of categories with descriptions. Could be considered prose. But we could break into
for each category. However to preserve all detail, we could keep as
with the whole block. But that might be long. The instruction: Prefer a few substantive sections over many thin ones. So we could keep as a single
containing the whole core competencies text. But we need to ensure we don't lose any detail. We'll include the whole block as a
. - Benefits: we have statement: "Beyond offering a competitive total rewards package, we prioritize a people-first culture and offer various opportunities to support team member growth and success." We'll put as
. - Pay: Pay Range $91,500.00 - $148,100.00 plus explanation: "The above pay range reflects the minimum and maximum target pay for the position across all U.S. locations. Within this range, individual pay is determined by various factors, including the scope and responsibilities of the role, the candidate's experience, education and skills, as well as the equity of pay among team members in similar positions." We'll put as
. - Schedule: Work Schedule: Routine shift hours. Infrequent overtime, weekend, or shift rotation. Also Demands/Deadlines: "High volume and variable work demands and deadlines impose strain on routine basis or considerable stress intermittently; OR regular direct contacts with distressed individuals within the immediate work environment; and/or exposure to demands and pressures from persons other than immediate supervisor." This is part of Working Conditions but maybe we can include under Schedule? Actually schedule section should contain work schedule info. The Demands/Deadlines is more about working conditions. But we have no separate heading for Working Conditions. Could we incorporate Demands/Deadlines into Schedule? Might be odd. Better to include Demands/Deadlines under Schedule? The instruction: include a section ONLY when the posting has real, specific content for it. We have specific content for Work Schedule and also for Demands/Deadlines. But we don't have a heading for Demands/Deadlines. Could we treat Demands/Deadlines as part of Schedule? Not ideal. Could we create a separate section like "Working Conditions"? Not in allowed headings. The allowed headings are limited to those listed. So we must fit content into those headings. We could put Demands/Deadlines under Schedule as additional info, but that may be mixing. However the instruction says prefer a few substantive sections over many thin ones. So we could combine schedule and demands into Schedule section. Thus Schedule section will include both Work Schedule and Demands/Deadlines. Now we need to ensure we don't include boilerplate like EEO statements, accommodation contact, etc. Remove those. Now produce HTML fragment. Structure:
About the role
...
Responsibilities
- ... ...
Requirements
Accredited Bachelor's degree in mechnical/electrical Engineering or related field with five (5) or more years of related experience.
Qualifications
- for any list of duties/requirements/benefits. For prose, use
- for any list. The core competencies includes paragraphs with bullet-like sentences but not explicit list. We could convert each sentence into a list item. However the instruction: Use