Sr. Analyst, Sales Operations
Salesforce · Seattle, WA · 1 mo ago
Hybrid$94k–$142k/yrFull-time
We need to output only HTML fragment, with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We must not repeat job title as heading. Remove boilerplate like cookie/navigation/legal/EEO etc. Also remove duplicated lines, application instructions. Must preserve all substantive info.
We need to parse the posting.
Let's extract sections:
- About Salesforce: description paragraph about company, mission, etc. This could be "About the role"? Actually "About Salesforce" is about company. The instruction says use
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We must not repeat job title as heading. Remove boilerplate like cookie/navigation/legal/EEO etc. Also remove duplicated lines, application instructions. Must preserve all substantive info.
We need to parse the posting.
Let's extract sections:
- About Salesforce: description paragraph about company, mission, etc. This could be "About the role"? Actually "About Salesforce" is about company. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" maybe includes description of role and company. We'll include a section "About the role" with the paragraph(s) describing the role and company.
- Responsibilities: bullet list of responsibilities.
- Required Skills/Experience: list of required skills/experience.
- Nice To Have Skills/Experience: could be considered "Skills" or "Qualifications"? We have separate sections for Skills and Qualifications. We need to decide mapping. The posting includes "Required Skills/Experience" and "Nice To Have Skills/Experience". Could treat "Required Skills/Experience" as "Requirements" or "Qualifications". The instruction says we can use sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when there is real specific content.
We have:
- Responsibilities: bullet list.
- Required Skills/Experience: bullet list.
- Nice To Have Skills/Experience: bullet list.
- Benefits: paragraph about benefits and link.
- Pay: salary range.
- Schedule: not mentioned explicitly. There's no schedule info. So we should not include Schedule section.
- Qualifications: maybe we can treat education requirement as Qualifications. The posting includes "B.S. in a quantitative discipline". That's qualification. Could be part of Requirements though. But we can separate: Qualifications: B.S. in quantitative discipline. Requirements: 4+ years experience etc. Skills: Excel, PowerPoint, communication etc. Nice to have: other skills.
We need to avoid filler like "commensurate with experience". Not present.
We must not include boilerplate like "Accommodations", "Posting Statement", "EEO", etc. Remove those.
Also remove lines like "To get the best candidate experience, please consider applying for a maximum of 3 roles within 12 months..." That's application instruction? It's a note about applying max 3 roles. Probably considered application instruction; we should remove.
Also remove "Job Category Operations Job Details". That's metadata; we can drop.
Also remove "Unleash Your Potential" paragraph? That's promotional but maybe considered benefits? It's about benefits and resources; could be part of Benefits section. It mentions benefits and resources support you to find balance and be your best, AI agents accelerate impact. That's somewhat benefits. We'll include in Benefits.
Also "Apply today to not only shape the future..." is application instruction; remove.
Also "Accommodations" etc remove.
Also "Posting Statement" etc remove.
Also "Salesforce offers a variety of benefits..." that's benefits.
Also "The typical base salary range for this position is $94,000 - $142,300 annually." That's Pay.
Now we need to format.
We'll produce:
About the role
About the role
... paragraph(s) describing role and company.
We need to combine the About Salesforce paragraph and maybe the role description: "The Sr. Analyst will be joining our Quota and Capacity Planning team, where she/he will be supporting regional Sales and Strategy team through the company’s annual quota planning cycle and throughout the year as the organization changes. This position will require developing a deep and intimate understanding of the business and forging relationships with Sales Leaders, Strategy, and cross functional teams." We'll put that in About the role. Responsibilities: list items. We need to extract responsibilities bullet points: - Develop and own concurrent data reporting projects and models to help drive insights for the regional strategy teams, based on an intimate knowledge of your support area - Advise regional teams as to impact of go to market decisions on sales teams’ quotas during the company’s annual planning cycle - Assist the Quota and Capacity Planning team in finding opportunities for increased optimization and effectiveness in our existing processes and models That's it. Required Skills/Experience bullet list: - 4+ years of work experience, ideally in Sales Operations, Sales Strategy, FP&A, or Finance, where business analysis and insights was in the DNA - B.S. in a quantitative discipline (e.g. Business, Statistics, Math, Finance, Engineering) - Power-user proficiency in Excel and ability to tell a story in PowerPoint - Excellent spoken and written communication, interpersonal, relationship-building skills - Ability to work both independently and with a team - Proven core values based on collaboration, transparency, equality, and putting the customer first - Proven analytical and problem-solving skills, along with attention to detail - Strong, team-oriented leadership skills. Able to independently identify, frame, and confront issues and make tough decisions. Nice To Have Skills/Experience bullet list: - Experience with sales coverage models, quota setting methodologies, territory alignment - Comfortable in an environment where priorities change rapidly from varying GTM decisions and requires the ability to pivot seamlessly to new projects - Exceptionally strong communicator with the ability to independently craft a full range of clear, high-impact communications with top-level company executives. - Ability to communicate in an open and authentic manner in all situations. - Ability to succeed in a collaborative, start-up paced environment which may include extended time commitments during annual quota setting season. - Ability to establish and build close working relationships. - Strong personal credibility and counseling skills. - Team-oriented planner and decision-maker. - Ability to motivate, collaborate, and work successfully in a team environment. - Capable to work well under deadlines and juggle multiple priorities. - Strong meeting management skills. - Knowledge of Claude and Snowflake with interest in developing further expertise We could split into Skills and Qualifications sections. Let's decide: Qualifications: B.S. in a quantitative discipline. Skills: Excel, PowerPoint, communication, analytical, etc. Could also include experience years. But we have many items; maybe better to have: - Requirements: 4+ years experience, etc. - Qualifications: B.S. - Skills: Excel, PowerPoint, communication, analytical, leadership, etc. - Nice to have: separate maybe as Skills? But we only have Skills heading; we could put nice-to-have under Skills as well, but maybe better to have separate "Skills" for required skills and "Nice-to-have skills" not a heading. However instruction says we can use Skills heading; we could include both required and nice-to-have under Skills, but we need to preserve all info. Could separate into two subsections? Not allowed; only headings list. Could put all under Skills, but then we lose distinction. However we could include both required and nice-to-have under Skills, but we need to keep the content. That's okay. Alternatively we could have Requirements (experience), Qualifications (education), Skills (technical and soft skills), and maybe a separate "Preferred qualifications" not in list; but we can just put nice-to-have under Skills as well. We must not create sections with filler. So we will include:About the role
...
Responsibilities
- ...
Requirements
- ...
Qualifications
- ...
Skills
- ...
Benefits
...
Pay
...
We must not include Schedule. Now we need to ensure we don't include any boilerplate. Let's craft the About the role paragraph: "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. The Sr. Analyst will be joining our Quota and Capacity Planning team, where she/he will be supporting regional Sales and Strategy team through the company’s annual quota planning cycle and throughout the year as the organization changes. This position will require developing a deep and intimate understanding of the business and forging relationships with Sales Leaders, Strategy, and cross functional teams." That seems fine. Now Responsibilities list as above. Requirements list: 4+ years of work experience, ideally in Sales Operations, Sales Strategy, FP&A, or Finance, where business analysis and insights was in the DNA. Also maybe "Ability to work both independently and with a team" etc. But those are skills. We'll keep requirements as experience only? But we could include also "Proven core values based on collaboration, transparency, equality, and putting the customer first" etc. However those are more like skills/values. To avoid thin sections, we could combine experience and core values under Requirements. But we have many items; maybe better to put all required bullet points under Requirements, and then Skills for technical proficiency etc. However the instruction says we can have Requirements and Qualifications and Skills separate. We need to decide. Let's map: Requirements: 4+ years of work experience, ideally in Sales Operations, Sales Strategy, FP&A, or Finance, where business analysis and insights was in the DNA. Qualifications: B.S. in a quantitative discipline (e.g. Business, Statistics, Math, Finance, Engineering). Skills: Power-user proficiency in Excel and ability to tell a story in PowerPoint; Excellent spoken and written communication, interpersonal, relationship-building skills; Ability to work both independently and with a team; Proven core values based on collaboration, transparency, equality, and putting the customer first; Proven analytical and problem-solving skills, along with attention to detail; Strong, team-oriented leadership skills. Able to independently identify, frame, and confront issues and make tough decisions. Nice-to-have: we could also include under Skills as additional bullet points, maybe under a subheading? Not allowed. Could add them to Skills as well. Thus Skills will contain both required soft skills and nice-to-have. But we must not duplicate content. We'll list all. Now Benefits paragraph: combine the promotional paragraph about Unleash Your Potential and the benefits list. We need to preserve all substantive info: "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. Together, we’ll bring the power of Agentforce to organizations of all sizes and deliver amazing experiences that customers love." plus "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. More details about company benefits can be found at the following link: https://www.salesforcebenefits.com." Also "At Salesforce, we believe in equitable compensation practices that reflect the dynamic nature of labor markets across various regions." That's more about compensation; maybe part of Pay. We'll include Benefits paragraph with the above. Pay