Embedded Controls Engineer IV
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists
- Use
for prose
- Do NOT repeat job title as heading
- Do NOT put Job ID/requisition numbers as headings
- Preserve ALL substantive information
- Remove boilerplate (EEO, equal opportunity, scam warnings, application instructions, etc.)
- Include section ONLY when posting has real, specific content
- Never emit heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Output ONLY HTML fragment, no /, no markdown code fences
Let me parse the content:
Job Summary: "The Embedded Controls Engineer IV plays an important role in advancing the design and performance of internal combustion engines (ICE), through engine development, data-driven analysis, engine controls system development, and design of system components. This position leverages data analytics, ATI Vision, and data acquisition tools to optimize system behavior, improve engine control, improve product reliability, and increase engine performance across a range of gaseous fueled applications."
Location: Waukesha, Wisconsin
Job type: Permanent
Salary: $120,000 - 150,000 per year
Work hours: 9am to 5pm
Education: Bachelors
Responsibilities: List of major responsibilities (bullet points)
Qualifications: Minimum Qualifications (list), Knowledge, Skills And Abilities (list), Preferred Qualifications (list)
Skills: A long comma-separated list at the end.
Also there's EEO boilerplate, Randstad Digital benefits info, posting duration - these should be removed.
Now, I need to structure sections:
1. About the role (Job Summary) - prose
2. Responsibilities - list
3. Requirements (Minimum Qualifications) - list
4. Qualifications (Knowledge, Skills And Abilities) - list? Or combine with requirements? The heading "Qualifications" could cover both minimum and preferred. But the rules say use headings like "Requirements", "Qualifications". I'll do "Requirements" for minimum, "Preferred qualifications" for preferred, and maybe "Skills" for the skills list.
But the rules: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I can use "Requirements" for minimum qualifications, "Qualifications" for knowledge/skills/abilities? Actually the posting has "Minimum Qualifications" and "Knowledge, Skills And Abilities" and "Preferred Qualifications". I'll create sections: "Requirements" for minimum qualifications, "Qualifications" for knowledge/skills/abilities, "Preferred qualifications" for preferred. But the rules say "Qualifications" as a heading example. I'll use "Requirements" for minimum, "Qualifications" for the knowledge/skills/abilities, and "Preferred qualifications" for preferred.
Alternatively, combine minimum and preferred under "Requirements" and "Preferred qualifications". I think better to have:
- About the role
- Responsibilities
- Requirements (minimum qualifications)
- Qualifications (knowledge, skills, abilities)
- Preferred qualifications
- Skills (the list)
- Pay (salary)
- Schedule (work hours)
- Location (maybe as a short p? Not a heading unless it's a section. The rules don't mention Location as a heading example. Could fold into a short p at top or in About the role. But the posting has location, job type, salary, work hours, education as metadata. The rules: "fold minor metadata into a short
or drop it." So I can put location, job type, education in a short paragraph at the beginning or in About the role. Salary and schedule have specific sections if they have real content. The posting states salary range and work hours, so I should include Pay and Schedule sections.
Benefits: The posting mentions benefits package but it's from Randstad Digital, not the employer? It says "Randstad Digital offers a comprehensive benefits package...". That's boilerplate from the recruiter. The rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". This includes benefits description from recruiter? It's not the employer's benefits. I'd drop it.
EEO statement: remove.
Posting duration: remove.
Now, let's craft HTML.
First, a short paragraph for metadata: location, job type, education. Could be a
before sections.
Then sections.
I'll write:
Location: Waukesha, Wisconsin. Job type: Permanent. Education: Bachelor's degree required.
About the role
The Embedded Controls Engineer IV plays an important role in advancing the design and performance of internal combustion engines (ICE), through engine development, data-driven analysis, engine controls system development, and design of system components. This position leverages data analytics, ATI Vision, and data acquisition tools to optimize system behavior, improve engine control, improve product reliability, and increase engine performance across a range of gaseous fueled applications.
Responsibilities
- Designs, validates, and brings new engine controls (throttles, mixers, fuel control, ignition systems) to market
- Specifies precise new engine design requirements
- Develops, tests, and integrates complex engine control components and evaluates overall effectiveness, cost (including cost/benefit analysis), reliability (risk analysis), and safety
- Designs, develops, executes, and evaluates testing, product specifications, and process validation plans
- Creates and reviews material part specifications and bills of materials
- Collaborates with internal manufacturing partners, contract manufacturers, designers, and product specialists to optimize complex and advanced component and system designs for manufacturability
- Supporting product development plans (schedule, product cost, meeting design inputs)
- Acts as a resource to mentor and teach less experienced engineers
- Travel to other Generac facilities as necessary
- Other duties as assigned
Requirements
- Bachelor of Science Degree in Mechanical or Electrical Engineering or related discipline
- 7+ years of relevant work experience
Qualifications
- Experience in automotive development and calibration, or a related engineering discipline
- Hands-on experience with engine and engine component development
- Experience in powertrain calibration software - ATI/CAN or similar
- Hands-on experience with ATI Vision as applied to engine control systems
- Extensive experience in new IC engine control system design and development
- Proficiency in developing internal combustion engines, including understanding of the effects of spark control, adjusting AFR for best performance and emissions, durability, control system components, intake/exhaust system pressure, and emissions testing
- Develops, tests, and integrates complex system components and evaluates overall effectiveness, cost (including cost/benefit analysis), reliability (risk analysis), and safety
- Designs, develops, executes, and evaluates testing, product specifications, and process validation plans
- Ability to perform detail-oriented work with a high degree of accuracy on multiple projects
- Expert with internal combustion engine performance development and specification
- Strong analytical and problem-solving skills, with a deep understanding of internal combustion engine design, operation, and testing
- Strong written and verbal communication skills with the ability to clearly interpret and present complex simulation results to technical and non-technical audiences
- Collaborate with internal manufacturing partners, contract manufacturers, designers, and product specialists to optimize complex and advanced designs for performance
Preferred qualifications
- Master's degree in mechanical engineering, Aerospace Engineering, Computer Science, or a related field of study
- Advanced hands-on experience in IC engines and engine system development
- Advanced experience using ATI Vision in the use for calibration development for internal combustion engines
- Advanced experience in applying MATLAB/Simulink and Python in internal combustion engine development
- Comprehensive knowledge of internal combustion engines and effective engine test methods
- Experience with MATLAB/Simulink, Python, Labview, Vision, Concerto or similar to modify embedded control software
- Extensive experience with internal combustion engine performance development and specification
- Understanding of thermodynamics and fluid dynamics
- Understanding of internal combustion engine thermodynamic cycles
- Demonstrated written communication and presentation skills
- Previous experience with SAP or equivalent ERP
- Ability to easily apply engineering knowledge and experience to improve products, services and processes
- Ability to translate technical information to all audiences
- Substantial data analysis and control/diagnostic feature creation skills
- Ample familiarity with systems engineering based problem solving
- Proven ability to work well with others as part of a diverse global team
Skills
- Component development
- Data analysis
- Data analytics
- Data-driven analysis
- Computer Science
- Labview
- MATLAB/Simulink
- Python
- SAP
- System development
- Systems engineering
- Detail-oriented
- Strong written and verbal communication
- Written communication
- Strong analytical and problem-solving skills
- Problem solving
- Reliability
- Work well with others
- Aerospace Engineering
- Automotive
- Bills of materials
- Calibration
- Control system
- Benefit analysis
- Data acquisition
- Presentation skills
- Design and development
- Embedded control
- Emissions testing
- Engine control
- Engine design
- Engine development
- Engine performance
- ERP
- Exhaust system
- Fluid dynamics
- Ignition systems
- Internal combustion engines
- IC engine
- Internal combustion engine
- Electrical Engineering
- Engineering knowledge
- Mechanical engineering
- Mentor
- Process validation
- Product development
- Powertrain
- Risk analysis
- Simulation
- System designs
- Technical information
- Test methods
- Testing
- Thermodynamics
- Product specifications
Pay
$120,000 - $150,000 per year
Schedule
9am to 5pm
That's it. No Benefits section because the benefits info is from recruiter boilerplate. No EEO. No application instructions.
Check rules: "Do NOT
for prose - Do NOT repeat job title as heading - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (EEO, equal opportunity, scam warnings, application instructions, etc.) - Include section ONLY when posting has real, specific content - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment, no /, no markdown code fences Let me parse the content: Job Summary: "The Embedded Controls Engineer IV plays an important role in advancing the design and performance of internal combustion engines (ICE), through engine development, data-driven analysis, engine controls system development, and design of system components. This position leverages data analytics, ATI Vision, and data acquisition tools to optimize system behavior, improve engine control, improve product reliability, and increase engine performance across a range of gaseous fueled applications." Location: Waukesha, Wisconsin Job type: Permanent Salary: $120,000 - 150,000 per year Work hours: 9am to 5pm Education: Bachelors Responsibilities: List of major responsibilities (bullet points) Qualifications: Minimum Qualifications (list), Knowledge, Skills And Abilities (list), Preferred Qualifications (list) Skills: A long comma-separated list at the end. Also there's EEO boilerplate, Randstad Digital benefits info, posting duration - these should be removed. Now, I need to structure sections: 1. About the role (Job Summary) - prose 2. Responsibilities - list 3. Requirements (Minimum Qualifications) - list 4. Qualifications (Knowledge, Skills And Abilities) - list? Or combine with requirements? The heading "Qualifications" could cover both minimum and preferred. But the rules say use headings like "Requirements", "Qualifications". I'll do "Requirements" for minimum, "Preferred qualifications" for preferred, and maybe "Skills" for the skills list. But the rules: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I can use "Requirements" for minimum qualifications, "Qualifications" for knowledge/skills/abilities? Actually the posting has "Minimum Qualifications" and "Knowledge, Skills And Abilities" and "Preferred Qualifications". I'll create sections: "Requirements" for minimum qualifications, "Qualifications" for knowledge/skills/abilities, "Preferred qualifications" for preferred. But the rules say "Qualifications" as a heading example. I'll use "Requirements" for minimum, "Qualifications" for the knowledge/skills/abilities, and "Preferred qualifications" for preferred. Alternatively, combine minimum and preferred under "Requirements" and "Preferred qualifications". I think better to have: - About the role - Responsibilities - Requirements (minimum qualifications) - Qualifications (knowledge, skills, abilities) - Preferred qualifications - Skills (the list) - Pay (salary) - Schedule (work hours) - Location (maybe as a short p? Not a heading unless it's a section. The rules don't mention Location as a heading example. Could fold into a short p at top or in About the role. But the posting has location, job type, salary, work hours, education as metadata. The rules: "fold minor metadata into a short
or drop it." So I can put location, job type, education in a short paragraph at the beginning or in About the role. Salary and schedule have specific sections if they have real content. The posting states salary range and work hours, so I should include Pay and Schedule sections. Benefits: The posting mentions benefits package but it's from Randstad Digital, not the employer? It says "Randstad Digital offers a comprehensive benefits package...". That's boilerplate from the recruiter. The rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". This includes benefits description from recruiter? It's not the employer's benefits. I'd drop it. EEO statement: remove. Posting duration: remove. Now, let's craft HTML. First, a short paragraph for metadata: location, job type, education. Could be a
before sections. Then sections. I'll write:
Location: Waukesha, Wisconsin. Job type: Permanent. Education: Bachelor's degree required.
About the role
The Embedded Controls Engineer IV plays an important role in advancing the design and performance of internal combustion engines (ICE), through engine development, data-driven analysis, engine controls system development, and design of system components. This position leverages data analytics, ATI Vision, and data acquisition tools to optimize system behavior, improve engine control, improve product reliability, and increase engine performance across a range of gaseous fueled applications.
Responsibilities
- Designs, validates, and brings new engine controls (throttles, mixers, fuel control, ignition systems) to market
- Specifies precise new engine design requirements
- Develops, tests, and integrates complex engine control components and evaluates overall effectiveness, cost (including cost/benefit analysis), reliability (risk analysis), and safety
- Designs, develops, executes, and evaluates testing, product specifications, and process validation plans
- Creates and reviews material part specifications and bills of materials
- Collaborates with internal manufacturing partners, contract manufacturers, designers, and product specialists to optimize complex and advanced component and system designs for manufacturability
- Supporting product development plans (schedule, product cost, meeting design inputs)
- Acts as a resource to mentor and teach less experienced engineers
- Travel to other Generac facilities as necessary
- Other duties as assigned
Requirements
- Bachelor of Science Degree in Mechanical or Electrical Engineering or related discipline
- 7+ years of relevant work experience
Qualifications
- Experience in automotive development and calibration, or a related engineering discipline
- Hands-on experience with engine and engine component development
- Experience in powertrain calibration software - ATI/CAN or similar
- Hands-on experience with ATI Vision as applied to engine control systems
- Extensive experience in new IC engine control system design and development
- Proficiency in developing internal combustion engines, including understanding of the effects of spark control, adjusting AFR for best performance and emissions, durability, control system components, intake/exhaust system pressure, and emissions testing
- Develops, tests, and integrates complex system components and evaluates overall effectiveness, cost (including cost/benefit analysis), reliability (risk analysis), and safety
- Designs, develops, executes, and evaluates testing, product specifications, and process validation plans
- Ability to perform detail-oriented work with a high degree of accuracy on multiple projects
- Expert with internal combustion engine performance development and specification
- Strong analytical and problem-solving skills, with a deep understanding of internal combustion engine design, operation, and testing
- Strong written and verbal communication skills with the ability to clearly interpret and present complex simulation results to technical and non-technical audiences
- Collaborate with internal manufacturing partners, contract manufacturers, designers, and product specialists to optimize complex and advanced designs for performance
Preferred qualifications
- Master's degree in mechanical engineering, Aerospace Engineering, Computer Science, or a related field of study
- Advanced hands-on experience in IC engines and engine system development
- Advanced experience using ATI Vision in the use for calibration development for internal combustion engines
- Advanced experience in applying MATLAB/Simulink and Python in internal combustion engine development
- Comprehensive knowledge of internal combustion engines and effective engine test methods
- Experience with MATLAB/Simulink, Python, Labview, Vision, Concerto or similar to modify embedded control software
- Extensive experience with internal combustion engine performance development and specification
- Understanding of thermodynamics and fluid dynamics
- Understanding of internal combustion engine thermodynamic cycles
- Demonstrated written communication and presentation skills
- Previous experience with SAP or equivalent ERP
- Ability to easily apply engineering knowledge and experience to improve products, services and processes
- Ability to translate technical information to all audiences
- Substantial data analysis and control/diagnostic feature creation skills
- Ample familiarity with systems engineering based problem solving
- Proven ability to work well with others as part of a diverse global team
Skills
- Component development
- Data analysis
- Data analytics
- Data-driven analysis
- Computer Science
- Labview
- MATLAB/Simulink
- Python
- SAP
- System development
- Systems engineering
- Detail-oriented
- Strong written and verbal communication
- Written communication
- Strong analytical and problem-solving skills
- Problem solving
- Reliability
- Work well with others
- Aerospace Engineering
- Automotive
- Bills of materials
- Calibration
- Control system
- Benefit analysis
- Data acquisition
- Presentation skills
- Design and development
- Embedded control
- Emissions testing
- Engine control
- Engine design
- Engine development
- Engine performance
- ERP
- Exhaust system
- Fluid dynamics
- Ignition systems
- Internal combustion engines
- IC engine
- Internal combustion engine
- Electrical Engineering
- Engineering knowledge
- Mechanical engineering
- Mentor
- Process validation
- Product development
- Powertrain
- Risk analysis
- Simulation
- System designs
- Technical information
- Test methods
- Testing
- Thermodynamics
- Product specifications
Pay
$120,000 - $150,000 per year
Schedule
9am to 5pm
That's it. No Benefits section because the benefits info is from recruiter boilerplate. No EEO. No application instructions. Check rules: "Do NOT