Technical Writer

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Key info: - Application window closing date: "We anticipate the application window for this opening will close on - 25 Sep 2026". That's metadata; we can put in a short

maybe. - Intro paragraph: "At MiniMed, you can begin a lifelong career of exploration and innovation, while helping make a difference in the lives of people living with diabetes around the globe. You'll lead with purpose, breaking down barriers to innovation for a more connected, compassionate world." That's prose. - About The Role: heading "About The Role". Content: "The Technical Writer scopes, revises and drafts a variety of patient-facing technical literature needed to support a broad medical device portfolio Technical writer will be responsible for executing project requirements in the creation of technical literature. Responsibilities may include the following and other duties may be assigned." Then list of responsibilities (bulleted). We need to separate About the role (maybe a short paragraph) and Responsibilities as separate sections. - Responsibilities list: bullet points: Develop of a working understanding of medical device products Work with required subject matter experts to align content changes Author new literature in the Component Content Management System Review literature to ensure compliance with all known requirements and departmental SOPs Collaborate with graphic design team on layouts, drawings, images, and branding needs Ensure all required approvals are obtained so literature can complete required technical review Proactively identify gaps and work with team members to determine responses Note: "Develop of a working understanding" maybe grammar but keep as is. - Must Have: Minimum Requirements: "Bachelor’s degree with 2+ years’ relevant experience, or Advanced degree with 0 years of experience." - Nice To Have: Experience writing in a highly regulated environment, Experience writing patient-facing literature, Experience authoring in a Component Content Management System (CCMS) - Physical Job Requirements: This is a section but maybe we can treat as Requirements? It includes physical demands etc. Might be considered "Requirements" or "Physical Job Requirements". The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can put physical requirements under Requirements or maybe a separate section? The instruction says "Prefer a few substantive sections over many thin ones." So we could combine Minimum Requirements and Nice To Have into a Requirements section (or Qualifications). Also Physical Job Requirements could be part of Requirements. We need to decide sections: - About the role: heading

About the role

with paragraph(s) summarizing role. - Responsibilities:

Responsibilities

with

