NA Sales Representative, Data Platform Healthcare

We need to output HTML fragment only, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the job description and extract sections. The posting includes: - Overview (intro) maybe "About the role"? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections have content. We have: - Overview: "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." That's like a description of the role. Could be "About the role". - What You'll Do: list of duties: bullet points. - What We're Looking For: qualifications/experience. - Why Oracle: maybe not needed. - Responsibilities: later there is a "Responsibilities" heading with bullet points. - Qualifications: later there is a "Qualifications" heading with bullet points and disclaimer. - Benefits: later there is a benefits list. - Pay: there is "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." - Schedule: not mentioned. - Skills: maybe not explicit separate; but we could combine qualifications and skills. We need to avoid filler sections. So we should include sections that have real content: About the role (overview), Responsibilities, Qualifications (maybe combine with Requirements?), Benefits, Pay. Possibly Skills if we have explicit skill list; but we have "What We're Looking For" which includes experience, etc. That could be "Requirements" or "Qualifications". The instruction lists both Requirements and Qualifications as possible headings. We need to decide which to use. We have a "Qualifications" section later with bullet points. Also "What We're Looking For" is similar to qualifications. To avoid duplication, we could combine them under Qualifications. Or we could have Requirements (what we're looking for) and Qualifications (the later bullet list). But they'd be similar; better to have one substantive section. We should not create sections with placeholder text. So we need to check each potential section: - About the role: we have overview paragraph. Good. - Responsibilities: we have a "Responsibilities" heading with bullet points: "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." That's substantive. - Requirements: we have "What We're Looking For" bullet list: 8+ years experience, etc. That's substantive. - Qualifications: we have a "Qualifications" heading with bullet list: includes disclaimer about immunization, etc. That's also substantive but includes some boilerplate (disclaimer about immunization/occupational health mandates, drug testing). That's maybe still substantive but includes legal disclaimer. We might keep it but we need to remove boilerplate like EEO etc. The disclaimer about immunization/occupational health mandates is specific to role; we can keep. However we also have a later "About Us" and EEO etc which we should remove. - Benefits: we have a list of benefits after "Oracle US offers a comprehensive benefits package which includes the following:" then bullet list. That's substantive. - Pay: we have hiring range, equity, commission mix. That's substantive. - Schedule: not mentioned, so we should not include. - Skills: not explicit separate; we could omit. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We need to use

  for each section heading. Then under each, use

  for prose,

  • for lists. We must preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include all details from those sections. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to check for duplicated lines: The "What You'll Do" and "Responsibilities" may overlap but we need to keep both? The instruction says preserve ALL substantive information; do not invent or summarize away detail. If there is overlapping content, we should keep both? Might be duplication but we should keep as is? However we should remove duplicated lines. The "What You'll Do" and later "Responsibilities" are somewhat similar but not identical. The "What You'll Do" includes: 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. The "Responsibilities" section: 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. These are not exact duplicates; they both contain substantive info. We should keep both? But they are under different headings: "What You'll Do" could be considered part of About the role or Responsibilities. Since we have a Responsibilities section, we could merge the "What You'll Do" into Responsibilities to avoid duplication. However the instruction says preserve ALL substantive information; we can combine them under Responsibilities as a list, ensuring we don't lose any detail. That would be acceptable as we are not removing info, just reorganizing. But we must not invent or summarize away detail; combining is fine as long as we keep all points. Similarly, "What We're Looking For" and "Qualifications" may overlap; we can combine. We need to decide on final sections: - About the role: overview paragraph (the intro). Could also include the first paragraph about Oracle seeking etc. We'll keep that as prose. - Responsibilities: combine "What You'll Do" and the later "Responsibilities" bullet list into a single list under Responsibilities. - Requirements: maybe we can treat "What We're Looking For" as Requirements. But we also have Qualifications section with disclaimer etc. We could combine them into Qualifications. However the instruction lists both Requirements and Qualifications as possible headings. We could have Requirements (experience, industry, etc.) and Qualifications (disclaimer, etc.) but that may be thin. Better to have one Qualifications section that includes both experience requirements and the disclaimer. But we need to avoid filler. Let's see content: "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. "Qualifications" heading bullet list (after disclaimer): - Disclaimer: Certain U.S. based or U.S. customer or client-facing roles may be required to comply with applicable requirements, such as immunization/occupational health mandates, and/or drug testing requirements. - 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: [list] ... Actually the benefits list is under that same heading? Wait the text after "Qualifications" includes disclaimer, then "Range and benefit information provided in this posting are specific to the stated locations only US: ..." then benefits list. Actually the benefits list appears after that paragraph. So the "Qualifications" section includes disclaimer, pay range, benefits description. That seems like mixing of pay and benefits. But we have separate Pay and Benefits sections we want to create. So we need to parse correctly. Let's re-excerpt the relevant part: "Qualifications Disclaimer: Certain U.S. based or U.S. customer or client-facing roles may be required to comply with applicable requirements, such as immunization/occupational health mandates, and/or drug testing requirements. 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