Embedded Controls Engineer
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for lists,
for prose
3. Do NOT repeat job title as heading
4. Do NOT put Job ID/requisition numbers as headings
5. Preserve ALL substantive information
6. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions)
7. Include a section ONLY when there's real specific content - never emit heading followed by filler/placeholder text
8. Never create Pay/Schedule/Benefits sections unless posting actually states them
9. Output ONLY HTML fragment - no /, no markdown code fences
Let me analyze the job posting:
- Job Summary: "The Embedded Controls Engineer plays a central role..." - this is "About the role" content
- Location: Waukesha, Wisconsin - metadata, fold into short
or drop
- Job type: Permanent - metadata
- Salary: $120,000 - 150,000 per year - this is Pay content
- Work hours: 9am to 5pm - this is Schedule content
- Education: Bachelors - part of qualifications
- Responsibilities: "Essential Duties and Responsibilities:" with bullet points
- Qualifications: "Minimum Qualifications:" with bullet points
- Knowledge Skills And Abilities: list of skills/abilities
- Preferred Qualifications: list
- Skills: comma-separated list at the end
- Then boilerplate: Equal Opportunity Employer, Randstad Digital benefits, posting open for 30 days
I need to structure this into sections:
1. About the role (from Job Summary)
2. Responsibilities (from Essential Duties)
3. Requirements/Qualifications (Minimum Qualifications)
4. Skills (Knowledge Skills And Abilities + Preferred Qualifications + Skills list)
5. Pay (salary range given)
6. Schedule (work hours given)
7. Benefits (comprehensive benefits package mentioned)
Wait, the rules say: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting DOES state salary, work hours, and benefits. So I should include them.
But also: "fold minor metadata into a short
or drop it" - location, job type, education could be folded into a short paragraph or dropped. Education is part of qualifications.
Let me organize:
- About the role: Job Summary paragraph
- Responsibilities: the 8 bullet points under Essential Duties
- Requirements: Minimum Qualifications (3 items)
- Qualifications: Knowledge Skills And Abilities (the prose list) + Preferred Qualifications (10 items)
- Skills: the comma-separated skills list at the end
- Pay: salary range
- Schedule: work hours
- Benefits: benefits package description
But the rules say "Prefer a few substantive sections over many thin ones." And "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I can use these headings.
I should combine "Requirements" and "Qualifications" maybe? The posting has "Minimum Qualifications" and "Knowledge Skills And Abilities" and "Preferred Qualifications". I could make "Requirements" for minimum qualifications, and "Qualifications" for the skills/abilities and preferred. Or combine into one "Qualifications" section with sub-lists.
The rules say "Requirements, Qualifications" as separate example headings. I'll do:
- About the role
- Responsibilities
- Requirements (Minimum Qualifications)
- Qualifications (Knowledge Skills And Abilities + Preferred Qualifications)
- Skills (the skills list)
- Pay
- Schedule
- Benefits
But the skills list at the end is just keywords, many duplicating earlier content. I'll include it as a Skills section.
Now, for the boilerplate: remove EEO statement, Randstad Digital specific benefits details (but keep the benefits mentioned), posting open for 30 days, accommodation contact.
The benefits mentioned: "medical, prescription, dental, vision, AD&D, and life insurance offerings, short-term disability, and a 401K plan (all benefits are based on eligibility)." That's substantive.
Pay: "$120,000 - 150,000 per year" and "Pay offered to a successful candidate will be based on several factors including the candidate's education, work experience, work location, specific job duties, certifications, etc." I'll include both.
Schedule: "9am to 5pm"
Location: "Waukesha, Wisconsin" - fold into a short
maybe in About the role or separate? The rules say fold minor metadata into short
or drop. I'll include in About the role paragraph.
Job type: Permanent - maybe drop or include in About the role.
Education: Bachelors - covered in Requirements.
Now, write HTML.
I need to be careful: no markdown code fences, just HTML fragment.
Let me draft:
About the role
The Embedded Controls Engineer plays a central role in advancing the physical design, calibration, and operational performance of internal combustion engines across gaseous fuel applications. This position leverages data analytics, ATI Vision, and data acquisition tools to optimize engine control behavior, spark timing, air-fuel ratio (AFR), emissions compliance, and physical component durability. Location: Waukesha, Wisconsin. Job type: Permanent.
Responsibilities
- Create system-level engine code using Matlab/Simulink to support engine and generator design and development.
- Conduct simulated and functional analyses to evaluate engine performance of mechanical and energy systems.
- Conduct system evaluation and testing to aid in optimizing an engine's steady state and transient performance.
- Interpret testing results and collaborates with cross-functional teams through code design reviews and technical discussions to guide product development.
- Contribute to the development of software and code analysis best practices to improve efficiency and accuracy.
- Document code objectives, methods, and results using standardized reporting formats.
- Apply data analysis techniques, including Matlab/Simulink modeling and Python-based scripting and machine learning, to support code performance forecasting.
- Stay informed on relevant technologies, tools, and industry trends to support continuous improvement.
Requirements
- Bachelor of Science Degree in Mechanical or Electrical Engineering or related discipline
- 5+ years of relevant work experience
Qualifications
Knowledge, Skills, and Abilities:
- Proficiency in applying Matlab/Simulink to internal combustion engine related systems, including steady state, transient, fault codes, SPNs, SAE J1939 CAN networks, sensor integration, and embedded systems.
- Experienced in automotive standards.
- Experience with co-simulation environments, including Software-in-the-Loop (SiL) and Hardware-in-the-Loop (HiL).
- Familiarity with machine learning and predictive analytics techniques applied to engine performance and emissions modeling.
- Familiarity with generator design.
- 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.
Preferred Qualifications:
- Master's degree in Electrical Engineering, Mechanical Engineering, Aerospace Engineering, Computer Science, or a related field of study.
- Advanced engine and engine system code writing in Matlab/Simulink.
- Advanced experience applying MATLAB/Simulink and Python to internal combustion engine design.
- Advanced experience using ATI Vision to set calibrations in internal combustion engines.
- Advanced experience in applying MATLAB/Simulink and Python in engineering analysis and simulation.
- Advanced proficiency in applying Matlab/Simulink code to complex propulsion systems, with demonstrated success in optimizing transients, steady state, and overall performance.
- Deep expertise in internal combustion engine control code, operational dynamics, and advanced testing methodologies.
- Extensive experience designing and executing co-simulation workflows, including SiL and HiL integration for real-time system validation.
- Exceptional ability to synthesize and present complex code insights to diverse technical and non-technical stakeholders, influencing design decisions.
- Proficient in applying machine learning and advanced predictive analytics to optimize engine performance with experience developing custom code.
- Superior analytical acumen and strategic problem-solving capabilities, with a track record of delivering high-impact engineering solutions.
- Excellent written and verbal communication skills with the ability to clearly interpret and present complex simulation results to technical and non-technical audiences.
- Familiarity with gaseous fuel systems for internal combustion engines.
Skills
- advanced testing
- CAN networks
- data analysis techniques
- embedded software
- Hardware-in-the-Loop
- Computer Science
- Matlab/Simulink
- machine learning
- Python-based
- Python
- real-time system
- scripting
- code analysis
- system evaluation
- analytical acumen
- Strong written and verbal communication
- Excellent written and verbal communication
- Strong analytical and problem-solving skills
- strategic problem-solving
- Aerospace Engineering
- automotive
- continuous improvement
- calibrations
- standardized reporting
- design and development
- embedded systems
- energy systems
- engine control
- engine performance
- forecasting
- fuel systems
- functional analyses
- internal combustion engines
- internal combustion engine
- Electrical Engineering
- Mechanical Engineering
- influencing
- modeling
- predictive analytics
- product development
- propulsion systems
- J1939
- sensor integration
- simulated
- simulation environments
- simulation
- engineering analysis
- testing
- workflows
Pay
$120,000 - $150,000 per year. Pay offered to a successful candidate will be based on several factors including the candidate's education, work experience, work location, specific job duties, certifications, etc.
Schedule
9am to 5pm
Benefits
Comprehensive benefits package including medical, prescription, dental, vision, AD&D, and life insurance offerings, short-term disability, and a 401K plan (all benefits are based on eligibility).
That seems complete. I removed the EEO boilerplate, the Randstad Digital specific accommodation contact, the "posting open for 30 days". I preserved all substantive info.
for prose 3. Do NOT repeat job title as heading 4. Do NOT put Job ID/requisition numbers as headings 5. Preserve ALL substantive information 6. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) 7. Include a section ONLY when there's real specific content - never emit heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless posting actually states them 9. Output ONLY HTML fragment - no /, no markdown code fences Let me analyze the job posting: - Job Summary: "The Embedded Controls Engineer plays a central role..." - this is "About the role" content - Location: Waukesha, Wisconsin - metadata, fold into short
or drop - Job type: Permanent - metadata - Salary: $120,000 - 150,000 per year - this is Pay content - Work hours: 9am to 5pm - this is Schedule content - Education: Bachelors - part of qualifications - Responsibilities: "Essential Duties and Responsibilities:" with bullet points - Qualifications: "Minimum Qualifications:" with bullet points - Knowledge Skills And Abilities: list of skills/abilities - Preferred Qualifications: list - Skills: comma-separated list at the end - Then boilerplate: Equal Opportunity Employer, Randstad Digital benefits, posting open for 30 days I need to structure this into sections: 1. About the role (from Job Summary) 2. Responsibilities (from Essential Duties) 3. Requirements/Qualifications (Minimum Qualifications) 4. Skills (Knowledge Skills And Abilities + Preferred Qualifications + Skills list) 5. Pay (salary range given) 6. Schedule (work hours given) 7. Benefits (comprehensive benefits package mentioned) Wait, the rules say: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting DOES state salary, work hours, and benefits. So I should include them. But also: "fold minor metadata into a short
or drop it" - location, job type, education could be folded into a short paragraph or dropped. Education is part of qualifications. Let me organize: - About the role: Job Summary paragraph - Responsibilities: the 8 bullet points under Essential Duties - Requirements: Minimum Qualifications (3 items) - Qualifications: Knowledge Skills And Abilities (the prose list) + Preferred Qualifications (10 items) - Skills: the comma-separated skills list at the end - Pay: salary range - Schedule: work hours - Benefits: benefits package description But the rules say "Prefer a few substantive sections over many thin ones." And "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I can use these headings. I should combine "Requirements" and "Qualifications" maybe? The posting has "Minimum Qualifications" and "Knowledge Skills And Abilities" and "Preferred Qualifications". I could make "Requirements" for minimum qualifications, and "Qualifications" for the skills/abilities and preferred. Or combine into one "Qualifications" section with sub-lists. The rules say "Requirements, Qualifications" as separate example headings. I'll do: - About the role - Responsibilities - Requirements (Minimum Qualifications) - Qualifications (Knowledge Skills And Abilities + Preferred Qualifications) - Skills (the skills list) - Pay - Schedule - Benefits But the skills list at the end is just keywords, many duplicating earlier content. I'll include it as a Skills section. Now, for the boilerplate: remove EEO statement, Randstad Digital specific benefits details (but keep the benefits mentioned), posting open for 30 days, accommodation contact. The benefits mentioned: "medical, prescription, dental, vision, AD&D, and life insurance offerings, short-term disability, and a 401K plan (all benefits are based on eligibility)." That's substantive. Pay: "$120,000 - 150,000 per year" and "Pay offered to a successful candidate will be based on several factors including the candidate's education, work experience, work location, specific job duties, certifications, etc." I'll include both. Schedule: "9am to 5pm" Location: "Waukesha, Wisconsin" - fold into a short
maybe in About the role or separate? The rules say fold minor metadata into short
or drop. I'll include in About the role paragraph. Job type: Permanent - maybe drop or include in About the role. Education: Bachelors - covered in Requirements. Now, write HTML. I need to be careful: no markdown code fences, just HTML fragment. Let me draft:
About the role
The Embedded Controls Engineer plays a central role in advancing the physical design, calibration, and operational performance of internal combustion engines across gaseous fuel applications. This position leverages data analytics, ATI Vision, and data acquisition tools to optimize engine control behavior, spark timing, air-fuel ratio (AFR), emissions compliance, and physical component durability. Location: Waukesha, Wisconsin. Job type: Permanent.
Responsibilities
- Create system-level engine code using Matlab/Simulink to support engine and generator design and development.
- Conduct simulated and functional analyses to evaluate engine performance of mechanical and energy systems.
- Conduct system evaluation and testing to aid in optimizing an engine's steady state and transient performance.
- Interpret testing results and collaborates with cross-functional teams through code design reviews and technical discussions to guide product development.
- Contribute to the development of software and code analysis best practices to improve efficiency and accuracy.
- Document code objectives, methods, and results using standardized reporting formats.
- Apply data analysis techniques, including Matlab/Simulink modeling and Python-based scripting and machine learning, to support code performance forecasting.
- Stay informed on relevant technologies, tools, and industry trends to support continuous improvement.
Requirements
- Bachelor of Science Degree in Mechanical or Electrical Engineering or related discipline
- 5+ years of relevant work experience
Qualifications
Knowledge, Skills, and Abilities:
- Proficiency in applying Matlab/Simulink to internal combustion engine related systems, including steady state, transient, fault codes, SPNs, SAE J1939 CAN networks, sensor integration, and embedded systems.
- Experienced in automotive standards.
- Experience with co-simulation environments, including Software-in-the-Loop (SiL) and Hardware-in-the-Loop (HiL).
- Familiarity with machine learning and predictive analytics techniques applied to engine performance and emissions modeling.
- Familiarity with generator design.
- 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.
Preferred Qualifications:
- Master's degree in Electrical Engineering, Mechanical Engineering, Aerospace Engineering, Computer Science, or a related field of study.
- Advanced engine and engine system code writing in Matlab/Simulink.
- Advanced experience applying MATLAB/Simulink and Python to internal combustion engine design.
- Advanced experience using ATI Vision to set calibrations in internal combustion engines.
- Advanced experience in applying MATLAB/Simulink and Python in engineering analysis and simulation.
- Advanced proficiency in applying Matlab/Simulink code to complex propulsion systems, with demonstrated success in optimizing transients, steady state, and overall performance.
- Deep expertise in internal combustion engine control code, operational dynamics, and advanced testing methodologies.
- Extensive experience designing and executing co-simulation workflows, including SiL and HiL integration for real-time system validation.
- Exceptional ability to synthesize and present complex code insights to diverse technical and non-technical stakeholders, influencing design decisions.
- Proficient in applying machine learning and advanced predictive analytics to optimize engine performance with experience developing custom code.
- Superior analytical acumen and strategic problem-solving capabilities, with a track record of delivering high-impact engineering solutions.
- Excellent written and verbal communication skills with the ability to clearly interpret and present complex simulation results to technical and non-technical audiences.
- Familiarity with gaseous fuel systems for internal combustion engines.
Skills
- advanced testing
- CAN networks
- data analysis techniques
- embedded software
- Hardware-in-the-Loop
- Computer Science
- Matlab/Simulink
- machine learning
- Python-based
- Python
- real-time system
- scripting
- code analysis
- system evaluation
- analytical acumen
- Strong written and verbal communication
- Excellent written and verbal communication
- Strong analytical and problem-solving skills
- strategic problem-solving
- Aerospace Engineering
- automotive
- continuous improvement
- calibrations
- standardized reporting
- design and development
- embedded systems
- energy systems
- engine control
- engine performance
- forecasting
- fuel systems
- functional analyses
- internal combustion engines
- internal combustion engine
- Electrical Engineering
- Mechanical Engineering
- influencing
- modeling
- predictive analytics
- product development
- propulsion systems
- J1939
- sensor integration
- simulated
- simulation environments
- simulation
- engineering analysis
- testing
- workflows
Pay
$120,000 - $150,000 per year. Pay offered to a successful candidate will be based on several factors including the candidate's education, work experience, work location, specific job duties, certifications, etc.
Schedule
9am to 5pm
Benefits
Comprehensive benefits package including medical, prescription, dental, vision, AD&D, and life insurance offerings, short-term disability, and a 401K plan (all benefits are based on eligibility).
That seems complete. I removed the EEO boilerplate, the Randstad Digital specific accommodation contact, the "posting open for 30 days". I preserved all substantive info.