Jobs · Virginia

Named Account Executive, Enterprise Non-Profit (Mid Atlantic/Chicago)

Salesforce · McLean, VA · 1 mo ago
Hybrid$123k–$165k/yrFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "To get the best candidate experience..." line (application advice). Remove "Accommodations" etc? That's legal/EEO? It's about accommodations request form; likely considered boilerplate/legal; remove. Also remove "Posting Statement" etc. Also remove "Apply today" etc. Keep substantive content: About Salesforce, About Salesforce.org, About The Role, Your Impact (list of duties), Your Experience (list of requirements), Unleash Your Potential (benefits?), Pay info (salary range). Also maybe "Benefits" from later paragraph: "Salesforce offers a variety of benefits...". Also "Accommodations" removed. Also "Your recruiter can share more about the specific salary range". Keep pay info. We need to map content to sections. Headings: - About the role: could be "About The Role" paragraph. - Responsibilities: list of duties from "Your Impact" bullet list (the long list). Also maybe some from earlier "Job Description" paragraph? But we should include duties. - Requirements: maybe "Your Experience" list (minimum 7-10 years etc). Also maybe "Financial Acumen" etc. - Qualifications: maybe overlapping with Requirements; but we can combine? The instruction: prefer few substantive sections over many thin ones. Could combine Requirements and Qualifications into one? But we need to follow headings list; we can include only those with content. Could include Requirements and Qualifications both if they have distinct content. Let's see: "Your Experience" includes experience, skills, abilities. That could be Requirements. Qualifications maybe similar; but we could treat "Your Experience" as Requirements, and maybe "Skills" as separate? There's also "Solid business acumen around forecasting and customer management" etc. Might be skills. Better to have sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. We need to avoid empty sections. Let's extract: About the role: The paragraph starting "About The Role As an established Strategic Account Executive..." includes description. Responsibilities: The bullet list under "Your Impact". Also maybe earlier "Job Description: As a Strategic Account Executive..." but that's similar. We'll use the bullet list. Requirements: The list under "Your Experience": Minimum of 7-10 years..., Outstanding communication..., Willingness..., Strong problem-solving..., You've built global engagement..., You have experience collaborating..., Financial Acumen, Solid career longevity..., Understands what an account plan..., Solid business acumen..., Self-motivated... Skills: Could extract specific skills: Outstanding communication and interpersonal skills, Strong problem-solving and negotiation abilities, Financial Acumen, Solid business acumen around forecasting and customer management, Storytelling skills (mentioned earlier), Ability to travel, etc. But we might just treat Requirements as includes skills; but we need a Skills section if we have distinct content. Could combine Requirements and Skills into one? But instruction: prefer few substantive sections over many thin ones. So maybe we just have About the role, Responsibilities, Requirements (which includes experience and skills), Benefits, Pay. That's 5 sections. Benefits: The paragraph about benefits: "Salesforce offers a variety of benefits to help you live well including: time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), and an employee stock purchasing program." Also earlier "Unleash Your Potential When you join Salesforce, you’ll be limitless..." mentions benefits and resources support you to find balance and be your best, and our AI agents accelerate your impact. That's more generic; but we can include the specific benefits list. Pay: The salary range paragraphs. Schedule: No info about schedule (like full-time, hours). Not present, so omit Schedule. Now need to format: Use

