Enterprise Corporate Sales Account Executive

We need to produce HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate like cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove repeated "About Salesforce" paragraphs? We need to keep substantive info about role: "ECS Enterprise Account Executive" description, "Your Impact", "Your Qualifications", list of attributes, maybe "Accommodations" (but that's boilerplate? It's about disability accommodation request; might be considered boilerplate but it's specific? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Accommodations request form might be considered part of application instructions? It's about requesting accommodation; could be considered boilerplate but it's a specific instruction. However they said remove application instructions. The accommodations request is an instruction for applicants needing accommodation; likely considered application instruction, so remove. Also remove "Posting Statement" etc. Also remove duplicated lines. We need to extract substantive content: About Salesforce (multiple repetitions) but we can keep a concise description? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep all substantive info, but we can deduplicate? It says remove duplicated lines. So we should keep unique substantive content, not repeat same paragraphs. Let's parse the posting: - Intro: "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." That's application instruction; remove. - "Job Category Sales" maybe metadata; could be minor metadata; fold into short p or drop. Likely drop. - "Job Details About Salesforce Salesforce is the #1 AI CRM, where humans with agents drive customer success together. Here, ambition meets action. Tech meets trust. And innovation isn’t a buzzword — it’s a way of life. The world of work as we know it is changing and we're looking for Trailblazers who are passionate about bettering business and the world through AI, driving innovation, and keeping Salesforce's core values at the heart of it all. Ready to level-up your career at the company leading workforce transformation in the agentic era? You’re in the right place! Agentforce is the future of AI, and you are the future of Salesforce. Applications for this position will be accepted on an ongoing basis." That's about Salesforce; we can keep as "About Salesforce" maybe under "About the role"? Actually "About the role" heading is for role description. But we have "About Salesforce" repeated multiple times. We could treat that as "About the company" but not a required heading. The allowed headings are specific list; we should only use those headings if content matches. There's no explicit "About the company" heading. Could we put under "About the role"? Might be okay but it's about company not role. However we need to preserve substantive info; we could include it as a

without heading? 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 says use those for section headings. It says "include a section ONLY when the posting has real, specific content for it". So we can create sections with those headings if content matches. For generic company description, maybe we can put under "About the role" as it's about the role context. Or we could just include as a

without heading? The instruction says use those headings for section headings; doesn't forbid other headings but likely they expect only those headings. Safer to wrap company description in a

without heading? But then we wouldn't be using heading; still okay? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use h3 for those headings if we have them. It doesn't say we cannot have other headings, but to follow the pattern, we likely should only use those headings. So we need to map content to those headings. Let's identify content: - About the role: description of role: "ECS Enterprise Account Executive The Salesforce ECS AE is a seller supporting an enterprise account base focused on Customer 360 solutions that empower organizations of all sizes to connect with their customers across every touchpoint. We're driven by a deep understanding of our customers' needs — because we're committed to their success too. No other CRM company invests in product innovation the way we do, giving our clients access to truly innovative technology. As part of Salesforce, pioneers in cloud computing, we offer an outstanding experience to our customers and employees." Also "Your Impact You will work closely with current customers and prospective customers as a trusted advisor to deeply understand their outstanding company challenges and goals. You will advise customers on the Salesforce Platform to voice support for solutions that will help them reach their business goals and blaze new trails within their organizations. You will chip in to our business growth in a fast-paced, collaborative, and fun atmosphere, as a valued member of our Ohana." That could be Responsibilities. - Responsibilities: list of duties: maybe bullet points from "Your Impact". Could be turned into

• . - Requirements: maybe "Depending on the segment, the years of experience and abilities needed to be successful will vary from 5-10+ yrs of quota-carrying software or technology sales and account management experience. In addition, a bachelor's degree is strongly preferred." - Qualifications: maybe the list of attributes: "Consultative selling experience Prospecting Skills Strong Communication Skills Has a driven spirit Can collaborate and influence in a “win as a team” environment Resourceful Coachable Has a drive for results Is a trusted advisor to customers and colleagues Engagement Strong eye for business Can articulate value Solution Selling Ability Strong Discovery Skills Objection Handling Skills Planning and Closing Skills" These could be Skills or Qualifications. The headings list includes both Qualifications and Skills. We need to decide where to put what. The posting has "Your Qualifications" then list of attributes. So we can put that under Qualifications. Skills maybe not separately listed; but we could treat the attributes as Skills. However we already used Qualifications for that list. Could also have Skills empty; better to omit Skills section if no specific content. - Benefits: there is a section later: "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: "Posting Statement ... Learn more about Equality at www.equality.com and explore our company benefits at www.salesforcebenefits.com." Also later: "Salesforce offers a variety of benefits..." So we have benefits content. - Pay: there is salary range info: "The typical base salary range for this position is $77,550 - $133,100 annually. Your recruiter can share more about the specific salary range for the job location during the hiring process. 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 $85,300 - $146,500 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." - Schedule: not mentioned; no schedule info. So omit Schedule section. - Also there is "Accommodations" but we consider application instruction; remove. - Also "Posting Statement" about equality etc; that's EEO boilerplate; remove. - Also "Unleash Your Potential" paragraph about benefits and resources; could be considered benefits? It mentions benefits and resources support you to find balance and be your best, and our AI agents accelerate your impact. That's somewhat fluff; but it's substantive? Might be considered benefits but it's vague. Could include under Benefits as additional prose. We must not invent or summarize away detail; we need to preserve all substantive info. So we need to include all the substantive paragraphs we identified, not omit any detail. However we can combine similar content but must not lose detail. We need to be careful not to omit any specifics like years of experience, bachelor's degree, list of attributes, salary ranges, benefits list. We also need to remove duplicated lines: there are multiple repetitions of "About Salesforce" paragraphs. We should keep only one copy of each unique paragraph. Let's extract unique substantive paragraphs: 1. Intro about Salesforce being #1 AI CRM etc (first paragraph). Actually there are multiple similar paragraphs: "About Salesforce Salesforce is the #1 AI CRM, where humans with agents drive customer success together..." then later "About Salesforce We’re Salesforce, the Customer Company, inspiring the future of business with AI+ Data +CRM." then later "About Salesforce We’re Salesforce, the Customer Company, encouraging the future of business with AI+ Data +CRM." These are similar but not identical; each has slight variations. We should keep all unique ones? The instruction says remove duplicated lines. These are not exact duplicates but similar; they are repetitive content. Might be considered duplicated lines? They are not identical but convey same idea. Safer to keep one representative? But we risk losing detail. However the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." If we keep only one, we might be summarizing away detail (the variations). But the variations are minor; still they are substantive? Might be considered boilerplate. The repeated "About Salesforce" sections are likely boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So duplicated lines should be removed. So we should keep only one instance of the "About Salesforce" description. Which one? Choose the most detailed? The first one mentions #1 AI CRM, agents, ambition meets action, etc. The second mentions inspiring future of business with AI+Data+CRM, core values, Trailblazer, etc. The third similar to second. The first seems more vivid. We'll keep the first. 2. Role description: "ECS Enterprise Account Executive The Salesforce ECS AE is a seller supporting an enterprise account base focused on Customer 360 solutions that empower organizations of all sizes to connect with their customers across every touchpoint. We're driven by a deep understanding of our customers' needs — because we're committed to their success too. No other CRM company invests in product innovation the way we do, giving our clients access to truly innovative technology. As part of Salesforce, pioneers in cloud computing, we offer an outstanding experience to our customers and employees." 3. Your Impact paragraph: "Your Impact You will work closely with current customers and prospective customers as a trusted advisor to deeply understand their outstanding company challenges and goals. You will advise customers on the Salesforce Platform to voice support for solutions that will help them reach their business goals and blaze new trails within their organizations. You will chip in to our business growth in a fast-paced, collaborative, and fun atmosphere, as a valued member of our Ohana." 4. Your Qualifications paragraph: "Depending on the segment, the years of experience and abilities needed to be successful will vary from 5-10+ yrs of quota-carrying software or technology sales and account management experience. In addition, a bachelor's degree is strongly preferred." 5. List of attributes: "Consultative selling experienceProspecting SkillsStrong Communication SkillsHas a