Technology Solutions Software Engineer II-III
Hyster-Yale Materials Handling · Greenville-Washington, North Carolina Area · 1 mo ago
HybridFull-time
We need to produce HTML fragment with sections only if content present. Use for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. Preserve all substantive info.
We need to parse the posting.
Job Title: Technology Solutions Software Engineer II-III (not used as heading). Job Category: Engineering (maybe not needed). Job Description includes sections: "What starts with YOU..." etc.
We need to extract:
- About the role: maybe the introductory paragraph: "Hyster-Yale Materials Handling, Inc, a world-class manufacturer of industrial lift trucks, has an outstanding opportunity for an exceptional and talented Technology Solutions Software Engineer II-III based at our Greenville, NC location." Could be considered About the role.
- Responsibilities: "What You Will Do" bullet list.
- Requirements: maybe "What You Will Need" (Level II and Level III). Could be Requirements.
- Qualifications: maybe "Who You Are" (personal attributes). Could be Qualifications.
- Skills: "Skills, Experience, & Abilities" (including Level II/III specifics). Could be Skills.
- Benefits: "What We Offer" includes competitive pay, tuition reimbursement, supportive work environment, hybrid work option, opportunities for growth and development. A full benefits package: paid time off; medical, dental, vision, and life insurance, employer-sponsored profit sharing and 401(k). Also earlier mention of benefit package.
- Pay: Not explicitly stated; only "competitive pay" but no numbers. The rule: do NOT create Pay section unless posting actually states them. It says "competitive pay" but no specific amount. Is that considered stating pay? It's vague. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "competitive pay" is vague but still states that pay is competitive; maybe it's acceptable? However they said avoid filler like "commensurate with experience". "competitive pay" is similar vague. Safer to not create Pay section unless explicit numbers or range. So we omit Pay.
- Schedule: Not stated; only "Work Hours 40" and "Time Type Full time". That's schedule info: full time, 40 hours. Could be considered schedule. The rule: create Schedule section only if posting actually states them. It does state "Time Type Full time" and "Work Hours 40". So we can include Schedule section with that info.
- Benefits: we have details.
We also need to include maybe "About the company" but not required.
We must not include duplicated lines, cookie/navigation/legal/EEO etc. At end there is EEO statement; remove.
We need to preserve all substantive info.
Let's extract content.
About the role: maybe combine first two sentences: "Hyster-Yale Materials Handling, Inc, a world-class manufacturer of industrial lift trucks, has an outstanding opportunity for an exceptional and talented Technology Solutions Software Engineer II-III based at our Greenville, NC location." Also maybe "What starts with YOU, moves the world!" is a tagline; could be included.
Responsibilities: list from "What You Will Do":
- Design, develop, test, and maintain embedded software solutions that support connected products, intelligent control systems, and vehicle communications.
- Collaborate with cross-functional engineering teams to define system requirements, develop scalable software architectures, and deliver high-quality technical solutions that meet performance, reliability, and customer expectations.
- Verify and validate software through simulation, testing, and troubleshooting activities, ensuring compliance with functional and technical requirements throughout the product lifecycle.
- Partner with manufacturing, product management, suppliers, and service teams to support product development, issue resolution, and continuous improvement initiatives.
- Level III Additions: Provide technical leadership through code reviews, design oversight, supplier collaboration, and mentoring of early-career engineers while driving software development best practices.
We should keep as bullet list.
Requirements: "What You Will Need" includes Level II and Level III details.
We need to preserve all substantive info. Let's extract:
Level II: Bachelor's degree in Electrical Engineering, Computer Engineering, Computer Science, Software Engineering, or a related technical field with a minimum of 2 years of relevant experience developing embedded software systems. Master's degree in Electrical Engineering, Computer Engineering, Computer Science, Software Engineering, or a related technical field preferred.
Level III: Bachelor's or Master's degree in Electrical Engineering, Computer Engineering, Computer Science, Software Engineering, or a related technical field with a minimum of 4 years of relevant experience developing embedded software systems.
We could present as bullet list.
Qualifications: "Who You Are" paragraph:
- A collaborative problem-solver who enjoys working across disciplines to deliver innovative technology solutions.
- A self-motivated engineer who takes ownership of projects and balances independent work with effective teamwork.
- A strong communicator who can translate complex technical concepts to diverse audiences and build productive relationships with stakeholders.
- Detail-oriented and analytical, with a passion for developing reliable, high-quality software and continuously improving processes.
- Adaptable and curious, eager to learn new technologies and contribute to evolving products and engineering practices.
We can bullet.
Skills: "Skills, Experience, & Abilities" includes many details. Let's parse:
- Basic specialized knowledge/skill in engineering analysis, system design, integration, testing, and technical documentation.
- Basic (Level II) or intermediate (Level III) knowledge/skill in embedded control systems, electrical systems, software testing practices, and system verification methodologies.
- Demonstrated proficiency in the core technical and professional competencies required for successful performance in the role.
- Embedded software programming skills with intermediate (Level II) or expert (Level III) proficiency in programming languages such as C, C++, and/or Assembly; and/or basic (Level II) or intermediate (Level III) proficiency in modeling control systems and algorithms using tools such as MATLAB and Simulink.
- Basic (Level II) or intermediate (Level III) proficiency in real-time control networks, networked communications, and communication protocols such as CAN bus (SAE J1939, CANopen), Ethernet, wireless, or cellular communications technologies.
- Basic (Level II) or intermediate (Level III) knowledge of control system design and architectures, including both electronic hardware and embedded software components.
- Level III Additions:
- Basic knowledge/skill in industry standards, project scheduling, and technical leadership.
- Basic knowledge of software architectures for embedded control systems and connected technologies.
- Ability to lead code reviews, design reviews, and provide technical guidance to less experienced engineers.
We can bullet.
Benefits: "What We Offer":
- Competitive pay (maybe we keep as benefit? but we decided not to create Pay section; but we can include competitive pay within Benefits as a bullet? The rule: only create Benefits section if posting actually states them. It does state benefits. So we can include competitive pay as part of Benefits bullet list. However we must not create Pay section separate. So we include competitive pay in Benefits.
- Tuition reimbursement
- Supportive work environment
- Hybrid work option
- Opportunities for growth and development
- Full benefits package: paid time off; medical, dental, vision, and life insurance; employer-sponsored profit sharing and 401(k).
Also earlier: "We are an equal opportunity employer with an excellent benefit package including medical, dental and life insurance, 401(k) and profit sharing." That's duplicate; we can ignore duplicate.
Schedule: "Job Type Permanent", "Time Type Full time", "Work Hours 40", "Travel Required 10-25%". So schedule includes full time, 40 hours per week, travel 10-25%.
We can include schedule bullet list.
Now produce HTML.
We need headings:
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. Preserve all substantive info.
We need to parse the posting.
Job Title: Technology Solutions Software Engineer II-III (not used as heading). Job Category: Engineering (maybe not needed). Job Description includes sections: "What starts with YOU..." etc.
We need to extract:
- About the role: maybe the introductory paragraph: "Hyster-Yale Materials Handling, Inc, a world-class manufacturer of industrial lift trucks, has an outstanding opportunity for an exceptional and talented Technology Solutions Software Engineer II-III based at our Greenville, NC location." Could be considered About the role.
- Responsibilities: "What You Will Do" bullet list.
- Requirements: maybe "What You Will Need" (Level II and Level III). Could be Requirements.
- Qualifications: maybe "Who You Are" (personal attributes). Could be Qualifications.
- Skills: "Skills, Experience, & Abilities" (including Level II/III specifics). Could be Skills.
- Benefits: "What We Offer" includes competitive pay, tuition reimbursement, supportive work environment, hybrid work option, opportunities for growth and development. A full benefits package: paid time off; medical, dental, vision, and life insurance, employer-sponsored profit sharing and 401(k). Also earlier mention of benefit package.
- Pay: Not explicitly stated; only "competitive pay" but no numbers. The rule: do NOT create Pay section unless posting actually states them. It says "competitive pay" but no specific amount. Is that considered stating pay? It's vague. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "competitive pay" is vague but still states that pay is competitive; maybe it's acceptable? However they said avoid filler like "commensurate with experience". "competitive pay" is similar vague. Safer to not create Pay section unless explicit numbers or range. So we omit Pay.
- Schedule: Not stated; only "Work Hours 40" and "Time Type Full time". That's schedule info: full time, 40 hours. Could be considered schedule. The rule: create Schedule section only if posting actually states them. It does state "Time Type Full time" and "Work Hours 40". So we can include Schedule section with that info.
- Benefits: we have details.
We also need to include maybe "About the company" but not required.
We must not include duplicated lines, cookie/navigation/legal/EEO etc. At end there is EEO statement; remove.
We need to preserve all substantive info.
Let's extract content.
About the role: maybe combine first two sentences: "Hyster-Yale Materials Handling, Inc, a world-class manufacturer of industrial lift trucks, has an outstanding opportunity for an exceptional and talented Technology Solutions Software Engineer II-III based at our Greenville, NC location." Also maybe "What starts with YOU, moves the world!" is a tagline; could be included.
Responsibilities: list from "What You Will Do":
- Design, develop, test, and maintain embedded software solutions that support connected products, intelligent control systems, and vehicle communications.
- Collaborate with cross-functional engineering teams to define system requirements, develop scalable software architectures, and deliver high-quality technical solutions that meet performance, reliability, and customer expectations.
- Verify and validate software through simulation, testing, and troubleshooting activities, ensuring compliance with functional and technical requirements throughout the product lifecycle.
- Partner with manufacturing, product management, suppliers, and service teams to support product development, issue resolution, and continuous improvement initiatives.
- Level III Additions: Provide technical leadership through code reviews, design oversight, supplier collaboration, and mentoring of early-career engineers while driving software development best practices.
We should keep as bullet list.
Requirements: "What You Will Need" includes Level II and Level III details.
We need to preserve all substantive info. Let's extract:
Level II: Bachelor's degree in Electrical Engineering, Computer Engineering, Computer Science, Software Engineering, or a related technical field with a minimum of 2 years of relevant experience developing embedded software systems. Master's degree in Electrical Engineering, Computer Engineering, Computer Science, Software Engineering, or a related technical field preferred.
Level III: Bachelor's or Master's degree in Electrical Engineering, Computer Engineering, Computer Science, Software Engineering, or a related technical field with a minimum of 4 years of relevant experience developing embedded software systems.
We could present as bullet list.
Qualifications: "Who You Are" paragraph:
- A collaborative problem-solver who enjoys working across disciplines to deliver innovative technology solutions.
- A self-motivated engineer who takes ownership of projects and balances independent work with effective teamwork.
- A strong communicator who can translate complex technical concepts to diverse audiences and build productive relationships with stakeholders.
- Detail-oriented and analytical, with a passion for developing reliable, high-quality software and continuously improving processes.
- Adaptable and curious, eager to learn new technologies and contribute to evolving products and engineering practices.
We can bullet.
Skills: "Skills, Experience, & Abilities" includes many details. Let's parse:
- Basic specialized knowledge/skill in engineering analysis, system design, integration, testing, and technical documentation.
- Basic (Level II) or intermediate (Level III) knowledge/skill in embedded control systems, electrical systems, software testing practices, and system verification methodologies.
- Demonstrated proficiency in the core technical and professional competencies required for successful performance in the role.
- Embedded software programming skills with intermediate (Level II) or expert (Level III) proficiency in programming languages such as C, C++, and/or Assembly; and/or basic (Level II) or intermediate (Level III) proficiency in modeling control systems and algorithms using tools such as MATLAB and Simulink.
- Basic (Level II) or intermediate (Level III) proficiency in real-time control networks, networked communications, and communication protocols such as CAN bus (SAE J1939, CANopen), Ethernet, wireless, or cellular communications technologies.
- Basic (Level II) or intermediate (Level III) knowledge of control system design and architectures, including both electronic hardware and embedded software components.
- Level III Additions:
- Basic knowledge/skill in industry standards, project scheduling, and technical leadership.
- Basic knowledge of software architectures for embedded control systems and connected technologies.
- Ability to lead code reviews, design reviews, and provide technical guidance to less experienced engineers.
We can bullet.
Benefits: "What We Offer":
- Competitive pay (maybe we keep as benefit? but we decided not to create Pay section; but we can include competitive pay within Benefits as a bullet? The rule: only create Benefits section if posting actually states them. It does state benefits. So we can include competitive pay as part of Benefits bullet list. However we must not create Pay section separate. So we include competitive pay in Benefits.
- Tuition reimbursement
- Supportive work environment
- Hybrid work option
- Opportunities for growth and development
- Full benefits package: paid time off; medical, dental, vision, and life insurance; employer-sponsored profit sharing and 401(k).
Also earlier: "We are an equal opportunity employer with an excellent benefit package including medical, dental and life insurance, 401(k) and profit sharing." That's duplicate; we can ignore duplicate.
Schedule: "Job Type Permanent", "Time Type Full time", "Work Hours 40", "Travel Required 10-25%". So schedule includes full time, 40 hours per week, travel 10-25%.
We can include schedule bullet list.
Now produce HTML.
We need headings: About the role
, Responsibilities
, Requirements
, Qualifications
, Skills
, Benefits
, Schedule
.
We must not include empty sections.
Let's craft.
Use
for prose paragraphs,
- for lists.
We need to ensure we don't repeat job title.
Let's write.
About the role: maybe two sentences: tagline and description.
What starts with YOU, moves the world!
Hyster-Yale Materials Handling, Inc, a world-class manufacturer of industrial lift trucks, has an outstanding opportunity for an exceptional and talented Technology Solutions Software Engineer II-III based at our Greenville, NC location.
Responsibilities: list.- Design, develop, test, and maintain embedded software solutions that support connected products, intelligent control systems, and vehicle communications.
- Collaborate with cross-functional engineering teams to define system requirements, develop scalable software architectures, and deliver high-quality technical solutions that meet performance, reliability, and customer expectations.
- Verify and validate software through simulation, testing, and troubleshooting activities, ensuring compliance with functional and technical requirements throughout the product lifecycle.
- Partner with manufacturing, product management, suppliers, and service teams to support product development, issue resolution, and continuous improvement initiatives.
- Level III Additions: Provide technical leadership through code reviews, design oversight, supplier collaboration, and mentoring of early-career engineers while driving software development best practices.
- Level II: Bachelor's degree in Electrical Engineering, Computer Engineering, Computer Science, Software Engineering, or a related technical field with a minimum of 2 years of relevant experience developing embedded software systems. Master's degree in Electrical Engineering, Computer Engineering, Computer Science, Software Engineering, or a related technical field preferred.
- Level III: Bachelor's or Master's degree in Electrical Engineering, Computer Engineering, Computer Science, Software Engineering, or a related technical field with a minimum of 4 years of relevant experience developing embedded software systems.
- A collaborative problem-solver who enjoys working across disciplines to deliver innovative technology solutions.
- A self-motivated engineer who takes ownership of projects and balances independent work with effective teamwork.
- A strong communicator who can translate complex technical concepts to diverse audiences and build productive relationships with stakeholders.
- Detail-oriented and analytical, with a passion for developing reliable, high-quality software and continuously improving processes.
- Adaptable and curious, eager to learn new technologies and contribute to evolving products and engineering practices.
- Basic specialized knowledge/skill in engineering analysis, system design, integration, testing, and technical documentation.
- Basic (Level II) or intermediate (Level III) knowledge/skill in embedded control systems, electrical systems, software testing practices, and system verification methodologies.
- Demonstrated proficiency in the core technical and professional competencies required for successful performance in the role.
- Embedded software programming skills with intermediate (Level II) or expert (Level III) proficiency in programming languages such as C, C++, and/or Assembly; and/or basic (Level II) or intermediate (Level III) proficiency in modeling control systems and algorithms using tools such as MATLAB and Simulink.
- Basic (Level II) or intermediate (Level III) proficiency in real-time control networks, networked communications, and communication protocols such as CAN bus (SAE J1939, CANopen), Ethernet, wireless, or cellular communications technologies.
- Basic (Level II) or intermediate (Level III) knowledge of control system design and architectures, including both electronic hardware and embedded software components.
- Level III Additions:
- Basic knowledge/skill in industry standards, project scheduling, and technical leadership.
- Basic knowledge of software architectures for embedded control systems and connected technologies.
- Ability to lead code reviews, design reviews