Prosthesis Supply and Inventory Coordinator

We need to output HTML fragment with sections: About the role? Actually the posting includes "Why Mayo Clinic" paragraph, then "Benefits Highlights", then "Responsibilities", then "Qualifications", then "Exemption Status", "Compensation Detail", "Benefits Eligible", "Schedule", etc. We need to follow rules: Use

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 (the page already shows it) and 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. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include. The posting includes: "Why Mayo Clinic" (intro), "Benefits Highlights", "Responsibilities", "Qualifications", "Exemption Status", "Compensation Detail", "Benefits Eligible", "Schedule", "Site Description". Also "Equal Opportunity" etc which is boilerplate to remove. Also "Recruiter Elizabeth Brownewell" maybe minor metadata. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have "Why Mayo Clinic" could be "About the role"? Actually "About the role" is generic; we could use that heading for the introductory paragraph about Mayo Clinic and the role? The posting includes "Why Mayo Clinic" describing the organization. Could be considered "About the role". We'll put that under

  About the role

  with paragraph. Then we have Responsibilities: we have a paragraph describing responsibilities. Could be bullet list? It's a paragraph with multiple sentences each starting with "is responsible for", "performs", "has responsibility". We could turn each into
• . Use
  • for any list of duties/requirements/benefits. So we should list duties as bullet points. Qualifications: we have bullet-like list: High School diploma or GED required. Minimum of three years' perioperative... Computer proficiency... Vocational training... Knowledge of medical terminology preferred. We can list as
    • . Benefits: we have Benefits Highlights with bullet points: Medical, Dental, Vision, Pre-Tax Savings, Retirement. Use
      • . Pay: we have Compensation Detail: $22.12 - $31.21 / hour. Also Benefits Eligible Yes. Could be Pay section includes hourly rate and benefits eligible? The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state compensation detail and benefits eligible. So we can have Pay section with paragraph: "$22.12 - $31.21 per hour. Benefits eligible: Yes." Or we could separate Benefits and Pay. But we already have Benefits section. So Pay section includes compensation detail and maybe benefits eligible? Actually benefits eligible is separate but could be in Benefits section? Might be okay to include in Pay. But we already have Benefits section for highlights. We'll keep Pay section for compensation detail only. Benefits Eligible could be noted in Benefits section? Might be redundant. We'll include Pay section with compensation detail. Schedule: we have Schedule Full Time Hours/Pay Period 80, Schedule Details Monday-Friday, 7am-3:30pm, Travel to other sites across the health system may be required. Weekend Schedule Not applicable at this time. International Assignment No. So we can put Schedule section with paragraph(s) or bullet list. Use

        for prose. Could list details. We also have Site Description which is not in allowed headings; we could fold into About the role? Or maybe we can omit because not required? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep site description. Where to put? Could be under About the role as additional paragraph. Or we could create a custom heading? Not allowed; only allowed headings list. But we could embed site description in About the role paragraph. That preserves info. Also Recruiter Elizabeth Brownewell: minor metadata; we can fold into a short

        or drop. Probably drop as minor metadata. Equal Opportunity boilerplate: remove. Now ensure we don't create sections with filler text. All sections have real content. We need to output only HTML fragment, no /. Use

        headings,

        ,

        • . Let's craft:

          About the role

          Mayo Clinic is top-ranked in more specialties than any other care provider according to U.S. News & World Report. As we work together to put the needs of the patient first, we are also dedicated to our employees, investing in competitive compensation and comprehensive benefit plans – to take care of you and your family, now and in the future. And with continuing education and advancement opportunities at every turn, you can build a long, successful career with Mayo Clinic.

          Just as our reputation has spread beyond our Minnesota roots, so have our locations. Today, our employees are located at our three major campuses in Phoenix/Scottsdale, Arizona, Jacksonville, Florida, Rochester, Minnesota, and at Mayo Clinic Health System campuses throughout Midwestern communities, and at our international locations. Each Mayo Clinic location is a special place where our employees thrive in both their work and personal lives.

          Responsibilities

          • Responsible for inventory management including supplies, instrumentation, equipment, and prosthesis/implants to support patient care.
          • Performs inventory control processes and communicates any variances to members of the perioperative team.
          • Assures data integrity, performing quality assurance checks of patient billing information and other data sources.

          Qualifications

          • High School diploma or GED required.
          • Minimum of three years' perioperative, surgical supply, sterile processing or experience working in a role requiring attention to detail, quality assurance, data integrity, and investigation required.
          • Computer proficiency with a variety of software, including word processing, spread sheets, databases, or other applications required.
          • Vocational training in medical support field preferred.
          • Knowledge of medical terminology preferred.

          Benefits

          • Medical: Multiple plan options.
          • Dental: Delta Dental or reimbursement account for flexible coverage.
          • Vision: Affordable plan with national network.
          • Pre-Tax Savings: HSA and FSAs for eligible expenses.
          • Retirement: Competitive retirement package to secure your future.

          Pay

          $22.12 - $31.21 per hour.

          Schedule

          Full time (80 hours per pay period). Monday‑Friday, 7:00 am‑3:30 pm. Travel to other sites across the health system may be required. Weekend schedule not applicable at this time. No international assignment.

          Check for any duplicated lines: we removed boilerplate. Ensure we didn't include "Benefits Eligible Yes" anywhere; we omitted it. Could be considered substantive; but we already have Benefits section. The posting says "Benefits Eligible Yes". Should we preserve that? It's a piece of info about eligibility for benefits. Could be included in Benefits section as a note. But we already have Benefits section describing plan options. Adding a line "Benefits eligible: Yes." could be useful. However the instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. We have Benefits section already; we can add a line inside Benefits section about eligibility. But we need to preserve ALL substantive information. So we should include that info. Let's add a
        • Benefits eligible: Yes.
        inside Benefits
        . Or we could add a

        after Benefits list. But better to add as list item. Similarly, we might want to include "Exemption Status Nonexempt". That's substantive; but not in allowed headings. Could we fold into About the role or Qualifications? Probably not. Could we add a section? Not allowed headings. But we could incorporate into About the role as a minor detail? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it. Exemption Status is not minor metadata? It's about FLSA classification. Might be considered minor metadata? Possibly we can fold into a short

        under About the role or Qualifications. But better to keep it. However we don't have a heading for it. We could add a

        after Qualifications maybe. But the instruction says we can fold minor metadata into a short

        or drop it. Exemption Status could be considered minor metadata. Let's drop it? But we need to preserve ALL substantive information. Is exemption status substantive? It's about whether the role is exempt or nonexempt; could be relevant. I'd say it's substantive. But we don't have a heading for it. Could we create a custom heading? 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, but says "Use

        for section headings (e.g. ...)" implying we should use those headings for sections. It doesn't explicitly forbid other headings, but to be safe we should stick to those. However we could incorporate exemption status into Qualifications or About the role as a sentence. Let's add a sentence in Qualifications: "Exemption status: Nonexempt." But that mixes with qualifications. Might be okay. Alternatively, we could add a

        after Qualifications: "Exemption status: Nonexempt." That's a short paragraph, not a heading. That would preserve info without creating a new heading. That seems acceptable: fold minor metadata into a short

        . Exemption status maybe not minor but we can treat as such. Similarly, "Site Description" we already folded into About the role. Recruiter name: minor metadata, we can drop. Now check for any other info: "Department Nursing" maybe minor metadata; we can drop. "City Red Wing State MN Remote NO" maybe location? Actually says City Red Wing State MN Remote NO. That seems like location: Red Wing, MN, Remote? Not sure. Could be location info. Might be substantive. Could we fold into About the role? Possibly add a sentence: "Located in Red Wing, MN (remote)." But the posting says City Red Wing State MN Remote NO. Might be indicating location: Red Wing, MN, not remote? Actually "Remote NO" means not remote. So location is Red Wing, MN. We could incorporate that into About the role: "This position is based in Red Wing, MN." But we need to preserve all substantive info. Let's add a sentence in About the role: "This position is based in Red Wing, MN." Now check for any other: "Schedule Details Monday-Friday, 7am-330pm" we used. "Travel to other sites across the health system may