Quality and Reliability Engineer

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections that have real specific content. The posting includes: - Title: Quality & Reliability Engineer (but we must not repeat job title as heading) - Department: CMS National Accounts - Location: Fully remote within the United States - Travel: Approximately 10–20% domestic and international travel We have sections: "About Custom Mechanical Solutions" (company description). Could map to "About the role"? Actually "About the role" is a heading we can use for description of role. The posting includes "The opportunity" describing role. Also "What you will own" (responsibilities). Also "You will probably love this role if..." (maybe skills or traits). Also "Required qualifications" and "Preferred qualifications". Also "Compensation and benefits" includes base salary and bonus eligibility. Also "Why CMS National Accounts" (maybe benefits or culture). Also "Compensation and benefits" includes base salary range. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not invent sections lacking content. We need to decide which sections we have content for. - About the role: we have description of role: "The opportunity..." plus maybe "Turn field challenges into better products..." etc. So we can put that. - Responsibilities: "What you will own" list of duties. That's responsibilities. - Requirements: maybe "Required qualifications". That's qualifications but we have separate headings for Requirements and Qualifications. Could treat "Required qualifications" as Requirements, and "Preferred qualifications" as Qualifications (or Skills). But we need to follow instruction: use headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide to map: - About the role: description of role and opportunity. - Responsibilities: "What you will own" bullet list. - Requirements: "Required qualifications" bullet list. - Qualifications: "Preferred qualifications" bullet list. - Skills: maybe we could extract from "You will probably love this role if..." which are traits/skills. Could also include technical skills from required qualifications but those are already in Requirements. We could put skills like "Root cause analysis, CAPA, 8D, 5 Why, fishbone, FMEA", "Technical communication", "Travel ability", etc. But we need to avoid duplication. Perhaps better to not create Skills if content is thin. But we have some skill-like statements in "You will probably love this role if..." which are more about personal traits. Could treat as Skills. - Benefits: we have "Compensation and benefits" includes base salary and bonus eligibility, also mention of Meriton’s benefits programs. Could also include travel expectations? Travel is not benefit but schedule? Travel could be considered Schedule? Actually schedule heading is for work schedule (remote, travel%). We have location and travel expectations. That fits Schedule. - Pay: base salary range. - Benefits: other benefits like bonus eligibility, participation in Meriton’s benefits programs. - Schedule: remote work, travel 10-20%, travel to Mexico up to four times per year. We must not create sections with placeholder text like "commensurate with experience". We have actual numbers. We must not repeat job title as heading. We must not include Job ID etc. We must remove boilerplate like EEO statement. We must preserve all substantive information. We need to output only HTML fragment, no /, no markdown fences. We need to use

for section headings,

• for any list of duties/requirements/benefits, and

  for prose. We need to ensure we don't create empty sections. Let's extract content. Company description: "Custom Mechanical Solutions delivers energy-efficient HVAC systems across the Pacific Northwest, with deep expertise in healthcare, education, data centers, and retrofit projects. We work with top manufacturers to meet performance and sustainability goals—always focused on quality, care, and progress.If you're ready to grow your career, we’re glad you found us. At CMS, you’ll join a team that supports your development and gives you space to make an impact. We review every application carefully and appreciate your interest in growing your career with our team." Then "About Custom Mechanical Solutions" paragraph: "Custom Mechanical Solutions (CMS) provides commercial HVAC equipment and technical solutions for complex building applications. We partner with contractors, engineers, building owners, and manufacturers throughout the equipment lifecycle—from system design and delivery through startup, troubleshooting, and field support.As part of the Meriton family of companies, CMS maintains its specialized technical expertise and customer-focused approach while benefiting from the resources and long-term investment of a growing national organization." We could combine these into About the role? Actually About the role should be about the role, not company. But we have no explicit "About the role" heading in source; we can create it using the description of the role and opportunity. The "The opportunity" paragraph: "CMS is looking for a Quality & Reliability Engineer to own and continuously improve the field-to-factory quality feedback loop for custom commercial and industrial HVAC equipment. You will lead technical investigations, turn incomplete field information into clear problem statements, and keep root-cause and corrective-action work moving through verified closure.This is a hands-on, highly collaborative role. You will work across field operations, project teams, customers, engineering, manufacturing, suppliers, and factory quality leaders. Your work will help teams respond faster, create repeatable repairs, reduce recurrence, and apply lessons learned to future projects." Also "Work from where you are. This is a fully remote position that can be based anywhere within the United States. Approximately 10-20% domestic and international travel is expected, including travel to customer sites and manufacturing facilities in Mexico. Travel may be heavier initially while you build relationships with key stakeholders and learn the factory systems. Travel to Mexico is generally expected up to four times per year to support investigations, gather technical evidence, collaborate with factory teams, and validate corrective actions." That could go under Schedule. Now responsibilities: "What you will own" bullet list: - Lead field-to-factory investigations. Coordinate quality issues from initial report through containment, root cause, corrective action, and verified closure. - Turn field intelligence into action. Gather the technical evidence needed for faster decisions and translate recurring trends into improvements in design, manufacturing, supplier controls, installation guidance, training, and documentation. - Create field-ready solutions. Develop clear, controlled Field Service Bulletins with approved repair steps, safety requirements, acceptance criteria, and closeout evidence. - Drive clarity and accountability. Keep owners, milestones, risks, decisions, and overdue actions visible. Remove blockers and escalate high-impact or aging issues when needed. - Use data to improve the program. Maintain quality dashboards and reports, identify systemic trends and emerging risks, and provide concise updates to leadership, project teams, customers, and factory partners. - Go where the evidence is. Travel to customer sites and manufacturing facilities in Mexico to inspect equipment, support troubleshooting, gather evidence, collaborate with factory teams, and validate repair effectiveness. We can make each as

