Jobs · Sales · California

SAP Mid-Market Sales Executive – West Coast

Accenture · San Francisco, CA · 1 mo ago
HybridSales$87k–$140k/yrFull-time
We need to produce HTML fragment with sections: About the role? The posting includes "We Are:" description, "The Work:", "Responsibilities:", "Here’s What You Need:", "Bonus Points if:", "In addition to base pay...", compensation details, benefits, location salary ranges, etc. We must not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have real content. We have: - About the role: The "We Are:" and "The Work:" paragraphs describe role. Could be "About the role". Use

About the role

then

with combined description. - Responsibilities: There's a "Responsibilities:" list. Use

Responsibilities

then
  • each bullet. - Requirements/Qualifications: "Here’s What You Need:" includes minimum experience, education. Could be Requirements. Also "Bonus Points if:" could be Qualifications or Skills. We need to decide. We have sections: Requirements (minimum), Qualifications (bonus), Skills (maybe language, industry experience). But we should not create thin sections; prefer few substantive sections. We could combine Requirements and Qualifications into one section "Requirements" containing both minimum and bonus. Or separate if substantive. We have Pay: compensation details: base pay range per location, incentive compensation. That's substantive. So we need Pay section. Benefits: "Accenture offers a market competitive suite of benefits..." That's substantive. So Benefits section. Schedule: travel requirement 25% to 50% travel. That's schedule? Could be Schedule section. It mentions travel requirement. Could be placed under Responsibilities? But we have a Schedule heading allowed; we can include travel % there. We must not create sections with filler like "commensurate with experience". We have actual data. We must not include boilerplate like EEO, accommodation, legal statements. Remove those. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the posting that are substantive: company description, role description, responsibilities list, requirements (minimum experience, education), bonus points, compensation (base pay ranges per location, incentive compensation), benefits, travel schedule. We must not include duplicated lines. Ensure we don't repeat same info. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. Company description: "We Are: Accenture is a leading global professional services company that helps the world’s leading businesses, governments and other organizations build their digital core, optimize their operations, accelerate revenue growth and enhance citizen services—creating tangible value at speed and scale. We are a talent and innovation led company with 738,000 people serving clients in more than 120 countries. Technology is at the core of change today, and we are one of the world’s leaders in helping drive that change, with strong ecosystem relationships. We combine our strength in technology with unmatched industry experience, functional expertise and global delivery capability. There is never a typical day at Accenture, but that’s why we love it here! This is an extraordinary chance to create a rewarding career at Accenture Technology. Working in a digitally driven, innovation-led environment where you can help clients shift to the New using leading-edge technologies on some of the coolest projects you can imagine." The Work: "This is an entrepreneurial role where the best candidate will thrive on thought leadership and hands-on development of a newly established business area for SAP. As a Sales Leader, you will use your sales acumen, creativity, and analytical skills to solve clients’ most complex business problems. You will lead the end-to-end sales lifecycle — prospecting, qualification, solution shaping, and negotiation — while serving as a trusted advisor to C-suite and senior business and IT executives." We can combine these into About the role. Responsibilities list: - Lead fit/gap and other working sessions to understand client environments (SAP and non-SAP systems) and co-develop a strategy to organize data in support of AI initiatives. - Work in conjunction with pre-sales and delivery teams to ensure customer requirements are addressed and scoped properly. - Prospect for new customers and nurture existing customers to win add-on business. - Manage a prospect list and pipeline with consistent CRM hygiene across all customers, prospects, and channel opportunities. - Engage with regional SAP sales teams to align on joint pursuit strategies and partner opportunities. - Participate in company market events and collaborate with colleagues to grow product and solution knowledge. - Position requires travel to client sites and regional events as required, must be flexible to travel 25% to 50% Note: travel is part of responsibilities but could also be schedule. We'll keep it in responsibilities; but we also need Schedule section maybe. However we have travel % as schedule info. Could put under Schedule. But we already have it in responsibilities; we could move it to Schedule to avoid duplication. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. If we move it, we still preserve it. It's okay to not duplicate. So we can put travel under Schedule. Thus responsibilities list without travel bullet. Now Requirements/Qualifications: "Here’s What You Need:": - Minimum of 7 years’ experience as a direct seller and/or VP – either within the technology space or in combination with selling in a relevant industry - Minimum of 2 years’ experience with SAP or comparable (Oracle, Infor, etc.) as a seller or user. - Minimum of 2 years’ experience selling software licenses and/or subscriptions and carrying a sales target of preferably $5M or more - Bachelor's degree or equivalent (minimum 12 years) work experience. (If Associate’s Degree, must have minimum 6 years work experience) Bonus Points if: - Direct experience selling and/or delivering solutions and services – specifically S/4, BTP, Ariba, or Supply Chain solutions - You have proven track record of building a book of business and managing a robust pipeline with cross-functional collaboration across pre-sales, delivery, alliances, and marketing teams. - Experience selling to the C-suite - You have familiarity with AI-driven data strategy use cases within the SAP ecosystem. - You have strong experience in High Tech, Energy, Distribution, or any complex manufacturing industry. - Bi-lingual in either Spanish or French We could have a section "Requirements" for the minimum, and another "Qualifications" for bonus points. Or combine into "Requirements". The instruction: prefer a few substantive sections over many thin ones. Having two sections (Requirements and Qualifications) might be okay if both substantive. But we could also have "Requirements" containing both minimum and bonus points, but then we lose distinction. However we have headings allowed: Requirements, Qualifications, Skills. Could assign: - Requirements: minimum experience/education. - Qualifications: bonus points. - Skills: maybe language, industry experience? But those are already in qualifications. We could make Skills for language and industry experience. But we already have those in bonus points. Might be thin. Better: Use Requirements for minimum, Qualifications for bonus points, and maybe Skills for language/bilingual? But bilingual is already in bonus points. Given we want few sections, maybe just Requirements (including both minimum and bonus) and then Benefits, Pay, Schedule. That's four sections plus About the role. But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can omit those not needed. So we can have About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. That's six sections. We need to ensure we don't create empty sections. Now Pay: compensation details: "In addition to base pay, this Sales role is eligible for additional incentive compensation which is based on achievement toward individual sales metrics, subject to Plan terms Compensation at Accenture varies depending on a wide array of factors, which may include but are not limited to the specific office location, role, skill set, and level of experience. As required by local law, Accenture provides a reasonable range of compensation for roles that may be hired as set forth below. We anticipate this job posting will be posted until 11/08/2026. Accenture offers a market competitive suite of benefits including medical, dental, vision, life, and long-term disability coverage, a 401(k) plan, bonus opportunities, paid holidays, and paid time off. See more information on our benefits here: U.S. Employee Benefits | Accenture Role Location Annual Salary Range California $87,400 to $140,400 Colorado $87,400 to $140,400 Connecticut $87,400 to $140,400 District of Columbia $87,400 to $140,400 Illinois $87,400 to $140,400 Maine $87,400 to $140,400 Maryland $87,400 to $140,400 Massachusetts $87,400 to $140,400 Minnesota $87,400 to $140,400 New York $87,400 to $140,400 New Jersey $87,400 to $140,400 Ohio $87,400 to $140,400 Virginia $87,400 to $140,400 Washington $87,400 to $140,400" We need to preserve all that. However we must not include the posting end date? That's maybe metadata but could be considered minor; we could drop or include in a short p. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. The posting date is minor metadata; we could include in a short p under Pay or maybe omit. Better to include as a short p: "This job posting is anticipated to be posted until 11/08/2026." That's minor but we can keep. But we also have benefits paragraph duplicated: "Accenture offers a market competitive suite of benefits..." appears both in Pay section and later? Actually appears after compensation description. We'll need to avoid duplication. We'll keep benefits in Benefits section, not in Pay. Thus Pay section should contain: base pay incentive description, compensation variability statement, salary ranges per location, and maybe the posting end date as minor metadata. Benefits section: list of benefits: medical, dental, vision, life, long-term disability coverage, a 401(k) plan, bonus opportunities, paid holidays, and paid time off. Also note "See more information on our benefits here: U.S. Employee Benefits | Accenture" - we can keep as a link? But we cannot add maybe but we can keep as plain text. Schedule section: travel 25% to 50% to client sites and regional events as required. Now we need to ensure we don't include boilerplate like EEO, accommodation, legal statements. Remove those. Now craft HTML. We'll start with

    About the role

    then

    containing combined description. We need to ensure we don't repeat job title. Let's write About the role paragraph: Combine the We Are and The Work paragraphs. We'll produce something like:

    Accenture is a leading global professional services company that helps the world’s leading businesses, governments and other organizations build their digital core, optimize their operations, accelerate revenue growth and enhance citizen services—creating tangible value at speed and scale. We are a talent and innovation led company with 738,000 people serving clients in more than 120 countries. Technology is at the core of change today, and we are one of the world’s leaders in helping drive that change

Similar jobs