Corporate Account Executive - Oracle NetSuite Consumer Services

We need to output only HTML fragment, no /. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We need to extract content. Job description includes: - Intro paragraph about Oracle NetSuite, etc. That could be "About the role" maybe? Actually "About the role" is typical heading. We can put the introductory description there. - Responsibilities: bullet list under "What You Will Do!" with many items. - Requirements: maybe "What We're Looking For!" includes bullet list of qualifications/experience. - Qualifications: there is a "Qualifications" section later with disclaimer and pay range, benefits details. Actually there is a "Qualifications" heading in the posting. It includes disclaimer, pay range, benefits. So we should treat that as Qualifications. - Benefits: there is a "Why Join Netsuite" section with bullet points: Competitive compensation, Comprehensive benefits, etc. Also there is a detailed benefits list under Qualifications. We need to decide: The posting has a "Why Join Netsuite" with bullet points: Sell the industry’s leading cloud ERP platform; Join Oracle’s world-class sales organization; Work alongside experienced sales leaders; Competitive compensation with uncapped earning potential; Comprehensive benefits and opportunities for long-term career growth; Be part of a collaborative culture... That's more like benefits/perks. Then later under Qualifications there is a detailed benefits list. So we could have Benefits section with that detailed list. Pay section: we have pay range info: "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from $31.73 - $50.72 per hour; from: $66,000 - $105,500 per year. May be eligible for equity. Eligible for commission with an estimated pay mix of 50 / 50." That's pay info. So we can create Pay section. Schedule: Not mentioned. So we should not include Schedule. Skills: Not explicitly separate; maybe we could put under Requirements or Qualifications. But we have a Skills heading optional; we should only include if there is real specific content. The posting mentions skills like communication, presentation, executive relationship-building, business acumen, etc. Could be placed under Skills. However we already have Requirements and Qualifications sections. To avoid duplication, we could put skill-related items under Requirements or Qualifications. The instruction: Prefer a few substantive sections over many thin ones. So we might combine skills into Requirements or Qualifications. But we have separate headings allowed; we can include Skills if we have content. Let's see: The posting includes "Strong communication, presentation, and executive relationship-building skills." etc. That's skill. Also "Ability to manage multiple opportunities while maintaining accurate forecasts." etc. Could be skill. We could create a Skills section with those bullet points. However we also have Requirements section that includes similar items. Might be duplication. Better to follow the headings: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Possibly also Skills if we have distinct content not covered elsewhere. But we can incorporate skill items into Requirements. Let's structure:

About the role

Intro paragraph(s) about Oracle NetSuite, role description.

Responsibilities

• ... each bullet from "What You Will Do!"

Requirements

• ... bullet list from "What We're Looking For!"

Qualifications

Disclaimer about US based roles etc.

Pay range details: Hiring Range in USD from $31.73 - $50.72 per hour; $66,000 - $105,500 per year. May be eligible for equity. Eligible for commission with an estimated pay mix of 50/50.

Oracle US offers a comprehensive benefits package which includes the following: ... (list)

