Recruiting Project Manager (Contract)
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real, specific content. We have content for About Salesforce (company description) maybe "About the role"? The posting has "About Salesforce" which is about company, not role. Could treat as "About the role"? But they said use headings like About the role, Responsibilities, etc. We can map "About Salesforce" to "About the role"? Might be better to use "About the role" heading and put the company description there? However they said do NOT repeat the job title as a heading; they didn't forbid using About the role for company description. Usually "About the role" is a short description of the role. The posting includes "Position Overview" which is about role. So we can use "About the role" heading for Position Overview. Then "About Salesforce" could be omitted? It's company info, maybe not needed. But we could include as a separate section like "About Salesforce" but not in allowed headings list. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to stick to those headings. So we will have sections: About the role (Position Overview), Responsibilities, Requirements (maybe combine Required Skills/Experience and Other Skills/Preferred Requirements), Skills (maybe separate?), Benefits, Pay. The posting includes benefits description and salary range. So we include Benefits and Pay sections.
We must not include sections with placeholder text. We have actual content for each.
We need to use - for any list of duties/requirements/benefits. For prose use
.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out things like "To get the best candidate experience, please consider applying for a maximum of 3 roles within 12 months..." etc. Also remove "Accommodations", "Posting Statement", etc. Also remove the AI tools statement, accommodations request form, etc. Also remove the equal opportunity employer paragraph. Also remove the link to benefits? Actually benefits description includes a link; we can keep the description but maybe drop the link? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The link is part of benefits details; we could keep it as part of the benefits prose. It's not boilerplate. It's okay.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content.
About Salesforce 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."
That's company description; could be placed under "About the role"? But maybe better to have a separate "About Salesforce" heading? Not in list but could be okay. However they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but suggests those. Safer to include only those headings that have content. We have Position Overview content; we can put that under "About the role". The company description could be considered part of "About the role"? Might be a stretch but we can include it as part of that section. However the Position Overview is more specific to role. We could split: "About the role" includes Position Overview; we could also add a separate "About Salesforce" but not in allowed list; risk of being considered filler? Probably okay but to be safe, we can incorporate company description into About the role section as introductory context.
Responsibilities: list of bullet points. We need to convert each sentence into
- . Let's extract responsibilities bullet points:
- Lead end-to-end planning and execution of assigned Recruiting Transformation projects: define scope, milestones, dependencies, resourcing, and success criteria; own the project plan, schedule, issues, and risks — managing multiple concurrent projects of moderate-to-high complexity across business areas and owners.
- Build and maintain detailed project plans, timelines, and RAID logs; proactively identify and mitigate risks, and manage project intake, prioritization, and change control, ensuring scope changes are documented, assessed for impact, and approved.
- Coordinate cross-functional workstreams (SMEs, Optimization, Compliance, Enablement) and manage dependencies with other teams and business functions to keep deliverables on time, in scope, and on budget.
- Interact daily with development, support, and cross-functional business teams and global process owners to shape program plans and schedules and ensure smooth delivery of solutions and deliverables.
- Track and report project status, metrics, and health (RAG status) to stakeholders and leadership on a regular cadence.
- Own project documentation: charters, status reports, meeting notes, decision logs, and process/change-management artifacts.
- Drive clear, consistent communication across teams and stakeholders — status updates, escalations, and readouts — and support change management and enablement planning for project rollouts, including stakeholder socialization.
- Facilitate project meetings, working sessions, and reviews; drive decisions and follow-through on action items, and provide leadership to local and virtual project teams, building a collaborative, productive environment.
- Conduct post-project reviews/retrospectives to capture lessons learned, and assist in developing/delivering presentations and status readouts for leaders and senior executives.
We'll put each as
- .
Required Skills/Experience: list:
- Proven experience managing projects from initiation through close-out, including scope, schedule, risk, and quality management.
- Expert project management skills across planning, capacity planning, and methodologies (Agile, Waterfall, or hybrid) and tools.
- Familiarity with recruiting/talent acquisition processes and systems (e.g., ATS platforms, sourcing, interview lifecycle) strongly preferred; prior experience supporting or working within a Recruiting or Talent function is a plus.
- Excellent written and verbal communication skills, including active listening and sound judgment for different audiences; comfortable presenting to senior-level stakeholders and sponsors.
- Strong critical-thinking skills — able to break down ambiguous, cross-functional problems into structured plans; comfortable with ambiguity and motivated to solve complex, fast-moving problems.
- Ability to quickly build close working relationships and work effectively with virtual and global cross-functional teams of varying backgrounds and seniority.
- Strong influencing and negotiation skills, with demonstrated leadership experience on large, complex projects.
- Experience with data gathering, tracking metrics, and translating data into status insights and recommendations.
- Formal project management training/education.
Other Skills/Preferred Requirements:
- Professional project management certification (e.g., PMP, CAPM, or similar).
- This is contract position
We need to decide sections: Could combine Required Skills/Experience and Other Skills/Preferred Requirements into a single "Requirements" section, or separate "Requirements" and "Skills". The instruction list includes Requirements, Qualifications, Skills. We could put required experience under "Requirements", and certification under "Skills". Or we could have "Requirements" for required skills/experience, and "Skills" for preferred certification and contract note. However contract position is not a skill; maybe we can put it under Requirements as a note. But better to follow typical: Requirements = required skills/experience; Skills = preferred/certifications. We'll do that.
Thus:
Requirements
... required skills ...
Skills
... professional project management certification ... This is contract position ...
Benefits: The posting includes: "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."
We need to put that as - for each benefit? Could be a list. We'll list each benefit as
- . Also include the link maybe as a separate
after list.
Pay: The posting includes: "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 $117,400 - $177,600 annually. The range represents base salary only, and does not include company bonus, incentive for sales roles, equity or benefits, as applicable."
We need to output Pay section with that prose. Not a list.
Schedule: No schedule info given, so we omit Schedule section.
We also need to include About the role section (Position Overview). Let's extract Position Overview paragraph:
"We're looking for a Project Manager to lead day-to-day planning and execution of Recruiting Transformation projects — turning program-level strategy into scoped plans, milestones, and delivered outcomes, in close partnership with program leads and cross-functional stakeholders. This role requires strong project management fundamentals, excellent communication, and the ability to manage multiple moderate-to-high complexity projects across business and technical teams."
We'll put that as
under About the role.
We also might include a brief About Salesforce description? Could be omitted; but we might lose some substantive info. However the instruction says preserve ALL substantive information. The About Salesforce paragraph is substantive. If we omit it, we lose info. So we need to include it somewhere. Could we add a section "About the company"? Not in list but maybe acceptable. However they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." implies those are examples, not exclusive. So we can add other headings as needed, but better to stick to those to avoid risk. Could we incorporate the About Salesforce paragraph into About the role section as introductory context? That would preserve it. The About the role section would then contain both company description and position overview. That's okay; it's still substantive. Let's do that: About the role section includes two paragraphs: first the company description, second the position overview.
Thus:
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.
We're looking for a Project Manager to lead day-to-day planning and execution of Recruiting Transformation projects — turning program-level strategy into scoped plans, milestones, and delivered outcomes, in close partnership with program leads and cross-functional stakeholders. This role requires strong
- for any list of duties/requirements/benefits. For prose use
. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out things like "To get the best candidate experience, please consider applying for a maximum of 3 roles within 12 months..." etc. Also remove "Accommodations", "Posting Statement", etc. Also remove the AI tools statement, accommodations request form, etc. Also remove the equal opportunity employer paragraph. Also remove the link to benefits? Actually benefits description includes a link; we can keep the description but maybe drop the link? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The link is part of benefits details; we could keep it as part of the benefits prose. It's not boilerplate. It's okay. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. About Salesforce 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." That's company description; could be placed under "About the role"? But maybe better to have a separate "About Salesforce" heading? Not in list but could be okay. However they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but suggests those. Safer to include only those headings that have content. We have Position Overview content; we can put that under "About the role". The company description could be considered part of "About the role"? Might be a stretch but we can include it as part of that section. However the Position Overview is more specific to role. We could split: "About the role" includes Position Overview; we could also add a separate "About Salesforce" but not in allowed list; risk of being considered filler? Probably okay but to be safe, we can incorporate company description into About the role section as introductory context. Responsibilities: list of bullet points. We need to convert each sentence into
- . Let's extract responsibilities bullet points: - Lead end-to-end planning and execution of assigned Recruiting Transformation projects: define scope, milestones, dependencies, resourcing, and success criteria; own the project plan, schedule, issues, and risks — managing multiple concurrent projects of moderate-to-high complexity across business areas and owners. - Build and maintain detailed project plans, timelines, and RAID logs; proactively identify and mitigate risks, and manage project intake, prioritization, and change control, ensuring scope changes are documented, assessed for impact, and approved. - Coordinate cross-functional workstreams (SMEs, Optimization, Compliance, Enablement) and manage dependencies with other teams and business functions to keep deliverables on time, in scope, and on budget. - Interact daily with development, support, and cross-functional business teams and global process owners to shape program plans and schedules and ensure smooth delivery of solutions and deliverables. - Track and report project status, metrics, and health (RAG status) to stakeholders and leadership on a regular cadence. - Own project documentation: charters, status reports, meeting notes, decision logs, and process/change-management artifacts. - Drive clear, consistent communication across teams and stakeholders — status updates, escalations, and readouts — and support change management and enablement planning for project rollouts, including stakeholder socialization. - Facilitate project meetings, working sessions, and reviews; drive decisions and follow-through on action items, and provide leadership to local and virtual project teams, building a collaborative, productive environment. - Conduct post-project reviews/retrospectives to capture lessons learned, and assist in developing/delivering presentations and status readouts for leaders and senior executives. We'll put each as
- .
Required Skills/Experience: list:
- Proven experience managing projects from initiation through close-out, including scope, schedule, risk, and quality management.
- Expert project management skills across planning, capacity planning, and methodologies (Agile, Waterfall, or hybrid) and tools.
- Familiarity with recruiting/talent acquisition processes and systems (e.g., ATS platforms, sourcing, interview lifecycle) strongly preferred; prior experience supporting or working within a Recruiting or Talent function is a plus.
- Excellent written and verbal communication skills, including active listening and sound judgment for different audiences; comfortable presenting to senior-level stakeholders and sponsors.
- Strong critical-thinking skills — able to break down ambiguous, cross-functional problems into structured plans; comfortable with ambiguity and motivated to solve complex, fast-moving problems.
- Ability to quickly build close working relationships and work effectively with virtual and global cross-functional teams of varying backgrounds and seniority.
- Strong influencing and negotiation skills, with demonstrated leadership experience on large, complex projects.
- Experience with data gathering, tracking metrics, and translating data into status insights and recommendations.
- Formal project management training/education.
Other Skills/Preferred Requirements:
- Professional project management certification (e.g., PMP, CAPM, or similar).
- This is contract position
We need to decide sections: Could combine Required Skills/Experience and Other Skills/Preferred Requirements into a single "Requirements" section, or separate "Requirements" and "Skills". The instruction list includes Requirements, Qualifications, Skills. We could put required experience under "Requirements", and certification under "Skills". Or we could have "Requirements" for required skills/experience, and "Skills" for preferred certification and contract note. However contract position is not a skill; maybe we can put it under Requirements as a note. But better to follow typical: Requirements = required skills/experience; Skills = preferred/certifications. We'll do that.
Thus:
Requirements
- ... required skills ...
Skills
- ... professional project management certification ... This is contract position ...
- for each benefit? Could be a list. We'll list each benefit as
- . Also include the link maybe as a separate
after list. Pay: The posting includes: "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 $117,400 - $177,600 annually. The range represents base salary only, and does not include company bonus, incentive for sales roles, equity or benefits, as applicable." We need to output Pay section with that prose. Not a list. Schedule: No schedule info given, so we omit Schedule section. We also need to include About the role section (Position Overview). Let's extract Position Overview paragraph: "We're looking for a Project Manager to lead day-to-day planning and execution of Recruiting Transformation projects — turning program-level strategy into scoped plans, milestones, and delivered outcomes, in close partnership with program leads and cross-functional stakeholders. This role requires strong project management fundamentals, excellent communication, and the ability to manage multiple moderate-to-high complexity projects across business and technical teams." We'll put that as
under About the role. We also might include a brief About Salesforce description? Could be omitted; but we might lose some substantive info. However the instruction says preserve ALL substantive information. The About Salesforce paragraph is substantive. If we omit it, we lose info. So we need to include it somewhere. Could we add a section "About the company"? Not in list but maybe acceptable. However they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." implies those are examples, not exclusive. So we can add other headings as needed, but better to stick to those to avoid risk. Could we incorporate the About Salesforce paragraph into About the role section as introductory context? That would preserve it. The About the role section would then contain both company description and position overview. That's okay; it's still substantive. Let's do that: About the role section includes two paragraphs: first the company description, second the position overview. Thus:
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.
We're looking for a Project Manager to lead day-to-day planning and execution of Recruiting Transformation projects — turning program-level strategy into scoped plans, milestones, and delivered outcomes, in close partnership with program leads and cross-functional stakeholders. This role requires strong