Clinical Specialist CRM - Fairfax, VA

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Only include sections that have real specific content. We need to parse the job posting. Key info: - Application window close date: - 21 Sep 2026 (maybe "Application window closes Sep 21, 2026"). - "Careers that change lives start here." etc. Not needed. - "We anticipate the application window for this opening will close on - 21 Sep 2026" -> we can include as a short paragraph maybe under a heading? Not a required heading. Could be part of About the role? Might be meta. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a short

with that info. - "Careers that change lives start here." maybe not needed. - "Medtronic is a global leader..." maybe part of About the role. - "Your unique talents will help shape the future..." also about role. - "A Day in the Life" maybe not a heading; we have "A Day in the Life" repeated. - "We are seeking a committed professional to join our team." etc. - "While this is a remote position not located at a physical Medtronic site, the candidate hired will be required to reside within the territory and drive to multiple accounts throughout the region. A valid driver's license is essential for this role." - "Bring your talents to a leader..." - "Rooted in our long history..." - "We support your growth..." - "Join us for a career that changes lives." - "CAREERS THAT CHANGE LIVES - POSITION DESCRIPTION: Provide technical, educational, operational and sales support to assist the district in meeting Cardiac Rhythm Management (CRM) sales and customer service objectives." - Then bullet list of responsibilities: Technical Support, Operational Support, Educational Support, Sales Support, Ongoing Technical Development. - Then "MUST HAVE - BASIC QUALIFICATIONS:" with education/experience combos. - Then "NICE TO HAVE - DESIRED/PREFERRED QUALIFICATIONS:" list. - Then "PHYSICAL JOB REQUIREMENTS:" list. - Then "Travel Requirements: Minimum travel of 10%" - Then benefits: "We offer a wide range of benefits, resources, and competitive compensation plans designed to support you at every career and life stage. Learn more about our benefits here." - Then "In addition to Base Salary, this position is eligible for a Sales Incentive Plan (SIP), which provides the opportunity to earn significant incentive compensation for achieving or exceeding your goals." - Then "The provided base salary range is used nationally. The rate offered is compliant with federal/local regulations and may vary by experience, certification/education, market conditions, location, etc." Thus we have content for Benefits, Pay (base salary range, SIP). Schedule: mention weekend/holiday work, weeknight call coverage, travel 10%, etc. So we can include Schedule section. We need to avoid boilerplate: EEO, legal, scam warnings, etc. Remove duplicated lines. We need to preserve all substantive information. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we may combine some: Requirements and Qualifications maybe overlapping. The instruction: Use headings for those categories if content exists. We have basic qualifications (MUST HAVE) and nice-to-have (NICE TO HAVE). Could put under Requirements (basic) and Qualifications (preferred). Or combine. We also have Skills: maybe from desired qualifications list (Microsoft tools, communication, etc.) Could be Skills. Physical job requirements maybe part of Requirements? Could be separate but not in list of allowed headings. Not required to include if not matching allowed headings. But we could include under Requirements or maybe under a generic section? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples; we could also use other headings? Probably better to stick to those. Physical job requirements could go under Requirements. Travel requirement maybe under Schedule. Now produce HTML fragment. We need to avoid repeating job title as heading. Not needed. We'll output something like:

Application window closes Sep 21, 2026.

About the role

Medtronic is a global leader in healthcare technology with a mission to alleviate pain, restore health, and extend life. ...

But we need to preserve all substantive information; we must not omit details like remote position, residing within territory, driver's license, etc. So include those. Let's craft About the role paragraph summarizing: remote position, must reside within territory, drive to multiple accounts, valid driver's license essential, role provides technical, educational, operational and sales support for CRM, etc. Also mention mission, growth, training, mentorship. We need to be careful not to invent. Now Responsibilities: list items under

