Consulting, Contracting Manager
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. No placeholder like "commensurate with experience". We need to preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Also no job title heading, no Job ID.
We need to parse the posting.
Let's extract sections:
- About the role? The posting starts with "Shape the future of market access and commercial contracting across the pharmaceutical landscape ..." then mission/vision/values etc. Could be "About the role" or "About Envision". But we need to decide headings. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if content exists.
We have content about role responsibilities: "How will you make an impact at Envision Pharma Group?" then "Role responsibilities" with subheadings: Commercial Contracting & Client Delivery, Leadership & Collaboration. We can put under Responsibilities
and then list items.
We have "Do you have what we are looking for? Skills & expertise" then bullet list of qualifications: Bachelor's degree, 10 years experience, deep expertise, etc. That could be under Requirements
or Skills
. The instruction includes both Requirements and Skills as possible headings. We need to decide. Probably combine qualifications under Requirements, and skills under Skills. But we have overlapping. Let's separate: Requirements: Bachelor's degree or equivalent experience; Minimum 10 years' experience within pharmaceutical commercial contracting, Market Access, payer strategy, or related consulting environments; Deep expertise across Market Access agreements and pharmaceutical commercial contracting; Experience supporting: Payers, PBMs, Managed Care, Government programs, Channel agreements and Manufacturer contracting strategies; Strong contract drafting and negotiation experience; Understanding of contract implications relating to: Government Pricing, Gross-to-Net and Commercial reimbursement structures; Ability to work autonomously and provide proactive client recommendations; Strong stakeholder management and communication skills across technical and commercial audiences; Willingness to travel as required.
Skills: maybe same list? But we can treat the list as Skills & expertise. Could put under Skills
. However we also have Requirements maybe just education and years experience. But the instruction says prefer a few substantive sections over many thin ones. So maybe we combine into one section: Responsibilities, Requirements (including skills), Benefits/Pay/Schedule if present.
We have "Why join us?" paragraph describing benefits: collaborative team, etc. Also "The provided salary range reflects the potential base salary for this role in the United States and will vary based on experience, qualifications, and responsibilities. Alongside a competitive salary, we offer a comprehensive rewards and benefits package designed to support and recognise our people." That's about Pay and Benefits but not specific numbers. It says salary range reflects potential base salary and will vary; not a specific range. It's vague but still mentions salary and benefits. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state salary range (though not specific numbers) and mentions benefits package. So we can include Pay and Benefits sections? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state that there is a salary range and benefits package, albeit not specific. That's still stating them. So we can include Pay and Benefits sections with the given text. However we must avoid placeholder like "commensurate with experience" etc. The text says "The provided salary range reflects the potential base salary for this role in the United States and will vary based on experience, qualifications, and responsibilities." That's not a placeholder like "commensurate with experience" but it's still vague. It's okay? The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The phrase "will vary based on experience, qualifications, and responsibilities" is similar to "varies". That might be considered placeholder. The instruction says never emit a heading followed by filler/placeholder text. So if we include Pay section, we must ensure we have specific content, not just "will vary". The posting does not give actual numbers, so maybe we should omit Pay section because it's not specific. Similarly Benefits: "Alongside a competitive salary, we offer a comprehensive rewards and benefits package designed to support and recognise our people." That's vague but still states benefits exist. It's not specific details. Might be considered filler? The instruction says never create Benefits sections unless posting actually states them. It does state they offer a benefits package, but not details. Could be considered stating them. However to be safe, maybe we omit Benefits and Pay sections because they lack specifics. The instruction: "Prefer a few substantive sections over many thin ones." So we could have About the role (maybe mission/vision), Responsibilities, Requirements/Skills. Let's see.
We have "About the role" content: The initial paragraphs about Envision vision, mission, values, and the opportunity description. That could be under About the role.
We have Responsibilities: detailed.
We have Skills & expertise: qualifications.
We could also have a section "Why join us?" but that's similar to Benefits. Could be under Benefits but it's vague. Might be okay to include as "Why join us?" but not in the list of allowed headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could put "Why join us?" under Benefits? Or we could omit.
Let's decide to include: About the role, Responsibilities, Requirements (or Skills). Since we have both qualifications and skills, we could combine into Requirements (includes education, experience, skills). Or we could have Requirements and Skills separate but that may be thin. Better to have one Requirements section covering all.
Thus output:
About the role
Responsibilities
and then list items. We have "Do you have what we are looking for? Skills & expertise" then bullet list of qualifications: Bachelor's degree, 10 years experience, deep expertise, etc. That could be underRequirements
orSkills
. The instruction includes both Requirements and Skills as possible headings. We need to decide. Probably combine qualifications under Requirements, and skills under Skills. But we have overlapping. Let's separate: Requirements: Bachelor's degree or equivalent experience; Minimum 10 years' experience within pharmaceutical commercial contracting, Market Access, payer strategy, or related consulting environments; Deep expertise across Market Access agreements and pharmaceutical commercial contracting; Experience supporting: Payers, PBMs, Managed Care, Government programs, Channel agreements and Manufacturer contracting strategies; Strong contract drafting and negotiation experience; Understanding of contract implications relating to: Government Pricing, Gross-to-Net and Commercial reimbursement structures; Ability to work autonomously and provide proactive client recommendations; Strong stakeholder management and communication skills across technical and commercial audiences; Willingness to travel as required. Skills: maybe same list? But we can treat the list as Skills & expertise. Could put underSkills
. However we also have Requirements maybe just education and years experience. But the instruction says prefer a few substantive sections over many thin ones. So maybe we combine into one section: Responsibilities, Requirements (including skills), Benefits/Pay/Schedule if present. We have "Why join us?" paragraph describing benefits: collaborative team, etc. Also "The provided salary range reflects the potential base salary for this role in the United States and will vary based on experience, qualifications, and responsibilities. Alongside a competitive salary, we offer a comprehensive rewards and benefits package designed to support and recognise our people." That's about Pay and Benefits but not specific numbers. It says salary range reflects potential base salary and will vary; not a specific range. It's vague but still mentions salary and benefits. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state salary range (though not specific numbers) and mentions benefits package. So we can include Pay and Benefits sections? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state that there is a salary range and benefits package, albeit not specific. That's still stating them. So we can include Pay and Benefits sections with the given text. However we must avoid placeholder like "commensurate with experience" etc. The text says "The provided salary range reflects the potential base salary for this role in the United States and will vary based on experience, qualifications, and responsibilities." That's not a placeholder like "commensurate with experience" but it's still vague. It's okay? The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The phrase "will vary based on experience, qualifications, and responsibilities" is similar to "varies". That might be considered placeholder. The instruction says never emit a heading followed by filler/placeholder text. So if we include Pay section, we must ensure we have specific content, not just "will vary". The posting does not give actual numbers, so maybe we should omit Pay section because it's not specific. Similarly Benefits: "Alongside a competitive salary, we offer a comprehensive rewards and benefits package designed to support and recognise our people." That's vague but still states benefits exist. It's not specific details. Might be considered filler? The instruction says never create Benefits sections unless posting actually states them. It does state they offer a benefits package, but not details. Could be considered stating them. However to be safe, maybe we omit Benefits and Pay sections because they lack specifics. The instruction: "Prefer a few substantive sections over many thin ones." So we could have About the role (maybe mission/vision), Responsibilities, Requirements/Skills. Let's see. We have "About the role" content: The initial paragraphs about Envision vision, mission, values, and the opportunity description. That could be under About the role. We have Responsibilities: detailed. We have Skills & expertise: qualifications. We could also have a section "Why join us?" but that's similar to Benefits. Could be under Benefits but it's vague. Might be okay to include as "Why join us?" but not in the list of allowed headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could put "Why join us?" under Benefits? Or we could omit. Let's decide to include: About the role, Responsibilities, Requirements (or Skills). Since we have both qualifications and skills, we could combine into Requirements (includes education, experience, skills). Or we could have Requirements and Skills separate but that may be thin. Better to have one Requirements section covering all. Thus output:About the role
... (vision, mission, values, opportunity description)
Responsibilities
- ... (list each duty) ...
Requirements
- ... (list each qualification/skill) ...
. Possibly break into multiple paragraphs but one
is fine. Now Responsibilities: Under "How will you make an impact at Envision Pharma Group?" then "Role responsibilities" then two subheadings: Commercial Contracting & Client Delivery and Leadership & Collaboration. We need to list duties. Let's extract bullet points: Commercial Contracting & Client Delivery: - You will lead and deliver consulting engagements supporting pharmaceutical manufacturers across Market Access and commercial contracting activities including: - Supporting clients in the preparation, negotiation, and optimisation of Market Access agreements including: Managed Care, PBM agreements, Medicare and Medicaid contracting, Group Purchasing Organisations (GPOs), Integrated Delivery Networks (IDNs) and Distributors, specialty pharmacies and broader channel partners - Advising clients on commercial agreement strategy throughout the contracting lifecycle - Reviewing, assessing and negotiating Market Access and commercial agreements, identifying business implications, risks, and opportunities - Developing contract language and recommendations that align with commercial objectives while reducing contractual risk - Supporting clients with contracting strategy, process optimisation, governance and operational improvements - Providing guidance regarding agreement structures, pricing implications, and downstream business impact including Gross-to-Net considerations and government pricing considerations - Maintaining contracting support tools, trackers, and engagement documentation - Delivering projects within agreed budgets, timelines, and quality expectations Leadership & Collaboration: - As a senior member of the Consulting team, you will: - Coach and mentor team members supporting project delivery - Provide guidance, feedback and development support - Contribute to a collaborative, high-performing culture - Identify efficiencies and continuous improvement opportunities across engagement delivery - Support knowledge sharing and capability development across the team We need to put each as
- for any list of duties/requirements/benefits. So we can have a flat list; we can include sub-bullets as separate
- items. It's okay to flatten. Thus responsibilities list items: - Lead and deliver consulting engagements supporting pharmaceutical manufacturers across Market Access and commercial contracting activities including: - Support clients in the preparation, negotiation, and optimisation of Market Access agreements including: Managed Care, PBM agreements, Medicare and Medicaid contracting, Group Purchasing Organisations (GPOs), Integrated Delivery Networks (IDNs) and Distributors, specialty pharmacies and broader channel partners - Advise clients on commercial agreement strategy throughout the contracting lifecycle - Review, assess and negotiate Market Access and commercial agreements, identifying business implications, risks, and opportunities - Develop contract language and recommendations that align with commercial objectives while reducing contractual risk - Support clients with contracting strategy, process optimisation, governance and operational improvements - Provide guidance regarding agreement structures, pricing implications, and downstream business impact including Gross-to-Net considerations and government pricing considerations - Maintain contracting support tools, trackers, and engagement documentation - Deliver projects within agreed budgets, timelines, and quality expectations - Coach and mentor team members supporting project delivery - Provide guidance, feedback and development support - Contribute to a collaborative, high-performing culture - Identify efficiencies and continuous improvement opportunities across engagement delivery - Support knowledge sharing and capability development across the team We need to keep the original wording but can adjust grammar to be consistent. Keep as is. Now Requirements/Skills: Under "Do you have what we are looking for? Skills & expertise" then bullet list: - Bachelor's degree or equivalent experience - Minimum 10 years' experience within pharmaceutical commercial contracting, Market Access, payer strategy, or related consulting environments - Deep expertise across Market Access agreements and pharmaceutical commercial contracting - Experience supporting: Payers, PBMs, Managed Care, Government programs, Channel agreements and Manufacturer contracting strategies - Strong contract drafting and negotiation experience - Understanding of contract implications relating to: Government Pricing, Gross-to-Net and Commercial reimbursement structures - Ability to work autonomously and provide proactive client recommendations - Strong stakeholder management and communication skills across technical and commercial audiences - Willingness