Jobs · Sales

Senior Sales Consultant

Oracle · United States · 1 mo ago
RemoteRemoteSales$44.38–$80.29/hrFull-time
We need to output HTML fragment with sections: About the role? The job description includes a paragraph at top: "Job Description You will work cross-functionally..." That's basically about the role. Then Responsibilities with sub-sections: Customer Engagement & Relationship Building, Strategic Sales Support, Continuous Learning & Career Development. Then Qualifications with sub-sections: Technical Skill Set, Domain Knowledge, Communication & Influence. Also there is a Qualifications Disclaimer (should be removed as boilerplate? It's about immunization etc. It's likely boilerplate; we should remove. Also pay and benefits info: they gave range and benefit info. So we need Pay and Benefits sections. Also maybe Schedule? Not present. So we include Pay and Benefits sections. We must not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to map content to appropriate headings. The posting has "Job Description" (we can treat as About the role). Then "Responsibilities" heading. Then "Qualifications" heading. Within Qualifications there are sub-sections but we can keep as paragraphs or lists. Also there is a "Qualifications Disclaimer" which we drop. Then there is pay and benefits info: we need Pay and Benefits sections. We should not create sections with filler. So we will have:

About the role

... (the description paragraph)

Responsibilities

then we need to list responsibilities. The responsibilities have subheadings: Customer Engagement & Relationship Building, Strategic Sales Support, Continuous Learning & Career Development. We could either make each as

but spec only says use

