Enterprise Project Manager (Location Flexible)
RSM US LLP · Dallas, TX · 3 wk ago
Project Management$103k–$176k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes intro paragraphs about company and role. We need to use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We must include a section only when posting has real, specific content for it. We need to parse content.
The posting includes:
- Intro: "We are the leading provider..." This is about company and role. Could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
We have:
- Role description: "Join our team as an Enterprise Project Manager, where you’ll shape key initiatives and drive measurable results across the organization. This highly visible role offers the opportunity to lead complex, cross-functional projects, partner with senior stakeholders, and strengthen the discipline of delivery through clear governance, thoughtful planning, and consistent execution. In this role, you will serve as a central connector across teams and align priorities, clarify scope, and ensure delivery against time, budget, and quality expectations. You’ll establish and maintain effective project governance, manage dependencies across workstreams, and provide transparent communications and reporting to help leaders make timely decisions and keep enterprise initiatives on track. You’ll be empowered to right-size governance to the risk and complexity of the work—simplifying process where possible while protecting outcomes."
Then there is a list of "Role Expectations" with bullet points (starting with "Establish lightweight playbooks..."). Those are responsibilities.
Then "Required Qualifications" bullet list.
Then "Preferred Qualifications" bullet list.
Then "Desired Attributes" bullet list.
Then benefits: "At RSM, we offer a competitive benefits and compensation package for all our people. We offer flexibility in your schedule, empowering you to balance life’s demands, while also maintaining your ability to serve clients. Learn more about our total rewards at https://rsmus.com/careers/working-at-rsm/benefits."
Then compensation range: "Compensation Range: $102,800 - $176,000 Individuals selected for this role will be eligible for a discretionary bonus based on firm and individual performance."
Thus we have content for:
- About the role: maybe the introductory paragraph(s) describing role and company.
- Responsibilities: the Role Expectations bullet list (maybe also some of the earlier description could be responsibilities, but we can put the bullet list as responsibilities).
- Requirements: maybe combine Required Qualifications and Preferred Qualifications? The instruction has separate headings: Requirements, Qualifications, Skills. We need to decide what goes where. Usually "Requirements" could be required qualifications, "Qualifications" could be preferred qualifications, "Skills" could be desired attributes or specific skills. But we must only create sections if there is real specific content.
We have:
- Required Qualifications: list of 5 bullet points.
- Preferred Qualifications: list of 4 bullet points.
- Desired Attributes: list of 4 bullet points.
We could map:
- Requirements: Required Qualifications.
- Qualifications: Preferred Qualifications.
- Skills: Desired Attributes (or maybe combine with proficiency in tools etc). But the Desired Attributes are more about attributes; still could be considered skills.
Alternatively we could combine Required and Preferred into Qualifications and not have separate Requirements. But we need to follow instruction: use headings as given; we can omit sections if no content. We have content for all three: Required, Preferred, Desired. So we can create three sections: Requirements (Required Qualifications), Qualifications (Preferred Qualifications), Skills (Desired Attributes). That seems reasonable.
Benefits: we have a sentence about competitive benefits and flexibility, plus link. That's specific enough to create Benefits section.
Pay: we have compensation range and bonus eligibility. That's specific, so Pay section.
Schedule: we have "We offer flexibility in your schedule". That's specific enough for Schedule section.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate: EEO, accommodation, etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. We must not include the EEO paragraph, accommodation, etc. Also remove the line about "Learn more about our total rewards at ..."? That is part of benefits, we can keep as part of benefits description. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits link is not boilerplate; it's part of benefits. Keep.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all bullet points exactly as given (maybe slight rephrase? but must preserve). We'll output as
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We must include a section only when posting has real, specific content for it. We need to parse content.
The posting includes:
- Intro: "We are the leading provider..." This is about company and role. Could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
We have:
- Role description: "Join our team as an Enterprise Project Manager, where you’ll shape key initiatives and drive measurable results across the organization. This highly visible role offers the opportunity to lead complex, cross-functional projects, partner with senior stakeholders, and strengthen the discipline of delivery through clear governance, thoughtful planning, and consistent execution. In this role, you will serve as a central connector across teams and align priorities, clarify scope, and ensure delivery against time, budget, and quality expectations. You’ll establish and maintain effective project governance, manage dependencies across workstreams, and provide transparent communications and reporting to help leaders make timely decisions and keep enterprise initiatives on track. You’ll be empowered to right-size governance to the risk and complexity of the work—simplifying process where possible while protecting outcomes."
Then there is a list of "Role Expectations" with bullet points (starting with "Establish lightweight playbooks..."). Those are responsibilities.
Then "Required Qualifications" bullet list.
Then "Preferred Qualifications" bullet list.
Then "Desired Attributes" bullet list.
Then benefits: "At RSM, we offer a competitive benefits and compensation package for all our people. We offer flexibility in your schedule, empowering you to balance life’s demands, while also maintaining your ability to serve clients. Learn more about our total rewards at https://rsmus.com/careers/working-at-rsm/benefits."
Then compensation range: "Compensation Range: $102,800 - $176,000 Individuals selected for this role will be eligible for a discretionary bonus based on firm and individual performance."
Thus we have content for:
- About the role: maybe the introductory paragraph(s) describing role and company.
- Responsibilities: the Role Expectations bullet list (maybe also some of the earlier description could be responsibilities, but we can put the bullet list as responsibilities).
- Requirements: maybe combine Required Qualifications and Preferred Qualifications? The instruction has separate headings: Requirements, Qualifications, Skills. We need to decide what goes where. Usually "Requirements" could be required qualifications, "Qualifications" could be preferred qualifications, "Skills" could be desired attributes or specific skills. But we must only create sections if there is real specific content.
We have:
- Required Qualifications: list of 5 bullet points.
- Preferred Qualifications: list of 4 bullet points.
- Desired Attributes: list of 4 bullet points.
We could map:
- Requirements: Required Qualifications.
- Qualifications: Preferred Qualifications.
- Skills: Desired Attributes (or maybe combine with proficiency in tools etc). But the Desired Attributes are more about attributes; still could be considered skills.
Alternatively we could combine Required and Preferred into Qualifications and not have separate Requirements. But we need to follow instruction: use headings as given; we can omit sections if no content. We have content for all three: Required, Preferred, Desired. So we can create three sections: Requirements (Required Qualifications), Qualifications (Preferred Qualifications), Skills (Desired Attributes). That seems reasonable.
Benefits: we have a sentence about competitive benefits and flexibility, plus link. That's specific enough to create Benefits section.
Pay: we have compensation range and bonus eligibility. That's specific, so Pay section.
Schedule: we have "We offer flexibility in your schedule". That's specific enough for Schedule section.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate: EEO, accommodation, etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. We must not include the EEO paragraph, accommodation, etc. Also remove the line about "Learn more about our total rewards at ..."? That is part of benefits, we can keep as part of benefits description. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits link is not boilerplate; it's part of benefits. Keep.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all bullet points exactly as given (maybe slight rephrase? but must preserve). We'll output as - for each bullet.
We need to ensure we don't include filler like "commensurate with experience". Not present.
Now craft HTML.
Structure:
About the role
We are the leading provider of professional services to the middle market globally, our purpose is to instill confidence in a world of change, empowering our clients and people to realize their full potential. Our exceptional people are the key to our unrivaled, culture and talent experience and our ability to be compelling to our clients. You’ll find an environment that inspires and empowers you to thrive both personally and professionally. There’s no one like you and that’s why there’s nowhere like RSM. Join our team as an Enterprise Project Manager, where you’ll shape key initiatives and drive measurable results across the organization. This highly visible role offers the opportunity to lead complex, cross-functional projects, partner with senior stakeholders, and strengthen the discipline of delivery through clear governance, thoughtful planning, and consistent execution. In this role, you will serve as a central connector across teams and align priorities, clarify scope, and ensure delivery against time, budget, and quality expectations. You’ll establish and maintain effective project governance, manage dependencies across workstreams, and provide transparent communications and reporting to help leaders make timely decisions and keep enterprise initiatives on track. You’ll be empowered to right-size governance to the risk and complexity of the work—simplifying process where possible while protecting outcomes.
Then Responsibilities: the Role Expectations bullet list.
We need to capture each bullet exactly as in text:
"Establish lightweight playbooks, templates, and routines that make delivery easier—not more bureaucratic."
"Shape how work gets done: influence operating models, clarify decision rights, and improve cross-team handoffs and accountability."
"Right-size governance: tailor the level of rigor to the risk and complexity of the work, removing friction while protecting outcomes."
"Partner closely with leaders: facilitate decisions, surface tradeoffs early, and keep enterprise priorities moving."
"Deliver measurable results: focus teams on outcomes, adoption, and sustained impact—not just activity and status."
"Help define the culture: model a pragmatic, action-oriented approach that keeps momentum high and red tape low."
"This is not a status-reporting role—you will be expected to create momentum, drive decisions, and deliver."
"Convert enterprise priorities into clear project charters, success measures, plans, and deliverables aligned to strategic goals."
"Own end-to-end execution from initiation through closeout, managing scope, schedule, resources, and quality to deliver agreed outcomes."
"Drive delivery across multiple teams and business areas by managing dependencies, facilitating decisions, and removing roadblocks with business and technology partners."
"Run fit-for-purpose governance models and provide reliable and concise status, risks, and recommendations to sponsors and stakeholders."
"Proactively identify and mitigate risks and issues, and partner with change management stakeholders to drive adoption and sustain outcomes."
Make sure to keep punctuation.
Now Requirements: Required Qualifications bullet list:
"6-7 years of project management experience delivering cross-functional initiatives (business and/or technology)."
"Demonstrated ability to lead complex work with multiple stakeholders, dependencies, and competing priorities while maintaining momentum and accountability."
"Strong facilitation and communication skills, including presenting clear status, risks, and decision points to senior leaders and steering groups."
"Proficiency with core project management practices and artifacts (charters, schedules, RAID logs, action tracking, change control) and common tools (e.g., MS Project, Smartsheet, Jira, Azure DevOps, or equivalent)."
"Experience establishing fit-for-purpose governance and maintaining delivery transparency through concise reporting, dashboards, and stakeholder communications."
Now Qualifications: Preferred Qualifications bullet list:
"Project management certification (e.g., PMP, PgMP, PMI-ACP, or equivalent)."
"Experience leading Agile, waterfall, and/or hybrid delivery—selecting the right approach and right-sizing ceremonies and documentation."
"Experience working within an enterprise portfolio or program environment, including dependency management across multiple projects."
"Change management and adoption experience (e.g., stakeholder impact assessment, communications, training coordination) in partnership with enterprise change resources."
Now Skills: Desired Attributes bullet list:
"Outcome-focused leader who balances strategic thinking with hands-on execution and follows through on commitments."
"Exceptional relationship-building skills with a track record of influencing without authority and aligning diverse stakeholders."
"Clear, concise communicator who can simplify complexity, tailor messages to the audience, and drive timely decisions."
"Pragmatic, action-oriented executor who avoids unnecessary administrative red tape, simplifies overly complex processes, and keeps teams focused on timely delivery and measurable results through project completion."
Now Benefits: we have sentences: "At RSM, we offer a competitive benefits and compensation package for all our people. We offer flexibility in your schedule, empowering you to balance life’s demands, while also maintaining your ability to serve clients. Learn more about our total rewards at https://rsmus.com/careers/working-at-rsm/benefits."
We could keep as a paragraph.
Now Pay: "Compensation Range: $102,800 - $176,000 Individuals selected for this role will be eligible for a discretionary bonus based on firm and individual performance."
We could make a paragraph.
Now Schedule: "We offer flexibility in your schedule, empowering you to balance life’s demands, while also maintaining your ability to serve clients." Actually that sentence already appears in benefits. But we can still have schedule section with that sentence. However we must not duplicate content? The instruction says preserve ALL substantive information; do not invent or summarize away detail. Duplicated lines: we should remove duplicated lines. The sentence about flexibility appears both in benefits and schedule? Actually the benefits paragraph includes that sentence. If we also put schedule section with same sentence, that would be duplication. We should avoid duplication. Perhaps we can keep schedule section with just that sentence, but then we would have duplicated content (the same sentence appears in benefits). The instruction says remove duplicated lines. So we should not repeat the same sentence. We need to decide where to place it. The benefits section already includes that sentence; schedule section could be omitted if no other specific schedule info. But we have "We offer flexibility in your schedule" as schedule info. If we put it only in benefits, we still have schedule info covered. But we need a Schedule section only if posting has real specific content for it. The posting does mention flexibility in schedule, which is schedule-related. So we could include Schedule section with that sentence, but then we would have duplication if we also keep it in benefits. We could adjust benefits section to not include that sentence, moving it to schedule. However the benefits paragraph also mentions competitive benefits and compensation package and link. We could split: Benefits: competitive benefits and compensation package, link. Schedule: flexibility in schedule. That avoids duplication.
Thus we will parse:
Benefits: "At RSM, we offer a competitive benefits and compensation package for all our people. Learn more about our total rewards at https://rsmus.com/careers/working-at-rsm/benefits."
Schedule: "We offer flexibility in your schedule, empowering you to balance life’s demands, while also maintaining your ability to serve clients."
That preserves all info without duplication.
Now Pay: keep as is.
Now ensure we don't include any boilerplate like EEO etc. We'll omit those paragraphs
About the role
We are the leading provider of professional services to the middle market globally, our purpose is to instill confidence in a world of change, empowering our clients and people to realize their full potential. Our exceptional people are the key to our unrivaled, culture and talent experience and our ability to be compelling to our clients. You’ll find an environment that inspires and empowers you to thrive both personally and professionally. There’s no one like you and that’s why there’s nowhere like RSM. Join our team as an Enterprise Project Manager, where you’ll shape key initiatives and drive measurable results across the organization. This highly visible role offers the opportunity to lead complex, cross-functional projects, partner with senior stakeholders, and strengthen the discipline of delivery through clear governance, thoughtful planning, and consistent execution. In this role, you will serve as a central connector across teams and align priorities, clarify scope, and ensure delivery against time, budget, and quality expectations. You’ll establish and maintain effective project governance, manage dependencies across workstreams, and provide transparent communications and reporting to help leaders make timely decisions and keep enterprise initiatives on track. You’ll be empowered to right-size governance to the risk and complexity of the work—simplifying process where possible while protecting outcomes.
Then Responsibilities: the Role Expectations bullet list. We need to capture each bullet exactly as in text: "Establish lightweight playbooks, templates, and routines that make delivery easier—not more bureaucratic." "Shape how work gets done: influence operating models, clarify decision rights, and improve cross-team handoffs and accountability." "Right-size governance: tailor the level of rigor to the risk and complexity of the work, removing friction while protecting outcomes." "Partner closely with leaders: facilitate decisions, surface tradeoffs early, and keep enterprise priorities moving." "Deliver measurable results: focus teams on outcomes, adoption, and sustained impact—not just activity and status." "Help define the culture: model a pragmatic, action-oriented approach that keeps momentum high and red tape low." "This is not a status-reporting role—you will be expected to create momentum, drive decisions, and deliver." "Convert enterprise priorities into clear project charters, success measures, plans, and deliverables aligned to strategic goals." "Own end-to-end execution from initiation through closeout, managing scope, schedule, resources, and quality to deliver agreed outcomes." "Drive delivery across multiple teams and business areas by managing dependencies, facilitating decisions, and removing roadblocks with business and technology partners." "Run fit-for-purpose governance models and provide reliable and concise status, risks, and recommendations to sponsors and stakeholders." "Proactively identify and mitigate risks and issues, and partner with change management stakeholders to drive adoption and sustain outcomes." Make sure to keep punctuation. Now Requirements: Required Qualifications bullet list: "6-7 years of project management experience delivering cross-functional initiatives (business and/or technology)." "Demonstrated ability to lead complex work with multiple stakeholders, dependencies, and competing priorities while maintaining momentum and accountability." "Strong facilitation and communication skills, including presenting clear status, risks, and decision points to senior leaders and steering groups." "Proficiency with core project management practices and artifacts (charters, schedules, RAID logs, action tracking, change control) and common tools (e.g., MS Project, Smartsheet, Jira, Azure DevOps, or equivalent)." "Experience establishing fit-for-purpose governance and maintaining delivery transparency through concise reporting, dashboards, and stakeholder communications." Now Qualifications: Preferred Qualifications bullet list: "Project management certification (e.g., PMP, PgMP, PMI-ACP, or equivalent)." "Experience leading Agile, waterfall, and/or hybrid delivery—selecting the right approach and right-sizing ceremonies and documentation." "Experience working within an enterprise portfolio or program environment, including dependency management across multiple projects." "Change management and adoption experience (e.g., stakeholder impact assessment, communications, training coordination) in partnership with enterprise change resources." Now Skills: Desired Attributes bullet list: "Outcome-focused leader who balances strategic thinking with hands-on execution and follows through on commitments." "Exceptional relationship-building skills with a track record of influencing without authority and aligning diverse stakeholders." "Clear, concise communicator who can simplify complexity, tailor messages to the audience, and drive timely decisions." "Pragmatic, action-oriented executor who avoids unnecessary administrative red tape, simplifies overly complex processes, and keeps teams focused on timely delivery and measurable results through project completion." Now Benefits: we have sentences: "At RSM, we offer a competitive benefits and compensation package for all our people. We offer flexibility in your schedule, empowering you to balance life’s demands, while also maintaining your ability to serve clients. Learn more about our total rewards at https://rsmus.com/careers/working-at-rsm/benefits." We could keep as a paragraph. Now Pay: "Compensation Range: $102,800 - $176,000 Individuals selected for this role will be eligible for a discretionary bonus based on firm and individual performance." We could make a paragraph. Now Schedule: "We offer flexibility in your schedule, empowering you to balance life’s demands, while also maintaining your ability to serve clients." Actually that sentence already appears in benefits. But we can still have schedule section with that sentence. However we must not duplicate content? The instruction says preserve ALL substantive information; do not invent or summarize away detail. Duplicated lines: we should remove duplicated lines. The sentence about flexibility appears both in benefits and schedule? Actually the benefits paragraph includes that sentence. If we also put schedule section with same sentence, that would be duplication. We should avoid duplication. Perhaps we can keep schedule section with just that sentence, but then we would have duplicated content (the same sentence appears in benefits). The instruction says remove duplicated lines. So we should not repeat the same sentence. We need to decide where to place it. The benefits section already includes that sentence; schedule section could be omitted if no other specific schedule info. But we have "We offer flexibility in your schedule" as schedule info. If we put it only in benefits, we still have schedule info covered. But we need a Schedule section only if posting has real specific content for it. The posting does mention flexibility in schedule, which is schedule-related. So we could include Schedule section with that sentence, but then we would have duplication if we also keep it in benefits. We could adjust benefits section to not include that sentence, moving it to schedule. However the benefits paragraph also mentions competitive benefits and compensation package and link. We could split: Benefits: competitive benefits and compensation package, link. Schedule: flexibility in schedule. That avoids duplication. Thus we will parse: Benefits: "At RSM, we offer a competitive benefits and compensation package for all our people. Learn more about our total rewards at https://rsmus.com/careers/working-at-rsm/benefits." Schedule: "We offer flexibility in your schedule, empowering you to balance life’s demands, while also maintaining your ability to serve clients." That preserves all info without duplication. Now Pay: keep as is. Now ensure we don't include any boilerplate like EEO etc. We'll omit those paragraphs