Field Clinical Specialist - Phoenix

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes description about company, opportunity, essential duties and responsibilities, required education etc, salary range, benefits. So we can have sections: About the role (maybe from "The Opportunity" paragraph), Responsibilities (list of duties), Requirements (education/experience etc), Skills (maybe from required knowledge/skills), Benefits (list of benefits), Pay (salary range). Schedule? Not provided (travel 80% etc but not schedule). So we omit Schedule. We must not repeat job title as heading. Use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO etc. At end there is "Equal Opportunity Employer Veterans/Disabled" - remove. Also "EBR Systems, Inc. does not accept unsolicited resumes..." that's application instruction? It's a note about recruitment agencies; maybe considered boilerplate? It's not exactly application instructions but could be considered a note; but we should remove? The instruction says remove application instructions. That line is about not accepting unsolicited resumes; it's a recruitment instruction. Likely remove. Also "Please refrain from solicitations at this time." remove. Also remove duplicated lines: there is duplicate Physical Requirements paragraph repeated; we should keep only one instance. We need to ensure we include all substantive info: company description, opportunity, duties list, required education/experience, skills, benefits, salary range. Let's extract. Company description paragraph: "About EBR Systems At EBR Systems, we're not imagining the future of cardiac care. We're building it. We are the team behind the world's first FDA-approved leadless left ventricular endocardial pacing device for heart failure. It's a breakthrough that's redefining what's possible, and it's just the beginning. Based in Silicon Valley, we're advancing the WiSE System, a first-of-its-kind device in cardiac rhythm management. Your work here has a direct line to patients whose lives depend on what we build. We hire people who want to solve hard problems and who care about getting it right. We invest in our people as much as our technology. Expect a collaborative, transparent culture, real career growth in a fast-moving startup, competitive compensation, equity, comprehensive benefits, and generous PTO. If you want your work to matter, EBR is where you belong." That's about the company; could be placed under "About the role"? Actually "About the role" heading is for role description. The company description could be part of "About the role" or maybe we could have a separate "About the company" but not in allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should put company description under About the role? The "About the role" heading likely expects description of the role, but we can also include company overview there. The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's examples, not strict list; we can use those headings. We'll use About the role for role overview and company description. Then Responsibilities: list of duties from "Essential duties and responsibilities include, but are not limited to, the following:" and sub-bullets. We need to turn each duty into

  . The duties are grouped under headings like Clinical & Technical Support, Technical & Educational Assistance, etc. We could keep those as subheadings? Not allowed; only headings we can use are the listed ones. But we could keep the duty headings as plain text inside

  or as . Probably better to keep them as part of the li text. We must preserve all substantive information; not invent or summarize away detail. So we need to include each duty bullet exactly as given, but we can format as list items. Let's list duties: - Clinical & Technical Support: Provide on-site clinical assistance and technical expertise during LV leadless therapy procedures. Identify suitable patients, ensure adherence to best practices, and troubleshoot devices as needed. Assist in pre-procedure planning and post-procedure follow up to address any technical or clinical issues. - Technical & Educational Assistance Offer comprehensive training sessions, presentations, and hands-on demonstrations for healthcare professionals. Guide users through imaging modalities, procedure workflows, and evolving product features. - Customer & Site Management Build and maintain productive relationships with physicians, research coordinators, and clinical teams. Serve as the primary point of contact for assigned sites, facilitating device utilization, procedural planning, and logistical support. Provide continuous support and resources to help physicians achieve clinical and operational goals. - Physician & Staff Training Develop and deliver educational materials, including models, simulations, and in-service programs. Ensure teams understand device functionality, procedural techniques, and clinical data interpretation. - Data & Feedback Integration Gather feedback on device performance, procedural efficiency, and patient outcomes for internal teams. Implement systematic feedback collection methods, such as surveys, interviews, and focus groups, to gather comprehensive insights. Analyze feedback data to identify trends, areas for improvement, and opportunities for innovation. Collaborate with engineering and product development to inform product enhancements and future innovations. - Reporting & Compliance Ensure all clinical activities comply with all regulatory requirements and company policies. Generate accurate documentation for continuous record keeping. Adhere to all company policies, compliance standards, and ethical guidelines. Ensure compliance with healthcare facility requirements by securing and maintaining vendor credentials to gain access for sales activities and client support. - Other Duties And Responsibilities Other duties as assigned. We need to keep the exact phrasing; note some missing punctuation. We'll keep as is. Next, Required Education, Knowledge, Skills, And Abilities: includes education options, proficiency, experience, etc. We can split into Requirements (education/experience) and Skills (knowledge, skills, abilities). The heading list includes Requirements, Qualifications, Skills. We could put education/experience under Requirements, and then maybe Qualifications for certifications? Not present. We'll put education/experience under Requirements, and then Skills for proficiency etc. Let's parse: "Required Education, Knowledge, Skills, And Abilities High school diploma plus 11 years of relevant clinical support experience; or Associate degree plus 9 years of relevant clinical support experience; or Bachelor’s degree plus 7 years of relevant clinical support experience; or Advanced degree plus 5 years of relevant clinical support experience. (Clinical support may include field clinical specialist roles, clinical engineering, or related hospital-based positions.) Proficiency in CRM software, Microsoft Office Suite/applications, virtual meeting tools, and project management tools. Experience in cardiac rhythm management, structural heart, or advanced cardiac therapies. Familiarity with echocardiographic imaging, trans-septal techniques, and related cardiac intervention workflows. Demonstrated ability to communicate complex clinical concepts, train diverse audiences, and thrive in interventional cardiac procedure settings. Familiarity with cardiac imaging and hospital decision-making processes. Strong communication, negotiation, and presentation skills with the ability to effectively influence the target audience. Ability to develop physician champions and navigate complex account environments. Willingness to travel approximately 80% of the time to various locations, including but not limited to healthcare facilities, industry events, and EBR office(s), with frequent travel to healthcare facilities within the assigned territories. This may include weekend, overnight, and international travel. A valid driver’s license is required to perform essential job functions as reliable, cost- effective, and timely travel cannot be achieved through alternative transportation methods. Compliance with applicable driving and state regulations is also mandatory. Required to stand, walk and sit; talk or hear; use hands to finger, handle or feel objects or controls; reach with hands and arms. Required to stoop, kneel, bend, crouch and lift up to 20 pounds. Specific vision abilities required by this job include close vision, distance vision, depth perception, color vision and the ability to adjust focus. Subject to extended periods of sitting and/or standing, vision to monitor, and moderate noise levels." We need to avoid duplication: there is later a repeated Physical Requirements paragraph identical; we will keep only one. We'll split: Requirements: education/experience (the bullet list of education options). Skills: proficiency, experience, familiarity, abilities, etc. Also include travel willingness, driver's license, physical requirements maybe under Skills? Could be separate but we don't have a heading for Physical Requirements; we could include under Skills as part of abilities. Or we could create a separate section but not allowed; better to include under Skills. Benefits: list from "EBR Systems, Inc. offers a great place to work as well as generous benefits and growth opportunities:" then bullet list. Let's extract benefits: - Medical, dental, and vision insurance provided at no cost for employee-only coverage - 401(k) matching plan - Paid Time Off – starting at 3 weeks per year - Competitive salary with opportunities for career growth - Employee stock options - Life & AD&D and long-term disability insurance - Education assistance - Voluntary commuter benefits and pet insurance - Weekly company lunches and occasional happy hour events - Meaningful work and much more! We should keep as list. Pay: Salary Range $120,000 - $170,000 Base pay is one part of your total compensation. The salary offered will depend on several factors, including, but not limited to your experience, knowledge, skills, location, internal equity, and market alignment. Addition compensation may include bonuses and equity, along with a comprehensive benefits package. We'll put that under Pay heading. Schedule: Not provided; we omit. Now we need to output only HTML fragment, no /, no markdown. We'll structure:

  About the role

  ... company description + opportunity paragraph ...

  But we have two paragraphs: company description and "The Opportunity" paragraph. We could combine into one

  or separate

  s. Use

  for prose; we can have multiple

  under same section. Let's craft About the role section: include company description and the opportunity description. Company description paragraph as above. The Opportunity paragraph: "As a Field Clinical Specialist, you will provide comprehensive clinical, technical, and educational support to ensure the safe and effective use of our leadless left ventricular (LV) Cardiac Resynchronization Therapy (CRT) devices. Working closely with physicians, electrophysiology (EP) lab staff, and other healthcare professionals, you will deliver in-depth product training, procedural guidance, and ongoing support. Your expertise and engagement will be instrumental in improving patient outcomes and achieving the company’s strategic goals." We'll put that as another

  . Then Responsibilities:

  Responsibilities

  with each duty as
  • . Then Requirements:

    Requirements

    education options ... maybe as

    ? The instruction: Use
    • for any list of duties/requirements/benefits. So education options is a list; we should make it a
      • . Similarly skills list as
        • . Benefits as
          • . Pay maybe as

            (not a list). We'll follow. Thus: Requirements:

            • High school diploma plus 11 years of relevant clinical support experience; or
            ... but we need to keep the "or" separators. Could keep each option as separate
            • with the "or" at end of previous? Better to keep as one
            • containing the whole sentence with options separated by "or". But that is not a list of items; it's a single requirement with alternatives. However instruction says use
              • for any list of duties/requirements/benefits. This is a list of alternatives; we could still make each alternative a
              • . Let's do: