Join Our Quality Team!

We need to output HTML fragment with sections: About the role? Actually the posting includes sections: Roles We Hire For (list of roles), What Levels We Hire, What we are looking for, Education & Experience, About Rennscot MFG, ITAR Requirement (maybe not needed? It's a requirement but not a standard heading; we can include as a paragraph maybe under a generic heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Only include sections when posting has real specific content. So we need to map content to these headings. We have: - About the role: could be description of roles? The posting includes "Roles We Hire For" with details for each role. That could be under "About the role" or "Responsibilities". Probably "About the role" is appropriate for overview of role(s). Could also have "Responsibilities" for each role's duties. But we need to avoid duplication. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which headings to include based on content. We have content: description of each role (Quality Inspector, CMM Programmer, Quality Engineer) with duties. That fits "Responsibilities". Also we have "What Levels We Hire" describing entry/mid/senior levels. That could be "Qualifications" or "Skills"? Might be "Qualifications". Also "What we are looking for" includes precision mindset, technical grounding, continuous improvement, ownership, commitment to growing. That's like "Skills" or "Requirements". Also "Education & Experience" is clearly "Education & Experience" but not in list; we could use "Qualifications" or "Requirements". The list includes "Qualifications". So we can put education/experience under Qualifications. We have "About Rennscot MFG" description of company. That could be "About the role"? Actually "About the role" is about the job, not company. Maybe we could use "About the role" for role description, and "About Rennscot MFG" could be omitted? But we need to preserve all substantive information. Could include as a

under a generic heading like "About the Company" but not in allowed headings. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

for section headings (e.g. ...). Likely we should stick to those headings only. But we need to include company info somewhere. Could put it under "About the role"? That seems odd. Maybe we can treat "About Rennscot MFG" as part of "About the role" (the role at the company). Or we could add a

without heading? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't say we must wrap everything in headings; we can have

elements outside headings. So we can include a

for company description without a heading. That's acceptable. Similarly, ITAR Requirement is a requirement; could be under "Requirements". EEO statement is boilerplate to remove. Compensation Range: $75K - $130K is Pay info, so we need a Pay section. Schedule? Not mentioned. Benefits? Not mentioned. So we omit those. Thus sections: -

About the role

: maybe a brief overview: "We are building our Quality team..." etc. Could include the introductory paragraphs about Rennscot MFG and the team. But we already have company description separate. Could put the introductory motivational paragraphs under About the role. -

Responsibilities

: list of duties for each role. Could combine into a single list? Might be better to have subheadings? Not allowed; only

headings. Could have multiple

sections for each role? But they'd be same heading level; maybe we can have separate

for each role? The instruction says use

for section headings (e.g. About the role, Responsibilities...). It doesn't forbid multiple same headings, but better to have one Responsibilities section with sublists? Could use

• for each duty, and we can group by role using or

  inside li? Might be okay. Simplify: Provide a

  with each role's responsibilities as separate
  • containing a Role: then description. -

    Qualifications

    : include Education & Experience, Levels we hire, What we are looking for (skills). Could combine. -

    Skills

    : maybe separate technical skills? But we already have Qualifications. Could combine. Better to follow typical structure: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule. We have Pay. Thus:

    About the role

    : include intro about Rennscot MFG building Quality team, mission, etc.

    Responsibilities

    : list duties for each role.

    Qualifications

    : include Education & Experience, Levels we hire.

    Skills

    : include What we are looking for (precision mindset, technical grounding, continuous improvement, ownership, commitment to growing) plus ITAR requirement? Actually ITAR is a requirement, could be under Qualifications.

    Pay

    : include compensation range. We must not include Benefits or Schedule. Now ensure we preserve all substantive information: need to include details about each role, levels, what we are looking for, education/experience, company description, ITAR requirement, compensation. We must remove boilerplate: EEO statement, navigation, cookie, legal, scam-warning, application instructions (Submit your resume...). Also remove "Job Type: On-Site Job Location: Woburn, MA. At this time, we are only considering applicants within a 100-mile radius. No relocation assistance provided." That's location info; is that substantive? It's about job location and eligibility. Could be considered metadata; but instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. Location is minor metadata; we could include a short

    with location and job type. But we might drop it? The instruction: "fold minor metadata into a short

    or drop it." So we can include a short

    for location and job type. However we already have Pay section; we could add a

    before sections. But we must not repeat the job title as a heading. The job title is not given explicitly; it's maybe "Quality Inspector / CMM Programmer / Quality Engineer". We'll not add heading. Now craft HTML. We'll start with a

    for location and job type: "Job Type: On‑Site | Location: Woburn, MA (within 100‑mile radius). No relocation assistance provided." Then

    About the role

    with paragraphs: Rennscot MFG description and team building. Then

    Responsibilities

    with
    • for each role. Then

      Qualifications

      with
      • for Education & Experience and Levels we hire. Then

        Skills

        with
        • for What we are looking for. Then

          Pay

          with

          compensation range. Make sure not to include any filler like "commensurate with experience". Not present. Now write. Check for any duplicated lines: we need to avoid repeating same content. Let's extract content: Intro: "At Rennscot MFG, precision is not a setting on a machine — it is a standard built into everything we do and everyone we hire. We manufacture high-performance components through CNC machining and L-PBF additive manufacturing for the world's most demanding industries. Every part we make carries weight — literally and figuratively — and the people who ensure those parts are right are at the center of everything. We are building our Quality team and we want to hear from people who care about getting it right. Whether you are just starting out in metrology, growing your CMM programming skills, or you are a seasoned Quality Engineer with years of AS9100 experience under your belt — there may be a place for you here. We hire across all levels and are always interested in connecting with quality-minded people who want to do meaningful work alongside a team that invests in them." That's good for About the role. Roles We Hire For: - Quality Inspector — You ensure every product manufactured at Rennscot is of the highest quality and meets all customer specifications. You conduct in-process and final inspections using CMMs, optical comparators, surface plate tools, micrometers, and calipers. You read and interpret technical drawings and GD&T callouts, document your findings accurately, and flag non-conformances before they become problems. You bring care, attention to detail, and a standards-first mindset to every part you touch. - CMM Programmer — You turn complex geometries into precise measurement programs. Using PC-DMIS, Calypso, or equivalent software, you develop, prove out, and optimize CMM programs that establish the measurement foundation for our entire quality workflow. You understand GD&T deeply, think systematically about measurement strategy, and take pride in programs that are efficient, accurate, and built to last. - Quality Engineer — You connect the dots between inspection data, root cause, and continuous improvement. Depending on your experience level, you may be writing quality plans and NCRs, driving corrective and preventive actions, collaborating cross-functionally with Manufacturing Engineering, Production, and Project Engineering, or shaping the quality systems and metrology strategy that the whole organization relies on. At every level, you are someone who designs quality in — not just inspects it at the end. What Levels We Hire: - Entry-level: Building foundational skills in inspection, measurement, and quality documentation in a structured, supportive environment - Mid-level: Applying proven technical depth independently across more complex work, supporting team development and cross-functional collaboration - Senior: Leading quality programs, mentoring others, driving systemic improvements, and shaping quality strategy at an organizational or enterprise level - No matter where you are in your career, you will find that growth here is in your own hands. What we are looking for: - A precision mindset. You take quality seriously — not because someone is watching, but because the work matters. Our parts go to space and protect those who serve, and you feel the weight of that. - Technical grounding in metrology. You have hands-on experience with CMM operation or programming, GD&T per ASME Y14.5, and advanced measurement tools. At more senior levels, you bring expertise in SPC, FMEA, NCR/CAR/PAR management, and quality management system frameworks (AS9100, ISO 9001). - A continuous improvement instinct. You are not satisfied with finding problems — you want to solve them, prevent them from recurring, and build better processes in their place. You bring solutions, not just problems. - Ownership. Everyone at Rennscot is treated as an owner and their voice is heard. We expect the same in return — pride in your work, accountability for your outcomes, and a genuine investment in the team around you. - A commitment to growing. Whether you are building foundational skills or advancing the state of the field, you actively seek opportunities to learn. Experience with additive manufacturing quality, SPC, or CMM programming software such as PC-DMIS or Calypso is a plus at any level. Education & Experience: - We evaluate candidates based on the totality of their skills and experience. A range of educational backgrounds are welcomed: High School Diploma with relevant hands-on experience in quality inspection or metrology; Associate's or technical degree