Aquestive District Sales Manager
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use appropriate headings based on content. We must not repeat job title as heading. We should include sections only when posting has real specific content.
We have content: About Aquestive Therapeutics (company description). Could be "About the Company" but they gave example "About the role". However we can use "About the Company" as heading? The examples are just examples; we can choose appropriate headings. Probably better to use "About the Company". But they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So they expect those exact headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we can use those headings if applicable. We have content for About the role? There's a section "The Role". Could map to "About the role". Responsibilities: we have "Key Responsibilities". Qualifications: we have "Qualifications". Skills: not explicitly separate but could be part of Qualifications. Benefits: we have benefits. Pay: we have salary range. Schedule: not provided, so we should not include Schedule heading.
We also have "Who Thrives Here" which could be maybe "Skills" or "Attributes"? Not in list. Could we include a section like "Who Thrives Here"? The instruction says prefer a few substantive sections over many thin ones. Could incorporate that into Qualifications or maybe as a separate section like "Ideal Candidate". But they didn't list that as example; but we can still include if content is substantive. However they said use those examples; not strict. I'd include sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Also maybe "About the Company" as a separate section? The posting includes "About Aquestive Therapeutics". That is substantive. Could map to "About the role"? Not exactly. Could use "About the Company". But they didn't list that as example; but we can still include. However they said use those examples for section headings; maybe they expect us to use those exact headings when applicable, but we can also add others if needed? Safer to stick to the given list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role (The Role). Responsibilities (Key Responsibilities). Requirements (maybe Qualifications). Qualifications (maybe Requirements). Skills (maybe we can pull from Qualifications). Benefits (Available benefits). Pay (Expected salary range). Schedule: none, so omit.
We need to avoid repeating job title as heading. Also drop Job ID etc. Remove boilerplate: EEO, drug test, background check, etc. Also remove "The Company is required to provide a reasonable estimate..." etc? That's part of Pay section? Actually that's about salary range disclosure; we can keep salary range but drop the explanatory sentence? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the sentence about salary range determination? It's substantive? It's about how final determinations will be made. Might be considered substantive. But we can keep it as part of Pay section.
Also we need to remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we remove the EEO paragraph, drug test/background check, etc.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we can use those headings if applicable. We have content for About the role? There's a section "The Role". Could map to "About the role". Responsibilities: we have "Key Responsibilities". Qualifications: we have "Qualifications". Skills: not explicitly separate but could be part of Qualifications. Benefits: we have benefits. Pay: we have salary range. Schedule: not provided, so we should not include Schedule heading.
We also have "Who Thrives Here" which could be maybe "Skills" or "Attributes"? Not in list. Could we include a section like "Who Thrives Here"? The instruction says prefer a few substantive sections over many thin ones. Could incorporate that into Qualifications or maybe as a separate section like "Ideal Candidate". But they didn't list that as example; but we can still include if content is substantive. However they said use those examples; not strict. I'd include sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Also maybe "About the Company" as a separate section? The posting includes "About Aquestive Therapeutics". That is substantive. Could map to "About the role"? Not exactly. Could use "About the Company". But they didn't list that as example; but we can still include. However they said use those examples for section headings; maybe they expect us to use those exact headings when applicable, but we can also add others if needed? Safer to stick to the given list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role (The Role). Responsibilities (Key Responsibilities). Requirements (maybe Qualifications). Qualifications (maybe Requirements). Skills (maybe we can pull from Qualifications). Benefits (Available benefits). Pay (Expected salary range). Schedule: none, so omit.
We need to avoid repeating job title as heading. Also drop Job ID etc. Remove boilerplate: EEO, drug test, background check, etc. Also remove "The Company is required to provide a reasonable estimate..." etc? That's part of Pay section? Actually that's about salary range disclosure; we can keep salary range but drop the explanatory sentence? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the sentence about salary range determination? It's substantive? It's about how final determinations will be made. Might be considered substantive. But we can keep it as part of Pay section.
Also we need to remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we remove the EEO paragraph, drug test/background check, etc.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
... (The Role paragraph)
Responsibilities
- ... each responsibility ...
Qualifications
Required: ...
Preferred: ...
Maybe also include Skills? Could embed within Qualifications.Benefits
- ... each benefit
Pay
Expected salary range: $180,000 - $210,000 per year. 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.
We should also include About Aquestive Therapeutics? That's company description. Could be part of About the role? Might be better to include a section "About the Company". But not in list. However we could incorporate that into About the role? The "About the role" section currently is just the role description; we could prepend company description there. But the instruction: "About the role" heading example; maybe they expect that section to contain both company and role? Not sure. We could add another heading "About the Company". Since it's substantive, we should include it. The instruction didn't forbid adding other headings; they just gave examples. So we can add. Thus:About the Company
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. Now list responsibilities: we need to extract each bullet from "Key Responsibilities". There are several bullet groups: 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. We need to flatten into