Manager, ServiceNow Solutions
for each heading. Use - for any list of duties/requirements/benefits, and
for prose. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Preserve all substantive info. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". So we need to extract sections.
Let's parse the job description.
We have:
- Job Description Summary: description of role.
- Job Description: includes hybrid workstyle, note about work visa not eligible.
- Qualifications Required: list of required qualifications.
- Preferred Experience: list of preferred.
- Responsibilities: list of responsibilities with subheadings.
- Success Measures: list of success measures.
- Education: High School (HS) (Required)
- Work Experience: General Experience - 3 to 6 years (but earlier required 7+ years? There's inconsistency; but we preserve as given.)
- Certifications: none listed.
- Travel: Less than 25%
- Workstyle: Hybrid
- The total compensation for this position includes base salary or wages, and may include components such as additional compensation (cash or equity), discretionary bonuses, or commissions. This position is eligible for a benefits package that may include medical, dental, and vision; life insurance; critical illness insurance and accident insurance; disability benefits; retirement savings; paid time off (including vacation, holidays, and sick leave); and parental leave. Eligibility for benefits and specific offerings may vary based on position and employment status. To view more details of the benefits offered, visit Myrjbenefits.com.
- Then some culture statements.
We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide what goes where.
- About the role: likely the summary and description (first paragraphs). Could include hybrid workstyle note.
- Responsibilities: list of responsibilities (People Leadership & Talent Development etc.)
- Requirements: maybe required qualifications (the "Qualifications Required:" list). Also Education, Work Experience, Travel, Workstyle? Might be considered Requirements.
- Qualifications: maybe the "Preferred Experience" list? Or we could treat "Qualifications" as required qualifications, and "Skills" as preferred? But we have both sections. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). So we need to allocate content accordingly.
We have required qualifications list: "7+ years of experience in technology delivery, business analysis, application development, or platform solutions; 3+ years of experience leading technical, analyst, or delivery-focused teams; Experience managing operational support and project-based delivery within Agile environments; Strong leadership, communication, stakeholder management, and organizational skills; Demonstrated ability to balance multiple priorities and drive execution across complex initiatives; Experience with resource planning, workload management, and delivery oversight". That's required.
Preferred Experience list: "Experience with the ServiceNow platform and ServiceNow application delivery; Knowledge of Agile, Scrum, Kanban, and Software Development Life Cycle (SDLC) methodologies; Experience supporting enterprise platforms and large-scale technology initiatives; ServiceNow, Agile, Scrum, PMP, or related certifications; Experience leading teams through organizational growth, transformation, or delivery model changes". That's preferred.
We also have Education: High School (HS) (Required). Work Experience: General Experience - 3 to 6 years (contradicts required but we keep). Travel: Less than 25%. Workstyle: Hybrid.
We could put Education, Work Experience, Travel, Workstyle under Requirements or Qualifications. The instruction: "Prefer a few substantive sections over many thin ones." So we might combine.
We need to include Benefits section: we have benefits description.
Pay section: we have compensation description: base salary, additional compensation, discretionary bonuses, commissions. That's pay.
Schedule: we have hybrid workstyle: expected to work from office at least three days per week, including either Monday or Friday. That's schedule.
Thus we can create sections:
- About the role: summary + job description paragraph (including hybrid note? maybe schedule separate). But we can include hybrid note in About the role? However schedule separate. We'll put About the role: the role summary (first two paragraphs) maybe excluding schedule note.
- Responsibilities: list of responsibilities (the bullet points under Responsibilities heading). We'll format as
- .
- Requirements: could include required qualifications list plus Education, Work Experience, Travel, Workstyle? But Workstyle is schedule; maybe schedule separate. We'll keep Requirements as required qualifications + Education + Work Experience + Travel.
- Qualifications: maybe preferred qualifications list.
- Skills: maybe we could list skills from required/preferred? But we already have qualifications. Could combine? But we need to output sections only if real content. We have content for Skills? Could extract skills like leadership, communication, stakeholder management, organizational skills, resource planning, etc. But those are already in qualifications. Might be redundant. Perhaps we can omit Skills if no distinct content. But we need to decide.
The instruction: "Prefer a few substantive sections over many thin ones." So we could omit Skills if not distinct. But we have headings list as examples, not mandatory. So we can include only sections with real content.
Thus we will include: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
We need to ensure we don't include filler like "commensurate with experience". Not present.
Now we need to format.
We'll produce:
About the role
... (summary paragraphs)
Responsibilities
- People Leadership & Talent Development: Lead, coach, mentor, and develop a team of ServiceNow Business Analysts and Developers
... etc.
But we need to preserve the subheadings inside responsibilities? The responsibilities list includes headings like "People Leadership & Talent Development", "Demand, Capacity & Resource Management", etc. We could keep them as part of the li text.
Thus each li: "People Leadership & Talent Development: Lead, coach, mentor, and develop a team of ServiceNow Business Analysts and Developers". But we cannot use ? Not prohibited. We can just include plain text.
We'll keep as: "People Leadership & Talent Development – Lead, coach, mentor, and develop a team of ServiceNow Business Analysts and Developers". Use dash.
Now Requirements section: include required qualifications list (the bullet points). Also Education, Work Experience, Travel.
We'll format as - each.
Qualifications section: preferred experience list.
Benefits section: description of benefits.
Pay section: compensation description.
Schedule section: hybrid workstyle expectation.
Now we need to ensure we don't include boilerplate like "Please note: This role is not eligible for Work Visa sponsorship, either currently or in the future." That's substantive? It's a note about visa sponsorship. Should we keep? It's substantive info. It's not boilerplate? It's a specific condition. We could include in About the role or Requirements. Probably include in About the role as a note.
Also "Raymond James’ work environment is designed to reinforce our values-based culture while supporting the competitiveness, profitability, and long-term growth of our firm." That's fluff but maybe substantive? It's generic. Might be considered boilerplate? It's about work environment. Could be considered fluff. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those. It's a values statement. Might be okay to keep but could be considered filler. I'd keep it in About the role.
Also the success measures section: "Success Measures The Manager, ServiceNow Solutions Will Be Successful By ..." That's substantive; could be part of Responsibilities or a separate section? Not in our list headings. Could incorporate into Responsibilities or About the role. But we have no heading for Success Measures. We could add a section "Success Measures" but not in allowed headings list? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings only. So we should not create other headings like Success Measures. We can embed that content under Responsibilities or About the role. Probably under Responsibilities as part of success measures.
Thus we will incorporate success measures into Responsibilities section as additional bullet points.
Now we need to ensure we don't duplicate lines.
Let's extract the exact text.
Job Description Summary:
"The Manager, ServiceNow Solutions is responsible for leading a team of ServiceNow Business Analysts and Developers that support both Run-the-Business (RTB) operations and the delivery of enhancements and strategic initiatives across the ServiceNow platform. Reporting to the Director, ServiceNow, this role provides people leadership, delivery oversight, resource management, and operational governance for a team aligned to the ServiceNow demand pipeline. The Manager, ServiceNow Solutions is accountable for ensuring the successful execution of platform enhancements, managing team capacity and priorities, fostering a high-performing culture, and maintaining strong partnerships with business stakeholders, architecture, engineering, and platform leadership teams. This role serves as the primary leader for the Solutions organization, balancing day-to-day operational support with longer-term strategic delivery while driving accountability, transparency, and continuous improvement across the team."
Job Description paragraph:
"This role is a hybrid workstyle: with the associate expected to work from a Raymond James office location at least three days per week, including either Monday or Friday. Raymond James’ work environment is designed to reinforce our values-based culture while supporting the competitiveness, profitability, and long-term growth of our firm. Please note: This role is not eligible for Work Visa sponsorship, either currently or in the future."
Qualifications Required list:
"7+ years of experience in technology delivery, business analysis, application development, or platform solutions
3+ years of experience leading technical, analyst, or delivery-focused teams
Experience managing operational support and project-based delivery within Agile environments
Strong leadership, communication, stakeholder management, and organizational skills
Demonstrated ability to balance multiple priorities and drive execution across complex initiatives
Experience with resource planning, workload management, and delivery oversight"
Preferred Experience list:
"Experience with the ServiceNow platform and ServiceNow application delivery
Knowledge of Agile, Scrum, Kanban, and Software Development Life Cycle (SDLC) methodologies
Experience supporting enterprise platforms and large-scale technology initiatives
ServiceNow, Agile, Scrum, PMP, or related certifications
Experience leading teams through organizational growth, transformation, or delivery model changes"
Responsibilities list (with headings):
"People Leadership & Talent Development
Lead, coach, mentor, and develop a team of ServiceNow Business Analysts and Developers
Demand, Capacity & Resource Management
Partner with Demand Management and leadership to align incoming work with available team capacity
Stakeholder Management & Business Partnership
Serve as a primary point of contact for business stakeholders, process owners, and technology partners.
Solution Delivery & Analysis Oversight
Guide and oversee business analysis activities including requirements gathering, process evaluation, solution design, and user story development
Operational Excellence & Continuous Improvement
Drive consistent processes, standards, and ways of working across the Solutions team
Governance, Risk & Compliance
Ensure compliance with established ServiceNow governance processes, architecture standards, and SDLC requirements."
Success Measures list:
"Building and developing a high-performing team of Business Analysts and Developers
Delivering strategic initiatives and operational commitments predictably and efficiently
Ensuring effective alignment between business priorities, demand, and team capacity
Improving stakeholder satisfaction through transparency
for prose. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Preserve all substantive info. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". So we need to extract sections. Let's parse the job description. We have: - Job Description Summary: description of role. - Job Description: includes hybrid workstyle, note about work visa not eligible. - Qualifications Required: list of required qualifications. - Preferred Experience: list of preferred. - Responsibilities: list of responsibilities with subheadings. - Success Measures: list of success measures. - Education: High School (HS) (Required) - Work Experience: General Experience - 3 to 6 years (but earlier required 7+ years? There's inconsistency; but we preserve as given.) - Certifications: none listed. - Travel: Less than 25% - Workstyle: Hybrid - The total compensation for this position includes base salary or wages, and may include components such as additional compensation (cash or equity), discretionary bonuses, or commissions. This position is eligible for a benefits package that may include medical, dental, and vision; life insurance; critical illness insurance and accident insurance; disability benefits; retirement savings; paid time off (including vacation, holidays, and sick leave); and parental leave. Eligibility for benefits and specific offerings may vary based on position and employment status. To view more details of the benefits offered, visit Myrjbenefits.com. - Then some culture statements. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. - About the role: likely the summary and description (first paragraphs). Could include hybrid workstyle note. - Responsibilities: list of responsibilities (People Leadership & Talent Development etc.) - Requirements: maybe required qualifications (the "Qualifications Required:" list). Also Education, Work Experience, Travel, Workstyle? Might be considered Requirements. - Qualifications: maybe the "Preferred Experience" list? Or we could treat "Qualifications" as required qualifications, and "Skills" as preferred? But we have both sections. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). So we need to allocate content accordingly. We have required qualifications list: "7+ years of experience in technology delivery, business analysis, application development, or platform solutions; 3+ years of experience leading technical, analyst, or delivery-focused teams; Experience managing operational support and project-based delivery within Agile environments; Strong leadership, communication, stakeholder management, and organizational skills; Demonstrated ability to balance multiple priorities and drive execution across complex initiatives; Experience with resource planning, workload management, and delivery oversight". That's required. Preferred Experience list: "Experience with the ServiceNow platform and ServiceNow application delivery; Knowledge of Agile, Scrum, Kanban, and Software Development Life Cycle (SDLC) methodologies; Experience supporting enterprise platforms and large-scale technology initiatives; ServiceNow, Agile, Scrum, PMP, or related certifications; Experience leading teams through organizational growth, transformation, or delivery model changes". That's preferred. We also have Education: High School (HS) (Required). Work Experience: General Experience - 3 to 6 years (contradicts required but we keep). Travel: Less than 25%. Workstyle: Hybrid. We could put Education, Work Experience, Travel, Workstyle under Requirements or Qualifications. The instruction: "Prefer a few substantive sections over many thin ones." So we might combine. We need to include Benefits section: we have benefits description. Pay section: we have compensation description: base salary, additional compensation, discretionary bonuses, commissions. That's pay. Schedule: we have hybrid workstyle: expected to work from office at least three days per week, including either Monday or Friday. That's schedule. Thus we can create sections: - About the role: summary + job description paragraph (including hybrid note? maybe schedule separate). But we can include hybrid note in About the role? However schedule separate. We'll put About the role: the role summary (first two paragraphs) maybe excluding schedule note. - Responsibilities: list of responsibilities (the bullet points under Responsibilities heading). We'll format as
- .
- Requirements: could include required qualifications list plus Education, Work Experience, Travel, Workstyle? But Workstyle is schedule; maybe schedule separate. We'll keep Requirements as required qualifications + Education + Work Experience + Travel.
- Qualifications: maybe preferred qualifications list.
- Skills: maybe we could list skills from required/preferred? But we already have qualifications. Could combine? But we need to output sections only if real content. We have content for Skills? Could extract skills like leadership, communication, stakeholder management, organizational skills, resource planning, etc. But those are already in qualifications. Might be redundant. Perhaps we can omit Skills if no distinct content. But we need to decide.
The instruction: "Prefer a few substantive sections over many thin ones." So we could omit Skills if not distinct. But we have headings list as examples, not mandatory. So we can include only sections with real content.
Thus we will include: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
We need to ensure we don't include filler like "commensurate with experience". Not present.
Now we need to format.
We'll produce:
About the role
... (summary paragraphs)
Responsibilities
- People Leadership & Talent Development: Lead, coach, mentor, and develop a team of ServiceNow Business Analysts and Developers ... etc.
But we need to preserve the subheadings inside responsibilities? The responsibilities list includes headings like "People Leadership & Talent Development", "Demand, Capacity & Resource Management", etc. We could keep them as part of the li text.
Thus each li: "People Leadership & Talent Development: Lead, coach, mentor, and develop a team of ServiceNow Business Analysts and Developers". But we cannot use ? Not prohibited. We can just include plain text.
We'll keep as: "People Leadership & Talent Development – Lead, coach, mentor, and develop a team of ServiceNow Business Analysts and Developers". Use dash.
Now Requirements section: include required qualifications list (the bullet points). Also Education, Work Experience, Travel.
We'll format as - each.
Qualifications section: preferred experience list.
Benefits section: description of benefits.
Pay section: compensation description.
Schedule section: hybrid workstyle expectation.
Now we need to ensure we don't include boilerplate like "Please note: This role is not eligible for Work Visa sponsorship, either currently or in the future." That's substantive? It's a note about visa sponsorship. Should we keep? It's substantive info. It's not boilerplate? It's a specific condition. We could include in About the role or Requirements. Probably include in About the role as a note.
Also "Raymond James’ work environment is designed to reinforce our values-based culture while supporting the competitiveness, profitability, and long-term growth of our firm." That's fluff but maybe substantive? It's generic. Might be considered boilerplate? It's about work environment. Could be considered fluff. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those. It's a values statement. Might be okay to keep but could be considered filler. I'd keep it in About the role.
Also the success measures section: "Success Measures The Manager, ServiceNow Solutions Will Be Successful By ..." That's substantive; could be part of Responsibilities or a separate section? Not in our list headings. Could incorporate into Responsibilities or About the role. But we have no heading for Success Measures. We could add a section "Success Measures" but not in allowed headings list? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings only. So we should not create other headings like Success Measures. We can embed that content under Responsibilities or About the role. Probably under Responsibilities as part of success measures. Thus we will incorporate success measures into Responsibilities section as additional bullet points. Now we need to ensure we don't duplicate lines. Let's extract the exact text. Job Description Summary: "The Manager, ServiceNow Solutions is responsible for leading a team of ServiceNow Business Analysts and Developers that support both Run-the-Business (RTB) operations and the delivery of enhancements and strategic initiatives across the ServiceNow platform. Reporting to the Director, ServiceNow, this role provides people leadership, delivery oversight, resource management, and operational governance for a team aligned to the ServiceNow demand pipeline. The Manager, ServiceNow Solutions is accountable for ensuring the successful execution of platform enhancements, managing team capacity and priorities, fostering a high-performing culture, and maintaining strong partnerships with business stakeholders, architecture, engineering, and platform leadership teams. This role serves as the primary leader for the Solutions organization, balancing day-to-day operational support with longer-term strategic delivery while driving accountability, transparency, and continuous improvement across the team." Job Description paragraph: "This role is a hybrid workstyle: with the associate expected to work from a Raymond James office location at least three days per week, including either Monday or Friday. Raymond James’ work environment is designed to reinforce our values-based culture while supporting the competitiveness, profitability, and long-term growth of our firm. Please note: This role is not eligible for Work Visa sponsorship, either currently or in the future." Qualifications Required list: "7+ years of experience in technology delivery, business analysis, application development, or platform solutions 3+ years of experience leading technical, analyst, or delivery-focused teams Experience managing operational support and project-based delivery within Agile environments Strong leadership, communication, stakeholder management, and organizational skills Demonstrated ability to balance multiple priorities and drive execution across complex initiatives Experience with resource planning, workload management, and delivery oversight" Preferred Experience list: "Experience with the ServiceNow platform and ServiceNow application delivery Knowledge of Agile, Scrum, Kanban, and Software Development Life Cycle (SDLC) methodologies Experience supporting enterprise platforms and large-scale technology initiatives ServiceNow, Agile, Scrum, PMP, or related certifications Experience leading teams through organizational growth, transformation, or delivery model changes" Responsibilities list (with headings): "People Leadership & Talent Development Lead, coach, mentor, and develop a team of ServiceNow Business Analysts and Developers Demand, Capacity & Resource Management Partner with Demand Management and leadership to align incoming work with available team capacity Stakeholder Management & Business Partnership Serve as a primary point of contact for business stakeholders, process owners, and technology partners. Solution Delivery & Analysis Oversight Guide and oversee business analysis activities including requirements gathering, process evaluation, solution design, and user story development Operational Excellence & Continuous Improvement Drive consistent processes, standards, and ways of working across the Solutions team Governance, Risk & Compliance Ensure compliance with established ServiceNow governance processes, architecture standards, and SDLC requirements." Success Measures list: "Building and developing a high-performing team of Business Analysts and Developers Delivering strategic initiatives and operational commitments predictably and efficiently Ensuring effective alignment between business priorities, demand, and team capacity Improving stakeholder satisfaction through transparency