Aquestive District Sales Manager

We need to output HTML fragment with sections: About the role? Actually we have "About Aquestive Therapeutics" then "The Role", "Key Responsibilities", "Qualifications", "Who Thrives Here", "Compliance", "The Company is required to provide a reasonable estimate..." includes salary range and benefits. Also "Available benefits include..." So we need sections: About the role? 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: About the role (maybe "About the role" corresponds to "The Role" paragraph). Responsibilities (Key Responsibilities). Qualifications (Qualifications). Benefits (Available benefits). Pay (Expected salary range). Possibly "Who Thrives Here" could be considered "Skills" or maybe not needed; but we could include as a section like "Who Thrives Here" but not in the list of suggested headings; but we can still use

  for any section heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those standard headings when applicable, but we can also have other headings? Probably better to stick to those headings and map content accordingly. We have "About Aquestive Therapeutics" which is about the company, not the role. Could be "About the role"? Actually "About the role" is a heading for description of the role. We have "The Role" paragraph describing role. So we can put that under

  About the role

  . Responsibilities: Key Responsibilities. Qualifications: Qualifications. Benefits: Available benefits. Pay: Expected salary range. Schedule: Not mentioned (travel 60-75% maybe schedule? but schedule is not explicit; we could omit schedule as not stated. Skills: Could be "Who Thrives Here" describing desired traits; but that is more like competencies/skills. Could map to Skills section. However the instruction says prefer a few substantive sections over many thin ones. We could combine Who Thrives Here into Qualifications or Skills? Might be better to have a Skills section for those traits. But we already have Qualifications (required and preferred). Who Thrives Here is more about cultural fit; could be omitted? But we must preserve ALL substantive information; we cannot omit details. So we need to include that info somewhere. Could add a section like "Who Thrives Here" as its own heading, but that is not in the suggested list but still a 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 suggests using those. However to be safe, we could incorporate Who Thrives Here content into a Skills section (since it's about skills/attributes). Or we could add a section "Who Thrives Here" as

  Who Thrives Here

  . The instruction didn't say we cannot use other headings; just gave examples. I'd lean to include it as its own section to preserve info. Compliance: There's a Compliance paragraph about maintaining alignment etc. Could be its own section or part of Responsibilities? It's a separate block. Could be its own section "Compliance". Not in examples but okay. We also have statements about drug test, background check, EEO etc. Those are boilerplate legal/EEO; we must remove them. So we drop the EEO paragraph and the drug test/background check? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should drop the EEO paragraph and also the drug test/background check? That is also legal/employment requirement; might be considered boilerplate? It's a condition of employment; but it's not EEO. It's a requirement; but it's still legal. The instruction says remove legal boilerplate. So we should drop that as well. Also the statement about "The above statements are intended to describe the general nature..." is also boilerplate; drop. Also "As part of Aquestive’s employment process..." drop. Also "Aquestive provides equal employment opportunities..." drop. Also "The Company is required to provide a reasonable estimate..." that's about salary range; we need to keep salary range. That paragraph includes salary range statement; we need to keep that. The rest of that paragraph about final determinations etc is also legal boilerplate; we can drop but keep the salary range sentence. We'll need to extract the salary range sentence: "Expected salary range: $180,000 - $210,000/per year." Keep that. Also "Available benefits include bonus eligibility, health care and other insurance benefits (for employee and family), retirement benefits, paid holidays, vacation, and sick days." Keep that. Now we need to format. We'll produce:

  About the role

  As a District Sales Manager, you'll be the architect of launch success in your region, building a team that doesn't just hit numbers, but changes patient outcomes. You'll recruit talent, develop future leaders, and translate corporate strategy into territory-level wins. This isn't management from a distance; you'll be in the field coaching your territory representatives through complex sales cycles, celebrating breakthrough moments, and holding the line on performance and integrity.

  But we also have "About Aquestive Therapeutics" paragraph about company. Should we include that? It's substantive info about company. Could be part of About the role? Or we could have a separate section "About the company". Not in examples but we could include as

  About Aquestive Therapeutics

  . However instruction says use h3 for section headings (e.g. About the role, Responsibilities...). It didn't forbid other headings. But to be safe, we could incorporate company info into About the role section? Might be okay to have a separate About the company section. But the instruction says "Prefer a few substantive sections over many thin ones." Adding another section may be thin but it's substantive. However we already have many sections; maybe we can merge company info into About the role? The About the role currently only includes role description; we could add company overview as a paragraph before role description. That would be fine. Thus About the role section will contain both company overview and role description. Now Responsibilities: we need to list bullet points from Key Responsibilities. We'll create
  • for each bullet. We need to preserve all substantive info: The bullet points are: - Build & Lead a High-Performing Team - Recruit exceptional Therapeutic Specialty Representatives who combine sales excellence with mission alignment. - Develop your team through consistent field coaching, structured feedback, and individualized development plans. - Create a culture of accountability and growth where representatives take ownership of their territories and support each other's success. - Foster diversity, equity, and inclusion across your region—ensuring every team member has the support and opportunities to thrive. - Identify and cultivate future leaders within your team. - Drive Strategic Execution - Partner with VP of Sales, Areas Sales Director and peer DSMs to shape national sales strategy, leveraging field-level insights to inform direction. - Translate corporate objectives into district business plans that account for local market dynamics, competitive landscapes, and payer environments. - Establish clear performance metrics and tracking mechanisms that connect daily activities to launch milestones. - Analyze territory performance data to identify gaps, opportunities, and best practices worth scaling. - Coach for Impact - Conduct frequent field rides that balance observation, real-time coaching, and collaborative problem-solving. - Help representatives master the consultative selling approach required for Anaphylm's value proposition. - Guide your team through objection handling, particularly around payer access and product differentiation. - Connect daily sales activities to the broader mission—helping representatives see how their work removes barriers for patients who need an effective, easy-to-carry, easy-to-use epinephrine rescue medication. - Navigate Market Access Complexity - Develop fluency in payer landscapes—national plans, formularies, and local coverage nuances. - Translate payer insights into actionable pull-through strategies for your team. - Collaborate with Market Access and Hub Services to resolve coverage barriers and accelerate patient starts. - Track and share market access wins, barrier patterns, and successful resolution strategies. - Foster Cross-Functional Alignment - Partner with Marketing, Medical Affairs, Training, and Market Access to ensure consistent brand execution. - Serve as the voice of the field—sharing customer insights, competitive intelligence, and execution challenges that inform broader strategy. - Facilitate collaboration with specialty pharmacy partners and patient services teams. - Represent your region in national sales meetings, strategy sessions, and launch planning forums. - Ensure Operational Excellence - Drive CRM discipline across your team—ensuring high-quality documentation of calls, payer feedback, and sampling activity. - Monitor compliance with all regulatory requirements including PDMA, AE/product complaint reporting, and promotional guidelines. - Conduct regular territory business reviews that assess performance, identify improvement areas, and align on priorities. - Manage district budget and resources efficiently to maximize ROI. But note "Ensure Operational Excellence" appears as a subheading under Foster Cross-Functional Alignment? Actually in the text it's a separate bullet after Foster Cross-Functional Alignment. We'll treat as its own bullet. We need to preserve all bullet points exactly. Now Qualifications: we have Required and Preferred. We'll create
    • for each. Required: - Bachelor's degree - Minimum 5 years leading pharmaceutical or specialty sales teams (front-line management experience required) - Proven success leading teams through product launches—ideally in specialty, allergy, or related therapeutic areas - Deep understanding of sales strategy, market access dynamics, and HCP engagement models - Track record of developing talent and improving team performance through effective coaching - Strong analytical skills with ability to translate data into strategic action - Willingness to travel 60 – 75%, including overnight stays for field rides, customer events, and company meetings Preferred: - Experience in rescue medication, allergy, or products addressing medication adherence/administration barriers - Background in specialty pharmacy or hub services operations - Previous management of geographically dispersed team Now Benefits: we have "Available benefits include bonus eligibility, health care and other insurance benefits (for employee and family), retirement benefits, paid holidays, vacation, and sick days." We'll put that as
      • each item? Could be a single

        but instruction says use

        • for any list of duties/requirements/benefits. So we should list each benefit as
        • . So items: bonus eligibility, health care and other insurance benefits (for employee and family), retirement benefits, paid holidays, vacation, sick days. Now Pay: we have Expected salary range: $180,000 - $210,000/per year. We'll put as

          maybe or

          ? It's not a list; we can use

          . Now Who Thrives Here: we need to preserve that content. It's a list