Specialty Sales Representative – Cardiometabolic Rare Disease

We need to output HTML fragment with sections: About the role? Actually we have description includes "About Arrowhead Pharmaceuticals" and "Key Responsibilities", "Qualifications", "Compensation & Benefits". Also maybe "Skills & Competencies". The instructions: 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. We need to decide which sections to include. The posting includes: About Arrowhead Pharmaceuticals (company overview). Key Responsibilities (with sub-bullets). Qualifications (Experience, Skills & Competencies). Compensation & Benefits (Compensation & Benefits). Also maybe "Skills & Competencies" could be separate section "Skills". But we can combine Qualifications and Skills into one "Qualifications" section with sublists? The instruction says use headings like Qualifications, Skills, Benefits, Pay, Schedule. We can have separate sections for Qualifications and Skills if there is content. The posting has "Qualifications" heading with subheadings Experience and Skills & Competencies. We could split:

  Qualifications

  for experience requirements, and

  Skills

  for skills & competencies. Or we could keep one Qualifications section with both experience and skills lists. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Qualifications and Skills into one section? But they gave examples of headings including Skills separate. However we can decide to have Qualifications (experience) and Skills (competencies) as separate if they are substantive. Both are substantive. Let's do two sections: Qualifications (experience) and Skills (skills & competencies). Also Benefits section (Compensation & Benefits). Also maybe About the role? The posting includes "About Arrowhead Pharmaceuticals" which is company overview, not exactly "About the role". Could use

  About the company

  but they didn't list that as example. They gave examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings. "About Arrowhead Pharmaceuticals" could be considered "About the role"? Not exactly. But we could treat it as "About the role" (description of role and company). However they said do NOT repeat the job title as a heading. The job title is Specialty Sales Representatives. So we can have a section "About the role" containing the description paragraph about the role and maybe company overview. But the description includes both role and company. We could split: first paragraph about role, then "About Arrowhead Pharmaceuticals" as company overview. Could put both under "About the role". That seems okay. Responsibilities: we have Key Responsibilities with bullet points. Use

  Responsibilities

  with
  • for each bullet. Qualifications: we have Experience bullet points. Use

    Qualifications

    with
    • . Skills: we have Skills & Competencies bullet points. Use

      Skills

      with
      • . Benefits: we have Compensation & Benefits. Use

        Benefits

        with
        • for each benefit item (base salary, incentive, equity, car allowance, comprehensive benefits). Also maybe Pay? They said only create Pay/Schedule/Benefits sections if posting actually states them. The posting states compensation details, so we can have Benefits section covering compensation and benefits. Could also have Pay section separate but they said prefer few sections. So we can combine compensation and benefits into Benefits. Schedule: not mentioned, so omit. We need to output only HTML fragment, no /, no markdown fences. We must preserve all substantive information. Ensure we don't lose any details. Let's extract content. Description paragraph: "Arrowhead Pharmaceuticals is seeking experienced, high-performing, and driven Specialty Sales Representatives to join our expanding commercial organization. This is a unique opportunity to play a meaningful role in the launch and growth of our cardiometabolic portfolio, including Plozasiran (siRNA targeting APOC3), developed for patients with rare and high-need cardiovascular conditions such as Familial Chylomicronemia Syndrome (FCS) and Severe Hypertriglyceridemia (SHTG). This role is critical to delivering launch excellence by driving prescriber activation, accelerating therapy adoption, and ensuring sustained utilization within complex healthcare environments. The Specialty Sales Representative will operate with strategic agility, strong clinical acumen, and disciplined execution to positively impact patient outcomes." About Arrowhead Pharmaceuticals paragraph: "Arrowhead Pharmaceuticals, Inc. (Nasdaq: ARWR) is a clinical stage biopharmaceutical company that develops medicines that treat intractable diseases by silencing the genes that cause them. Using a broad portfolio of RNA chemistries and efficient modes of delivery, Arrowhead therapies trigger the RNA interference mechanism to induce rapid, deep, and durable knockdown of target genes. RNA interference, or RNAi, is a mechanism present in living cells that inhibits the expression of a specific gene, thereby affecting the production of a specific protein. Arrowhead’s RNAi-based therapeutics leverage this natural pathway of gene silencing. Arrowhead is focused on developing innovative drugs for diseases with a genetic basis, typically characterized by the overproduction of one or more proteins that are involved with disease. The depth and versatility of our RNAi technologies enables us to potentially address conditions in virtually any therapeutic area and pursue disease targets that are not otherwise addressable by small molecules and biologics. Arrowhead is leading the field in bringing the promise of RNAi to address diseases outside of the liver, and our clinical pipeline includes disease targets in the liver and lung with a promising pipeline of preclinical candidates. Arrowhead’s corporate headquarters is in Pasadena, CA with research and development teams in Madison, WI and San Diego, CA. Our employees are nimble, science-driven innovators who are collaborating to bring new therapies to patients in need." Key Responsibilities: bullet list: - Territory & Strategic Business Planning - Develop and execute comprehensive, data-driven territory business plans aligned to brand strategy and launch objectives. - Analyze territory data (prescribing trends, account potential, access landscape) to identify growth opportunities and prioritize high-value targets. - Manage territory budget responsibly, including speaker programs and promotional initiatives. - Consistently achieve or exceed sales goals and performance metrics. - Prescriber Activation & Clinical Engagement - Deliver compelling, compliant, and clinically accurate product education within approved labeling. - Articulate complex clinical data and value propositions tailored to cardiologists, lipid specialists, endocrinologists, and targeted PCPs. - Differentiate Arrowhead therapies within a competitive and evolving cardiometabolic landscape. - Execute speaker programs, educational events, and peer-to-peer engagements to drive awareness and adoption. - Support appropriate patient identification and therapy initiation through thoughtful provider engagement. - Stakeholder & Account Management - Build and sustain strong, trust-based relationships with healthcare professionals, office staff, and institutional stakeholders. - Navigate complex health systems and coordinate effectively within IDNs in partnership with Key Account Managers. - Identify access barriers and collaborate with Market Access and patient services to support pull-through. - Maintain consistent, high-quality engagement and service across accounts to drive durable utilization. - Cross-Functional Collaboration - Partner closely with Marketing, Medical Affairs, Market Access, Health IT, and Patient Services to align territory execution with enterprise strategy. - Provide actionable field insights regarding market dynamics, competitive activity, and customer feedback. - Compliance & Operational Excellence - Maintain full compliance with company policies, industry regulations, and promotional standards. - Accurately document field activity and manage CRM reporting in a timely manner. - Demonstrate disciplined execution, accountability, and ethical conduct in all engagements. - Travel & Engagement - Represent Arrowhead at regional and national meetings, training programs, and key conferences (~30% travel required). - Overnight travel may be necessary depending on territory geography. Qualifications (Experience): - Bachelor's degree or equivalent experience and minimum 5 years of pharmaceutical sales experience required. - Demonstrated success launching or expanding complex therapies requiring access navigation and clinical depth required. - 3+ years in specialty, rare disease, or cardiovascular therapeutic areas strongly preferred. - Experience working within integrated delivery networks (IDNs) or complex healthcare systems preferred. Skills & Competencies: - Strong territory planning and account management capabilities with a data-driven mindset. - Ability to interpret and communicate complex clinical data confidently and credibly. - Excellent communication, presentation, and relationship-building skills. - High level of business acumen and ability to identify strategic growth opportunities. - Resilience, adaptability, and ability to thrive in a fast-paced launch environment. - Proven track record of achieving or exceeding performance targets. - Strong organizational skills and ability to manage competing priorities effectively. Compensation & Benefits: - Competitive base salary: $160,000-$180,000 plus incentive compensation (20-30% target bonus). - Equity (RSUs) and car allowance program. - Comprehensive benefits package including health, dental, vision, and 401(k). Also final motivational sentence: "Ready to make a difference? Join us in our mission to bring transformative RNAi therapies to patients with rare cardiovascular conditions. Apply now to be part of something extraordinary." This is application instruction / call to action; we should remove application instructions per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should drop that final paragraph. Now we need to format. We'll have sections:

          About the role

          ... (combine first two paragraphs? Actually first paragraph about role, second about company. Could combine both into one

          but that may be long. Could split into two

          under same heading. That's fine. Then

          Responsibilities

          with
          • for each bullet. Should we keep sub-bullets? The original had main categories with sub-bullets. We could flatten: each sub-bullet as
          • . Or we could keep categories as
          • with nested
            . The instruction: Use
            • for any list of duties/requirements/benefits. It didn't forbid nested lists. Safer to flatten each duty as
            • . We'll lose the category headings but still preserve all duties. Could also keep categories as
            • with bold text? But we must not invent formatting beyond HTML. Could do
            • Territory & Strategic Business Planning: ... but that adds extra text not in original? It's okay to keep the category heading as part of the
            • text. We'll include the category heading as part of the
            • text, then sub-items as separate
            • maybe indented? But nested lists would be okay. Let's do nested lists: outer
              for each main category, inner
              for sub-bullets. That still uses
              • . That should be fine. Similarly for Qualifications and Skills: they are simple lists; we can just
                • . Benefits: list items. Now ensure we don't include any filler like "commensurate with experience". Not