But we also have Benefits section separate; maybe we should move the detailed benefits list to Benefits section, and keep Qualifications just about disclaimer and pay? However Qualifications heading is present in posting; we should keep it. The posting's "Qualifications" includes disclaimer, pay range, benefits. So we could keep Qualifications as is, containing disclaimer, pay, benefits. Then we might not need a separate Benefits section. But we also have "Why Join Netsuite" which is more like benefits/perks but not detailed. Could be omitted or put under Benefits if we want. However instruction: include a section ONLY when the posting has real, specific content for it. The "Why Join Netsuite" has specific content (sell leading platform, join world-class org, etc.) That could be considered Benefits/Perks. But we already have benefits listed in Qualifications. To avoid duplication, we could treat "Why Join Netsuite" as Benefits section, and keep Qualifications for disclaimer and pay only. However the posting explicitly labels a section "Qualifications". We should respect that heading if we include it. But we can also decide not to include Qualifications if we think it's thin? It has disclaimer, pay range, benefits details - that's substantive. So we should include Qualifications. Thus we may have Benefits section from "Why Join Netsuite". Let's extract those bullet points: - Sell the industry’s leading cloud ERP platform. - Join Oracle’s world-class sales organization with exceptional training and career development. - Work alongside experienced sales leaders, solution consultants, and enablement teams invested in your success. - Competitive compensation with uncapped earning potential. - Comprehensive benefits and opportunities for long-term career growth. - Be part of a collaborative culture where innovation, inclusion, and customer success drive everything we do. That's substantive. Now Benefits section could also include the detailed benefits list from Qualifications? But that would duplicate. Perhaps we should put the detailed list under Benefits, and keep Qualifications just about disclaimer and pay range. However the posting's Qualifications includes the benefits list; but we can reassign? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. We must keep the benefits list somewhere. If we put it under Benefits, we still preserve it. The Qualifications section would then only contain disclaimer and pay range. That's still substantive (disclaimer and pay). That's okay. Thus we will have:

About the role

Intro paragraphs.

Responsibilities

...

Requirements

...

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 $31.73 - $50.72 per hour; from: $66,000 - $105,500 per year. May be eligible for equity. Eligible for commission with an estimated pay mix of 50 / 50.

Benefits

• Sell the industry’s leading cloud ERP platform.
• Join Oracle’s world-class sales organization with exceptional training and career development.
• Work alongside experienced sales leaders, solution consultants, and enablement teams invested in your success.
• Competitive compensation with uncapped earning potential.
• Comprehensive benefits and opportunities for long-term career growth.
• Be part of a collaborative culture where innovation, inclusion, and customer success drive everything we do.

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

We also have Pay section? We already included pay range in Qualifications. But we could also create a Pay section separate. However we already have pay info in Qualifications; we could keep it there and not create Pay section to avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So we can keep pay inside Qualifications. We also have Schedule: none. Skills: we could incorporate skill items into Requirements or Qualifications. But we already have Requirements covering experience and skills. The "What We're Looking For!" includes many skill-like items. So we can keep Requirements as is. Now we need to extract bullet points exactly. Responsibilities bullets from "What You Will Do!": - Own and execute the full sales cycle for net-new logo acquisition within your assigned territory. - Generate pipeline through strategic prospecting, outbound outreach, networking, referrals, and partner collaboration. - Conduct consultative discovery to understand customers’ financial, operational, and business challenges. - Position NetSuite’s ERP, CRM, Accounting, Professional Services Automation (PSA), and ecommerce solutions by connecting technology to measurable business outcomes. - Build executive relationships with CFOs, Controllers, COOs, founders, owners, and operations leaders. - Develop compelling business cases, proposals, and presentations that demonstrate clear ROI. - Lead negotiations and successfully close complex software agreements. - Maintain accurate forecasting, account planning, and pipeline management within CRM. - Partner closely with Business Development Representatives, Solution Consultants, Marketing, and Customer Success to maximize revenue opportunities. - Consistently achieve and exceed quarterly and annual sales quotas. Note there is an exclamation after "What You Will Do!" but we ignore. Requirements bullets from "What We're Looking For!": - The ideal candidate is a motivated hunter with a proven track record of generating pipeline, winning new business, and managing complex SaaS sales cycles. - 1+ years of quota-carrying SaaS or technology sales experience. - Demonstrated success closing net-new business. - Experience managing opportunities from prospecting through contract negotiation and close. - Strong communication, presentation, and executive relationship-building skills. - Ability to manage multiple opportunities while maintaining accurate forecasts. - Experience selling ERP, accounting, CRM, financial management, PSA, ecommerce, or other business application software. - Proven ability to build self-sourced pipeline through outbound prospecting. - Success selling to finance, operations, or executive-level decision makers. - Strong business acumen with the ability to translate operational and financial challenges into technology solutions. - Experience navigating multi-stakeholder