Data Quality Specialist

Here's a thinking process: 1. **Analyze the Request:** - Input: A job posting for a Data Quality Specialist at Piper Companies. - Task: Reformat into clean, well-structured semantic HTML. - Rules: - Use `

` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use `

• ` for lists of duties/requirements/benefits - Use `

  ` for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID / requisition numbers as headings - fold minor metadata into 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 - Output ONLY the HTML fragment — no /, no markdown code fences 2. **Analyze the Input Text:** Let me extract the relevant parts: - Company: Piper Companies - Role: Data Quality Specialist - Location: Lititz, PA - Summary: Support leading organization within consumer healthcare and manufacturing industry. Focus on improving investigation and CAPA performance through data analysis, governance, accountability, and cross-functional collaboration. - Responsibilities: (list of 8 bullet points) - Qualifications: (list of 5 bullet points, with some detail) - Compensation/Pay: Pay Rate: $20-25/hr, Contract Opportunity, Comprehensive Benefits: Medical, Dental, Vision, 401K, PTO, Sick Leave (as required by law), and Paid Holidays - Application Period: This job opens for applications on 9/3/2026. Applications for this job will be accepted for at least 30 days from the posting date. - Keywords: list of keywords Now, rules application: - Section headings:

  for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule - But: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text" - "never create Pay/Schedule/Benefits sections unless the posting actually states them" - The posting has specific Pay info: $20-25/hr, Contract Opportunity, Comprehensive Benefits list. So Pay and Benefits sections are warranted. - Schedule: Not mentioned. So I should NOT create a Schedule section. - Application Period: Has specific dates/duration, but the rules say "Remove... application instructions." And "Remove... duplicated lines, and application instructions." So I should drop the application period text. - Keywords: Probably drop or maybe fold into Skills? Rules say remove boilerplate, duplicated lines, and application instructions. Keywords might be considered part of the posting but not necessarily needed. I'll consider if they add value. The rules say "Preserve ALL substantive information; do NOT invent or summarize away detail." Keywords are somewhat substantive but often considered filler. I'll likely drop them or maybe include as a brief

  if needed, but rules prefer few substantive sections over many thin ones. I'll likely omit them to keep it clean, or maybe fold into a small note. Let me re-read: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Keywords aren't explicitly listed, but "duplicated lines" might apply. I'll omit keywords to stay safe and focused on substantive content. - Job title: "Do NOT repeat the job title as a heading (the page already shows it)" - so I won't add an or for "Data Quality Specialist". I'll start directly with sections. - Job ID / requisition numbers: Not present in the text, so fine. - "Fold minor metadata into a short

  or drop it." - Application period is minor metadata, I'll drop it per "Remove... application instructions." - "Preserve ALL substantive information" - responsibilities, qualifications, pay, benefits are substantive. Now, map to sections: - About the role: The first paragraph describes the role. I'll use

  About the role

  and then

  with the description. - Responsibilities:

  Responsibilities

  followed by
  • items. - Requirements: The posting doesn't have a explicit "Requirements" section heading, but has "Qualifications of the Data Quality Specialist". I'll map that to

    Requirements

    or

    Qualifications

    . The rules say use headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I need to decide. The posting has "Qualifications" content. It also has skills implied. I'll likely use

    Qualifications

    for the qualifications list, and maybe

    Skills

    if there's distinct skills content, but the qualifications already include skills. Let's see: "Qualifications of the Data Quality Specialist: 1-2 years of experience... Knowledge of Good Documentation Practices... Strong organizational, communication, critical thinking, and problem-solving skills. Bachelor’s degree preferred..." That's both qualifications and skills. I'll probably use

    Qualifications

    and include all that content there, or split into Qualifications and Skills if distinct. To be safe and follow "Prefer a few substantive sections over many thin ones", I'll combine related content. But the rules list specific headings as examples. I'll use

    Qualifications

    for that list, and maybe

    Skills

    if I need to, but I'll check if there's separate "Skills" content. There isn't really separate from qualifications. I'll just use

    Qualifications

    . - Pay: The posting has "Compensation for the Data Quality Specialist: Pay Rate: $20-25/hr Contract Opportunity Comprehensive Benefits: Medical, Dental, Vision, 401K, PTO, Sick Leave (as required by law), and Paid Holidays". So I'll create

    Pay

    and

    Benefits

    . Wait, rules: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. But it also says "include a section ONLY when the posting has real, specific content for it". It has specific pay rate and benefits list. So I'll create Pay and Benefits sections. However, the Benefits content is detailed. I'll make

    Pay

    with the pay rate, and

    Benefits

    with the benefits list. But wait: "never emit a heading followed by filler/placeholder text". The benefits list is specific, so it's fine. - Schedule: Not mentioned. So NO Schedule section. - About the role: I'll include the first paragraph. Let's structure: -

    About the role

    ...description...

    -

    Responsibilities

    • ...items...
    -

    Qualifications

    • ...items...
    -

    Pay

    ...pay rate and contract type...

    -

    Benefits

    • ...benefits...
    Check rules again: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It lists "Requirements" and "Skills" as examples. The posting has "Qualifications" content. I could use

    Requirements

    but the content is labeled "Qualifications". I think using

    Qualifications

    is fine, as it matches the content label. I'll stick with Qualifications. For Skills, the qualifications already include skills, so I won't create a separate Skills section unless there's distinct skill content beyond qualifications. To avoid thin sections, I'll merge skills into Qualifications or just use Qualifications. Let's re-read carefully: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This is telling me what headings to use and what they correspond to. I should use these headings if the content exists. The posting has "Qualifications of the Data Quality Specialist:" so

    Qualifications

    . It has responsibilities listed, so

    Responsibilities

    . It has pay and benefits, so

    Pay

    and

    Benefits

    . It doesn't have a explicit "Requirements" section separate from qualifications, and it doesn't have a "Skills" section separate from qualifications. I'll use

    Qualifications

    for the qualifications content. I might not use

    Skills

    if there's nothing beyond what's in Qualifications. Same for "Requirements" - the qualifications serve as requirements. What about "About the role"? The first paragraph: "Piper Companies is seeking a Data Quality Specialist to support a leading organization within the consumer healthcare and manufacturing industry located in Lititz, PA. This individual will focus on improving investigation and CAPA performance through data analysis, governance, accountability, and cross-functional collaboration." That's the about role content. Responsibilities: 8 bullet points. Qualifications: 5 bullet points (but some are paragraphs within bullets). Pay: "$20-25/hr Contract Opportunity" Benefits: "Comprehensive Benefits: Medical, Dental, Vision, 401K, PTO, Sick Leave (as required by law), and Paid Holidays" Application period: "This job opens for applications on 9/3/2026. Applications for this job will be accepted for at least 30 days from the posting date." Rules say remove application instructions. So drop. Keywords: drop. Now, format each section: About the role:

    Piper Companies is seeking a Data Quality Specialist to support a leading organization within the consumer healthcare and manufacturing industry located in Lititz, PA. This individual will focus on improving investigation and CAPA performance through data analysis, governance, accountability, and cross-functional collaboration.

    Responsibilities:
    • Analyze and trend investigation and CAPA data to identify recurring issues, risks, and opportunities for improvement.
    • Develop and maintain quality reports, metrics, dashboards, and performance trackers.
    • Monitor investigation and CAPA timelines to ensure compliance with quality requirements and internal expectations.
    • Communicate investigation and CAPA status updates across multiple departments and stakeholders.
    • Facilitate meetings and ensure appropriate stakeholder engagement throughout the investigation lifecycle.
    • Support quality governance activities while ensuring adherence to company quality policies and procedures.
    • Maintain a strong presence on the manufacturing floor to support quality operations initiatives.
    Qualifications: