NA Sales Representative, Data Platform Healthcare
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We must not repeat job title as heading. Remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions.
We need to preserve all substantive information.
Let's parse the job description.
Content:
- Overview: "Data Platform Account Executive – Healthcare & Life Sciences (Multi-Cloud) Drive the Future of Healthcare with Data, AI, and Cloud Overview Oracle is seeking a high-performing Data Platform Account Executive to help Healthcare and Life Sciences organizations transform how they leverage data, analytics, AI, and cloud technologies. This role focuses on strategic enterprise accounts across Providers, Payors, Pharmaceutical, Biotechnology, Medical Device, and Research organizations, helping customers modernize data architectures and accelerate business outcomes through Oracle's industry-leading Data Platform and Cloud portfolio. If you thrive in complex enterprise sales, enjoy building executive relationships, and have a passion for helping customers solve critical business challenges, we'd love to meet you."
- What You'll Do: bullet list (Develop and grow strategic Healthcare & Life Sciences accounts. Build trusted relationships with C-level executives and key business stakeholders. Drive sales of Oracle's Data Platform, Database, Analytics, AI, and Cloud solutions. Lead customer discussions around data modernization, AI adoption, analytics transformation, and digital innovation. Position Oracle as a strategic partner for multi-cloud and hybrid cloud initiatives spanning OCI, AWS, Microsoft Azure, and Google Cloud. Generate, manage, and close complex enterprise opportunities while maintaining a strong sales pipeline and forecast. Collaborate with Oracle's cloud, AI, industry, and solution engineering teams to deliver customer success.)
- What We're Looking For: bullet list (8+ years of successful enterprise technology sales experience. Experience selling Data Platform, Database, Analytics, AI, Cloud Infrastructure, SaaS, PaaS, or related solutions. Healthcare and/or Life Sciences industry experience strongly preferred. Demonstrated success selling to CIOs, CTOs, CDOs, and other executive stakeholders. Proven track record of exceeding quota and closing complex enterprise deals. Understanding of modern data architectures, AI/ML, analytics, and cloud technologies. Familiarity with multi-cloud strategies involving OCI, AWS, Azure, and GCP. Strong prospecting, account planning, communication, and executive presentation skills.)
- Why Oracle: paragraph.
- Responsibilities: list (Primary job duty is to sell technology software products and related services in a defined territory. Identifies, qualifies and closes new opportunities. Manages accounts including the entire sales process from business development prospecting and specifications through contract negotiations, signing, and post-sales support. Leverages the Oracle sales model to maximize revenue growth and increase local market share. Builds and expands business partner revenue and self sufficiency.)
- Qualifications: includes disclaimer about immunization etc. Then "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $126,600 - $217,700 per year. May be eligible for equity. Eligible for commission with an estimated pay mix of 45 / 55. Oracle maintains broad salary ranges for its roles in order to account for variations in knowledge, skills, experience, market conditions and locations, as well as reflect Oracle's differing products, industries and lines of business. Candidates are typically placed into the range based on the preceding factors as well as internal peer equity. Oracle US offers a comprehensive benefits package which includes the following: Medical, dental, and vision insurance, including expert medical opinion Short term disability and long term disability Life insurance and AD&D Supplemental life insurance (Employee/Spouse/Child) Health care and dependent care Flexible Spending Accounts Pre-tax commuter and parking benefits 401(k) Savings and Investment Plan with company match Paid time off: Flexible Vacation is provided to all eligible employees assigned to a salaried (non-overtime eligible) position. Accrued Vacation is provided to all other employees eligible for vacation benefits. For employees working at least 35 hours per week, the vacation accrual rate is 13 days annually for the first three years of employment and 18 days annually for subsequent years of employment. Vacation accrual is prorated for employees working between 20 and 34 hours per week. Employees working fewer than 20 hours per week are not eligible for vacation. 11 paid holidays Paid sick leave: 72 hours of paid sick leave upon date of hire. Refreshes each calendar year. Unused balance will carry over each year up to a maximum cap of 112 hours. Paid parental leave Adoption assistance Employee Stock Purchase Plan Financial planning and group legal Voluntary benefits including auto, homeowner and pet insurance The role will generally accept applications for at least three calendar days from the posting date or as long as the job remains posted. As part of Oracle's onboarding process and consistent with applicable law, US-based employees are required to complete identity verification, which involves the collection and processing of their biometric information. Accommodations to this requirement may be granted following an individualized assessment."
- About Us: paragraph.
- Then EEO etc.
We need to include sections: About the role (maybe "Overview" or "About the role"? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map content to these headings.
We have:
- About the role: could be the overview and "What You'll Do" maybe. But we need to decide.
- Responsibilities: we have a separate "Responsibilities" section.
- Requirements: maybe "What We're Looking For" (experience requirements). Could map to Requirements.
- Qualifications: we have Qualifications section (including salary range, benefits). But also there is a "Qualifications" heading in the posting. So we can use that.
- Skills: maybe we can extract skills from "What We're Looking For" but that is more experience. Could still include Skills if we have specific skill list. The posting includes "Strong prospecting, account planning, communication, and executive presentation skills." That's skills. Also "Understanding of modern data architectures, AI/ML, analytics, and cloud technologies." etc. Could be skills.
- Benefits: we have benefits list in Qualifications section.
- Pay: we have hiring range and commission info.
- Schedule: not present (no schedule info). So we should not include Schedule.
We must not create sections with filler like "commensurate with experience". We have actual pay range.
We need to output only HTML fragment, no /, no markdown.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information; do not invent or summarize away detail.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
Thus we need to strip:
- The disclaimer about immunization etc? That's part of Qualifications but maybe considered boilerplate? It's a disclaimer about US-based roles may be required to comply with immunization/occupational health mandates, and/or drug testing requirements. That's likely boilerplate but it's substantive? It's a requirement. Might be considered legal boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is a legal disclaimer about immunization etc. Might be considered legal boilerplate. Safer to remove it? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove that line.
- Also the line about "The role will generally accept applications for at least three calendar days from the posting date or as long as the job remains posted." That's application instructions; remove.
- Also the line about identity verification and biometric info; that's also legal/onboarding; maybe remove as boilerplate? It's about onboarding process. Might be considered legal. Probably remove.
- Also the EEO statement at the end; remove.
- Also the "About Us" paragraph maybe not boilerplate; it's substantive about Oracle's mission. Keep.
- Also the "Why Oracle" paragraph; keep.
- Also the "What You'll Do" and "What We're Looking For" sections; keep.
- Also the "Responsibilities" section; keep.
- Also the "Qualifications" section (including salary range, benefits). Keep but need to strip the disclaimer lines.
- Also the "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $126,600 - $217,700 per year. May be eligible for equity. Eligible for commission with an estimated pay mix of 45 / 55." That's pay info.
- Also the benefits list.
- Also the "Oracle maintains broad salary ranges..." etc. That's explanatory; keep? It's substantive about salary ranges. Keep.
- Also the "Candidates are typically placed into the range based on the preceding factors as well as internal peer equity." Keep.
- Also the "Oracle US offers a comprehensive benefits package which includes the following:" then list.
We need to format as sections.
Let's decide on sections:
- About the role: could combine overview and "What You'll Do". But we have separate "What You'll Do" which is duties. Could map to Responsibilities? Actually Responsibilities section already exists later. Might be duplication. The posting has both "What You'll Do" and later "Responsibilities". They are similar but not identical. We need to preserve all substantive information; we can combine them under Responsibilities? But we have a separate Responsibilities heading later. To avoid duplication, we could keep both sections but maybe merge? The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid thin sections. We could have sections: About the role (overview), Responsibilities (combining What You'll Do and Responsibilities), Requirements (What We're Looking For), Qualifications (including salary, benefits, etc.), Skills (maybe extract from What We're Looking For), Benefits (maybe separate), Pay (salary range and commission). But we need to avoid duplication.
Let's think: The posting already has headings: "What You'll Do", "What We're Looking For", "Why Oracle", "Responsibilities", "Qualifications", "About Us". We can map to our allowed headings.
We could output:
About the role
with overview paragraph.
Responsibilities
with combined list from "What You'll Do" and the Responsibilities bullet list.
Requirements
with list from "What We're Looking For".
Qualifications
with maybe the disclaimer? But we removed disclaimer. Could include the statement about salary range and benefits? Actually Qualifications heading in posting includes salary range and benefits. But we also have Benefits and Pay sections. Might be better to split: Qualifications for experience/education? But we already have Requirements for experience. Qualifications could be for education/certifications? Not present. So maybe we skip Qualifications heading and instead have Benefits and Pay sections.
But the instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't require us to use all; only include when posting has real specific content.
We have content for:
- About the role (overview)
- Responsibilities (duties)
- Requirements (experience/skills)
- Skills (maybe we can extract specific skills)
- Benefits (list)
- Pay (salary range, commission)
- Maybe not Qualifications (since we have Requirements and Skills). But we could treat Qualifications as the combination of Requirements and Skills? But we already have separate.
Better to follow the posting's headings: "What You'll Do" -> Responsibilities. "What We're Looking
- for any list of duties/requirements/benefits, and
for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we need to strip: - The disclaimer about immunization etc? That's part of Qualifications but maybe considered boilerplate? It's a disclaimer about US-based roles may be required to comply with immunization/occupational health mandates, and/or drug testing requirements. That's likely boilerplate but it's substantive? It's a requirement. Might be considered legal boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is a legal disclaimer about immunization etc. Might be considered legal boilerplate. Safer to remove it? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove that line. - Also the line about "The role will generally accept applications for at least three calendar days from the posting date or as long as the job remains posted." That's application instructions; remove. - Also the line about identity verification and biometric info; that's also legal/onboarding; maybe remove as boilerplate? It's about onboarding process. Might be considered legal. Probably remove. - Also the EEO statement at the end; remove. - Also the "About Us" paragraph maybe not boilerplate; it's substantive about Oracle's mission. Keep. - Also the "Why Oracle" paragraph; keep. - Also the "What You'll Do" and "What We're Looking For" sections; keep. - Also the "Responsibilities" section; keep. - Also the "Qualifications" section (including salary range, benefits). Keep but need to strip the disclaimer lines. - Also the "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $126,600 - $217,700 per year. May be eligible for equity. Eligible for commission with an estimated pay mix of 45 / 55." That's pay info. - Also the benefits list. - Also the "Oracle maintains broad salary ranges..." etc. That's explanatory; keep? It's substantive about salary ranges. Keep. - Also the "Candidates are typically placed into the range based on the preceding factors as well as internal peer equity." Keep. - Also the "Oracle US offers a comprehensive benefits package which includes the following:" then list. We need to format as sections. Let's decide on sections: - About the role: could combine overview and "What You'll Do". But we have separate "What You'll Do" which is duties. Could map to Responsibilities? Actually Responsibilities section already exists later. Might be duplication. The posting has both "What You'll Do" and later "Responsibilities". They are similar but not identical. We need to preserve all substantive information; we can combine them under Responsibilities? But we have a separate Responsibilities heading later. To avoid duplication, we could keep both sections but maybe merge? The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid thin sections. We could have sections: About the role (overview), Responsibilities (combining What You'll Do and Responsibilities), Requirements (What We're Looking For), Qualifications (including salary, benefits, etc.), Skills (maybe extract from What We're Looking For), Benefits (maybe separate), Pay (salary range and commission). But we need to avoid duplication. Let's think: The posting already has headings: "What You'll Do", "What We're Looking For", "Why Oracle", "Responsibilities", "Qualifications", "About Us". We can map to our allowed headings. We could output:
About the role
with overview paragraph.Responsibilities
with combined list from "What You'll Do" and the Responsibilities bullet list.Requirements
with list from "What We're Looking For".Qualifications
with maybe the disclaimer? But we removed disclaimer. Could include the statement about salary range and benefits? Actually Qualifications heading in posting includes salary range and benefits. But we also have Benefits and Pay sections. Might be better to split: Qualifications for experience/education? But we already have Requirements for experience. Qualifications could be for education/certifications? Not present. So maybe we skip Qualifications heading and instead have Benefits and Pay sections. But the instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't require us to use all; only include when posting has real specific content. We have content for: - About the role (overview) - Responsibilities (duties) - Requirements (experience/skills) - Skills (maybe we can extract specific skills) - Benefits (list) - Pay (salary range, commission) - Maybe not Qualifications (since we have Requirements and Skills). But we could treat Qualifications as the combination of Requirements and Skills? But we already have separate. Better to follow the posting's headings: "What You'll Do" -> Responsibilities. "What We're Looking