District Leader, RX - Columbus, OH (Division 03 Region 21 District 25)
CVS Health · Columbus, OH · 1 mo ago
On-siteBusiness Development$155k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes introductory paragraph about CVS Health mission etc. That could be "About the role" or maybe "About CVS Health". The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content.
We need to preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Also remove "Qualified applicants with arrest or conviction records..." that's EEO boilerplate, remove. Also remove "Our people fuel our future..." maybe not boilerplate but could be considered fluff? It's about culture; maybe keep as part of About the role? It's not specific to role but could be considered generic. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Our people fuel our future..." is not exactly those categories, but it's generic fluff. Might be okay to keep as part of About the role? However they said prefer a few substantive sections over many thin ones. We could combine mission statement into About the role.
We need sections: About the role (maybe includes mission and overview), Responsibilities (the bullet list under "To enable sustainable market success, the District Leader, Rx is specifically responsible to:" and also the "What You Will Do" subsections People Leadership & Development, Business / Financial Planning, Operations, Portfolio Growth). Those are responsibilities.
Requirements/Qualifications: Required Qualifications, Preferred Qualifications, Required Education.
Skills: maybe not separate; could be included in Qualifications.
Benefits: The posting mentions "This is a full time, benefit eligible position. CVS Health offers a competitive benefit package which includes, but is not limited to, Paid Time Off, Health/Dental/Vision insurance, Employee Stock Purchase Program, 401K with a company match, and a generous employee discount at all CVS stores." Also later "Great Benefits For Great People" section describing benefits. So we have benefits content.
Pay: There's a Pay Range section: "The Typical Pay Range For This Role Is $155,000.00 - $240,000.00". Also mention bonus, commission, equity award. So we should include Pay section.
Schedule: Not explicitly mentioned besides full time. Could infer full-time schedule but not explicit. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Schedule not stated explicitly besides "full time". Might be considered schedule info? It says "This is a full time, benefit eligible position." That indicates schedule: full-time. Could we include Schedule section with that? It's minimal but it's stated. However they said prefer few substantive sections over many thin ones. Could combine schedule into About the role or Benefits? Probably better to include Schedule section with "Full-time". But it's thin. Might be okay to omit Schedule as not explicit detail beyond full-time. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state full time, so we could include Schedule. But we need to decide.
Given they want few substantive sections, maybe we omit Schedule and just mention full-time in About the role or Benefits. But they said use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. If we omit Schedule, that's fine.
We need to output only HTML fragment, no /, no markdown.
We'll structure:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content.
We need to preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Also remove "Qualified applicants with arrest or conviction records..." that's EEO boilerplate, remove. Also remove "Our people fuel our future..." maybe not boilerplate but could be considered fluff? It's about culture; maybe keep as part of About the role? It's not specific to role but could be considered generic. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Our people fuel our future..." is not exactly those categories, but it's generic fluff. Might be okay to keep as part of About the role? However they said prefer a few substantive sections over many thin ones. We could combine mission statement into About the role.
We need sections: About the role (maybe includes mission and overview), Responsibilities (the bullet list under "To enable sustainable market success, the District Leader, Rx is specifically responsible to:" and also the "What You Will Do" subsections People Leadership & Development, Business / Financial Planning, Operations, Portfolio Growth). Those are responsibilities.
Requirements/Qualifications: Required Qualifications, Preferred Qualifications, Required Education.
Skills: maybe not separate; could be included in Qualifications.
Benefits: The posting mentions "This is a full time, benefit eligible position. CVS Health offers a competitive benefit package which includes, but is not limited to, Paid Time Off, Health/Dental/Vision insurance, Employee Stock Purchase Program, 401K with a company match, and a generous employee discount at all CVS stores." Also later "Great Benefits For Great People" section describing benefits. So we have benefits content.
Pay: There's a Pay Range section: "The Typical Pay Range For This Role Is $155,000.00 - $240,000.00". Also mention bonus, commission, equity award. So we should include Pay section.
Schedule: Not explicitly mentioned besides full time. Could infer full-time schedule but not explicit. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Schedule not stated explicitly besides "full time". Might be considered schedule info? It says "This is a full time, benefit eligible position." That indicates schedule: full-time. Could we include Schedule section with that? It's minimal but it's stated. However they said prefer few substantive sections over many thin ones. Could combine schedule into About the role or Benefits? Probably better to include Schedule section with "Full-time". But it's thin. Might be okay to omit Schedule as not explicit detail beyond full-time. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state full time, so we could include Schedule. But we need to decide.
Given they want few substantive sections, maybe we omit Schedule and just mention full-time in About the role or Benefits. But they said use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. If we omit Schedule, that's fine.
We need to output only HTML fragment, no /, no markdown.
We'll structure:
About the role
... mission intro and overview of role ...
Responsibilities
- ... each bullet from "To enable sustainable market success..." and subpoints under People Leadership & Development etc. Need to capture all specifics. We need to preserve all substantive information; do not invent or summarize away detail. So we need to list each responsibility as separate
- . Could group similar but must keep detail. Let's extract responsibilities: From "To enable sustainable market success, the District Leader, Rx is specifically responsible to:" then list: - Cultivate and maintain a healthy Pharmacist talent pipeline, including overseeing the development of interns, recruitment of new grads, and career progression for float and staff Pharmacists to maintain a strong Pharmacy Manager bench - Set the District talent agenda for hourly colleagues (i.e. Technicians), including oversight to ensure an appropriate staffing pipeline, District-level succession planning for key roles (e.g. Tech Plus and Tech Team Leader), and partnering with front store field leadership to cultivate cross-trained colleagues and total-store staffing where appropriate - Set and communicate District priorities, based on Corporate and Regional direction; ensure Pharmacy Managers understand the “why” behind new initiatives and are able to engage their teams to embrace change - Conduct regular formal and informal check-ins with all Pharmacy Managers to track progress against business and developmental goals - Improve District-level pharmacy performance measures (e.g. workflow, service, inventory management, patient care, etc.) by coaching Pharmacy Managers to identify and address root-cause barriers to success - Oversee patient safety and provide regulatory oversight; ensure the highest level of integrity when it comes to reporting and investigating patient safety and/or drug loss incidents - Grow the business through active pursuit and engagement with acquisitions, file buys, new stores, and remodels Then "What You Will Do" sections with subheadings but those are essentially responsibilities broken down. People Leadership & Development: - Cultivate the market’s Pharmacist talent pipeline, including ultimate oversight and development of interns, Float Pharmacists, Staff Pharmacists, and Pharmacy Managers - Manage District succession plans and promote District-level staffing of pharmacies - Oversee the consistent delivery and completion of all colleague training programs - Oversee the appropriate staffing, scheduling, and timely and correct payment of all market Pharmacists - Create a culture of recognition, empowerment, development, and inclusion that attracts and retains pharmacy talent at all levels - Identify, mentor, and develop future District Leadership talent - Deliver timely performance reviews and targeted coaching and counseling for individual Pharmacy Managers as needed Business / Financial Planning: - Develop and execute business plans and strategies to deliver on all business performance measures, e.g. P&L, scripts-to-budget, inventory management, payroll management, asset protection accountabilities, etc. - Actively review business reports to derive insights about District pharmacy performance; utilize metrics as a tool to diagnose root cause and inform the creation of action plans - Develop a deep understanding of the competitive landscape and business trends, using this information to proactively plan for risk and capitalize on opportunities Operations: - Set, communicate and execute on market goals - Engage pharmacy teams to deliver against new and existing programs and services with excellence - Champion differentiated customer service and personally close out any escalated customer service issues - Triage and address any emergent issues in the market, e.g. theft, extreme weather, no-shows, Board of Pharmacy visits, etc. - Ensure all pharmacies are ready for inventories, internal/external audits, and other regular activities requiring planning and preparation for success - Ensure compliance with all community responsibility activities - Ensure compliance with all Company policies and relevant federal, state, and local laws pertaining to pharmacy and pharmacy personnel Portfolio Growth: - Provide market-specific input to development of the local acquisition and real estate strategy; implement the local real estate strategy and provide acquisition support - Identify file buy and acquisition leads, cultivating relationships with competitors and ensuring retention of file buy assets We need to include all these as
- under Responsibilities. Could we separate into subsections? The instruction only says use
for section headings, and
- for any list of duties/requirements/benefits. It doesn't forbid nested headings inside Responsibilities, but we could just make one big list.
But to preserve structure, maybe we keep as one list; it's okay.
Now Requirements/Qualifications: We have Required Qualifications, Preferred Qualifications, Required Education.
We could make a section
Requirements
with- for Required Qualifications and maybe separate
Preferred Qualifications
but instruction says use headings for section headings like Requirements, Qualifications, Skills. Could combine Required and Preferred under Qualifications? Might be better to haveQualifications
with two sublists: Required and Preferred. But we need to follow instruction: usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have separate headings for Requirements and Qualifications if we want. But we need to avoid thin sections. Could combine Required and Preferred into Qualifications section with two
- maybe preceded by
indicating required vs preferred. But that might be okay. Simplify: Have
Qualifications
thenRequired:
- ...
Preferred:
- ...
Benefits
- with items: Paid Time Off, Health/Dental/Vision insurance, Employee Stock Purchase Program, 401K with a company match, generous employee discount at all CVS stores, medical, dental, vision coverage, retirement savings options, wellness programs, other resources (based on eligibility). Also mention comprehensive benefits package.
Pay section:
Pay
The typical pay range for this role is $155,000.00 - $240,000.00 base annual full-time salary. Actual base salary offer will depend on experience, education, geography and other relevant factors. This position is eligible for a CVS Health bonus, commission or short-term incentive program in addition to the base pay range, and includes an award target in the company’s equity award program.
We should not include boilerplate like "Our people fuel our future..." etc. Also remove the EEO line about arrest or conviction records. Also remove "Qualified applicants with arrest or conviction records will be considered for employment..." etc. Also remove "We anticipate the application window for this opening will close on: 11/17/2026." That's application instruction; remove. Also remove "Great Benefits For Great People" heading? That's part of benefits but we can incorporate content. Now produce HTML. Check for duplication: Ensure we didn't repeat any lines. Let's craft About the role paragraph: combine introductory mission and overview of role. Intro: "We’re building a world of health around every individual — shaping a more connected, convenient and compassionate health experience. At CVS Health®, you’ll be surrounded by passionate colleagues who care deeply, innovate with purpose, hold ourselves accountable and prioritize safety and quality in everything we do. Join us and be part of something bigger – helping to simplify health care one person, one family and one community at a time." Then role overview: "The District Leader, Rx plays a critical role in cultivating a culture of clinical and business excellence in retail pharmacies across their market. With clinical and business oversight of approximately 20 retail pharmacies and an average team headcount of 200 reports, the District Leader, Rx has ultimate responsibility for patient safety and business success in their market. An inspiring coach and leader of people, the District Leader, Rx is focused on building and developing a team of Pharmacy Managers who grow the business through their consistent delivery of unparalleled care and patient connection. Specifically, the District Leader, Rx partners with and coaches their team to deliver on the core business with excellence, embrace change in an evolving healthcare ecosystem, and launch new products, programs, and services to keep our communities healthy. A licensed Pharmacist themselves, the District Leader, Rx brings deep
- for any list of duties/requirements/benefits. It doesn't forbid nested headings inside Responsibilities, but we could just make one big list.
But to preserve structure, maybe we keep as one list; it's okay.
Now Requirements/Qualifications: We have Required Qualifications, Preferred Qualifications, Required Education.
We could make a section