Director, Commercial IT Systems
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. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to include sections only if there is real content. The posting includes: Location line, The Opportunity (about role), Primary Responsibilities, Qualifications, Annualized Base Salary, Compensation & Benefits, Company Overview, Diversity, Equity & Inclusion, Attention: Job Scam Alert (should be removed as boilerplate). Also "The physical and mental requirements..." maybe part of qualifications? It's generic but we can include as part of qualifications? It's not a list; it's prose about physical requirements. Might be considered boilerplate? It's not EEO but it's generic. Might be considered not needed? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The physical/mental requirements is not exactly that but could be considered boilerplate. However it's substantive? It's generic but maybe we keep as part of qualifications? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it unless it's clearly boilerplate like EEO. The physical/mental requirements is generic but still part of job description. I'd keep it as a paragraph under Qualifications or maybe a separate section "Requirements"? But we have Qualifications heading; we can include that paragraph there.
We need to decide sections: About the role (The Opportunity...), Responsibilities (Primary Responsibilities), Qualifications (including experience, skills, physical requirements), Pay (Annualized Base Salary), Benefits (Compensation & Benefits), Company Overview maybe as "About the Company"? Not listed in allowed headings but we could use "About the role" for role description; company overview maybe not needed but could be included as a section? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It says use those as examples; we can also use other headings if needed? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should stick to those headings. So we need to map content to those headings.
We have: About the role: The Opportunity paragraph.
Responsibilities: Primary Responsibilities (list).
Qualifications: Qualifications section (including experience, skills, physical requirements). Could also include Requirements but we can combine.
Benefits: Compensation & Benefits.
Pay: Annualized Base Salary.
We might not need Requirements separate if we put everything under Qualifications. But we could also have Requirements heading for the list of requirements (like 10+ years experience etc). However Qualifications already covers that. To avoid thin sections, we can combine.
We need to output only HTML fragment, no /, no markdown.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information. So we need to include the lists exactly as given.
Let's extract content.
Location line: "Location: This position may be performed remotely, but requires the flexibility and willingness to travel as needed." This is metadata; we can fold into a short
maybe under About the role or at top. Not a heading. We'll include as a paragraph before sections.
About the role: The Opportunity Praxis is building the commercial capabilities needed to bring new therapies to patients. We’re looking for a Director of Commercial Systems to own the strategy, roadmap, and business performance of the technology supporting commercial launch and growth. Reporting to the Vice President of Information Technology, you will lead Commercial Systems within IT. Partner with Sales, Marketing, Commercial Operations, and Market Access to translate business priorities into a coordinated roadmap, lead delivery, and ensure reliable systems and trusted data. You will directly manage enterprise applications strategy and development and partner with IT peers, Data & Analytics, and commercial business owners. This role combines strategic leadership with accountability for delivery, reliability, launch readiness, and adoption.
We'll put that in
.
Responsibilities: list of bullet points under "Primary Responsibilities". Need to convert each line to
- . The bullet points start with "Own the commercial systems strategy and roadmap." etc. We'll capture all.
Let's list them:
- Own the commercial systems strategy and roadmap.
- Translate launch milestones and business objectives into sequenced investments, clear priorities, and measurable outcomes across CRM, commercial data, field enablement, and connected commercial platforms.
- Establish business ownership and decision-making for commercial systems.
- Align stakeholders on requirements, process changes, data definitions, priorities, and acceptance criteria; resolve competing demands and escalate material tradeoffs.
- Lead commercial systems delivery from planning through adoption. Coordinate internal teams and implementation partners, manage dependencies and risks, and hold owners accountable for milestones, quality, and operational readiness.
- Own business requirements and service expectations for CRM and its connections to commercial data, digital engagement, and relevant ERP workflows.
- Partner with enterprise application owners to ensure end-to-end processes work across organizational boundaries.
- Partner with Data & Analytics to define the commercial data and reporting capabilities needed for launch and growth, including source requirements, data quality, timeliness, and business definitions.
- Establish dependable access to critical information and continuity when AI interfaces are unavailable.
- Own vendor performance, service expectations, and the commercial systems investment plan.
- Lead business cases, evaluate platform choices, and manage approved budgets, license utilization, and renewals with IT, Finance, Procurement, and Legal.
- Lead launch readiness, user acceptance, training, and change management with business owners.
- Establish adoption measures, support coverage, escalation paths, and contingency plans before systems become business-critical.
- Partner with IT, Security, Privacy, Legal, and Quality to incorporate access controls, data stewardship, change control, and applicable compliance requirements into commercial workflows and vendor delivery.
We need to ensure we keep the exact wording.
Qualifications: The qualifications section includes paragraphs and a list? It's a paragraph with numbered items? Actually it's a paragraph with sentences, not bullet list. It includes:
"Qualifications
10+ years of relevant experience in commercial technology, enterprise applications, commercial operations systems, or related roles, including leadership of complex cross-functional initiatives.
Experience supporting pharmaceutical or biotechnology commercial operations, with a track record delivering systems for a product launch or significant commercial expansion.
Strong understanding of CRM, field workflows, commercial data, digital engagement, and the integrations that connect them.
Experience with Veeva, Salesforce, or comparable enterprise platforms.
Ability to translate commercial strategy into a practical roadmap, business cases, priorities, and measurable outcomes; experience managing technology vendors and budgets.
Technical fluency in data flows, APIs, integration patterns, and cloud data platforms sufficient to challenge designs, assess dependencies, and guide delivery with engineering and analytics teams.
Experience leading requirements definition, user acceptance testing, change management, training, and transition to ongoing support.
Sound judgment in handling sensitive commercial and healthcare data, with experience partnering across IT, Security, Legal, Privacy, and Quality.
Clear communication, effective influence across functions, and a track record developing team capability and holding internal and external partners accountable.
Launch readiness: Critical commercial workflows are tested, supported, and ready when the business needs them.
Clear ownership: Decisions, priorities, and accountability are explicit; issues move to resolution without repeated executive intervention.
Business impact: Systems are adopted, data is trusted, and investments deliver measurable improvements in commercial execution.
Practical leadership and caring candor: You simplify complexity, surface risks early, challenge assumptions respectfully, and build strong delivery partnerships.
The physical and mental requirements of our roles include but are not limited to regular use of a computer, devices or other office equipment, clear communication, and occasional movement. You'll need comfort with screen work, basic hand coordination, and focus. Reasonable accommodations may be made to enable individuals with disabilities to perform these functions."
We need to preserve all. Should we format as
- for each line? The instruction: Use
- for any list of duties/requirements/benefits. This is a list of qualifications, so we should use
- . However some items are sentences with colon like "Launch readiness: Critical commercial workflows...". Still list items.
We'll wrap each line in
- . Ensure we keep the exact text.
Pay: Annualized Base Salary: $190,000 USD - $220,000 USD
We'll put under
Pay
with .
Benefits: Compensation & Benefits paragraph. It's a prose paragraph describing benefits. We'll put under
Benefits
with . The paragraph includes multiple sentences; we keep as is.
We might also include Company Overview? Not in allowed headings; but we could omit as not required? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit company overview, we lose substantive info. However we could include it under a heading like "About the role"? But that's already used. Could we add another heading like "Company Overview"? 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, not exclusive list. But to be safe, we could include it as a section with heading "About the Company" but not in list; risk of being considered extra. However the instruction says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings. But the examples given are typical sections. I'd include Company Overview as a section with About the Company
maybe. But the instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings. However to be safe, we could incorporate company overview into the About the role section? But that would mix role and company. Might be okay but could be considered mixing. The instruction says "Prefer a few substantive sections over many thin ones." So we could have About the role, Responsibilities, Qualifications, Pay, Benefits. That's five sections. Company overview could be merged into About the role? But the About the role currently is about the opportunity; we could add company overview after that as another paragraph within same section. That would preserve info without extra heading. That seems acceptable.
Thus we will have sections: About the role (includes location paragraph? maybe location separate paragraph before sections). We'll put location as a
before the first heading.
Then
About the role
with containing the Opportunity paragraph plus Company Overview paragraph (two paragraphs? Could be two
inside the section). We'll
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to include sections only if there is real content. The posting includes: Location line, The Opportunity (about role), Primary Responsibilities, Qualifications, Annualized Base Salary, Compensation & Benefits, Company Overview, Diversity, Equity & Inclusion, Attention: Job Scam Alert (should be removed as boilerplate). Also "The physical and mental requirements..." maybe part of qualifications? It's generic but we can include as part of qualifications? It's not a list; it's prose about physical requirements. Might be considered boilerplate? It's not EEO but it's generic. Might be considered not needed? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The physical/mental requirements is not exactly that but could be considered boilerplate. However it's substantive? It's generic but maybe we keep as part of qualifications? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it unless it's clearly boilerplate like EEO. The physical/mental requirements is generic but still part of job description. I'd keep it as a paragraph under Qualifications or maybe a separate section "Requirements"? But we have Qualifications heading; we can include that paragraph there. We need to decide sections: About the role (The Opportunity...), Responsibilities (Primary Responsibilities), Qualifications (including experience, skills, physical requirements), Pay (Annualized Base Salary), Benefits (Compensation & Benefits), Company Overview maybe as "About the Company"? Not listed in allowed headings but we could use "About the role" for role description; company overview maybe not needed but could be included as a section? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It says use those as examples; we can also use other headings if needed? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should stick to those headings. So we need to map content to those headings.
We have: About the role: The Opportunity paragraph.
Responsibilities: Primary Responsibilities (list).
Qualifications: Qualifications section (including experience, skills, physical requirements). Could also include Requirements but we can combine.
Benefits: Compensation & Benefits.
Pay: Annualized Base Salary.
We might not need Requirements separate if we put everything under Qualifications. But we could also have Requirements heading for the list of requirements (like 10+ years experience etc). However Qualifications already covers that. To avoid thin sections, we can combine.
We need to output only HTML fragment, no /, no markdown.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information. So we need to include the lists exactly as given.
Let's extract content.
Location line: "Location: This position may be performed remotely, but requires the flexibility and willingness to travel as needed." This is metadata; we can fold into a short
maybe under About the role or at top. Not a heading. We'll include as a paragraph before sections.
About the role: The Opportunity Praxis is building the commercial capabilities needed to bring new therapies to patients. We’re looking for a Director of Commercial Systems to own the strategy, roadmap, and business performance of the technology supporting commercial launch and growth. Reporting to the Vice President of Information Technology, you will lead Commercial Systems within IT. Partner with Sales, Marketing, Commercial Operations, and Market Access to translate business priorities into a coordinated roadmap, lead delivery, and ensure reliable systems and trusted data. You will directly manage enterprise applications strategy and development and partner with IT peers, Data & Analytics, and commercial business owners. This role combines strategic leadership with accountability for delivery, reliability, launch readiness, and adoption.
We'll put that in
.
Responsibilities: list of bullet points under "Primary Responsibilities". Need to convert each line to
- . The bullet points start with "Own the commercial systems strategy and roadmap." etc. We'll capture all.
Let's list them:
- Own the commercial systems strategy and roadmap.
- Translate launch milestones and business objectives into sequenced investments, clear priorities, and measurable outcomes across CRM, commercial data, field enablement, and connected commercial platforms.
- Establish business ownership and decision-making for commercial systems.
- Align stakeholders on requirements, process changes, data definitions, priorities, and acceptance criteria; resolve competing demands and escalate material tradeoffs.
- Lead commercial systems delivery from planning through adoption. Coordinate internal teams and implementation partners, manage dependencies and risks, and hold owners accountable for milestones, quality, and operational readiness.
- Own business requirements and service expectations for CRM and its connections to commercial data, digital engagement, and relevant ERP workflows.
- Partner with enterprise application owners to ensure end-to-end processes work across organizational boundaries.
- Partner with Data & Analytics to define the commercial data and reporting capabilities needed for launch and growth, including source requirements, data quality, timeliness, and business definitions.
- Establish dependable access to critical information and continuity when AI interfaces are unavailable.
- Own vendor performance, service expectations, and the commercial systems investment plan.
- Lead business cases, evaluate platform choices, and manage approved budgets, license utilization, and renewals with IT, Finance, Procurement, and Legal.
- Lead launch readiness, user acceptance, training, and change management with business owners.
- Establish adoption measures, support coverage, escalation paths, and contingency plans before systems become business-critical.
- Partner with IT, Security, Privacy, Legal, and Quality to incorporate access controls, data stewardship, change control, and applicable compliance requirements into commercial workflows and vendor delivery.
We need to ensure we keep the exact wording.
Qualifications: The qualifications section includes paragraphs and a list? It's a paragraph with numbered items? Actually it's a paragraph with sentences, not bullet list. It includes:
"Qualifications
10+ years of relevant experience in commercial technology, enterprise applications, commercial operations systems, or related roles, including leadership of complex cross-functional initiatives.
Experience supporting pharmaceutical or biotechnology commercial operations, with a track record delivering systems for a product launch or significant commercial expansion.
Strong understanding of CRM, field workflows, commercial data, digital engagement, and the integrations that connect them.
Experience with Veeva, Salesforce, or comparable enterprise platforms.
Ability to translate commercial strategy into a practical roadmap, business cases, priorities, and measurable outcomes; experience managing technology vendors and budgets.
Technical fluency in data flows, APIs, integration patterns, and cloud data platforms sufficient to challenge designs, assess dependencies, and guide delivery with engineering and analytics teams.
Experience leading requirements definition, user acceptance testing, change management, training, and transition to ongoing support.
Sound judgment in handling sensitive commercial and healthcare data, with experience partnering across IT, Security, Legal, Privacy, and Quality.
Clear communication, effective influence across functions, and a track record developing team capability and holding internal and external partners accountable.
Launch readiness: Critical commercial workflows are tested, supported, and ready when the business needs them.
Clear ownership: Decisions, priorities, and accountability are explicit; issues move to resolution without repeated executive intervention.
Business impact: Systems are adopted, data is trusted, and investments deliver measurable improvements in commercial execution.
Practical leadership and caring candor: You simplify complexity, surface risks early, challenge assumptions respectfully, and build strong delivery partnerships.
The physical and mental requirements of our roles include but are not limited to regular use of a computer, devices or other office equipment, clear communication, and occasional movement. You'll need comfort with screen work, basic hand coordination, and focus. Reasonable accommodations may be made to enable individuals with disabilities to perform these functions."
We need to preserve all. Should we format as
- for each line? The instruction: Use
- for any list of duties/requirements/benefits. This is a list of qualifications, so we should use
- . However some items are sentences with colon like "Launch readiness: Critical commercial workflows...". Still list items.
We'll wrap each line in
- . Ensure we keep the exact text.
Pay: Annualized Base Salary: $190,000 USD - $220,000 USD
We'll put under
Pay
with .
Benefits: Compensation & Benefits paragraph. It's a prose paragraph describing benefits. We'll put under
Benefits
with . The paragraph includes multiple sentences; we keep as is.
We might also include Company Overview? Not in allowed headings; but we could omit as not required? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit company overview, we lose substantive info. However we could include it under a heading like "About the role"? But that's already used. Could we add another heading like "Company Overview"? 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, not exclusive list. But to be safe, we could include it as a section with heading "About the Company" but not in list; risk of being considered extra. However the instruction says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings. But the examples given are typical sections. I'd include Company Overview as a section with About the Company
maybe. But the instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings. However to be safe, we could incorporate company overview into the About the role section? But that would mix role and company. Might be okay but could be considered mixing. The instruction says "Prefer a few substantive sections over many thin ones." So we could have About the role, Responsibilities, Qualifications, Pay, Benefits. That's five sections. Company overview could be merged into About the role? But the About the role currently is about the opportunity; we could add company overview after that as another paragraph within same section. That would preserve info without extra heading. That seems acceptable.
Thus we will have sections: About the role (includes location paragraph? maybe location separate paragraph before sections). We'll put location as a
before the first heading.
Then
About the role
with containing the Opportunity paragraph plus Company Overview paragraph (two paragraphs? Could be two
inside the section). We'll
- for any list of duties/requirements/benefits. Use
for prose. We need to preserve all substantive information. So we need to include the lists exactly as given. Let's extract content. Location line: "Location: This position may be performed remotely, but requires the flexibility and willingness to travel as needed." This is metadata; we can fold into a short
maybe under About the role or at top. Not a heading. We'll include as a paragraph before sections. About the role: The Opportunity Praxis is building the commercial capabilities needed to bring new therapies to patients. We’re looking for a Director of Commercial Systems to own the strategy, roadmap, and business performance of the technology supporting commercial launch and growth. Reporting to the Vice President of Information Technology, you will lead Commercial Systems within IT. Partner with Sales, Marketing, Commercial Operations, and Market Access to translate business priorities into a coordinated roadmap, lead delivery, and ensure reliable systems and trusted data. You will directly manage enterprise applications strategy and development and partner with IT peers, Data & Analytics, and commercial business owners. This role combines strategic leadership with accountability for delivery, reliability, launch readiness, and adoption. We'll put that in
. Responsibilities: list of bullet points under "Primary Responsibilities". Need to convert each line to
- . The bullet points start with "Own the commercial systems strategy and roadmap." etc. We'll capture all.
Let's list them:
- Own the commercial systems strategy and roadmap.
- Translate launch milestones and business objectives into sequenced investments, clear priorities, and measurable outcomes across CRM, commercial data, field enablement, and connected commercial platforms.
- Establish business ownership and decision-making for commercial systems.
- Align stakeholders on requirements, process changes, data definitions, priorities, and acceptance criteria; resolve competing demands and escalate material tradeoffs.
- Lead commercial systems delivery from planning through adoption. Coordinate internal teams and implementation partners, manage dependencies and risks, and hold owners accountable for milestones, quality, and operational readiness.
- Own business requirements and service expectations for CRM and its connections to commercial data, digital engagement, and relevant ERP workflows.
- Partner with enterprise application owners to ensure end-to-end processes work across organizational boundaries.
- Partner with Data & Analytics to define the commercial data and reporting capabilities needed for launch and growth, including source requirements, data quality, timeliness, and business definitions.
- Establish dependable access to critical information and continuity when AI interfaces are unavailable.
- Own vendor performance, service expectations, and the commercial systems investment plan.
- Lead business cases, evaluate platform choices, and manage approved budgets, license utilization, and renewals with IT, Finance, Procurement, and Legal.
- Lead launch readiness, user acceptance, training, and change management with business owners.
- Establish adoption measures, support coverage, escalation paths, and contingency plans before systems become business-critical.
- Partner with IT, Security, Privacy, Legal, and Quality to incorporate access controls, data stewardship, change control, and applicable compliance requirements into commercial workflows and vendor delivery.
We need to ensure we keep the exact wording.
Qualifications: The qualifications section includes paragraphs and a list? It's a paragraph with numbered items? Actually it's a paragraph with sentences, not bullet list. It includes:
"Qualifications
10+ years of relevant experience in commercial technology, enterprise applications, commercial operations systems, or related roles, including leadership of complex cross-functional initiatives.
Experience supporting pharmaceutical or biotechnology commercial operations, with a track record delivering systems for a product launch or significant commercial expansion.
Strong understanding of CRM, field workflows, commercial data, digital engagement, and the integrations that connect them.
Experience with Veeva, Salesforce, or comparable enterprise platforms.
Ability to translate commercial strategy into a practical roadmap, business cases, priorities, and measurable outcomes; experience managing technology vendors and budgets.
Technical fluency in data flows, APIs, integration patterns, and cloud data platforms sufficient to challenge designs, assess dependencies, and guide delivery with engineering and analytics teams.
Experience leading requirements definition, user acceptance testing, change management, training, and transition to ongoing support.
Sound judgment in handling sensitive commercial and healthcare data, with experience partnering across IT, Security, Legal, Privacy, and Quality.
Clear communication, effective influence across functions, and a track record developing team capability and holding internal and external partners accountable.
Launch readiness: Critical commercial workflows are tested, supported, and ready when the business needs them.
Clear ownership: Decisions, priorities, and accountability are explicit; issues move to resolution without repeated executive intervention.
Business impact: Systems are adopted, data is trusted, and investments deliver measurable improvements in commercial execution.
Practical leadership and caring candor: You simplify complexity, surface risks early, challenge assumptions respectfully, and build strong delivery partnerships.
The physical and mental requirements of our roles include but are not limited to regular use of a computer, devices or other office equipment, clear communication, and occasional movement. You'll need comfort with screen work, basic hand coordination, and focus. Reasonable accommodations may be made to enable individuals with disabilities to perform these functions."
We need to preserve all. Should we format as
- for each line? The instruction: Use
- for any list of duties/requirements/benefits. This is a list of qualifications, so we should use
- . However some items are sentences with colon like "Launch readiness: Critical commercial workflows...". Still list items. We'll wrap each line in
- . Ensure we keep the exact text.
Pay: Annualized Base Salary: $190,000 USD - $220,000 USD
We'll put under
Pay
with. Benefits: Compensation & Benefits paragraph. It's a prose paragraph describing benefits. We'll put under
Benefits
with. The paragraph includes multiple sentences; we keep as is. We might also include Company Overview? Not in allowed headings; but we could omit as not required? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit company overview, we lose substantive info. However we could include it under a heading like "About the role"? But that's already used. Could we add another heading like "Company Overview"? 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, not exclusive list. But to be safe, we could include it as a section with heading "About the Company" but not in list; risk of being considered extra. However the instruction says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings. But the examples given are typical sections. I'd include Company Overview as a section with
About the Company
maybe. But the instruction says "Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings. However to be safe, we could incorporate company overview into the About the role section? But that would mix role and company. Might be okay but could be considered mixing. The instruction says "Prefer a few substantive sections over many thin ones." So we could have About the role, Responsibilities, Qualifications, Pay, Benefits. That's five sections. Company overview could be merged into About the role? But the About the role currently is about the opportunity; we could add company overview after that as another paragraph within same section. That would preserve info without extra heading. That seems acceptable. Thus we will have sections: About the role (includes location paragraph? maybe location separate paragraph before sections). We'll put location as a
before the first heading. Then
About the role
withcontaining the Opportunity paragraph plus Company Overview paragraph (two paragraphs? Could be two
inside the section). We'll
- for any list of duties/requirements/benefits. This is a list of qualifications, so we should use
- for each line? The instruction: Use