Aquestive District Sales Manager
Inizio Engage · Newark, NJ · 1 mo ago
Business Development$180k–$210k/yrFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Content:
- Intro: Aquestive Therapeutics is directly hiring for a District Sales Manager role to lead markets across multiple states.
- About Aquestive Therapeutics: description.
- The Role: description.
- Key Responsibilities: bullet list (multiple subpoints).
- Qualifications: Required and Preferred.
- Who Thrives Here: maybe could be considered Skills? Or maybe it's a section about attributes. Could be considered Skills or Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings.
We have:
- About the role: could be "About the role" heading containing description of role (The Role paragraph). Also maybe "About Aquestive Therapeutics" could be part of About the role? But heading "About the role" is appropriate for role description. Could also include company description? Might be better to put company description under About the role? Or maybe we could have separate "About the company"? Not in list. So we put company description under About the role? Or maybe we skip it? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests these as examples. We should stick to these headings. So we need sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay. Possibly Requirements (maybe same as Qualifications). But we have both Required and Preferred qualifications. Could put under Qualifications. Requirements maybe not needed if we have Qualifications. But we could include Requirements as a subsection? The instruction: "Prefer a few substantive sections over many thin ones." So we should combine.
Thus sections:
- About the role: includes company overview and role description.
- Responsibilities: list of key responsibilities.
- Qualifications: includes Required and Preferred.
- Skills: maybe from "Who Thrives Here" (mission-driven leaders etc.) could be considered skills/attributes. Could also include analytical skills etc. But we already have skills in Qualifications. Could still have Skills section for attributes like "Mission-Driven Leaders", "Launch Veterans", etc. Might be okay.
- Benefits: from "Available benefits include bonus eligibility, health care and other insurance benefits (for employee and family), retirement benefits, paid holidays, vacation, and sick days."
- Pay: Expected salary range: $180,000 - $210,000/per year.
- Schedule: maybe travel willingness 60-75% including overnight stays. That's schedule/travel. Could be considered Schedule. So include Schedule section with travel expectation.
We must not include placeholder text like "commensurate with experience". Not present.
We must not include boilerplate like EEO etc. Remove those lines.
We must preserve all substantive info; do not invent or summarize away detail. So we need to keep details like 6 FDA approvals, 2.5 billion doses, 6 continents, Anaphylm™ launch, etc. Also details about responsibilities bullet points.
We need to format lists with
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests these as examples. We should stick to these headings. So we need sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay. Possibly Requirements (maybe same as Qualifications). But we have both Required and Preferred qualifications. Could put under Qualifications. Requirements maybe not needed if we have Qualifications. But we could include Requirements as a subsection? The instruction: "Prefer a few substantive sections over many thin ones." So we should combine.
Thus sections:
- About the role: includes company overview and role description.
- Responsibilities: list of key responsibilities.
- Qualifications: includes Required and Preferred.
- Skills: maybe from "Who Thrives Here" (mission-driven leaders etc.) could be considered skills/attributes. Could also include analytical skills etc. But we already have skills in Qualifications. Could still have Skills section for attributes like "Mission-Driven Leaders", "Launch Veterans", etc. Might be okay.
- Benefits: from "Available benefits include bonus eligibility, health care and other insurance benefits (for employee and family), retirement benefits, paid holidays, vacation, and sick days."
- Pay: Expected salary range: $180,000 - $210,000/per year.
- Schedule: maybe travel willingness 60-75% including overnight stays. That's schedule/travel. Could be considered Schedule. So include Schedule section with travel expectation.
We must not include placeholder text like "commensurate with experience". Not present.
We must not include boilerplate like EEO etc. Remove those lines.
We must preserve all substantive info; do not invent or summarize away detail. So we need to keep details like 6 FDA approvals, 2.5 billion doses, 6 continents, Anaphylm™ launch, etc. Also details about responsibilities bullet points.
We need to format lists with - . For prose use
.
We must not repeat job title as heading. So no
District Sales Manager
. Good.
We must not put Job ID/requisition numbers as headings.
We must output only HTML fragment, no /, no markdown fences.
Let's craft.
Structure:
About the role
... company overview and role description ...
Responsibilities
- ... each bullet ...
...
Qualifications
Required: ...
Preferred: ...
Alternatively could use for each but okay.
Skills
... from Who Thrives Here ... maybe list bullet points.
Benefits
Available benefits include bonus eligibility, health care and other insurance benefits (for employee and family), retirement benefits, paid holidays, vacation, and sick days.
Pay
Expected salary range: $180,000 - $210,000 per year.
Schedule
Willingness to travel 60–75%, including overnight stays for field rides, customer events, and company meetings.
Check for any other substantive info: "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." This is more about salary determination; we could include in Pay section maybe as extra sentence. But it's somewhat boilerplate but still substantive. Might keep.
Also "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 substantive but maybe could be omitted? It's not in the heading list; but we could include under a generic section? Not required. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This is not exactly those; it's about hiring process. Might be considered application instruction? It's a pre-employment requirement. Could be considered part of application instructions; maybe remove. Safer to remove.
Also "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." This is boilerplate; remove.
Also "As part of Aquestive’s employment process, final candidate will be required to complete a drug test and background check prior to employment commencing." Might be considered application instruction; remove.
Also "Aquestive provides equal employment opportunities..." that's EEO boilerplate; remove.
Thus we keep substantive content.
Now craft About the role paragraph: combine company overview and role description.
Company overview: "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."
Role description: "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."
Combine into one or two paragraphs.
Now Responsibilities: need to capture all bullet points from "Key Responsibilities". Let's list them:
- 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.
We need to preserve all these. Could group under with each bullet as - . Might be long but okay.
Now Qualifications: Required and Preferred.
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
Note: travel requirement appears also in Qualifications; we also have Schedule section for travel. Might duplicate. But we should keep both as they are substantive. However we might move travel to Schedule only and not duplicate in Qualifications. But the Qualifications includes travel as required. If we remove it from Qualifications, we lose that detail. But we could keep it in Qualifications and also have Schedule section referencing travel; duplication okay? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not prohibited but might be redundant. Better to keep travel in Qualifications and maybe not have separate Schedule section, or keep Schedule with other schedule details (maybe none). But we have schedule info only travel. Could put travel under Schedule and keep Qualifications without travel. But then we lose the explicit "Willingness to travel 60 – 75%, including overnight stays for field rides, customer events, and company meetings" as a qualification. However we could still keep it under Qual
. We must not repeat job title as heading. So no
District Sales Manager
. Good. We must not put Job ID/requisition numbers as headings. We must output only HTML fragment, no /, no markdown fences. Let's craft. Structure:About the role
... company overview and role description ...
Responsibilities
- ... each bullet ... ...
Qualifications
Required: ...
Preferred: ...
Alternatively could use- for each but okay.
- . Might be long but okay. Now Qualifications: Required and Preferred. 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 Note: travel requirement appears also in Qualifications; we also have Schedule section for travel. Might duplicate. But we should keep both as they are substantive. However we might move travel to Schedule only and not duplicate in Qualifications. But the Qualifications includes travel as required. If we remove it from Qualifications, we lose that detail. But we could keep it in Qualifications and also have Schedule section referencing travel; duplication okay? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not prohibited but might be redundant. Better to keep travel in Qualifications and maybe not have separate Schedule section, or keep Schedule with other schedule details (maybe none). But we have schedule info only travel. Could put travel under Schedule and keep Qualifications without travel. But then we lose the explicit "Willingness to travel 60 – 75%, including overnight stays for field rides, customer events, and company meetings" as a qualification. However we could still keep it under Qual
Skills
... from Who Thrives Here ... maybe list bullet points.
Benefits
Available benefits include bonus eligibility, health care and other insurance benefits (for employee and family), retirement benefits, paid holidays, vacation, and sick days.
Pay
Expected salary range: $180,000 - $210,000 per year.
Schedule
Willingness to travel 60–75%, including overnight stays for field rides, customer events, and company meetings.
Check for any other substantive info: "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." This is more about salary determination; we could include in Pay section maybe as extra sentence. But it's somewhat boilerplate but still substantive. Might keep. Also "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 substantive but maybe could be omitted? It's not in the heading list; but we could include under a generic section? Not required. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This is not exactly those; it's about hiring process. Might be considered application instruction? It's a pre-employment requirement. Could be considered part of application instructions; maybe remove. Safer to remove. Also "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." This is boilerplate; remove. Also "As part of Aquestive’s employment process, final candidate will be required to complete a drug test and background check prior to employment commencing." Might be considered application instruction; remove. Also "Aquestive provides equal employment opportunities..." that's EEO boilerplate; remove. Thus we keep substantive content. Now craft About the role paragraph: combine company overview and role description. Company overview: "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." Role description: "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." Combine into one or two paragraphs. Now Responsibilities: need to capture all bullet points from "Key Responsibilities". Let's list them: - 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. We need to preserve all these. Could group under- with each bullet as