• list. - Requirements / Qualifications: Could have

  Requirements

  with
  • for minimum and nice-to-have? Or separate Minimum Requirements and Nice To Have as sublists? Probably combine. - Benefits and Compensation: We have salary ranges, benefits description, STI, etc. So we can have

    Benefits

    and maybe

    Pay

    separate? The instruction says include Pay section only if posting actually states them. It does state salary ranges. So we should have Pay section. Benefits section also present. Could combine but better separate as they are distinct. - Schedule: Not mentioned. No schedule info. So omit. - Skills: Could be derived from Nice To Have? But we have no explicit Skills section. Could put under Requirements or Skills. The instruction says use headings like Skills if there is content. We have Nice To Have items which are skills/experience. Could make a Skills section. But we already have Requirements; maybe better to have Requirements (minimum) and Skills (nice-to-have). However we need to avoid thin sections. Could combine into Requirements with both minimum and nice-to-have. But we need to follow instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can choose which to include. We have content for About the role, Responsibilities, Requirements (minimum), Nice-to-have (skills/experience), Benefits, Pay. We could make sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. That seems reasonable. Now we need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID/requisition numbers as headings (none present). Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes EEO statement at end, plus some other legal text about Fair Chance Ordinance, etc. We must remove that. Also remove "Physical Job Requirements" maybe we incorporate into Requirements? But we need to keep substantive info: physical demands etc. That is part of Requirements? It's about physical demands for office roles. We should keep that info. Where to place? Could be under Requirements as a paragraph. Also there is a line: "The above statements are intended to describe the general nature and level of work being performed by employees assigned to this position, but they are not an exhaustive list of all the required responsibilities and skills of this position." That's boilerplate; we can remove. Also "Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions." That's also boilerplate but maybe part of physical requirements? It's a standard statement; we could keep as part of Requirements? It's generic; but maybe we keep as it's substantive? It's about accommodations. Might be considered boilerplate but it's part of the job description. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. This is not EEO but accommodations statement. Might be okay to keep. Also "For Office Roles: While performing the duties of this job, the employee is regularly required to be independently mobile. The employee is also required to interact with a computer and communicate with peers and co-workers. Contact your manager or local HR to understand the Work Conditions and Physical requirements that may be specific to each role." That's substantive about physical demands; keep. Now about Benefits & Compensation: we need to extract salary ranges, benefits description, STI, etc. Also note about regular employees eligibility etc. Keep. Now about MiniMed overview: that's company description; could be considered boilerplate? It's about the company; maybe we keep as part of About MiniMed? Not required but could be considered filler. The instruction says remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Company overview might be considered not essential but it's substantive about the company. However the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep it unless it's clearly boilerplate like EEO. The company overview is substantive about the organization; we can keep as a paragraph maybe under About MiniMed? But we don't have a heading for that. Could just include as a paragraph after Benefits? But we need to avoid thin sections. Could include as a paragraph under a heading like "About MiniMed"? Not in the list of headings but we could still use

    About MiniMed

    if we want. The instruction gave examples but not exclusive; we could add other headings if needed. However they said "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not limited. So we could add About MiniMed heading. But we need to avoid many thin sections. The company overview is a few sentences; we could incorporate into a paragraph under Benefits? Not ideal. Maybe better to have a section "About MiniMed". That's fine. Now we need to remove the EEO statement at the end and the Fair Chance Ordinance text. Also remove "It is the policy of MiniMed to provide equal employment opportunity (EEO) ..." and the subsequent paragraphs about Fair Chance. Also remove the line about "For further details about our comprehensive benefits, we encourage you to visit the link below." and the link? Actually there is a line: "For further details about our comprehensive benefits, we encourage you to visit the link below." Then "About MiniMed MiniMed Benefits Overview". That seems like a duplicated line? We'll remove that promotional link instruction. Also remove "Learn more about our business, and our mission here." etc. We need to keep the MiniMed mission statement: "At the heart of everything we do is a simple Mission: to make every day a better day for people with diabetes." That's substantive about company; keep. Now let's extract content: - Application window closing date: "We anticipate the application window for this opening will close on - 25 Sep 2026". We'll put as a short paragraph maybe at top. - Intro paragraph: "At MiniMed, you can begin a lifelong career of exploration and innovation, while helping make a difference in the lives of people living with diabetes around the globe. You'll lead with purpose, breaking down barriers to innovation for a more connected, compassionate world." - About The Role heading: we will make

    About the role

    with paragraph: "The Technical Writer scopes, revises and drafts a variety of patient-facing technical literature needed to support a broad medical device portfolio. Technical writer will be responsible for executing project requirements in the creation of technical literature." (Note: original had missing period; we can keep as is but ensure readability.) - Responsibilities heading:

    Responsibilities

    with
    • list of the 7 items. - Requirements heading:

      Requirements

      with maybe two subparts: Minimum Requirements and Nice-to-have (Skills). But we could split into Requirements (minimum) and Skills (nice-to-have). Let's do that: Requirements for minimum, Skills for nice-to-have. Also include physical job requirements under Requirements? Could add a paragraph after minimum. Thus:

      Requirements

      Minimum Requirements: Bachelor’s degree with 2+ years’ relevant experience, or Advanced degree with 0 years of experience.

      Physical Job Requirements: For office roles, the employee is regularly required to be independently mobile, interact with a computer, and communicate with peers and co-workers. Reasonable accommodations may be made to enable individuals with disabilities to perform essential functions.

      But we need to preserve the exact phrasing? Not required to be exact but preserve substantive information. We'll keep close. - Skills heading:

      Skills

      with
      • for nice-to-have items: Experience writing in a highly regulated environment, Experience writing patient-facing literature, Experience authoring in a Component Content Management System (CCMS). - Benefits heading:

        Benefits

        with paragraph describing benefits: health, dental, vision insurance, HSA, FSA, life insurance, long-term disability, dependent daycare spending account, incentive plans, 401(k) with match, short-term disability, paid time off and holidays, employee stock purchase plan, employee assistance program, non-qualified retirement plan supplement, capital accumulation plan (subject to IRS minimum earnings). Also note that regular employees working 20+ hours per week eligible. Also note that some benefits may not apply to Puerto Rico. Also note link to MiniMed Benefits Overview (we can mention but not include actual link). We'll keep substance. - Pay heading:

        Pay

        with paragraph: Salary ranges for U.S. (excl. PR) locations: $58,000.00 - $98,000.00. For roles located in California, Seattle WA, Washington DC, Boston MA, and New York City, the salary range is $64,000