Aquestive District Sales Manager

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Aquestive Therapeutics" and "The Role". The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. So we need sections based on content present. We have: - About Aquestive Therapeutics (company description) - could be "About the company"? But they gave example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map content to these headings where appropriate. We have "About Aquestive Therapeutics" (company overview). Could be placed under a heading like "About the company"? Not in list. But we could use "About the role" for description of role? Actually "The Role" section describes role. So we could put that under

About the role

. The company overview could be maybe omitted or placed as a

before sections? The instruction: "Prefer a few substantive sections over many thin ones." We can include About the role, Responsibilities, Requirements (maybe Qualifications), Benefits, Pay. Also maybe Skills? Not explicitly listed but could be derived from Qualifications. We'll include Qualifications. We must not include sections with filler like "commensurate with experience". Pay section: we have salary range $180,000 - $210,000 per year. So we can include Pay. Benefits: "Available benefits include bonus eligibility, health care and other insurance benefits (for employee and family), retirement benefits, paid holidays, vacation, and sick days." So we can include Benefits. Schedule: Not mentioned. Travel 60-75% including overnight stays. That's travel requirement, not schedule. Could be considered Schedule? Not exactly. Probably we should not create Schedule section because not explicit schedule like full-time, part-time, shift. So omit. Requirements: Could be qualifications required. We'll have Qualifications section for required and preferred. Could also have Requirements separate but we can combine. We need to preserve all substantive information. So we need to include details from About Aquestive Therapeutics, The Role, Key Responsibilities (list), Qualifications (required and preferred), Who Thrives Here (maybe could be part of Qualifications or separate? It's describing ideal candidate traits. Could be included under Qualifications or a separate "Skills" section? Might be better as a "Skills" section? But we have list of traits: Mission-Driven Leaders, Launch Veterans, Talent Developers, Strategic Executor, Emotionally Intelligent Coaches, Collaborative Partners, Resilient Competitors, Compliance. That's more like desired attributes. Could be placed under a section like "Qualifications" or "Skills". Since we have Qualifications already, we could add those as bullet points under Qualifications (maybe under "Preferred" or separate). But we need to preserve all info. We also have a compliance paragraph at end: "Compliance Maintain alignment with corporate policies..." That's basically a responsibility. Could be included under Responsibilities. We also have statements about drug test, background check, EEO etc. Those are boilerplate to remove per instructions: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we must drop the EEO statement, drug test/background check? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. The drug test and background check might be considered part of hiring process, not boilerplate? It's not explicitly listed as boilerplate but could be considered part of application instructions? It says "As part of Aquestive’s employment process, final candidate will be required to complete a drug test and background check prior to employment commencing." That's like a condition; could be considered application instruction? Might be considered boilerplate? Not sure. Safer to keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The drug test/background check could be considered application instructions. So we should remove it. Also the statement: "The above statements are intended to describe the general nature and level of the work being performed by colleagues assigned to this position. This is not intended as an exhaustive list of all responsibilities, duties, and skills required. Aquestive reserves the right to make changes to the job description whenever necessary." That's boilerplate legal; remove. Also "The Company is required to provide a reasonable estimate of the salary range for this job in certain states and cities within the United States. Final determinations with respect to salary will take into account a number of factors, which may include, but not be limited to the primary work location and the chosen candidate’s relevant skills, experience, and education." That's also boilerplate about salary range; but we need to keep the salary range itself. The surrounding text could be considered boilerplate; we can keep just the salary range sentence? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The salary range is substantive; the surrounding explanation maybe not needed but could be considered boilerplate. Might be safe to keep the sentence that includes the range, but we can trim to just the range. However we need to preserve all substantive information; the explanation about factors is not substantive? It's generic. I'd keep just the range. Now structure:

About the role

... (The Role description)

Responsibilities

• ... list items from Key Responsibilities (maybe grouped). We need to preserve all bullet points. The Key Responsibilities section has several bullet-like paragraphs each starting with a bold heading. We'll convert each to
• . We have: - Build & Lead a High-Performing Team (with sub-bullets) - Drive Strategic Execution - Coach for Impact - Navigate Market Access Complexity - Foster Cross-Functional Alignment - Ensure Operational Excellence Each has multiple subpoints. We could either keep each main heading as a
• and include subpoints as nested
  or just flatten? The instruction: use
  • for any list of duties/requirements/benefits. It doesn't forbid nesting. We'll keep main headings as
  • and include subpoints as
    • inside. We need to preserve all details. Then

      Qualifications

      with required and preferred. Could split into Required and Preferred subheadings? Not required but we can use
      • for each. We also have "Who Thrives Here" describing ideal candidate traits. Could be included under Qualifications as a separate list maybe "Desired Attributes". Could make a

        Skills

        for those traits. But we already have Qualifications; we could add a separate section "Skills" for those traits. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Who Thrives Here into Qualifications as bullet points under "Preferred" or separate "Preferred Qualifications". We'll treat them as part of Qualifications (Preferred). We'll list required qualifications then preferred qualifications then maybe "Ideal candidate traits" as part of preferred. We'll also include Benefits and Pay sections. Let's extract text. About Aquestive Therapeutics paragraph: "With more than 20 years of pioneering patient-centered innovation, we've transformed how millions access life-saving medications. Our track record speaks for itself: 6 FDA approvals, 2.5 billion doses delivered worldwide, and a presence across 6 continents. As we prepare to launch Anaphylm™, our latest breakthrough in overcoming patient barriers, we're building a sales team that shares our commitment to innovation that matters." We can put that under About the role? Actually About the role is about the role, not company. But we could include a short intro before sections. The instruction: do NOT repeat the job title as a heading. It didn't forbid a general paragraph before headings. We could include a

        for company overview then sections. But they said "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have sections like About the role, Responsibilities, etc. The company overview could be placed under About the role? Might be odd. Better to have a leading

        for company overview then sections. We'll output:

        With more than 20 years of pioneering patient-centered innovation, we've transformed how millions access life-saving medications. Our track record speaks for itself: 6 FDA approvals, 2.5 billion doses delivered worldwide, and a presence across 6 continents. As we prepare to launch Anaphylm™, our latest breakthrough in overcoming patient barriers, we're building a sales team that shares our commitment to innovation that matters.

        Then

        About the role

        with the role description paragraph: "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." Now Responsibilities: we need to list all subpoints. Let's extract each main heading and its subpoints. 1. 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. 2. 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. 3. 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. 4. 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. 5. 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 (actually this is next heading) Wait we need to separate. Actually after Foster Cross-Functional Alignment there is "Ensure Operational Excellence" as a separate main heading. So continue: 5. Foster Cross-Functional Alignment (list above) 6. 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. -