for section headings. It didn't forbid other headings, but we should follow spec: 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, but to be safe we can just use
  • for list items, maybe grouping under responsibilities with paragraphs. Could also embed subheadings as but not required. Simpler: produce
    • for each responsibility bullet. However the responsibilities are described in paragraphs with bold headings. We could break them into list items each starting with the bold heading. That preserves info. Similarly Qualifications: we have Technical Skill Set, Domain Knowledge, Communication & Influence. We'll produce list items. Pay: we have hiring range: $44.38 - $80.29 per hour; $92,300 - $167,000 per year. May be eligible for equity. Eligible for commission with estimated pay mix of 65/35 - 80/20. Benefits: list of benefits. We should not include boilerplate like "Range and benefit information provided in this posting are specific to the stated locations only US:" maybe we keep as part of Pay section? It's substantive. We'll include. We must not include application instructions, EEO, etc. Now produce HTML. Let's craft About the role paragraph: The initial two sentences appear twice? Actually the job description paragraph repeats: "You will work cross-functionally with sales, product development, and engineering teams to ensure our solutions are technically sound, market-relevant, and aligned with customer needs. Your ability to translate complex architecture into compelling, real-world solutions—paired with strong communication and presentation skills—will be instrumental in winning new business and building lasting, high-impact customer relationships." It appears twice (once under Job Description, once under Responsibilities). We should include only once. Thus About the role: that paragraph. Now Responsibilities: we need to capture all bullet points under the three subheadings. Let's extract: Customer Engagement & Relationship Building: - Act as a trusted advisor and technical thought leader for Oracle customers - Build and nurture strong relationships by understanding clients’ business challenges and strategic goals - Understand the needs and pains of the customer and then link them to a set of products/solutions provided by Oracle - Lead technical presentations, workshops, and strategic discussions that highlight the value of Oracle ‘sAI-native Cloud Applications powered by Oracle Cloud Infrastructure (OCI) - Simplify complex technical concepts into clear, business-relevant insights for diverse audiences - Respond to RFx’s and security questionnaires, with respect to product/solution information as needed. Strategic Sales Support: - Collaborate with sales teams to craft and execute strategies for engaging key accounts - Provide deep technical expertise and credibility throughout high-impact sales cycles - Qualify opportunities and design tailored presentations and demonstrations that showcase solutions that address specific customer needs - Contribute to compelling proposals, demos, and presentations that drive business outcomes Continuous Learning & Career Development: - Embrace a fast-paced, innovative-driven environment with continuous learning opportunities - Maintain awareness of relevant competitive Enterprise Applications products and technologies - Stay ahead of Oracle’s quarterly cloud innovations and expand your technical expertise across: - Oracle SaaS: ERP, SCM, EPM, and HCM—architecture, security, extensibility, integration, analytics - Oracle PaaS/OCI: Databases, development tools, integration platforms, analytics, identity management, Advanced Tech: Agentic AI, ML, OCI - Internal Enablement & Knowledge Sharing: - Mentor and educate internal teams across sales, marketing, and technical functions on Oracle’s latest technologies and capabilities - Create and deliver impactful training sessions and enablement materials - Championship of a culture of innovation, collaboration, and continuous improvement within the organization Note: The last bullet includes sub-bullets; we can flatten. Now Qualifications: Technical Skill Set: - Proficient in web and integration technologies: HTML, JavaScript, SQL, REST, SOAP - Understanding of security and infrastructure: WAF, SIEM, networking fundamentals, encryption fundamentals - Familiarity with relational databases, object-oriented programming, and middleware technologies - Experience with cloud-native architectures and platform services (PaaS) is a plus - Experience or familiarity with building Agentic Applications is a plus Domain Knowledge: - Strong understanding of enterprise business processes in ERP, SCM, EPM, and H (typo: HCM? It says H but likely HCM) - Experience with State and Local, Higher Education, Utilities, Oil Mining & Gas, and/or Engineering & Constructions is a plus, but not required Communication & Influence: - Skilled in delivering technical presentations, demos, and architecture discussions - Able to translate technical capabilities into business value for both technical and non-technical stakeholders Now Pay: - Hiring Range in USD from $44.38 - $80.29 per hour; from: $92,300 - $167,000 per year. - May be eligible for equity. - Eligible for commission with an estimated pay mix of 65/35 - 80/20. - 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. Benefits: - 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 should not include the line "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 instruction; drop. Also drop "Career Level - IC3" maybe not needed; it's metadata but could be included as a short paragraph? It's not a heading; we could include as a short paragraph under About the role? But spec says do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

      or drop it. Career Level is minor metadata; we could include as a short p after About the role? But it's not essential; we could drop. Safer to drop. Also drop "About Us" section? It's boilerplate? It's descriptive about Oracle; could be considered substantive? It's marketing fluff but still part of job description. The spec says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Us" is not explicitly prohibited; but it's generic marketing. Might be considered boilerplate? Not sure. Safer to keep? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The About Us paragraph is substantive? It's generic but still part of posting. I'd keep it as a section maybe "About Oracle" but not a required heading. Since we only have prescribed headings list, we could put it under About the role? But that would mix. Better to add a separate section? Not in list. Could add as

      after About the role before Responsibilities. It's not a heading, just a paragraph. That seems okay. Thus final HTML:

      About the role

      You will work cross-functionally with sales, product development, and engineering teams to ensure our solutions are technically sound, market-relevant, and aligned with customer needs. Your ability to translate complex architecture into compelling, real-world solutions—paired with strong communication and presentation skills—will be instrumental in winning new business and building lasting, high-impact customer relationships.

      Only Oracle brings together the data, infrastructure, applications, and expertise to power everything from industry innovations to life-saving care. And with AI embedded across our products and services, we help customers turn that promise into a better future for all. Discover your potential at a company leading the way in AI and cloud solutions that impact billions of lives. True innovation starts when everyone is empowered to contribute. That’s why we’re committed to growing a workforce that promotes opportunities for all with competitive benefits that support our people with flexible medical, life insurance, and retirement options. We also encourage employees to give back to their communities through our volunteer programs. We’re committed to including people with disabilities at all stages of the employment process. If you require accessibility assistance or accommodation for a disability at any point, let us know by emailing accommodation-request_mb@oracle.com or by calling 1-888-404-2494 in the United States.

      But note the accommodation request line is part of EEO/accessibility; might be considered boilerplate? It's about accommodation request; could be considered EEO-related. The spec says remove EEO/equal-opportunity/scam-warning boilerplate. This is accommodation request, which is related to disability accommodation; might be considered EEO. Safer to drop that paragraph. Also the line about Oracle being an Equal Employment Opportunity Employer etc is definitely

Similar jobs

Senior Sales Consultant

Terumo Blood and Cell TechnologiesLakewood, CO· 1 wk ago
Sales$127k–$158k/yrapply on careers.terumobct.com

Senior Sales Consultant

La-Z-Boy IncorporatedNewnan, GA· 2 wk ago
Business Development$18/hrapply on lazboy.wd1.myworkdayjobs.com

Senior Sales Consultant

La-Z-Boy IncorporatedKnoxville, TN· 3 wk ago
Business Development$18/hrapply on lazboy.wd1.myworkdayjobs.com

Senior Sales Consultant

Holiday Inn Club VacationsMyrtle Beach, SC· 2 mo ago
Business Developmentapply on recruiting.ultipro.com