Specialty Representative, Psychiatry - Southern Colorado
AbbVie · Colorado Springs, CO · 1 mo ago
Business DevelopmentFull-time
We need to output HTML fragment with sections: About the role? Actually we have Company Description, Job Description, Responsibilities, Qualifications, Additional Information (benefits, pay, schedule). We need to use for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must include sections only when posting has real specific content. We need to preserve all substantive info, no boilerplate.
We need to decide which sections to include.
From posting:
- Company Description: about AbbVie. Could be "About the role"? Actually "Company Description" could be "About AbbVie". But headings list includes "About the role". Not exactly. We could use "About the company" but not in list. The instruction: use
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must include sections only when posting has real specific content. We need to preserve all substantive info, no boilerplate.
We need to decide which sections to include.
From posting:
- Company Description: about AbbVie. Could be "About the role"? Actually "Company Description" could be "About AbbVie". But headings list includes "About the role". Not exactly. We could use "About the company" but not in list. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples; we can use other headings? Probably we should stick to those headings where applicable. We have content that matches: Responsibilities, Qualifications (maybe Requirements), Benefits, Pay, Schedule. Also maybe "Skills". The posting includes "Proven track record of leadership success and solid presentation skills..." which could be Skills. But we can put under Qualifications or Skills.
We need to avoid filler like "commensurate with experience" etc. That appears in "Talent will be hired at a level commensurate with experience." That's filler; we should remove that line. Also "Note: No amount of pay is considered to be wages..." is boilerplate legal; remove. Also EEO boilerplate remove. Also "Additional Information" includes pay range and benefits; we need to extract pay and benefits specifics.
Pay: The posting says: "Applicable only to applicants applying to a position in any location with pay disclosure requirements under state or local law: The compensation range described below is the range of possible base pay compensation that the Company believes in good faith it will pay for this role at the time of this posting based on the job grade for this position." It does not actually give numbers. So no specific pay range given. Therefore we should NOT create a Pay section because no actual numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Since no numbers, we omit Pay.
Schedule: Not mentioned. So omit Schedule.
Benefits: The posting says: "We offer a comprehensive package of benefits including paid time off (vacation, holidays, sick), medical/dental/vision insurance and 401(k) to eligible employees. This job is eligible to participate in our short-term incentive programs." That's specific benefits. So we can include Benefits section.
Also maybe "Additional Information" includes "Applicable only to applicants applying to a position in any location with pay disclosure requirements..." but we already determined no pay numbers. So we keep benefits.
Now Responsibilities: we have a block after "Responsibilities". Need to preserve all substantive info. The responsibilities block is a long sentence with many items separated by periods. We should break into - for each duty. The instruction: Use
- for any list of duties/requirements/benefits. So we should parse responsibilities into list items.
Similarly Qualifications: we have a block with many statements. Should be list.
Skills: maybe we can extract skills from qualifications: "Proven track record of leadership success and solid presentation skills. Strong business acumen and proficient use of business tools; possesses strategic and critical thinking capabilities. Proactively identifies customer style / behavior and adapts quickly all aspects of selling approach. Operates effectively in a matrix environment." plus preferred items. Could be separate Skills section. But we could also put under Qualifications. The instruction: prefer a few substantive sections over many thin ones. So maybe combine Qualifications and Skills into one Qualifications section. But we have headings list includes Qualifications and Skills separate. We could still have both if content distinct. However qualifications already includes skills; splitting may be thin. Better to have one Qualifications section that includes both requirements and skills. But we need to follow heading examples; we can use Qualifications heading and include both.
We also have "An essential requirement of your position is to satisfy all applicable health care industry representative (HCIR) credentialing requirements..." That's a requirement; include in Qualifications.
Also "Valid driver’s license: Ability to pass a pre-employment drug screening test and meet safe driving requirements. Driving a personal auto or company car or truck, or a powered piece of material handling equipment." That's also requirement.
Thus Qualifications section will contain list items: Bachelor’s degree... etc, HCIR credentialing, driver's license, etc.
Now Benefits section: list items: paid time off (vacation, holidays, sick), medical/dental/vision insurance, 401(k), short-term incentive programs.
Now Responsibilities section: need to break down the long paragraph into distinct duties.
Let's extract responsibilities sentences:
"Deliver sales performance, brand KPIs, financial targets, marketing objectives, etc. to meet or exceed on those objectives."
"Create pre-call plan objectives and execute post-call evaluation to continuously improve sales performance."
"Effectively handle objections, misunderstandings, concerns and consistently gain logical and reasonable calls to action to close on every sales call."
"Proactively and continuously aspire to serve customer needs, customer expectations and challenges to build trusted customer relationships and to achieve win-win agreements between AbbVie and customers"
"Develop and execute a call plan that achieves set call metrics and optimizes coverage and frequency to key customers to maximize access and sales opportunities."
"Continuously build understanding on customer needs and expectations, territory market landscape, competitors, market segments/dynamics, accounts, disease, product, clinical and sales expertise and share this market intelligence information with in-field team, brand team and sales manager to achieve alignment, to anticipate environmental changes and challenges and to optimize brand strategy and its execution."
"Differentiate AbbVie’s value proposition with health providers assigned and identify, develop, and maintain disease state experts and speakers/advocates to maximize brand performance"
We can make each a list item.
Now we also have earlier part before Responsibilities: "Execute brand strategy and tactics in field, sales performance, effectively manage assigned territory and targeted accounts, build strong customer relationships and customer needs solving capability to maximize short and long term sales performance placing the patient into the center of any efforts and operating within AbbVie’s business code of conduct, policies and all applicable laws and regulations." That seems like part of job description; could be included as a responsibility as well. Might be better to include as first responsibility.
Thus responsibilities list includes that as first item.
Now we need to output HTML fragment only, no /, no markdown.
We'll produce:
Responsibilities
- Execute brand strategy and tactics in the field, manage assigned territory and targeted accounts, build strong customer relationships and customer needs‑solving capability to maximize short‑ and long‑term sales performance, placing the patient at the center of efforts and operating within AbbVie’s business code of conduct, policies, and applicable laws and regulations.
- Deliver sales performance, brand KPIs, financial targets, marketing objectives, etc., to meet or exceed those objectives.
- Create pre‑call plan objectives and execute post‑call evaluation to continuously improve sales performance.
- Effectively handle objections, misunderstandings, and concerns; consistently gain logical and reasonable calls to action to close every sales call.
- Proactively serve customer needs, expectations, and challenges to build trusted customer relationships and achieve win‑win agreements between AbbVie and customers.
- Develop and execute a call plan that achieves set call metrics and optimizes coverage and frequency for key customers to maximize access and sales opportunities.
- Continuously build understanding of customer needs and expectations, territory market landscape, competitors, market segments/dynamics, accounts, disease, product, clinical and sales expertise; share this market intelligence with the in‑field team, brand team, and sales manager to achieve alignment, anticipate environmental changes and challenges, and optimize brand strategy and its execution.
- Differentiate AbbVie’s value proposition with assigned health‑care providers and identify, develop, and maintain disease‑state experts and speakers/advocates to maximize brand performance.
Then Qualifications:
Qualifications
- Bachelor’s degree in health, sciences, pharmacy, or business‑related field preferred; or relevant and equivalent industry experience (at least five (5) years total, with three (3) or more years in pharmaceutical/health/science industry) and a high school diploma/GED required.
- Proven track record of leadership success and solid presentation skills.
- Strong business acumen and proficient use of business tools; strategic and critical thinking capabilities.
- Ability to identify customer style/behavior and adapt selling approach accordingly.
- Effective operation in a matrix environment.
- Preferred: proven track record of success in sales performance within respective therapeutic areas.
- Preferred: commercial pharmaceutical industry experience (physician/account‑based selling, training, managed health care, or marketing).
- Preferred: in‑depth scientific, therapeutic, product, and competitive knowledge; recognized as an expert resource by relevant stakeholders.
- Preferred: English language proficiency verbally and in writing (for non‑English speaking countries).
- Must satisfy all applicable health‑care industry representative (HCIR) credentialing requirements (background checks, drug screens, proof of immunization/vaccination, fingerprinting, state‑ or city‑specific licenses) and maintain good standing/eligibility.
- Valid driver’s license; ability to pass a pre‑employment drug screening test and meet safe driving requirements; capable of driving a personal auto, company car/truck, or powered material‑handling equipment.
Benefits:
Benefits
- Paid time off (vacation, holidays, sick)
- Medical, dental, and vision insurance
- 401(k) plan
- Eligibility for short‑term incentive programs
We should not include About the role because we have no separate company description? Actually we have Company Description at start. Could be considered "About the role"? But 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 we could include "About the company" as a heading? Not in list. Safer to omit company description? But we must preserve ALL substantive information. The company description is substantive. We need to include it somewhere. Could be a section like "About AbbVie". Not in the list but maybe acceptable. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The e.g. suggests those are examples but not exclusive. However to be safe, we could incorporate company description into a brief paragraph before responsibilities, maybe as a
without heading. The instruction: Use
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. So we can have a
for company description prose. That seems fine.
Thus output: start with a
containing company description (trimmed). Then responsibilities, qualifications, benefits sections.
We must remove boilerplate: navigation, cookie, legal, EEO, scam-warning, duplicated lines, application instructions. Already removed.
Check for any leftover filler like "commensurate with experience" removed. Also "Talent will be hired at a level commensurate with experience." removed.
Check for any duplicated lines: we have not
- for each duty. The instruction: Use
- for any list of duties/requirements/benefits. So we should parse responsibilities into list items.
Similarly Qualifications: we have a block with many statements. Should be list.
Skills: maybe we can extract skills from qualifications: "Proven track record of leadership success and solid presentation skills. Strong business acumen and proficient use of business tools; possesses strategic and critical thinking capabilities. Proactively identifies customer style / behavior and adapts quickly all aspects of selling approach. Operates effectively in a matrix environment." plus preferred items. Could be separate Skills section. But we could also put under Qualifications. The instruction: prefer a few substantive sections over many thin ones. So maybe combine Qualifications and Skills into one Qualifications section. But we have headings list includes Qualifications and Skills separate. We could still have both if content distinct. However qualifications already includes skills; splitting may be thin. Better to have one Qualifications section that includes both requirements and skills. But we need to follow heading examples; we can use Qualifications heading and include both.
We also have "An essential requirement of your position is to satisfy all applicable health care industry representative (HCIR) credentialing requirements..." That's a requirement; include in Qualifications.
Also "Valid driver’s license: Ability to pass a pre-employment drug screening test and meet safe driving requirements. Driving a personal auto or company car or truck, or a powered piece of material handling equipment." That's also requirement.
Thus Qualifications section will contain list items: Bachelor’s degree... etc, HCIR credentialing, driver's license, etc.
Now Benefits section: list items: paid time off (vacation, holidays, sick), medical/dental/vision insurance, 401(k), short-term incentive programs.
Now Responsibilities section: need to break down the long paragraph into distinct duties.
Let's extract responsibilities sentences:
"Deliver sales performance, brand KPIs, financial targets, marketing objectives, etc. to meet or exceed on those objectives."
"Create pre-call plan objectives and execute post-call evaluation to continuously improve sales performance."
"Effectively handle objections, misunderstandings, concerns and consistently gain logical and reasonable calls to action to close on every sales call."
"Proactively and continuously aspire to serve customer needs, customer expectations and challenges to build trusted customer relationships and to achieve win-win agreements between AbbVie and customers"
"Develop and execute a call plan that achieves set call metrics and optimizes coverage and frequency to key customers to maximize access and sales opportunities."
"Continuously build understanding on customer needs and expectations, territory market landscape, competitors, market segments/dynamics, accounts, disease, product, clinical and sales expertise and share this market intelligence information with in-field team, brand team and sales manager to achieve alignment, to anticipate environmental changes and challenges and to optimize brand strategy and its execution."
"Differentiate AbbVie’s value proposition with health providers assigned and identify, develop, and maintain disease state experts and speakers/advocates to maximize brand performance"
We can make each a list item.
Now we also have earlier part before Responsibilities: "Execute brand strategy and tactics in field, sales performance, effectively manage assigned territory and targeted accounts, build strong customer relationships and customer needs solving capability to maximize short and long term sales performance placing the patient into the center of any efforts and operating within AbbVie’s business code of conduct, policies and all applicable laws and regulations." That seems like part of job description; could be included as a responsibility as well. Might be better to include as first responsibility.
Thus responsibilities list includes that as first item.
Now we need to output HTML fragment only, no /, no markdown.
We'll produce:
Responsibilities
- Execute brand strategy and tactics in the field, manage assigned territory and targeted accounts, build strong customer relationships and customer needs‑solving capability to maximize short‑ and long‑term sales performance, placing the patient at the center of efforts and operating within AbbVie’s business code of conduct, policies, and applicable laws and regulations.
- Deliver sales performance, brand KPIs, financial targets, marketing objectives, etc., to meet or exceed those objectives.
- Create pre‑call plan objectives and execute post‑call evaluation to continuously improve sales performance.
- Effectively handle objections, misunderstandings, and concerns; consistently gain logical and reasonable calls to action to close every sales call.
- Proactively serve customer needs, expectations, and challenges to build trusted customer relationships and achieve win‑win agreements between AbbVie and customers.
- Develop and execute a call plan that achieves set call metrics and optimizes coverage and frequency for key customers to maximize access and sales opportunities.
- Continuously build understanding of customer needs and expectations, territory market landscape, competitors, market segments/dynamics, accounts, disease, product, clinical and sales expertise; share this market intelligence with the in‑field team, brand team, and sales manager to achieve alignment, anticipate environmental changes and challenges, and optimize brand strategy and its execution.
- Differentiate AbbVie’s value proposition with assigned health‑care providers and identify, develop, and maintain disease‑state experts and speakers/advocates to maximize brand performance.
Qualifications
- Bachelor’s degree in health, sciences, pharmacy, or business‑related field preferred; or relevant and equivalent industry experience (at least five (5) years total, with three (3) or more years in pharmaceutical/health/science industry) and a high school diploma/GED required.
- Proven track record of leadership success and solid presentation skills.
- Strong business acumen and proficient use of business tools; strategic and critical thinking capabilities.
- Ability to identify customer style/behavior and adapt selling approach accordingly.
- Effective operation in a matrix environment.
- Preferred: proven track record of success in sales performance within respective therapeutic areas.
- Preferred: commercial pharmaceutical industry experience (physician/account‑based selling, training, managed health care, or marketing).
- Preferred: in‑depth scientific, therapeutic, product, and competitive knowledge; recognized as an expert resource by relevant stakeholders.
- Preferred: English language proficiency verbally and in writing (for non‑English speaking countries).
- Must satisfy all applicable health‑care industry representative (HCIR) credentialing requirements (background checks, drug screens, proof of immunization/vaccination, fingerprinting, state‑ or city‑specific licenses) and maintain good standing/eligibility.
- Valid driver’s license; ability to pass a pre‑employment drug screening test and meet safe driving requirements; capable of driving a personal auto, company car/truck, or powered material‑handling equipment.
Benefits
- Paid time off (vacation, holidays, sick)
- Medical, dental, and vision insurance
- 401(k) plan
- Eligibility for short‑term incentive programs
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we could include "About the company" as a heading? Not in list. Safer to omit company description? But we must preserve ALL substantive information. The company description is substantive. We need to include it somewhere. Could be a section like "About AbbVie". Not in the list but maybe acceptable. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The e.g. suggests those are examples but not exclusive. However to be safe, we could incorporate company description into a brief paragraph before responsibilities, maybe as a
without heading. The instruction: Use
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. So we can have a
for company description prose. That seems fine. Thus output: start with a
containing company description (trimmed). Then responsibilities, qualifications, benefits sections. We must remove boilerplate: navigation, cookie, legal, EEO, scam-warning, duplicated lines, application instructions. Already removed. Check for any leftover filler like "commensurate with experience" removed. Also "Talent will be hired at a level commensurate with experience." removed. Check for any duplicated lines: we have not
- for any list of duties/requirements/benefits. So we should parse responsibilities into list items.
Similarly Qualifications: we have a block with many statements. Should be list.
Skills: maybe we can extract skills from qualifications: "Proven track record of leadership success and solid presentation skills. Strong business acumen and proficient use of business tools; possesses strategic and critical thinking capabilities. Proactively identifies customer style / behavior and adapts quickly all aspects of selling approach. Operates effectively in a matrix environment." plus preferred items. Could be separate Skills section. But we could also put under Qualifications. The instruction: prefer a few substantive sections over many thin ones. So maybe combine Qualifications and Skills into one Qualifications section. But we have headings list includes Qualifications and Skills separate. We could still have both if content distinct. However qualifications already includes skills; splitting may be thin. Better to have one Qualifications section that includes both requirements and skills. But we need to follow heading examples; we can use Qualifications heading and include both.
We also have "An essential requirement of your position is to satisfy all applicable health care industry representative (HCIR) credentialing requirements..." That's a requirement; include in Qualifications.
Also "Valid driver’s license: Ability to pass a pre-employment drug screening test and meet safe driving requirements. Driving a personal auto or company car or truck, or a powered piece of material handling equipment." That's also requirement.
Thus Qualifications section will contain list items: Bachelor’s degree... etc, HCIR credentialing, driver's license, etc.
Now Benefits section: list items: paid time off (vacation, holidays, sick), medical/dental/vision insurance, 401(k), short-term incentive programs.
Now Responsibilities section: need to break down the long paragraph into distinct duties.
Let's extract responsibilities sentences:
"Deliver sales performance, brand KPIs, financial targets, marketing objectives, etc. to meet or exceed on those objectives."
"Create pre-call plan objectives and execute post-call evaluation to continuously improve sales performance."
"Effectively handle objections, misunderstandings, concerns and consistently gain logical and reasonable calls to action to close on every sales call."
"Proactively and continuously aspire to serve customer needs, customer expectations and challenges to build trusted customer relationships and to achieve win-win agreements between AbbVie and customers"
"Develop and execute a call plan that achieves set call metrics and optimizes coverage and frequency to key customers to maximize access and sales opportunities."
"Continuously build understanding on customer needs and expectations, territory market landscape, competitors, market segments/dynamics, accounts, disease, product, clinical and sales expertise and share this market intelligence information with in-field team, brand team and sales manager to achieve alignment, to anticipate environmental changes and challenges and to optimize brand strategy and its execution."
"Differentiate AbbVie’s value proposition with health providers assigned and identify, develop, and maintain disease state experts and speakers/advocates to maximize brand performance"
We can make each a list item.
Now we also have earlier part before Responsibilities: "Execute brand strategy and tactics in field, sales performance, effectively manage assigned territory and targeted accounts, build strong customer relationships and customer needs solving capability to maximize short and long term sales performance placing the patient into the center of any efforts and operating within AbbVie’s business code of conduct, policies and all applicable laws and regulations." That seems like part of job description; could be included as a responsibility as well. Might be better to include as first responsibility.
Thus responsibilities list includes that as first item.
Now we need to output HTML fragment only, no /, no markdown.
We'll produce: