Cardiovascular Territory Account Specialist – Wichita, KS
for each section heading.
We need to use - for any list of duties/requirements/benefits. For prose use
.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from those sections.
We need to strip out boilerplate like EEO, accessibility, etc.
Also remove duplicated lines: there may be repeated sentences.
Let's extract content.
First, Summary paragraph:
"This is a field-based and remote opportunity supporting key accounts in an assigned geography. Novartis is unable to offer relocation support for this role. Please only apply if this location is accessible to you. Company will not sponsor visas for this position. As a Territory Account Specialist (TAS), you’ll lead with purpose – crafting personalized experiences that reflect the unique needs of each account and Health Care Provider (HCP). Acting as the primary point of contact, you’ll build meaningful connections, identify shared priorities, and navigate solutions that link customers to Novartis resources – all with the goal of improving patient outcomes. Success in this role comes from balancing demand generation with strategic account engagement. You’ll bring expertise in clinical and account-based selling, access navigation, collaborative problem-solving, team orchestration, and omni-channel engagement."
That's the summary. We'll put that as a
before sections.
Next, About The Role heading: Actually the summary already covers about the role? There's a separate "About The Role" heading then "Key Responsibilities:" list. We'll treat "About The Role" as heading maybe with a short paragraph? The posting after "About The Role" directly goes to "Key Responsibilities:" with no prose. So we could either not include About The Role heading if no prose besides responsibilities. But instructions: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The "About The Role" heading is followed by responsibilities list, which is specific. So we can include heading "About The Role" and then the responsibilities list under it? But we also have a separate Responsibilities section. Might be redundant. Better to follow the structure: About The Role heading maybe with a brief description (none). Then Responsibilities heading with list. However we could combine: Use About The Role heading and then the responsibilities list under it, and not have a separate Responsibilities heading. But the instructions say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So they expect those headings. We'll follow that: About The Role heading (maybe with a short paragraph summarizing role? Could use the summary? But summary already used. Might be okay to have About The Role heading with a short paragraph derived from the summary? But we must not invent or summarize away detail; we can reuse the summary text as the About The Role paragraph. However the summary already appears at top; we could avoid duplication by not repeating. But we could keep summary as intro and then About The Role heading with maybe nothing? That would be filler. Better to not include About The Role heading if we already used summary as intro. But the instructions list About the role as an example heading; but they say include a section ONLY when posting has real, specific content for it. The posting does have an "About The Role" heading with content (the responsibilities). So we could treat About The Role heading and then put the responsibilities list under it, and not have a separate Responsibilities heading. However they also gave Responsibilities as an example heading; we could still have both but that would duplicate content. Let's decide: We'll have About The Role heading with a short paragraph (maybe the first two sentences of summary?) But that would be summarizing. Safer: Use About The Role heading and then put the responsibilities list directly under it (as ). Then we won't have a separate Responsibilities heading. That satisfies having a section with real content.
Similarly, we need Requirements section: The posting has "Essential Requirements" and "Desirable Requirements". Could combine under Requirements heading with two sub-sections? But we must use for section headings only; we cannot have subheadings unless we treat them as as well? Could have separate headings for Essential Requirements and Desirable Requirements. But the instruction list includes Requirements as a possible heading; we could have Requirements heading and then within it we have two lists: Essential Requirements and Desirable Requirements as
headings? Not allowed to use headings other than
. Could use
with bold? Not allowed. Better to have separate sections: Essential Requirements and Desirable Requirements as
each. But the instruction list didn't forbid other headings; they gave examples but said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings where applicable. However we can also add other headings if needed? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use h3 for those section headings; not that we cannot use other headings, but likely they expect only those. To be safe, we can map content to those headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have info for About the role (maybe summary), Responsibilities (list), Requirements (essential + desirable), Qualifications (maybe leveling guidelines?), Skills (maybe not explicit), Benefits, Pay. Schedule not present.
We could treat "Leveling Guidelines" as Qualifications. Or "Qualifications" heading could contain the leveling guidelines and experience requirements. The posting includes "Essential Requirements" (education, experience) and "Desirable Requirements" (experience across therapeutic groups etc.) and "Leveling Guidelines" (specific years). That's all qualifications. So we can put under Qualifications heading: combine essential, desirable, leveling guidelines.
Skills: Not explicitly listed; maybe we can omit Skills section.
Thus final sections: About the role (intro paragraph), Responsibilities (list), Qualifications (list of essential, desirable, leveling), Benefits (list), Pay (list of salary ranges). Also maybe include "Driving is an Essential Function" and "COVID-19 Vaccine Policy" and "For Field Roles with a Dedicated Training Period". Where to put those? They could be part of Requirements or Qualifications? Driving is an essential function - could be a requirement. COVID vaccine policy - maybe a requirement. Training period - maybe a requirement. We could include them under Qualifications as additional items.
We must preserve all substantive information. So we need to include those details somewhere.
Let's extract each piece.
Summary (intro): as above.
About the role: maybe we can use the first sentence of summary? But we already used summary as intro. Could we treat About the role heading with a short paragraph that is basically the summary? That would duplicate. To avoid duplication, maybe we omit About the role heading and start with Responsibilities heading. But the instructions list About the role as example; but they say include a section ONLY when posting has real, specific content for it. If we omit About the role heading, we are not including a section for it, which is okay if we consider that the summary already covers about the role. However the summary is more generic; but it's still about the role. I'd keep About the role heading with the summary paragraph to avoid missing content. But then we would have duplicate content if we also keep summary separate. We could just have About the role heading with the summary paragraph, and not have a separate intro paragraph. That satisfies About the role section.
Thus: About the role
This is a field-based and remote opportunity supporting key accounts in an assigned geography. Novartis is unable to offer relocation support for this role. Please only apply if this location is accessible to you. Company will not sponsor visas for this position. As a Territory Account Specialist (TAS), you’ll lead with purpose – crafting personalized experiences that reflect the unique needs of each account and Health Care Provider (HCP). Acting as the primary point of contact, you’ll build meaningful connections, identify shared priorities, and navigate solutions that link customers to Novartis resources – all with the goal of improving patient outcomes. Success in this role comes from balancing demand generation with strategic account engagement. You’ll bring expertise in clinical and account-based selling, access navigation, collaborative problem-solving, team orchestration, and omni-channel engagement.
Now Responsibilities: The list under "Key Responsibilities:" includes multiple sentences each starting with a verb. We'll make each as - .
List:
- Navigate and resolve challenges within accounts to ensure customer needs are met with effective, tailored solutions.
- Build a strategic territory plan by aligning shared priorities and applying insights and tactics that drive product demand and support better patient outcomes.
- Partner proactively with territory teammates, field teams, and home-office colleagues to address customer needs and deliver access support.
- Apply deep knowledge of the market,
. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from those sections. We need to strip out boilerplate like EEO, accessibility, etc. Also remove duplicated lines: there may be repeated sentences. Let's extract content. First, Summary paragraph: "This is a field-based and remote opportunity supporting key accounts in an assigned geography. Novartis is unable to offer relocation support for this role. Please only apply if this location is accessible to you. Company will not sponsor visas for this position. As a Territory Account Specialist (TAS), you’ll lead with purpose – crafting personalized experiences that reflect the unique needs of each account and Health Care Provider (HCP). Acting as the primary point of contact, you’ll build meaningful connections, identify shared priorities, and navigate solutions that link customers to Novartis resources – all with the goal of improving patient outcomes. Success in this role comes from balancing demand generation with strategic account engagement. You’ll bring expertise in clinical and account-based selling, access navigation, collaborative problem-solving, team orchestration, and omni-channel engagement." That's the summary. We'll put that as a
before sections. Next, About The Role heading: Actually the summary already covers about the role? There's a separate "About The Role" heading then "Key Responsibilities:" list. We'll treat "About The Role" as heading maybe with a short paragraph? The posting after "About The Role" directly goes to "Key Responsibilities:" with no prose. So we could either not include About The Role heading if no prose besides responsibilities. But instructions: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The "About The Role" heading is followed by responsibilities list, which is specific. So we can include heading "About The Role" and then the responsibilities list under it? But we also have a separate Responsibilities section. Might be redundant. Better to follow the structure: About The Role heading maybe with a brief description (none). Then Responsibilities heading with list. However we could combine: Use About The Role heading and then the responsibilities list under it, and not have a separate Responsibilities heading. But the instructions say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So they expect those headings. We'll follow that: About The Role heading (maybe with a short paragraph summarizing role? Could use the summary? But summary already used. Might be okay to have About The Role heading with a short paragraph derived from the summary? But we must not invent or summarize away detail; we can reuse the summary text as the About The Role paragraph. However the summary already appears at top; we could avoid duplication by not repeating. But we could keep summary as intro and then About The Role heading with maybe nothing? That would be filler. Better to not include About The Role heading if we already used summary as intro. But the instructions list About the role as an example heading; but they say include a section ONLY when posting has real, specific content for it. The posting does have an "About The Role" heading with content (the responsibilities). So we could treat About The Role heading and then put the responsibilities list under it, and not have a separate Responsibilities heading. However they also gave Responsibilities as an example heading; we could still have both but that would duplicate content. Let's decide: We'll have About The Role heading with a short paragraph (maybe the first two sentences of summary?) But that would be summarizing. Safer: Use About The Role heading and then put the responsibilities list directly under it (as ). Then we won't have a separate Responsibilities heading. That satisfies having a section with real content.
Similarly, we need Requirements section: The posting has "Essential Requirements" and "Desirable Requirements". Could combine under Requirements heading with two sub-sections? But we must use for section headings only; we cannot have subheadings unless we treat them as as well? Could have separate headings for Essential Requirements and Desirable Requirements. But the instruction list includes Requirements as a possible heading; we could have Requirements heading and then within it we have two lists: Essential Requirements and Desirable Requirements as
headings? Not allowed to use headings other than
. Could use
with bold? Not allowed. Better to have separate sections: Essential Requirements and Desirable Requirements as
each. But the instruction list didn't forbid other headings; they gave examples but said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings where applicable. However we can also add other headings if needed? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use h3 for those section headings; not that we cannot use other headings, but likely they expect only those. To be safe, we can map content to those headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have info for About the role (maybe summary), Responsibilities (list), Requirements (essential + desirable), Qualifications (maybe leveling guidelines?), Skills (maybe not explicit), Benefits, Pay. Schedule not present.
We could treat "Leveling Guidelines" as Qualifications. Or "Qualifications" heading could contain the leveling guidelines and experience requirements. The posting includes "Essential Requirements" (education, experience) and "Desirable Requirements" (experience across therapeutic groups etc.) and "Leveling Guidelines" (specific years). That's all qualifications. So we can put under Qualifications heading: combine essential, desirable, leveling guidelines.
Skills: Not explicitly listed; maybe we can omit Skills section.
Thus final sections: About the role (intro paragraph), Responsibilities (list), Qualifications (list of essential, desirable, leveling), Benefits (list), Pay (list of salary ranges). Also maybe include "Driving is an Essential Function" and "COVID-19 Vaccine Policy" and "For Field Roles with a Dedicated Training Period". Where to put those? They could be part of Requirements or Qualifications? Driving is an essential function - could be a requirement. COVID vaccine policy - maybe a requirement. Training period - maybe a requirement. We could include them under Qualifications as additional items.
We must preserve all substantive information. So we need to include those details somewhere.
Let's extract each piece.
Summary (intro): as above.
About the role: maybe we can use the first sentence of summary? But we already used summary as intro. Could we treat About the role heading with a short paragraph that is basically the summary? That would duplicate. To avoid duplication, maybe we omit About the role heading and start with Responsibilities heading. But the instructions list About the role as example; but they say include a section ONLY when posting has real, specific content for it. If we omit About the role heading, we are not including a section for it, which is okay if we consider that the summary already covers about the role. However the summary is more generic; but it's still about the role. I'd keep About the role heading with the summary paragraph to avoid missing content. But then we would have duplicate content if we also keep summary separate. We could just have About the role heading with the summary paragraph, and not have a separate intro paragraph. That satisfies About the role section.
Thus: About the role
This is a field-based and remote opportunity supporting key accounts in an assigned geography. Novartis is unable to offer relocation support for this role. Please only apply if this location is accessible to you. Company will not sponsor visas for this position. As a Territory Account Specialist (TAS), you’ll lead with purpose – crafting personalized experiences that reflect the unique needs of each account and Health Care Provider (HCP). Acting as the primary point of contact, you’ll build meaningful connections, identify shared priorities, and navigate solutions that link customers to Novartis resources – all with the goal of improving patient outcomes. Success in this role comes from balancing demand generation with strategic account engagement. You’ll bring expertise in clinical and account-based selling, access navigation, collaborative problem-solving, team orchestration, and omni-channel engagement.
Now Responsibilities: The list under "Key Responsibilities:" includes multiple sentences each starting with a verb. We'll make each as - .
List:
- Navigate and resolve challenges within accounts to ensure customer needs are met with effective, tailored solutions.
- Build a strategic territory plan by aligning shared priorities and applying insights and tactics that drive product demand and support better patient outcomes.
- Partner proactively with territory teammates, field teams, and home-office colleagues to address customer needs and deliver access support.
- Apply deep knowledge of the market,
for section headings only; we cannot have subheadings unless we treat them as as well? Could have separate headings for Essential Requirements and Desirable Requirements. But the instruction list includes Requirements as a possible heading; we could have Requirements heading and then within it we have two lists: Essential Requirements and Desirable Requirements as
headings? Not allowed to use headings other than
. Could use
with bold? Not allowed. Better to have separate sections: Essential Requirements and Desirable Requirements as
each. But the instruction list didn't forbid other headings; they gave examples but said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings where applicable. However we can also add other headings if needed? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use h3 for those section headings; not that we cannot use other headings, but likely they expect only those. To be safe, we can map content to those headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have info for About the role (maybe summary), Responsibilities (list), Requirements (essential + desirable), Qualifications (maybe leveling guidelines?), Skills (maybe not explicit), Benefits, Pay. Schedule not present.
We could treat "Leveling Guidelines" as Qualifications. Or "Qualifications" heading could contain the leveling guidelines and experience requirements. The posting includes "Essential Requirements" (education, experience) and "Desirable Requirements" (experience across therapeutic groups etc.) and "Leveling Guidelines" (specific years). That's all qualifications. So we can put under Qualifications heading: combine essential, desirable, leveling guidelines.
Skills: Not explicitly listed; maybe we can omit Skills section.
Thus final sections: About the role (intro paragraph), Responsibilities (list), Qualifications (list of essential, desirable, leveling), Benefits (list), Pay (list of salary ranges). Also maybe include "Driving is an Essential Function" and "COVID-19 Vaccine Policy" and "For Field Roles with a Dedicated Training Period". Where to put those? They could be part of Requirements or Qualifications? Driving is an essential function - could be a requirement. COVID vaccine policy - maybe a requirement. Training period - maybe a requirement. We could include them under Qualifications as additional items.
We must preserve all substantive information. So we need to include those details somewhere.
Let's extract each piece.
Summary (intro): as above.
About the role: maybe we can use the first sentence of summary? But we already used summary as intro. Could we treat About the role heading with a short paragraph that is basically the summary? That would duplicate. To avoid duplication, maybe we omit About the role heading and start with Responsibilities heading. But the instructions list About the role as example; but they say include a section ONLY when posting has real, specific content for it. If we omit About the role heading, we are not including a section for it, which is okay if we consider that the summary already covers about the role. However the summary is more generic; but it's still about the role. I'd keep About the role heading with the summary paragraph to avoid missing content. But then we would have duplicate content if we also keep summary separate. We could just have About the role heading with the summary paragraph, and not have a separate intro paragraph. That satisfies About the role section.
Thus: About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use h3 for those section headings; not that we cannot use other headings, but likely they expect only those. To be safe, we can map content to those headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have info for About the role (maybe summary), Responsibilities (list), Requirements (essential + desirable), Qualifications (maybe leveling guidelines?), Skills (maybe not explicit), Benefits, Pay. Schedule not present.
We could treat "Leveling Guidelines" as Qualifications. Or "Qualifications" heading could contain the leveling guidelines and experience requirements. The posting includes "Essential Requirements" (education, experience) and "Desirable Requirements" (experience across therapeutic groups etc.) and "Leveling Guidelines" (specific years). That's all qualifications. So we can put under Qualifications heading: combine essential, desirable, leveling guidelines.
Skills: Not explicitly listed; maybe we can omit Skills section.
Thus final sections: About the role (intro paragraph), Responsibilities (list), Qualifications (list of essential, desirable, leveling), Benefits (list), Pay (list of salary ranges). Also maybe include "Driving is an Essential Function" and "COVID-19 Vaccine Policy" and "For Field Roles with a Dedicated Training Period". Where to put those? They could be part of Requirements or Qualifications? Driving is an essential function - could be a requirement. COVID vaccine policy - maybe a requirement. Training period - maybe a requirement. We could include them under Qualifications as additional items.
We must preserve all substantive information. So we need to include those details somewhere.
Let's extract each piece.
Summary (intro): as above.
About the role: maybe we can use the first sentence of summary? But we already used summary as intro. Could we treat About the role heading with a short paragraph that is basically the summary? That would duplicate. To avoid duplication, maybe we omit About the role heading and start with Responsibilities heading. But the instructions list About the role as example; but they say include a section ONLY when posting has real, specific content for it. If we omit About the role heading, we are not including a section for it, which is okay if we consider that the summary already covers about the role. However the summary is more generic; but it's still about the role. I'd keep About the role heading with the summary paragraph to avoid missing content. But then we would have duplicate content if we also keep summary separate. We could just have About the role heading with the summary paragraph, and not have a separate intro paragraph. That satisfies About the role section.
Thus: About the role
This is a field-based and remote opportunity supporting key accounts in an assigned geography. Novartis is unable to offer relocation support for this role. Please only apply if this location is accessible to you. Company will not sponsor visas for this position. As a Territory Account Specialist (TAS), you’ll lead with purpose – crafting personalized experiences that reflect the unique needs of each account and Health Care Provider (HCP). Acting as the primary point of contact, you’ll build meaningful connections, identify shared priorities, and navigate solutions that link customers to Novartis resources – all with the goal of improving patient outcomes. Success in this role comes from balancing demand generation with strategic account engagement. You’ll bring expertise in clinical and account-based selling, access navigation, collaborative problem-solving, team orchestration, and omni-channel engagement.
Now Responsibilities: The list under "Key Responsibilities:" includes multiple sentences each starting with a verb. We'll make each as