Slackforce Senior Engineering Manager
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content accordingly.
We have:
- About Salesforce: description of company, mission, etc. Could be placed under "About the role" maybe.
- Responsibilities: bullet list under "What You Will Be Doing". That's responsibilities.
- Requirements: bullet list under "What You Should Have". That's requirements.
- Qualifications: maybe overlapping with requirements; but we can treat "What You Should Have" as Qualifications/Requirements. We need separate sections only if distinct content. The posting has "What You Should Have" which includes experience, degree, ability, technical experience, proven history, organized, performance conversations. That's qualifications/requirements.
- Skills: maybe not explicitly listed separate; could infer from responsibilities/requirements. But we should not create empty sections. If no explicit skills list, we skip Skills.
- Benefits: there is a paragraph about benefits near end: "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" mentions benefits and resources. So we have benefits content.
- Pay: not specified; they mention compensation determined by location etc but no specific pay. Should not create Pay section if not specific.
- Schedule: not specified.
Thus we will have sections: About the role (or About Salesforce), Responsibilities, Requirements (or Qualifications), Benefits.
We need to use for each heading. Use - for lists. Use
for prose.
We must not include boilerplate like accommodations, EEO, privacy statement, etc.
We must preserve all substantive information: need to include the description about Salesforce, the team, product, impact, etc. Also the responsibilities list exactly as given. Also the requirements list exactly as given. Also benefits list.
We must not invent or summarize away detail. Must keep all details.
Let's extract the substantive content.
From 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 a note about applying; maybe considered boilerplate? It's not about job; could be considered application instruction? It's a note to candidate about applying max 3 roles. Might be considered application instruction; we should remove? The instruction says remove application instructions. This is a note about applying max 3 roles; likely considered application instruction. So remove.
"Job Category Software Engineering Job Details" maybe metadata; remove.
"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. Slack is looking for an Engineering Manager on the Salesforce Integrations (Slackforce) engineering team. This team is focused on building new and innovative solutions within Slack focused on best in class first party integrations with the Salesforce platform. Our first product, Slack Sales Elevate, works to accelerate and optimize sales productivity to give sellers back 1 day every week. We are an engineering team partnered with Product, Product Marketing, Design and Data Analytics and the work we do has a top-line impact on company goals."
That's substantive about role and team.
Then "In this role, you will need to meld creative product thinking, a thirst for understanding people from a variety of backgrounds, and thoughtful use of data in order to build the best in class enterprise solutions. You’ll lead a hardworking team of frontend and backend engineers while growing out your team through recruiting efforts. We're looking for someone invested in their team's career development and that facilitates psychologically safe discussions around: project deliveries, process improvements, and mentorship. You should be well-versed in full-stack design principles and be able to give advice on code architecture and implementation."
That could be part of responsibilities or qualifications; but we already have responsibilities list later. This paragraph is more about expectations; could be part of responsibilities. We'll keep it as part of responsibilities maybe.
Then "What You Will Be Doing" list:
- Use data to make decisions about prioritization and impact, bringing a real passion for experimentation.
- Mentor and coach engineers on the team, helping them to develop into technical leaders and guiding them through the evolving skills required in an AI-assisted engineering landscape.
- Work closely with Product, Design, Data, and Marketing to conceive features that will help our users to successfully build their teams.
- Build roadmaps and long-term team vision in partnership with the Product team.
- Be accountable for driving project execution.
- Define and fulfill the engineering hiring plan for the team, including screening and interviewing.
- Anticipate future technical needs and craft plans to realize them, identifying practical ways to leverage AI to make our product and engineering workflows more effective.
- Collaborate with other engineering leaders on priorities, processes, and policies.
That's responsibilities.
Then "What You Should Have":
- You have 2+ years of engineering management experience leading productive, high-functioning teams.
- You have a bachelor's degree in Computer Science, Engineering or related field, or equivalent training, fellowship, or work experience.
- Ability to weigh several and often conflicting constraints to make rapid decisions in a multifaceted and quickly-growing company.
- You have enough technical experience to discuss architecture and product decisions with engineers, including practical knowledge of how to apply AI tools to solve real-world problems and drive efficiency.
- You have a proven history of shipping products with consistent execution.
- You are highly organized and thrive in rapid-paced environments.
- You don’t shy away from performance conversations and you recognize the relationship between objective feedback and career growth.
That's qualifications/requirements.
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. Together, we’ll bring the power of Agentforce to organizations of all sizes and deliver amazing experiences that customers love. Apply today to not only shape the future — but to redefine what’s possible — for yourself, for AI, and the world."
That's promotional; could be part of About the role? Might be considered boilerplate? It's about benefits and resources; but we already have benefits section later. Might be okay to include in About the role? But we should not duplicate. We'll keep benefits section later.
Then "Accommodations ..." remove.
Then "Please note that Salesforce uses artificial intelligence (AI) tools ..." remove (boilerplate).
Then "Please see our Candidate Privacy Statement ..." remove.
Then "Posting Statement Salesforce is an equal opportunity employer ..." remove (EEO).
Then "Know your rights: ..." remove.
Then "Recruiting, hiring, and promotion decisions ..." remove.
Then "In the United States, compensation offered will be determined by factors such as location, job level, job-related knowledge, skills, and experience. Certain roles may be eligible for incentive compensation, equity, and benefits." This is about pay but not specific; we should not create Pay section because no specific numbers. However we could include a brief note under Benefits? But instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It states compensation determined by factors etc but not specific pay. So we should not create Pay section.
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. More details about company benefits can be found at the following link: https://www.salesforcebenefits."
That's benefits; we will include Benefits section.
Thus final HTML:
About the role
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. Slack is looking for an Engineering Manager on the Salesforce Integrations (Slackforce) engineering team. This team is focused on building new and innovative solutions within Slack focused on best in class first party integrations with the Salesforce platform. Our first product, Slack Sales Elevate, works to accelerate and optimize sales productivity to give sellers back 1 day every week. We are an engineering team partnered with Product, Product Marketing, Design and Data Analytics and the work we do has a top-line impact on company goals. In this role, you will need to meld creative product thinking, a thirst for understanding people from a variety of backgrounds, and thoughtful use of data in order to build the best in class enterprise solutions. You’ll lead a hardworking team of frontend and backend engineers while growing out your team through recruiting efforts. We're looking for someone invested in their team's career development and that facilitates psychologically safe discussions around: project deliveries, process improvements, and mentorship. You should be well-versed in full-stack design principles and be able to give advice on code architecture and implementation.
Responsibilities
- Use data to make decisions about prioritization and impact, bringing a real passion for experimentation.
- Mentor and coach engineers on the team, helping them to develop into technical leaders and guiding them through the evolving skills required in an AI-assisted engineering landscape.
- Work closely with Product, Design, Data, and Marketing to conceive features that will help our users to successfully build their teams.
- Build roadmaps and long-term team vision in partnership with the Product team.
- Be accountable for driving project execution.
- Define and fulfill the engineering hiring plan for the team, including screening and interviewing.
- Anticipate future technical needs and craft plans to realize them, identifying practical ways to leverage AI to make our product and engineering workflows more effective.
- Collaborate with other engineering leaders on priorities, processes, and policies.
Requirements
- You have 2+ years of engineering management experience leading productive, high-functioning teams.
- You have a bachelor's degree in Computer Science, Engineering or related field, or equivalent training, fellowship, or work experience.
- Ability to weigh several and often conflicting constraints to make rapid decisions in a multifaceted and quickly-growing company.
- You have enough technical experience to discuss architecture and product decisions with engineers, including practical knowledge of how to apply AI tools to solve real-world problems and drive efficiency.
- for lists. Use
for prose. We must not include boilerplate like accommodations, EEO, privacy statement, etc. We must preserve all substantive information: need to include the description about Salesforce, the team, product, impact, etc. Also the responsibilities list exactly as given. Also the requirements list exactly as given. Also benefits list. We must not invent or summarize away detail. Must keep all details. Let's extract the substantive content. From 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 a note about applying; maybe considered boilerplate? It's not about job; could be considered application instruction? It's a note to candidate about applying max 3 roles. Might be considered application instruction; we should remove? The instruction says remove application instructions. This is a note about applying max 3 roles; likely considered application instruction. So remove. "Job Category Software Engineering Job Details" maybe metadata; remove. "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. Slack is looking for an Engineering Manager on the Salesforce Integrations (Slackforce) engineering team. This team is focused on building new and innovative solutions within Slack focused on best in class first party integrations with the Salesforce platform. Our first product, Slack Sales Elevate, works to accelerate and optimize sales productivity to give sellers back 1 day every week. We are an engineering team partnered with Product, Product Marketing, Design and Data Analytics and the work we do has a top-line impact on company goals." That's substantive about role and team. Then "In this role, you will need to meld creative product thinking, a thirst for understanding people from a variety of backgrounds, and thoughtful use of data in order to build the best in class enterprise solutions. You’ll lead a hardworking team of frontend and backend engineers while growing out your team through recruiting efforts. We're looking for someone invested in their team's career development and that facilitates psychologically safe discussions around: project deliveries, process improvements, and mentorship. You should be well-versed in full-stack design principles and be able to give advice on code architecture and implementation." That could be part of responsibilities or qualifications; but we already have responsibilities list later. This paragraph is more about expectations; could be part of responsibilities. We'll keep it as part of responsibilities maybe. Then "What You Will Be Doing" list: - Use data to make decisions about prioritization and impact, bringing a real passion for experimentation. - Mentor and coach engineers on the team, helping them to develop into technical leaders and guiding them through the evolving skills required in an AI-assisted engineering landscape. - Work closely with Product, Design, Data, and Marketing to conceive features that will help our users to successfully build their teams. - Build roadmaps and long-term team vision in partnership with the Product team. - Be accountable for driving project execution. - Define and fulfill the engineering hiring plan for the team, including screening and interviewing. - Anticipate future technical needs and craft plans to realize them, identifying practical ways to leverage AI to make our product and engineering workflows more effective. - Collaborate with other engineering leaders on priorities, processes, and policies. That's responsibilities. Then "What You Should Have": - You have 2+ years of engineering management experience leading productive, high-functioning teams. - You have a bachelor's degree in Computer Science, Engineering or related field, or equivalent training, fellowship, or work experience. - Ability to weigh several and often conflicting constraints to make rapid decisions in a multifaceted and quickly-growing company. - You have enough technical experience to discuss architecture and product decisions with engineers, including practical knowledge of how to apply AI tools to solve real-world problems and drive efficiency. - You have a proven history of shipping products with consistent execution. - You are highly organized and thrive in rapid-paced environments. - You don’t shy away from performance conversations and you recognize the relationship between objective feedback and career growth. That's qualifications/requirements. 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. Together, we’ll bring the power of Agentforce to organizations of all sizes and deliver amazing experiences that customers love. Apply today to not only shape the future — but to redefine what’s possible — for yourself, for AI, and the world." That's promotional; could be part of About the role? Might be considered boilerplate? It's about benefits and resources; but we already have benefits section later. Might be okay to include in About the role? But we should not duplicate. We'll keep benefits section later. Then "Accommodations ..." remove. Then "Please note that Salesforce uses artificial intelligence (AI) tools ..." remove (boilerplate). Then "Please see our Candidate Privacy Statement ..." remove. Then "Posting Statement Salesforce is an equal opportunity employer ..." remove (EEO). Then "Know your rights: ..." remove. Then "Recruiting, hiring, and promotion decisions ..." remove. Then "In the United States, compensation offered will be determined by factors such as location, job level, job-related knowledge, skills, and experience. Certain roles may be eligible for incentive compensation, equity, and benefits." This is about pay but not specific; we should not create Pay section because no specific numbers. However we could include a brief note under Benefits? But instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It states compensation determined by factors etc but not specific pay. So we should not create Pay section. 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. More details about company benefits can be found at the following link: https://www.salesforcebenefits." That's benefits; we will include Benefits section. Thus final HTML:
About the role
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. Slack is looking for an Engineering Manager on the Salesforce Integrations (Slackforce) engineering team. This team is focused on building new and innovative solutions within Slack focused on best in class first party integrations with the Salesforce platform. Our first product, Slack Sales Elevate, works to accelerate and optimize sales productivity to give sellers back 1 day every week. We are an engineering team partnered with Product, Product Marketing, Design and Data Analytics and the work we do has a top-line impact on company goals. In this role, you will need to meld creative product thinking, a thirst for understanding people from a variety of backgrounds, and thoughtful use of data in order to build the best in class enterprise solutions. You’ll lead a hardworking team of frontend and backend engineers while growing out your team through recruiting efforts. We're looking for someone invested in their team's career development and that facilitates psychologically safe discussions around: project deliveries, process improvements, and mentorship. You should be well-versed in full-stack design principles and be able to give advice on code architecture and implementation.
Responsibilities
- Use data to make decisions about prioritization and impact, bringing a real passion for experimentation.
- Mentor and coach engineers on the team, helping them to develop into technical leaders and guiding them through the evolving skills required in an AI-assisted engineering landscape.
- Work closely with Product, Design, Data, and Marketing to conceive features that will help our users to successfully build their teams.
- Build roadmaps and long-term team vision in partnership with the Product team.
- Be accountable for driving project execution.
- Define and fulfill the engineering hiring plan for the team, including screening and interviewing.
- Anticipate future technical needs and craft plans to realize them, identifying practical ways to leverage AI to make our product and engineering workflows more effective.
- Collaborate with other engineering leaders on priorities, processes, and policies.
Requirements
- You have 2+ years of engineering management experience leading productive, high-functioning teams.
- You have a bachelor's degree in Computer Science, Engineering or related field, or equivalent training, fellowship, or work experience.
- Ability to weigh several and often conflicting constraints to make rapid decisions in a multifaceted and quickly-growing company.
- You have enough technical experience to discuss architecture and product decisions with engineers, including practical knowledge of how to apply AI tools to solve real-world problems and drive efficiency.