• . We have categories: Technical Support, Operational Support, Educational Support, Sales Support, Ongoing Technical Development. Under each we have bullet points. We could flatten all responsibilities into a list, but better to keep subheadings? Not allowed maybe. Could just list each responsibility as separate
• . We'll preserve details. Let's extract each responsibility bullet: Technical Support: - Successfully completes CRM Field Technical Training – including online and field-based training - Performs checks/interrogations of all CRM medical device systems post sign-off - Supports implants of all CRM products post sign-off - Provides on-call support as needed on evenings and weekends post sign-off - Provide troubleshooting support as requested Operational Support: - Assures completion of patient registration and any other required hospital documentation - Helps manage consignment inventory and trunk inventory once obtained - Provides additional inventory support to meet customer needs - Maintains software on programmers throughout the district as directed - Assists with managing daily coverage logistics as needed Educational Support: - Educates and trains physicians, hospital personnel and office staff on products or solutions for which training has been completed - Assists with educating and training new Clinical Specialists and Sales Representatives post sign-off Sales Support: - Partners with DSM, Sales Reps and DM to learn market dynamics and local customer motivations and needs; has a basic understanding of how Medtronic CRM products and solutions offer value to the customer - Assists with obtaining customer POs throughout the quarter - Has a basic understanding of the competitive landscape - Independently identifies customer needs and opportunities and provides feedback to Sales Rep(s) to support sales objectives Ongoing Technical Development: - Stays up to date on new products, solutions and patient management offerings - Completes all assigned training in a timely manner - Performs other related duties as assigned Now Requirements (basic qualifications): Must have either: - High School Diploma PLUS a minimum 6 years of work experience in healthcare, field sales or work experience utilizing complex mathematics, mechanical concepts, science or computing - OR Associate’s Degree PLUS a minimum 4 years of work experience in healthcare, field sales or work experience utilizing complex mathematics, mechanical concepts, science or computing - OR Bachelor’s Degree PLUS a minimum 2 years of work experience in healthcare, field sales, or work experience utilizing complex mathematics, mechanical concepts, science or computing We'll put as list. Qualifications (nice-to-have): list: - Thorough working knowledge of medical terminology and the medical device industry - Proven ability to build/maintain positive relationships with peers and colleagues across organization levels - Strong work ethic in accomplishing objectives of the position - Expertise with Microsoft tools & other applications (i.e., SalesForce.com) - Ability to meet vendor credentialing requirements - Excellent customer service skills - Excellent interpersonal, written/verbal communication skills - Ability to coordinate/participate in numerous tasks/projects in a fast-paced environment in an organized manner while meeting deadlines Skills: maybe we could separate some of these as Skills, but we already have Qualifications. Could treat Qualifications as preferred qualifications, and Skills as maybe from physical job requirements? But we have physical job requirements list; we could put under Requirements or maybe under a separate Skills? The instruction says we can use Skills heading if we have content. Physical job requirements could be considered Skills? Not exactly. But we could include physical job requirements under Requirements as well. Better: Use Requirements for basic qualifications, Qualifications for nice-to-have, Skills for physical job requirements and maybe other skill-based items (Microsoft tools, communication). But we already have Microsoft tools in nice-to-have. Might be okay to put under Qualifications. Let's decide: We'll have: - About the role - Responsibilities - Requirements (basic qualifications) - Qualifications (nice-to-have) - Benefits - Pay - Schedule We'll embed physical job requirements maybe under Requirements as a sublist? But we need to keep headings only; we can include paragraphs under Requirements that cover both basic qualifications and physical job requirements. But that may mix. Could add a separate heading "Physical Requirements" but not in allowed list; maybe we can still use it? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. But to be safe, we can stick to those. Physical job requirements could go under Requirements. Similarly, travel requirement (minimum travel of 10%) could go under Schedule. Now Benefits: we have statement about wide range of benefits, resources, competitive compensation plans. Also mention learning more about benefits here. We'll keep that. Pay: base salary range used nationally, rate may vary, plus eligibility for Sales Incentive Plan (SIP) offering significant incentive compensation. Schedule: mention required to work number of weekends and holidays during the quarter, weeknight call coverage as needed, travel 10%, must reside within territory and drive to multiple accounts, valid driver's license essential, etc. Now produce HTML. We need to ensure no boilerplate: remove EEO, legal, scam warnings, duplicated lines, application instructions, etc. Also remove repeated lines like "Physical Job Requirements" duplicated. Let's craft. We'll start with a short paragraph for application window. Then About the role paragraph. Then Responsibilities with

  • . Then Requirements with maybe two subsections: Basic Qualifications and Physical Job Requirements. But we can't add headings inside? We could just list them as

    then

    . But we need to keep structure simple. Could do:

    Requirements

    Basic qualifications: ...

    Physical job requirements: ...

    maybe not needed. But we need to use
    • for any list of duties/requirements/benefits. So for basic qualifications we should use list. For physical job requirements also list. Thus:

      Requirements

      Basic qualifications

      but h4 not allowed? Not specified; we can use

      for prose and

      • for lists. Could embed headings inside

        using . That's okay. Thus:

        Requirements

        Basic qualifications:

        • High School Diploma PLUS a minimum 6 years of work experience in healthcare, field sales or work experience utilizing complex mathematics, mechanical concepts, science or computing
        • OR Associate’s Degree PLUS a minimum 4 years of work experience in healthcare, field sales or work experience utilizing complex mathematics, mechanical concepts, science or computing
        • OR Bachelor’s Degree PLUS a minimum 2 years of work experience in healthcare, field sales, or work experience utilizing complex mathematics, mechanical concepts, science or computing