• . Now "You will probably love this role if..." bullet list (traits): - When something fails, your first question is “Why?” and you keep digging until the evidence supports the answer. - You enjoy both the technical details and the bigger picture, from walking a jobsite and troubleshooting equipment to explaining the path forward clearly. - You take ownership without waiting for every step to be laid out, bring the right people together, and keep work moving until the issue is truly closed. - You are comfortable influencing across teams, even when you do not directly manage the people involved. - You want to help build and improve a quality program, not simply maintain one. We could treat these as Skills or maybe as "Skills" heading. Now Required qualifications bullet list: - A bachelor's degree in Mechanical, Electrical, Industrial, Manufacturing, or Quality Engineering, or an equivalent combination of technical education and relevant professional experience. - At least three years of relevant experience in manufacturing quality, field service, commissioning, reliability engineering, technical investigations, or related technical project support. - Strong mechanical and/or electrical investigation and troubleshooting skills. - Working knowledge of structured problem-solving methods such as RCA, CAPA, 8D, 5 Why, fishbone analysis, or FMEA. Ability to translate incomplete field information into clear technical problem statements and drive corrective actions through verified closure. - Ability to communicate complex technical issues clearly to technical and nontechnical audiences. - Ability to travel domestically and internationally approximately 10–20%, including travel to manufacturing facilities in Mexico. - A valid passport at the time of hire is preferred; candidates without one must be able to obtain one within the first 90 days of employment. Now Preferred qualifications bullet list: - Five or more years of relevant quality, reliability, field-service, commissioning, or technical investigation experience. - Direct experience with commercial or industrial HVAC equipment. Experience with custom air-handling equipment, controls, construction drawings and specifications, startup, commissioning, or active job-site processes. - Experience working directly with manufacturing facilities, suppliers, factory quality teams, or field-service organizations. - Experience developing technical repair procedures, Field Service Bulletins, corrective-action documentation, or quality dashboards. Now Compensation and benefits: - Base salary: $95,000-$125,000 annually, depending on experience. - This position is also eligible for a discretionary bonus. - Eligible employees may participate in Meriton’s benefits programs in accordance with applicable plan terms. Now "Why CMS National Accounts" paragraph: - You will join a fast-moving team supporting complex equipment and significant projects where expectations are high, and the connection between field performance and customer experience matters. This role offers the opportunity to make quality information more complete, corrective actions more durable, repairs more repeatable, and lessons learned more useful across a growing portfolio. - If you are ready to solve meaningful technical problems and help build a stronger quality and reliability program, we would like to hear from you. That could be part of Benefits or maybe a separate section like "About the team". But we have limited headings; we could incorporate into Benefits or maybe into About the role. But we already have About the role covering role description; we could add this as part of Benefits? Actually it's more about team/culture. Could treat as Benefits (non-monetary). But we already have Benefits heading for compensation/benefits; we could add a bullet list for benefits like "Fast-moving team, opportunity to make impact". However the instruction says use
  • for any list of duties/requirements/benefits. So we could make a Benefits section with bullet points: "Fast-moving team supporting complex equipment and significant projects", "Opportunity to make quality information more complete, corrective actions more durable, repairs more repeatable, lessons learned more useful", "Chance to solve meaningful technical problems and help build a stronger quality and reliability program". That seems okay. But we also have compensation details (base salary, bonus) which could go under Pay heading. Schedule heading: remote work, travel expectations. We need to ensure we don't create sections with placeholder text. All content we have is specific. Now we need to decide which headings to include. Potential sections: - About the role: combine "The opportunity" paragraph plus maybe company description? Actually About the role should focus on role, not company. We'll use the "The opportunity" paragraph and maybe the initial paragraph about CMS? The initial paragraph is about company; but we could include that as part of About the role? Might be okay but it's more about company. However we have no other place for company description; we could put it under About the role as introductory context. The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid including company description there. So we can put company description and opportunity in About the role