Aquestive District Sales Manager
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. Output ONLY the HTML fragment — no /, no markdown code fences.
Thus we need to decide which sections to include based on content.
We have:
- About Aquestive Therapeutics: description of company. Could be "About the role"? Actually "About the role" is a heading suggestion, but we have "About Aquestive Therapeutics". 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? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they want those headings if applicable. But we can also use other headings? Probably they want to map content to those standard headings. However we have "About Aquestive Therapeutics" which is about the company, not the role. Could map to "About the role"? Not exactly. But we could still include a section with heading About Aquestive Therapeutics
maybe acceptable? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but they gave examples. Safer to use those exact headings where content matches. For company description maybe we could put under "About the role"? Not ideal. However we could include a section "About the role" with description of the role (the "The Role" paragraph). That seems appropriate. The "About Aquestive Therapeutics" could be considered company overview, maybe we could put under "About the role"? But the instruction says do NOT repeat the job title as a heading. It didn't forbid company overview. I'd include a section with heading About Aquestive Therapeutics
as it's substantive.
But they said "Prefer a few substantive sections over many thin ones." So we might combine some.
Let's list substantive content:
- Company overview: "Aquestive Therapeutics is directly hiring... With more than 20 years..." etc.
- The Role description: "As a District Sales Manager, you'll be the architect..." paragraph.
- Key Responsibilities: multiple bullet points grouped under headings: Build & Lead a High-Performing Team, Drive Strategic Execution, Coach for Impact, Navigate Market Access Complexity, Foster Cross-Functional Alignment, Ensure Operational Excellence. Each has sub-bullets.
- Qualifications: Required and Preferred bullet lists.
- Who Thrives Here: bullet list of traits.
- Compliance: paragraph about compliance.
- Pay: Expected salary range: $180,000 - $210,000/per year.
- Benefits: "Available benefits include bonus eligibility, health care and other insurance benefits (for employee and family), retirement benefits, paid holidays, vacation, and sick days."
- Also mention drug test, background check, EEO statement (boilerplate to remove). Also "The Company is required to provide a reasonable estimate..." etc. That's part of pay/benefits maybe.
We need to remove boilerplate: EEO, drug test/background check maybe considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Drug test and background check could be considered legal/boilerplate; but it's part of hiring process. Might be considered boilerplate? Usually they'd say remove EEO and legal boilerplate. The drug test/background check is a condition of employment, could be considered legal. Safer to remove it. Also remove statements about "The above statements are intended to describe the general nature..." and "As part of Aquestive’s employment process..." and EEO paragraph. Also remove "The Company is required to provide a reasonable estimate..." maybe keep as part of Pay? Actually that sentence is about salary range disclosure requirement; we could keep it as part of Pay section context. But it's somewhat boilerplate. However it's substantive about salary range being required. Might keep.
We need to preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the salary range statement and benefits statement.
We need to format lists with - . For prose use
.
We need to decide sections.
Potential sections:
- About Aquestive Therapeutics (company overview) ->
About Aquestive Therapeutics
with .
- The Role ->
The Role
with .
- Responsibilities -> could be
Responsibilities
with - each major responsibility area, maybe each bullet as
- containing sub-bullets? Could nest
inside - . But instruction: Use
- for any list of duties/requirements/benefits. It doesn't forbid nested lists. We'll do top-level
with each responsibility area as - , and inside each
- we can have another
for sub-points.
- Qualifications -> Qualifications
with - for Required and Preferred maybe separate headings? Could do
Required
and Preferred
but they said use for section headings. Could still use inside? Not prohibited but maybe better to keep only sections. Could do two with headings inside - ? Might be messy. Could do
Required Qualifications
and Preferred Qualifications
. That seems okay as they are still . The instruction examples include Qualifications as a heading; we can split.
- Who Thrives Here -> maybe Who Thrives Here
with - .
- Compliance ->
Compliance
with .
- Pay ->
Pay
with containing salary range statement and maybe note about reasonable estimate.
- Benefits ->
Benefits
with listing benefits.
We should avoid thin sections: each of these has substantive content.
We must not include schedule (not present). So omit.
Now we need to ensure we don't include duplicated lines. Let's extract content precisely.
Company overview paragraph:
"Aquestive Therapeutics is directly hiring for a District Sales Manager role to lead markets across multiple states. About Aquestive Therapeutics 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."
Actually the text: "Aquestive Therapeutics is directly hiring for a District Sales Manager role to lead markets across multiple states. About Aquestive Therapeutics 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 combine into a paragraph.
The Role paragraph:
"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."
Now Responsibilities sections:
We have headings:
- 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 (actually this is separate heading) Wait the text: "Ensure Operational Excellence" is a separate heading after Foster Cross-Functional Alignment. Let's capture.
- 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
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. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include based on content. We have: - About Aquestive Therapeutics: description of company. Could be "About the role"? Actually "About the role" is a heading suggestion, but we have "About Aquestive Therapeutics". 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? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they want those headings if applicable. But we can also use other headings? Probably they want to map content to those standard headings. However we have "About Aquestive Therapeutics" which is about the company, not the role. Could map to "About the role"? Not exactly. But we could still include a section with heading About Aquestive Therapeutics
maybe acceptable? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but they gave examples. Safer to use those exact headings where content matches. For company description maybe we could put under "About the role"? Not ideal. However we could include a section "About the role" with description of the role (the "The Role" paragraph). That seems appropriate. The "About Aquestive Therapeutics" could be considered company overview, maybe we could put under "About the role"? But the instruction says do NOT repeat the job title as a heading. It didn't forbid company overview. I'd include a section with heading About Aquestive Therapeutics
as it's substantive.
But they said "Prefer a few substantive sections over many thin ones." So we might combine some.
Let's list substantive content:
- Company overview: "Aquestive Therapeutics is directly hiring... With more than 20 years..." etc.
- The Role description: "As a District Sales Manager, you'll be the architect..." paragraph.
- Key Responsibilities: multiple bullet points grouped under headings: Build & Lead a High-Performing Team, Drive Strategic Execution, Coach for Impact, Navigate Market Access Complexity, Foster Cross-Functional Alignment, Ensure Operational Excellence. Each has sub-bullets.
- Qualifications: Required and Preferred bullet lists.
- Who Thrives Here: bullet list of traits.
- Compliance: paragraph about compliance.
- Pay: Expected salary range: $180,000 - $210,000/per year.
- Benefits: "Available benefits include bonus eligibility, health care and other insurance benefits (for employee and family), retirement benefits, paid holidays, vacation, and sick days."
- Also mention drug test, background check, EEO statement (boilerplate to remove). Also "The Company is required to provide a reasonable estimate..." etc. That's part of pay/benefits maybe.
We need to remove boilerplate: EEO, drug test/background check maybe considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Drug test and background check could be considered legal/boilerplate; but it's part of hiring process. Might be considered boilerplate? Usually they'd say remove EEO and legal boilerplate. The drug test/background check is a condition of employment, could be considered legal. Safer to remove it. Also remove statements about "The above statements are intended to describe the general nature..." and "As part of Aquestive’s employment process..." and EEO paragraph. Also remove "The Company is required to provide a reasonable estimate..." maybe keep as part of Pay? Actually that sentence is about salary range disclosure requirement; we could keep it as part of Pay section context. But it's somewhat boilerplate. However it's substantive about salary range being required. Might keep.
We need to preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the salary range statement and benefits statement.
We need to format lists with - . For prose use
.
We need to decide sections.
Potential sections:
- About Aquestive Therapeutics (company overview) ->
About Aquestive Therapeutics
with .
- The Role ->
The Role
with .
- Responsibilities -> could be
Responsibilities
with - each major responsibility area, maybe each bullet as
- containing sub-bullets? Could nest
inside - . But instruction: Use
- for any list of duties/requirements/benefits. It doesn't forbid nested lists. We'll do top-level
with each responsibility area as - , and inside each
- we can have another
for sub-points.
- Qualifications -> Qualifications
with - for Required and Preferred maybe separate headings? Could do
Required
and Preferred
but they said use for section headings. Could still use inside? Not prohibited but maybe better to keep only sections. Could do two with headings inside - ? Might be messy. Could do
Required Qualifications
and Preferred Qualifications
. That seems okay as they are still . The instruction examples include Qualifications as a heading; we can split.
- Who Thrives Here -> maybe Who Thrives Here
with - .
- Compliance ->
Compliance
with .
- Pay ->
Pay
with containing salary range statement and maybe note about reasonable estimate.
- Benefits ->
Benefits
with listing benefits.
We should avoid thin sections: each of these has substantive content.
We must not include schedule (not present). So omit.
Now we need to ensure we don't include duplicated lines. Let's extract content precisely.
Company overview paragraph:
"Aquestive Therapeutics is directly hiring for a District Sales Manager role to lead markets across multiple states. About Aquestive Therapeutics 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."
Actually the text: "Aquestive Therapeutics is directly hiring for a District Sales Manager role to lead markets across multiple states. About Aquestive Therapeutics 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 combine into a paragraph.
The Role paragraph:
"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."
Now Responsibilities sections:
We have headings:
- 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 (actually this is separate heading) Wait the text: "Ensure Operational Excellence" is a separate heading after Foster Cross-Functional Alignment. Let's capture.
- 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
About Aquestive Therapeutics
maybe acceptable? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but they gave examples. Safer to use those exact headings where content matches. For company description maybe we could put under "About the role"? Not ideal. However we could include a section "About the role" with description of the role (the "The Role" paragraph). That seems appropriate. The "About Aquestive Therapeutics" could be considered company overview, maybe we could put under "About the role"? But the instruction says do NOT repeat the job title as a heading. It didn't forbid company overview. I'd include a section with heading About Aquestive Therapeutics
as it's substantive.
But they said "Prefer a few substantive sections over many thin ones." So we might combine some.
Let's list substantive content:
- Company overview: "Aquestive Therapeutics is directly hiring... With more than 20 years..." etc.
- The Role description: "As a District Sales Manager, you'll be the architect..." paragraph.
- Key Responsibilities: multiple bullet points grouped under headings: Build & Lead a High-Performing Team, Drive Strategic Execution, Coach for Impact, Navigate Market Access Complexity, Foster Cross-Functional Alignment, Ensure Operational Excellence. Each has sub-bullets.
- Qualifications: Required and Preferred bullet lists.
- Who Thrives Here: bullet list of traits.
- Compliance: paragraph about compliance.
- Pay: Expected salary range: $180,000 - $210,000/per year.
- Benefits: "Available benefits include bonus eligibility, health care and other insurance benefits (for employee and family), retirement benefits, paid holidays, vacation, and sick days."
- Also mention drug test, background check, EEO statement (boilerplate to remove). Also "The Company is required to provide a reasonable estimate..." etc. That's part of pay/benefits maybe.
We need to remove boilerplate: EEO, drug test/background check maybe considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Drug test and background check could be considered legal/boilerplate; but it's part of hiring process. Might be considered boilerplate? Usually they'd say remove EEO and legal boilerplate. The drug test/background check is a condition of employment, could be considered legal. Safer to remove it. Also remove statements about "The above statements are intended to describe the general nature..." and "As part of Aquestive’s employment process..." and EEO paragraph. Also remove "The Company is required to provide a reasonable estimate..." maybe keep as part of Pay? Actually that sentence is about salary range disclosure requirement; we could keep it as part of Pay section context. But it's somewhat boilerplate. However it's substantive about salary range being required. Might keep.
We need to preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the salary range statement and benefits statement.
We need to format lists with - . For prose use
.
We need to decide sections.
Potential sections:
- About Aquestive Therapeutics (company overview) ->
About Aquestive Therapeutics
with .
- The Role ->
The Role
with .
- Responsibilities -> could be
Responsibilities
with - each major responsibility area, maybe each bullet as
- containing sub-bullets? Could nest
inside - . But instruction: Use
- for any list of duties/requirements/benefits. It doesn't forbid nested lists. We'll do top-level
with each responsibility area as - , and inside each
- we can have another
for sub-points.
- Qualifications -> Qualifications
with - for Required and Preferred maybe separate headings? Could do
Required
and Preferred
but they said use for section headings. Could still use inside? Not prohibited but maybe better to keep only sections. Could do two with headings inside - ? Might be messy. Could do
Required Qualifications
and Preferred Qualifications
. That seems okay as they are still . The instruction examples include Qualifications as a heading; we can split.
- Who Thrives Here -> maybe Who Thrives Here
with - .
- Compliance ->
Compliance
with .
- Pay ->
Pay
with containing salary range statement and maybe note about reasonable estimate.
- Benefits ->
Benefits
with listing benefits.
We should avoid thin sections: each of these has substantive content.
We must not include schedule (not present). So omit.
Now we need to ensure we don't include duplicated lines. Let's extract content precisely.
Company overview paragraph:
"Aquestive Therapeutics is directly hiring for a District Sales Manager role to lead markets across multiple states. About Aquestive Therapeutics 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."
Actually the text: "Aquestive Therapeutics is directly hiring for a District Sales Manager role to lead markets across multiple states. About Aquestive Therapeutics 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 combine into a paragraph.
The Role paragraph:
"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."
Now Responsibilities sections:
We have headings:
- 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 (actually this is separate heading) Wait the text: "Ensure Operational Excellence" is a separate heading after Foster Cross-Functional Alignment. Let's capture.
- 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
. We need to decide sections. Potential sections: - About Aquestive Therapeutics (company overview) ->
About Aquestive Therapeutics
with. - The Role ->
The Role
with. - Responsibilities -> could be
Responsibilities
with- each major responsibility area, maybe each bullet as
- containing sub-bullets? Could nest
- inside
- . But instruction: Use
- for any list of duties/requirements/benefits. It doesn't forbid nested lists. We'll do top-level
- with each responsibility area as
- , and inside each
- we can have another
- for sub-points.
- Qualifications ->
- for Required and Preferred maybe separate headings? Could do
Required
andPreferred
but they said usefor section headings. Could still use
inside? Not prohibited but maybe better to keep only
sections. Could do two
- with headings inside
- ? Might be messy. Could do
Required Qualifications
andPreferred Qualifications
. That seems okay as they are still. The instruction examples include Qualifications as a heading; we can split. - Who Thrives Here -> maybe
Who Thrives Here
with- .
- Compliance ->
Compliance
with. - Pay ->
Pay
withcontaining salary range statement and maybe note about reasonable estimate. - Benefits ->
Benefits
withlisting benefits. We should avoid thin sections: each of these has substantive content. We must not include schedule (not present). So omit. Now we need to ensure we don't include duplicated lines. Let's extract content precisely. Company overview paragraph: "Aquestive Therapeutics is directly hiring for a District Sales Manager role to lead markets across multiple states. About Aquestive Therapeutics 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." Actually the text: "Aquestive Therapeutics is directly hiring for a District Sales Manager role to lead markets across multiple states. About Aquestive Therapeutics 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 combine into a paragraph. The Role paragraph: "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." Now Responsibilities sections: We have headings: - 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 (actually this is separate heading) Wait the text: "Ensure Operational Excellence" is a separate heading after Foster Cross-Functional Alignment. Let's capture. - 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
- .
- Compliance ->
- ? Might be messy. Could do
Qualifications
with - for Required and Preferred maybe separate headings? Could do
- for any list of duties/requirements/benefits. It doesn't forbid nested lists. We'll do top-level
- . But instruction: Use