Senior Mechanical Design Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones.
Thus we need to decide which sections to include based on content.
We have:
- About the role: The description includes a paragraph about role: "The Senior Mechanical Design Engineer supports product design for innovative startups...". That's about the role. So we can have
About the role
with a paragraph.
- Responsibilities: There's a list of responsibilities bullet points. So we can have Responsibilities
with - each.
- Requirements / Qualifications / Skills: There's "Essential Skills" list and "Additional Skills & Qualifications". Could combine into Requirements or Skills. We need to decide which heading to use. The instruction says we can use headings like Requirements, Qualifications, Skills. We should include a section for skills/qualifications if there is substantive content. There is essential skills list and additional skills. So we can have
Essential Skills
maybe but they said use headings like Skills. Could use Skills
and list both essential and additional? But we need to preserve all info; we could split into two sub-sections? But they said prefer a few substantive sections over many thin ones. Could combine essential and additional into one Skills section with two lists? Or we could have Requirements (essential) and Additional Skills as separate sections? Might be thin. Better to have one Skills section with both essential and additional combined, maybe separate paragraphs.
But we need to follow: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose Skills.
Thus Skills
with paragraphs: maybe a short intro then for essential skills and another for additional skills? Could combine into one list but that would lose distinction. However we can still preserve all info by having two lists under the same heading, each preceded by a describing.
Alternatively we could have Requirements (essential) and Additional Skills as separate sections but that might be considered thin but still substantive. The instruction: "Prefer a few substantive sections over many thin ones." Having two sections for skills might be okay if each is substantive. But we have essential skills list (about 9 items) and additional skills list (about 6 items). Both are substantive. Could make two sections:
Essential Skills
and Additional Skills & Qualifications
. However the allowed headings list includes Requirements, Qualifications, Skills. Not Essential Skills. But we could still use Skills heading and include both lists with headings inside? But they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to stick to those examples. So we can have Skills
and inside we can have two
paragraphs: one for Essential Skills, one for Additional Skills & Qualifications, each followed by
.
That seems okay.
- Benefits: There's a Pay And Benefits section with pay range and benefits list. So we need Benefits section (maybe also Pay). The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting states pay range and benefits. So we can have a Benefits section with list of benefits. Also we could have Pay section with pay range. But they said prefer a few substantive sections over many thin ones. Could combine Pay and Benefits into one section? But they gave examples of separate Pay and Benefits headings. However we could decide to have a Benefits section that includes pay range as part of it? The instruction: "include a section ONLY when the posting has real, specific content for it". Pay is specific content. Benefits is specific content. Could we have two sections: Pay and Benefits? That would be two sections but each substantive. The instruction says prefer a few substantive sections over many thin ones. Two sections is fine. Could also combine into a "Compensation and Benefits" section but not in the examples. Safer to follow examples: have Pay
with the pay range paragraph, and Benefits
with the benefits list.
- Schedule: Not mentioned. No schedule info. So we should not create Schedule section.
- Work Environment: Could be a section but not in the examples list. The examples list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Work Environment is not listed. Should we include it? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. But they also say "Prefer a few substantive sections over many thin ones." Work Environment is substantive. Could include as a section with heading Work Environment. However they didn't list it as example but it's okay. But to be safe, maybe we can incorporate work environment details into About the role or another section? The About the role currently is just the initial paragraph. We could expand About the role to include work environment details. But we must preserve all substantive information; we can put work environment details in About the role paragraph. That would keep fewer sections.
Similarly, Job Type & Location: Could be included in About the role or a short paragraph. The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Job type and location is not minor metadata? It's somewhat important. Could be included in About the role paragraph.
Thus we can have sections: About the role (includes description, work environment, job type/location), Responsibilities, Skills (essential + additional), Pay, Benefits.
We must not repeat job title as heading.
We must output only HTML fragment, no /, no markdown.
Let's craft.
First, About the role: combine the initial description paragraph, plus work environment description, plus job type & location.
Original description paragraph: "The Senior Mechanical Design Engineer supports product design for innovative startups whose products are not yet fully mature or in production. In this role, you act as a customer-facing expert, providing design feedback and improvements for manufacturability, particularly for clients with immature designs. You lead and mentor junior engineers while driving the development of mechanical systems, control panels, PLCs, and large system controls. The first project will focus on bringing a previously sourced component in-house for manufacturing and optimizing its design for production."
Work Environment paragraph: "The role is based in a large, modern manufacturing facility that produces products for multiple customers. The facility is relatively new and experiencing significant growth, expanding its customer base and project portfolio. You work closely with production and engineering teams on the shop floor and in office and lab spaces, using tools and technologies related to mechanical design, controls, HVAC, and power distribution. The environment offers frequent interaction with startup clients, fast-paced project cycles, and substantial opportunities to influence product design and manufacturability as the facility grows."
Job Type & Location: "This is a Contract position based out of Grantsville, UT."
We can combine into one or two paragraphs. Let's make one paragraph that includes all? Might be long but okay. Better to split into two paragraphs for readability: first paragraph about role duties, second about work environment and job type/location.
Thus About the role:
About the role
...
...
Now Responsibilities: list each bullet.
We need to extract responsibilities bullet points from the posting:
- Support product design for early-stage and startup clients whose products are not yet fully mature or in production.
- Review and refine customer designs to improve manufacturability, reliability, and scalability for large form factor products.
- Act as a customer-facing technical expert, clearly communicating design feedback, options, and recommendations.
- Lead the mechanical design of control panels, PLC-based control systems, and large systems controls.
- Develop and optimize HVAC thermal and liquid cooling systems to meet performance and reliability requirements.
- Design and integrate control and power distribution systems with a strong focus on PLC-oriented architectures.
- Own the first project to bring a sourced component in-house for manufacturing, including redesign for internal production processes.
- Collaborate closely with cross-functional teams in a large manufacturing environment to align design decisions with production capabilities.
- Provide leadership, guidance, and mentorship to newer engineers, helping them grow in mechanical and hardware design.
- Manage design activities, timelines, and priorities to ensure projects meet technical, quality, and schedule expectations.
- Participate in design reviews, documentation, and continuous improvement initiatives for mechanical and control systems.
- Engage directly with customers to understand requirements, translate them into engineering solutions, and address design issues proactively.
We'll put each as - .
Now Skills: Essential Skills list:
- Bachelor of Science in Mechanical Engineering (BSME) required.
- 5+ years of hardware and mechanical design experience, including large form factor products.
- Strong background in mechanical engineering and mechanical design for complex systems.
- Hands-on experience with HVAC thermal engineering and liquid cooling systems.
- Proven ability to design fluid systems and thermal management solutions.
- Experience designing control and power distribution systems with a PLC-oriented focus.
- Proficiency in designing control panels and large systems controls.
- Demonstrated ability to manage design projects and guide technical decision-making.
- Strong customer communication skills, with experience in customer-facing engineering roles.
- Ability to mentor and educate junior engineers on mechanical design best practices.
Additional Skills & Qualifications:
- Experience working with chassis and enclosure design for large hardware systems.
- background in thermal design and optimization for manufacturability and performance.
- Exposure to PLC programming concepts and integration with mechanical systems.
- Experience in a manufacturing-focused environment supporting multiple customer products.
- Interest in supporting new companies and startups in improving and maturing their product designs.
- Demonstrated ability to collaborate across disciplines, including production, operations, and controls engineering.
We'll make two paragraphs: one for Essential Skills, one for Additional Skills & Qualifications, each followed by a
.
Now Pay: The pay range: "$52.88 - $57.69/hr." plus explanation about individual compensation depending on factors. We'll keep that as a paragraph.
Now Benefits: list of benefits:
- Medical, dental & vision
- Critical Illness, Accident, and Hospital
- 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available
- Life Insurance (Voluntary Life & AD&D for the employee and dependents)
- Short and long-term disability
- Health Spending Account (HSA)
- Transportation benefits
- Employee Assistance Program
- Time Off/Leave (PTO, Vacation or Sick Leave)
We'll put as - .
We must not
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. Thus we need to decide which sections to include based on content. We have: - About the role: The description includes a paragraph about role: "The Senior Mechanical Design Engineer supports product design for innovative startups...". That's about the role. So we can have
About the role
with a paragraph. - Responsibilities: There's a list of responsibilities bullet points. So we can haveResponsibilities
with- each.
- Requirements / Qualifications / Skills: There's "Essential Skills" list and "Additional Skills & Qualifications". Could combine into Requirements or Skills. We need to decide which heading to use. The instruction says we can use headings like Requirements, Qualifications, Skills. We should include a section for skills/qualifications if there is substantive content. There is essential skills list and additional skills. So we can have
Essential Skills
maybe but they said use headings like Skills. Could useSkills
and list both essential and additional? But we need to preserve all info; we could split into two sub-sections? But they said prefer a few substantive sections over many thin ones. Could combine essential and additional into one Skills section with two lists? Or we could have Requirements (essential) and Additional Skills as separate sections? Might be thin. Better to have one Skills section with both essential and additional combined, maybe separate paragraphs. But we need to follow: Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose Skills. Thus
Skills
with paragraphs: maybe a short intro then- for essential skills and another
- .
Now Skills: Essential Skills list:
- Bachelor of Science in Mechanical Engineering (BSME) required.
- 5+ years of hardware and mechanical design experience, including large form factor products.
- Strong background in mechanical engineering and mechanical design for complex systems.
- Hands-on experience with HVAC thermal engineering and liquid cooling systems.
- Proven ability to design fluid systems and thermal management solutions.
- Experience designing control and power distribution systems with a PLC-oriented focus.
- Proficiency in designing control panels and large systems controls.
- Demonstrated ability to manage design projects and guide technical decision-making.
- Strong customer communication skills, with experience in customer-facing engineering roles.
- Ability to mentor and educate junior engineers on mechanical design best practices.
Additional Skills & Qualifications:
- Experience working with chassis and enclosure design for large hardware systems.
- background in thermal design and optimization for manufacturability and performance.
- Exposure to PLC programming concepts and integration with mechanical systems.
- Experience in a manufacturing-focused environment supporting multiple customer products.
- Interest in supporting new companies and startups in improving and maturing their product designs.
- Demonstrated ability to collaborate across disciplines, including production, operations, and controls engineering.
We'll make two paragraphs: one for Essential Skills, one for Additional Skills & Qualifications, each followed by a
- .
Now Pay: The pay range: "$52.88 - $57.69/hr." plus explanation about individual compensation depending on factors. We'll keep that as a paragraph.
Now Benefits: list of benefits:
- Medical, dental & vision
- Critical Illness, Accident, and Hospital
- 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available
- Life Insurance (Voluntary Life & AD&D for the employee and dependents)
- Short and long-term disability
- Health Spending Account (HSA)
- Transportation benefits
- Employee Assistance Program
- Time Off/Leave (PTO, Vacation or Sick Leave)
We'll put as
- . We must not
- for additional skills? Could combine into one list but that would lose distinction. However we can still preserve all info by having two lists under the same heading, each preceded by a
describing. Alternatively we could have Requirements (essential) and Additional Skills as separate sections but that might be considered thin but still substantive. The instruction: "Prefer a few substantive sections over many thin ones." Having two sections for skills might be okay if each is substantive. But we have essential skills list (about 9 items) and additional skills list (about 6 items). Both are substantive. Could make two sections:
Essential Skills
andAdditional Skills & Qualifications
. However the allowed headings list includes Requirements, Qualifications, Skills. Not Essential Skills. But we could still use Skills heading and include both lists with headings inside? But they said usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to stick to those examples. So we can have
Skills
and inside we can have twoparagraphs: one for Essential Skills, one for Additional Skills & Qualifications, each followed by
- .
That seems okay.
- Benefits: There's a Pay And Benefits section with pay range and benefits list. So we need Benefits section (maybe also Pay). The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting states pay range and benefits. So we can have a Benefits section with list of benefits. Also we could have Pay section with pay range. But they said prefer a few substantive sections over many thin ones. Could combine Pay and Benefits into one section? But they gave examples of separate Pay and Benefits headings. However we could decide to have a Benefits section that includes pay range as part of it? The instruction: "include a section ONLY when the posting has real, specific content for it". Pay is specific content. Benefits is specific content. Could we have two sections: Pay and Benefits? That would be two sections but each substantive. The instruction says prefer a few substantive sections over many thin ones. Two sections is fine. Could also combine into a "Compensation and Benefits" section but not in the examples. Safer to follow examples: have
Pay
with the pay range paragraph, andBenefits
with the benefits list. - Schedule: Not mentioned. No schedule info. So we should not create Schedule section. - Work Environment: Could be a section but not in the examples list. The examples list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Work Environment is not listed. Should we include it? The instruction: "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. But they also say "Prefer a few substantive sections over many thin ones." Work Environment is substantive. Could include as a section with heading Work Environment. However they didn't list it as example but it's okay. But to be safe, maybe we can incorporate work environment details into About the role or another section? The About the role currently is just the initial paragraph. We could expand About the role to include work environment details. But we must preserve all substantive information; we can put work environment details in About the role paragraph. That would keep fewer sections. Similarly, Job Type & Location: Could be included in About the role or a short paragraph. The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Job type and location is not minor metadata? It's somewhat important. Could be included in About the role paragraph. Thus we can have sections: About the role (includes description, work environment, job type/location), Responsibilities, Skills (essential + additional), Pay, Benefits. We must not repeat job title as heading. We must output only HTML fragment, no /, no markdown. Let's craft. First, About the role: combine the initial description paragraph, plus work environment description, plus job type & location. Original description paragraph: "The Senior Mechanical Design Engineer supports product design for innovative startups whose products are not yet fully mature or in production. In this role, you act as a customer-facing expert, providing design feedback and improvements for manufacturability, particularly for clients with immature designs. You lead and mentor junior engineers while driving the development of mechanical systems, control panels, PLCs, and large system controls. The first project will focus on bringing a previously sourced component in-house for manufacturing and optimizing its design for production." Work Environment paragraph: "The role is based in a large, modern manufacturing facility that produces products for multiple customers. The facility is relatively new and experiencing significant growth, expanding its customer base and project portfolio. You work closely with production and engineering teams on the shop floor and in office and lab spaces, using tools and technologies related to mechanical design, controls, HVAC, and power distribution. The environment offers frequent interaction with startup clients, fast-paced project cycles, and substantial opportunities to influence product design and manufacturability as the facility grows." Job Type & Location: "This is a Contract position based out of Grantsville, UT." We can combine into one or two paragraphs. Let's make one paragraph that includes all? Might be long but okay. Better to split into two paragraphs for readability: first paragraph about role duties, second about work environment and job type/location. Thus About the role:
About the role
...
...
Now Responsibilities: list each bullet. We need to extract responsibilities bullet points from the posting: - Support product design for early-stage and startup clients whose products are not yet fully mature or in production. - Review and refine customer designs to improve manufacturability, reliability, and scalability for large form factor products. - Act as a customer-facing technical expert, clearly communicating design feedback, options, and recommendations. - Lead the mechanical design of control panels, PLC-based control systems, and large systems controls. - Develop and optimize HVAC thermal and liquid cooling systems to meet performance and reliability requirements. - Design and integrate control and power distribution systems with a strong focus on PLC-oriented architectures. - Own the first project to bring a sourced component in-house for manufacturing, including redesign for internal production processes. - Collaborate closely with cross-functional teams in a large manufacturing environment to align design decisions with production capabilities. - Provide leadership, guidance, and mentorship to newer engineers, helping them grow in mechanical and hardware design. - Manage design activities, timelines, and priorities to ensure projects meet technical, quality, and schedule expectations. - Participate in design reviews, documentation, and continuous improvement initiatives for mechanical and control systems. - Engage directly with customers to understand requirements, translate them into engineering solutions, and address design issues proactively. We'll put each as - .
Now Skills: Essential Skills list:
- Bachelor of Science in Mechanical Engineering (BSME) required.
- 5+ years of hardware and mechanical design experience, including large form factor products.
- Strong background in mechanical engineering and mechanical design for complex systems.
- Hands-on experience with HVAC thermal engineering and liquid cooling systems.
- Proven ability to design fluid systems and thermal management solutions.
- Experience designing control and power distribution systems with a PLC-oriented focus.
- Proficiency in designing control panels and large systems controls.
- Demonstrated ability to manage design projects and guide technical decision-making.
- Strong customer communication skills, with experience in customer-facing engineering roles.
- Ability to mentor and educate junior engineers on mechanical design best practices.
Additional Skills & Qualifications:
- Experience working with chassis and enclosure design for large hardware systems.
- background in thermal design and optimization for manufacturability and performance.
- Exposure to PLC programming concepts and integration with mechanical systems.
- Experience in a manufacturing-focused environment supporting multiple customer products.
- Interest in supporting new companies and startups in improving and maturing their product designs.
- Demonstrated ability to collaborate across disciplines, including production, operations, and controls engineering.
We'll make two paragraphs: one for Essential Skills, one for Additional Skills & Qualifications, each followed by a