for section headings. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from those sections. Let's extract exact text. About the role paragraph: "About The Role As an established Strategic Account Executive, you know how to navigate through large organizations. You’re knowledgeable about your clients’ specific challenges and business objectives. You understand how to align your software offering to build a custom solution that your clients can’t live without. You understand what it means to sell a value based solution and engage/create alignment amongst Executives in the C-Suite, IT, and the Mission. Your storytelling skills are unmatched so presenting across multiple departments won’t be a problem for you. You excel in dynamic environments so shifting gears at a moment's notice and providing excellent customer service is what you consistently deliver." We need to keep that as prose

    . Responsibilities: The bullet list under "Your Impact". Let's copy each line exactly as given, preserving punctuation. Your Impact Success will be measured by overall performance in expanding existing/new accounts, with a keen emphasis on driving true Digital Transformation, all while delivering an exceptional customer experience Develop an in-depth understanding of Salesforce products and solutions. Act as the primary point of contact, ensuring that client inquiries and concerns are addressed promptly. Stay informed about industry trends and competitive offerings. Develop key customer stakeholder relationships and drive customer satisfaction Understand the challenges our customers are working to solve for and develop a strong pojnt of view as to how we can partner to help Develop and drive the overall long-term strategy for the account, aligned to customer business objectives Coordinate internal Salesforce resources to meet customer business needs Perform account planning at assigned accounts, coordinating with Prime and Cloud sales resources to ensure strategic alignment Share Salesforce value proposition for existing and/or new customers Keep clients informed about new product features, updates, and enhancements relevant to their needs. Identify and drive growth opportunities within existing accounts and work towards expanding Salesforce services. Address and resolve client issues in a timely and efficient manner. Utilize data analysis to pinpoint areas for improvement and make data-driven recommendations. Note there is a typo "pojnt". We must preserve as is. We need to wrap each as

  • . Also the first line "Success will be measured..." is a sentence; it's part of responsibilities. So include as li. Now Requirements: The list under "Your Experience". Let's extract each bullet. Your Experience Minimum of 7-10 years of full cycle SaaS closing experience Outstanding communication and interpersonal skills. Willingness and ability to travel to client locations as required. Strong problem-solving and negotiation abilities. You've built global engagement across multiple lines of business and broadened product support within an organization You have experience (and should enjoy!) collaborating with internal team members like Solutions Engineers and Customer Success Managers, Product Managers, and Co-Prime teammates Financial Acumen Solid career longevity and track record of success Understands what an account plan/mutual close plan is and how it leads to success Solid business acumen around forecasting and customer management Self-motivated with a commitment to achieving and exceeding sales targets. We need to preserve each as
  • . Note some lines have periods, some not. Keep as is. Now Benefits: The paragraph: "Salesforce offers a variety of benefits to help you live well including: time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), and an employee stock purchasing program." Also maybe earlier "Unleash Your Potential When you join Salesforce, you’ll be limitless in all areas of your life. Our benefits and resources support you to find balance and be your best, and our AI agents accelerate your impact so you can do your best." That's also benefits/prose. We could combine into a

    for benefits description and then a

      for list. But we must not invent. We'll include both sentences as prose then list. But we need to ensure we don't duplicate. The earlier sentence about benefits and resources is generic; still substantive. We'll include. Thus Benefits section:

      Benefits

      then

      Unleash Your Potential When you join Salesforce, you’ll be limitless in all areas of your life. Our benefits and resources support you to find balance and be your best, and our AI agents accelerate your impact so you can do your best.

      then

      Salesforce offers a variety of benefits to help you live well including: time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), and an employee stock purchasing program.

      Could also make a list but it's already a sentence with colon list; we could keep as

      . The instruction: Use

      • for any list of duties/requirements/benefits. The benefits list is a list; we could turn into
        • items. But the sentence includes colon then list separated by commas. Safer to keep as

          because it's not explicitly bullet list. However instruction says use

          • for any list of duties/requirements/benefits. The benefits are a list; we could split into items. But we must preserve ALL substantive information; splitting into items still preserves. Let's do that: create
            • time off programs
            • medical
            • dental
            • vision
            • mental health support
            • paid parental leave
            • life and disability insurance
            • 401(k)
            • employee stock purchasing program
            . Also keep the introductory sentence maybe as

            . That seems fine. Now Pay: The salary range paragraphs. We need to preserve all detail. The text: "At Salesforce, we believe in equitable compensation practices that reflect the dynamic nature of labor markets across various regions. The typical base salary range for this position is $123,200 - $164,850 annually There is a different range applicable to specific work locations. In California and New York, and select cities in the metropolitan areas of Boston, Chicago, Seattle, and Washington DC, the base pay range for this role in those locations is $135,300 - $181,000 per year. Your recruiter can share more about the specific salary range for the job location during the hiring process. The range represents base salary only, and does not include company bonus, incentive for sales roles, equity or benefits, as applicable." We need to keep as prose

            . Possibly split into multiple

            sentences but okay. Now we must not include any boilerplate like "Accommodations", "Posting Statement", "EEO", etc. Also remove the line "To get the best candidate experience, please consider applying for a maximum of 3 roles within 12 months to ensure you are not duplicating efforts." Also remove "Job Category Sales". Also remove "Job Details About Salesforce". Also remove "About Salesforce" paragraph? That's substantive about company; maybe we could include as "About Salesforce" but not a required heading; we could include under About the role? But we already have About the role. The "About Salesforce" paragraph at start is generic company description; could be considered part of About the role? But we already have About the role heading; we could add a preceding

            about Salesforce as part of About the role? However the instruction: Use

            for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should only use those headings when we have content. Could we add an

            About Salesforce? Not in list

Similar jobs