NA Sales Representative, Data Platform SLED
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content.
We have "What You'll Do" which is responsibilities. There's also a later "Responsibilities" heading with bullet list. Likely we should include Responsibilities section with that content.
We have "What We're Looking For" which is qualifications/requirements/skills. There's also a "Qualifications" heading later with bullet list and disclaimer. Also there is "Why Oracle" and "Why Join Oracle?" which could be Benefits? Actually benefits are listed later under "Oracle US offers a comprehensive benefits package". So Benefits section.
Pay: There's "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $110,000 - $194,400 per year. May be eligible for equity. Eligible for commission with an estimated pay mix of 45 / 55." That's pay info.
Schedule: Not mentioned. No schedule info. So we should not include Schedule section.
Skills: Could be extracted from "What We're Looking For" which includes skills like communication, presentation, negotiation, prospecting, territory management, etc. Also "Ability to develop executive relationships..." etc. So we can have Skills section.
Requirements: Could be the baseline requirements: 4+ years of enterprise technology sales experience, etc. Also "Experience selling one or more of the following: Cloud Infrastructure (IaaS) Platform as a Service (PaaS) Database Technologies Data Platforms Analytics Artificial Intelligence (AI) SaaS Enterprise Applications". Also "Experience selling into State & Local Government, Higher Education, K-12, or Public Sector organizations is preferred but not required." Also "Understanding of cloud computing, AI, analytics, databases, modern data architectures, and digital transformation initiatives." Also "Familiarity with Oracle Cloud Infrastructure (OCI), AWS, Microsoft Azure, Google Cloud Platform, or other cloud providers."
Qualifications: Could be the later "Qualifications" heading with bullet list: Disclaimer about immunization etc. Range and benefit info (but that's pay). Actually the "Qualifications" section includes disclaimer and then pay range and benefits. But we already extracted pay and benefits separately. The qualifications section also includes "Oracle maintains broad salary ranges..." etc. That's more about pay. Might be redundant. But we need to preserve all substantive info; we can include that text under Qualifications? However the instruction says use headings for sections like Qualifications, Skills, etc. We need to decide what goes where.
Better approach: Use sections:
- About the role: introductory paragraphs up to "What You'll Do"? Actually "About the role" could be the first paragraph(s) describing the role and mission.
- Responsibilities: content from "What You'll Do" and the later "Responsibilities" bullet list.
- Requirements: baseline requirements (4+ years experience, passion for hunting, etc.) maybe also "Experience selling one or more of the following..." etc.
- Qualifications: maybe the later "Qualifications" heading content (disclaimer, salary range, benefits). But we already have Pay and Benefits sections. However the instruction says include a section ONLY when posting has real, specific content for it. So we need to decide if we include Qualifications separate from Requirements and Skills. The posting has a "Qualifications" heading with disclaimer and salary/benefit info. That is specific content. So we should include Qualifications section with that content (disclaimer, salary range, benefits). But then we also have Benefits and Pay sections separately; we could avoid duplication by putting salary range and benefits under Qualifications, and not create separate Pay/Benefits sections. However the instruction says we can include Pay and Benefits sections if posting actually states them. It does state them. So we could still include them, but we must not duplicate content. We could split: Qualifications section includes the disclaimer and maybe the statement about Oracle maintains broad salary ranges etc. Pay section includes the hiring range and commission mix. Benefits section includes the benefits list. That would avoid duplication.
But the Qualifications heading currently includes both disclaimer and salary/benefit info. We can parse: after "Qualifications" heading, there is a disclaimer paragraph, then "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $110,000 - $194,400 per year. May be eligible for equity. Eligible for commission with an estimated pay mix of 45 / 55." Then a paragraph about Oracle maintains broad salary ranges... Then "Oracle US offers a comprehensive benefits package which includes the following:" then list.
Thus we can assign:
- Qualifications: disclaimer paragraph only? Or also the statement about Oracle maintains broad salary ranges? That statement is about salary ranges, which is pay-related. Might be better to put that in Pay section. But to avoid duplication, we could put the disclaimer in Qualifications, and the pay range and benefits in Pay and Benefits sections respectively.
But the instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Qualifications, Pay, Benefits into one section? But they ask to use headings for each. However we can decide to include only those sections that have substantive content. The posting has content for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Schedule not present.
We need to avoid filler like "commensurate with experience". Not present.
Thus we will output sections:
About the role
with paragraphs describing the role (the introductory part before "What You'll Do").
Responsibilities
with - items from "What You'll Do" and the later Responsibilities bullet list.
Requirements
with - items from "What We're Looking For" that are baseline requirements: 4+ years experience, passion for hunting, managing full sales cycle, experience selling one or more of the listed tech, experience selling into SLED preferred, ability to develop executive relationships, track record of achieving quotas, understanding of cloud/AI/analytics/databases/modern data architectures/digital transformation, familiarity with OCI/AWS/Azure/GCP or other cloud providers.
Skills
with - items from "What We're Looking For" that are skills: Strong communication, presentation, negotiation, prospecting, territory management skills. Self-starter who enjoys learning, collaborating, competing in fast-paced enterprise sales environment.
Also maybe "Ability to develop executive relationships..." could be skill but we already put in Requirements; but it's okay.
Benefits
with - items from the benefits list.
Pay
with containing the hiring range, equity eligibility, commission mix.
We should not include Qualifications section separately because we split its content into Requirements, Skills, Pay, Benefits. But we still have the disclaimer about immunization/occupational health mandates, drug testing. That is substantive and not covered elsewhere. Where to put it? Could be under Requirements as a note. Or we could create a Qualifications section just for that disclaimer. The instruction says include a section only when posting has real, specific content for it. The disclaimer is specific content. So we should include a Qualifications section for that disclaimer. However we already have Requirements and Skills sections; we could add Qualifications section with the disclaimer paragraph.
Thus final sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Qualifications (disclaimer). Order maybe as typical: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Qualifications. But any order is fine as long as headings are used.
We must not repeat job title as heading. Not include Job ID etc.
We must output only HTML fragment, no /, no markdown.
Let's extract exact text.
First, "About the role": The initial paragraphs up to "What You'll Do". Let's copy:
"Oracle is transforming how government agencies and educational institutions leverage data, artificial intelligence, and cloud technologies to better serve citizens, students, and communities. We're looking for a highly motivated Data Platform & OCI Account Executive to join our North America Cloud organization. This is an exceptional opportunity for an ambitious enterprise sales professional who thrives on prospecting, building pipeline, opening new accounts, and winning complex cloud opportunities. You'll own a broad territory across State, Local Government, and Education (SLED) organizations, developing new relationships and helping customers modernize their data platforms, accelerate AI adoption, migrate workloads to Oracle Cloud Infrastructure (OCI), and embrace secure multi-cloud architectures. If you enjoy building relationships, creating opportunities from the ground up, and owning the entire sales process—from first meeting to signed contract—this is the role for you."
That seems good.
Now Responsibilities: Combine "What You'll Do" bullet points and the later "Responsibilities" bullet list.
"What You'll Do" paragraphs (not bullet but sentences). Let's extract each duty as separate bullet.
From "What You'll Do":
- Develop new business opportunities across a large portfolio of State, Local Government, and Education accounts.
- Prospect into assigned accounts through executive outreach, networking, referrals, partner engagement, and strategic business development activities.
- Build relationships with CIOs, CTOs, Chief Data Officers, CISOs, IT leaders, agency executives, superintendents, university technology leaders, and line-of-business stakeholders.
- Position Oracle's Data Platform and Oracle Cloud Infrastructure (OCI) portfolio to solve customers' most strategic business and technology challenges.
- Lead customer discussions around data modernization, AI adoption, cloud migration, analytics, cybersecurity, application modernization, and digital transformation.
- Drive sales of Oracle Database, Autonomous Database, AI Services, Analytics, Data Integration, Data Lakehouse, OCI, and multi-cloud solutions.
- Develop and execute territory and account plans that consistently generate qualified pipeline and exceed sales objectives.
- Manage the complete enterprise sales cycle, including prospecting, qualification, discovery, solution development, executive presentations, negotiations, forecasting, and close.
- Partner closely with Oracle Cloud Engineering, Solution Engineering, AI Specialists, Customer Success, Consulting, Marketing, and executive leadership throughout the sales process.
- Maintain an accurate forecast and healthy pipeline using Oracle sales methodologies and CRM tools.
- Travel as needed to support customer engagement and territory development.
Then later "Responsibilities" bullet 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
Requirements
with- items from "What We're Looking For" that are baseline requirements: 4+ years experience, passion for hunting, managing full sales cycle, experience selling one or more of the listed tech, experience selling into SLED preferred, ability to develop executive relationships, track record of achieving quotas, understanding of cloud/AI/analytics/databases/modern data architectures/digital transformation, familiarity with OCI/AWS/Azure/GCP or other cloud providers.
Skills
with- items from "What We're Looking For" that are skills: Strong communication, presentation, negotiation, prospecting, territory management skills. Self-starter who enjoys learning, collaborating, competing in fast-paced enterprise sales environment.
Also maybe "Ability to develop executive relationships..." could be skill but we already put in Requirements; but it's okay.
Benefits
with- items from the benefits list.
Pay
withcontaining the hiring range, equity eligibility, commission mix. We should not include Qualifications section separately because we split its content into Requirements, Skills, Pay, Benefits. But we still have the disclaimer about immunization/occupational health mandates, drug testing. That is substantive and not covered elsewhere. Where to put it? Could be under Requirements as a note. Or we could create a Qualifications section just for that disclaimer. The instruction says include a section only when posting has real, specific content for it. The disclaimer is specific content. So we should include a Qualifications section for that disclaimer. However we already have Requirements and Skills sections; we could add Qualifications section with the disclaimer paragraph. Thus final sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Qualifications (disclaimer). Order maybe as typical: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Qualifications. But any order is fine as long as headings are used. We must not repeat job title as heading. Not include Job ID etc. We must output only HTML fragment, no /, no markdown. Let's extract exact text. First, "About the role": The initial paragraphs up to "What You'll Do". Let's copy: "Oracle is transforming how government agencies and educational institutions leverage data, artificial intelligence, and cloud technologies to better serve citizens, students, and communities. We're looking for a highly motivated Data Platform & OCI Account Executive to join our North America Cloud organization. This is an exceptional opportunity for an ambitious enterprise sales professional who thrives on prospecting, building pipeline, opening new accounts, and winning complex cloud opportunities. You'll own a broad territory across State, Local Government, and Education (SLED) organizations, developing new relationships and helping customers modernize their data platforms, accelerate AI adoption, migrate workloads to Oracle Cloud Infrastructure (OCI), and embrace secure multi-cloud architectures. If you enjoy building relationships, creating opportunities from the ground up, and owning the entire sales process—from first meeting to signed contract—this is the role for you." That seems good. Now Responsibilities: Combine "What You'll Do" bullet points and the later "Responsibilities" bullet list. "What You'll Do" paragraphs (not bullet but sentences). Let's extract each duty as separate bullet. From "What You'll Do": - Develop new business opportunities across a large portfolio of State, Local Government, and Education accounts. - Prospect into assigned accounts through executive outreach, networking, referrals, partner engagement, and strategic business development activities. - Build relationships with CIOs, CTOs, Chief Data Officers, CISOs, IT leaders, agency executives, superintendents, university technology leaders, and line-of-business stakeholders. - Position Oracle's Data Platform and Oracle Cloud Infrastructure (OCI) portfolio to solve customers' most strategic business and technology challenges. - Lead customer discussions around data modernization, AI adoption, cloud migration, analytics, cybersecurity, application modernization, and digital transformation. - Drive sales of Oracle Database, Autonomous Database, AI Services, Analytics, Data Integration, Data Lakehouse, OCI, and multi-cloud solutions. - Develop and execute territory and account plans that consistently generate qualified pipeline and exceed sales objectives. - Manage the complete enterprise sales cycle, including prospecting, qualification, discovery, solution development, executive presentations, negotiations, forecasting, and close. - Partner closely with Oracle Cloud Engineering, Solution Engineering, AI Specialists, Customer Success, Consulting, Marketing, and executive leadership throughout the sales process. - Maintain an accurate forecast and healthy pipeline using Oracle sales methodologies and CRM tools. - Travel as needed to support customer engagement and territory development. Then later "Responsibilities" bullet 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
- items from the benefits list.
- items from "What We're Looking For" that are skills: Strong communication, presentation, negotiation, prospecting, territory management skills. Self-starter who enjoys learning, collaborating, competing in fast-paced enterprise sales environment.
Also maybe "Ability to develop executive relationships..." could be skill but we already put in Requirements; but it's okay.