Finance Transformation Project Manager
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for lists of duties/requirements/benefits, and
for prose
3. Do NOT repeat the job title as a heading
4. Do NOT put Job ID/requisition numbers as headings
5. Preserve ALL substantive information
6. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions)
7. Include a section ONLY when the posting has real, specific content for it
8. Never emit a heading followed by filler/placeholder text
9. Never create Pay/Schedule/Benefits sections unless the posting actually states them
10. Output ONLY the HTML fragment — no /, no markdown code fences
Let me analyze the job posting:
The posting has:
- An introductory paragraph about the role (reporting structure, expectations)
- Company description (Dewberry)
- Responsibilities section with numbered subsections (2, 3, 4)
- Required Skills & Required Experience section
- Preferred Experience section
- What Success Looks Like section
- Some boilerplate at the end (work authorization, EEO, background screening)
I need to structure this into appropriate sections. The headings should be semantic: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But I should only include sections that have real content.
Looking at the content:
- "About the role" - the introductory paragraphs describe the role, reporting structure, expectations
- "Responsibilities" - there are three numbered areas (2, 3, 4) with detailed bullet points
- "Requirements" - the "Required Skills & Required Experience" section
- "Qualifications" - could be the preferred experience, but maybe combine with requirements? The rules say use Qualifications as a heading option. I'll separate Required and Preferred.
- "Skills" - could be part of requirements, but there's a list of specific skills mentioned
- "Benefits" - not mentioned in the posting
- "Pay" - not mentioned
- "Schedule" - not mentioned
So I'll create sections for: About the role, Responsibilities, Requirements, Qualifications (for preferred), and maybe Skills if distinct. But the rules say "Prefer a few substantive sections over many thin ones." I'll combine where appropriate.
The "Required Skills & Required Experience" includes both degree, years of experience, and specific skills. The "Preferred Experience" is separate. "What Success Looks Like" is more of a summary of expectations.
I'll structure as:
- About the role (intro paragraphs)
- Responsibilities (the three numbered areas with their bullet points)
- Requirements (required skills & experience)
- Qualifications (preferred experience)
- What Success Looks Like (could be a section, but maybe fold into About the role? It's distinct enough to be its own section)
The rules say use
for section headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". "What Success Looks Like" isn't in that list, but it's a substantive section. I could use for it as well, but the rules say "e.g." so it's not exhaustive. I'll include it as a section.
Now, I need to convert the content into HTML with
for prose and
- for lists.
Let me parse the responsibilities: They are numbered 2, 3, 4 with sub-bullets. I'll create a list for each major area, or combine into one list with sub-items? The rules say use
- for any list of duties. I'll make each major responsibility area a list item with nested lists? But the rules don't specify nested lists. Simpler: each bullet point as a separate
- in a single list per section? But there are three distinct areas. I'll create three subsections under Responsibilities? The rules say use
for section headings, not subheadings. I could use but not specified. Better to keep flat: one Responsibilities section with a list of all duties. However, the posting groups them into three categories. I'll create a list where each category is a list item with a strong label and then sub-bullets? But HTML doesn't have sub-bullets in - without nesting. I can nest
inside - . That's valid HTML. I'll do that.
Similarly for Requirements: there's a list of required items. I'll make a list.
Preferred Experience: list.
What Success Looks Like: list.
Now, remove boilerplate: "At this time, Dewberry will not sponsor a new applicant for work authorization. Dewberry is an Equal Opportunity Employer... Only recipients of an offer..." - remove.
Also remove "Job Description" at start? The posting starts with "Job Description Reporting to the Director..." - that's part of the intro.
Now, write the HTML.
I'll start with
About the role
then paragraphs.
Then Responsibilities
then a with three main - for each area, each containing a nested
for the bullet points.
But the responsibilities are numbered 2, 3, 4. The first one is "2. Business Knowledge & Process Mapping Finance Process & Technology Transformation" - that's a heading. Then a list of bullets. Similarly "3. Cross-Functional Project Leadership & Portfolio Management" and "4. Change Leadership, Communication & Relationship Management". I'll treat each as a top-level list item with the title as strong text, then nested list.
Alternatively, I could make each a separate but rules only mention for section headings. I'll stick to for main sections only. For subsections, I'll use within list items.
Let's craft.
First, About the role: There are several paragraphs. I'll combine them into a few tags.
Paragraph 1: "Reporting to the Director of Data Strategy & Analytics, the Finance Transformation Project Manager works across four primary areas — Accounting, Financial Operations, Financial Systems, and Data Strategy & Analytics — as well as other business and technology teams as needed. The role builds relationships across these areas, identifies opportunities for improvement, connects the right people and capabilities, and coordinates initiatives that span organizational boundaries. The Chief Financial Officer serves as executive sponsor for the broader Finance transformation portfolio."
Paragraph 2: "This role is expected to operate with a high degree of initiative, curiosity, independence, and judgment. The successful candidate will proactively build relationships, ask questions, identify opportunities, and help turn loosely defined problems into structured initiatives. The Director of Data Strategy & Analytics provides leadership, coaching, and guidance, while the Project Manager is expected to take ownership of navigating the organization and moving initiatives forward. Success requires exceptional communication and interpersonal skills, structured problem solving, sound judgment, organizational awareness, and the ability to influence and create momentum without relying on formal authority. The successful candidate will also be comfortable embracing new technology and using modern project-management, collaboration, automation, and AI tools as part of their day-to-day work."
Paragraph 3: Company description: "Dewberry is a leading, market-facing professional services firm with more than 60 locations and 2,500 professionals nationwide. What sets us apart from our competitors are our people. At Dewberry, we seek out exceptional talent and strive to deliver the highest quality of services to our clients. Whether you’re an experienced professional or a new graduate, you’ll have the chance to collaborate with the best and brightest and work on innovative and complex projects at the forefront of the industry. Our commitment to excellence stems from our personal integrity and from other defining attributes, which we call “Dewberry at Work,” that have inspired our employees to be successful for more than a half-century."
I'll keep these as separate paragraphs.
Now Responsibilities: I'll create a
with three - items, each containing a for the area title and a nested
for the bullets.
Area 1: "Business Knowledge & Process Mapping / Finance Process & Technology Transformation" (the heading is "2. Business Knowledge & Process Mapping Finance Process & Technology Transformation" - seems like two lines but it's one heading). I'll use "Business Knowledge & Process Mapping – Finance Process & Technology Transformation".
Bullets:
- Build relationships across Finance to understand priorities, workflows, pain points, and emerging needs, and proactively identify opportunities rather than waiting for assignment.
- Identify manual activities, inefficient handoffs, bottlenecks, and recurring problems, and evaluate opportunities to improve day-to-day work as well as planning, forecasting, analysis, and business support.
- Help stakeholders define problems, desired outcomes, requirements, dependencies, and measures of success before solutions are developed.
- Develop a working understanding of the ERP, EPM, CRM, HR, BI, and related platforms supporting Finance — sufficient to connect business needs with the appropriate technical experts and to translate operational needs into clear requirements.
- Coordinate initiatives involving process, system, data, or technology change, including requirements gathering, testing, validation, rollout, communication, training, and adoption.
- Identify dependencies across systems, processes, teams, and initiatives early enough for them to be addressed, and maintain visibility into commitments, decisions, and risks.
- Recognize when an issue requires a business decision and bring the appropriate leaders and subject-matter experts together to resolve it.
- Actively support responsible adoption of AI and automation across Finance by helping teams understand new capabilities, identify practical use cases, and incorporate approved tools into existing workflows — approaching emerging technology with curiosity and a willingness to experiment, learn, and adapt while recognizing appropriate governance, security, and human-review requirements.
- Translate technical concepts into understandable business language and business needs into productive discussions with technical teams.
- Help establish and maintain a structured and sustainable understanding of how Finance operates so that institutional knowledge can support process improvement, transformation, analytics, automation, and AI initiatives.
- Facilitate discovery with subject-matter experts to understand and document how important Finance processes operate in practice.
- Document and map end-to-end processes, roles, terminology, business rules, systems, dependencies, decision points, controls, and exceptions across Finance functions and information flows.
- Identify conflicting terminology, undocumented business rules, unclear ownership, process gaps, and areas where important institutional knowledge is concentrated with individual employees.
- Help establish practical standards, tools, and maintenance practices for process maps, process inventories, business glossaries, and related organizational knowledge.
- Facilitate validation of documented processes and business knowledge with the appropriate functional leaders and subject-matter experts.
- Partner with Data Strategy & Analytics to provide validated business and process knowledge that can inform semantic models, enterprise ontology, analytics, automation, and AI capabilities.
Area 2: "Cross-Functional Project Leadership & Portfolio Management"
Bullets:
- Turn loosely defined problems into structured initiatives with clear objectives, stakeholders, responsibilities, dependencies, timelines, and next steps.
- Exercise sound judgment in determining which issues can be advanced independently and which require leadership involvement, working with the Director of Data Strategy & Analytics, CFO, and appropriate functional leaders to align significant initiatives with broader Finance priorities.
- Build consensus where possible and surface competing priorities or unresolved decisions when leadership involvement is needed.
- Use ClickUp or comparable project and work-management platforms to create and maintain project plans, tasks, milestones, owners, dependencies, risks, decisions, and follow-up activities, keeping information accurate and current enough that stakeholders have reliable visibility into status and next steps.
- Develop dashboards, portfolio views, and other mechanisms that provide leadership with clear visibility across initiatives.
- Establish practical standards for project documentation, status reporting, and risk management that create accountability without introducing unnecessary administrative burden.
- Use automation and AI where appropriate to reduce manual project administration, improve reporting, identify risks, and summarize activity, preserving more time for stakeholder engagement and problem solving.
- Keep initiatives moving when responsibility crosses organizational boundaries
for prose 3. Do NOT repeat the job title as a heading 4. Do NOT put Job ID/requisition numbers as headings 5. Preserve ALL substantive information 6. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) 7. Include a section ONLY when the posting has real, specific content for it 8. Never emit a heading followed by filler/placeholder text 9. Never create Pay/Schedule/Benefits sections unless the posting actually states them 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting: The posting has: - An introductory paragraph about the role (reporting structure, expectations) - Company description (Dewberry) - Responsibilities section with numbered subsections (2, 3, 4) - Required Skills & Required Experience section - Preferred Experience section - What Success Looks Like section - Some boilerplate at the end (work authorization, EEO, background screening) I need to structure this into appropriate sections. The headings should be semantic: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But I should only include sections that have real content. Looking at the content: - "About the role" - the introductory paragraphs describe the role, reporting structure, expectations - "Responsibilities" - there are three numbered areas (2, 3, 4) with detailed bullet points - "Requirements" - the "Required Skills & Required Experience" section - "Qualifications" - could be the preferred experience, but maybe combine with requirements? The rules say use Qualifications as a heading option. I'll separate Required and Preferred. - "Skills" - could be part of requirements, but there's a list of specific skills mentioned - "Benefits" - not mentioned in the posting - "Pay" - not mentioned - "Schedule" - not mentioned So I'll create sections for: About the role, Responsibilities, Requirements, Qualifications (for preferred), and maybe Skills if distinct. But the rules say "Prefer a few substantive sections over many thin ones." I'll combine where appropriate. The "Required Skills & Required Experience" includes both degree, years of experience, and specific skills. The "Preferred Experience" is separate. "What Success Looks Like" is more of a summary of expectations. I'll structure as: - About the role (intro paragraphs) - Responsibilities (the three numbered areas with their bullet points) - Requirements (required skills & experience) - Qualifications (preferred experience) - What Success Looks Like (could be a section, but maybe fold into About the role? It's distinct enough to be its own section) The rules say use
for section headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". "What Success Looks Like" isn't in that list, but it's a substantive section. I could use for it as well, but the rules say "e.g." so it's not exhaustive. I'll include it as a section.
Now, I need to convert the content into HTML with
for prose and
- for lists.
Let me parse the responsibilities: They are numbered 2, 3, 4 with sub-bullets. I'll create a list for each major area, or combine into one list with sub-items? The rules say use
- for any list of duties. I'll make each major responsibility area a list item with nested lists? But the rules don't specify nested lists. Simpler: each bullet point as a separate
- in a single list per section? But there are three distinct areas. I'll create three subsections under Responsibilities? The rules say use
for section headings, not subheadings. I could use
but not specified. Better to keep flat: one Responsibilities section with a list of all duties. However, the posting groups them into three categories. I'll create a list where each category is a list item with a strong label and then sub-bullets? But HTML doesn't have sub-bullets in
- without nesting. I can nest
- inside
- . That's valid HTML. I'll do that.
Similarly for Requirements: there's a list of required items. I'll make a list.
Preferred Experience: list.
What Success Looks Like: list.
Now, remove boilerplate: "At this time, Dewberry will not sponsor a new applicant for work authorization. Dewberry is an Equal Opportunity Employer... Only recipients of an offer..." - remove.
Also remove "Job Description" at start? The posting starts with "Job Description Reporting to the Director..." - that's part of the intro.
Now, write the HTML.
I'll start with
About the role
then paragraphs. ThenResponsibilities
then a- with three main
- for each area, each containing a nested
- for the bullet points.
But the responsibilities are numbered 2, 3, 4. The first one is "2. Business Knowledge & Process Mapping Finance Process & Technology Transformation" - that's a heading. Then a list of bullets. Similarly "3. Cross-Functional Project Leadership & Portfolio Management" and "4. Change Leadership, Communication & Relationship Management". I'll treat each as a top-level list item with the title as strong text, then nested list.
Alternatively, I could make each a separate
- items, each containing a for the area title and a nested
- for the bullets.
Area 1: "Business Knowledge & Process Mapping / Finance Process & Technology Transformation" (the heading is "2. Business Knowledge & Process Mapping Finance Process & Technology Transformation" - seems like two lines but it's one heading). I'll use "Business Knowledge & Process Mapping – Finance Process & Technology Transformation".
Bullets:
- Build relationships across Finance to understand priorities, workflows, pain points, and emerging needs, and proactively identify opportunities rather than waiting for assignment.
- Identify manual activities, inefficient handoffs, bottlenecks, and recurring problems, and evaluate opportunities to improve day-to-day work as well as planning, forecasting, analysis, and business support.
- Help stakeholders define problems, desired outcomes, requirements, dependencies, and measures of success before solutions are developed.
- Develop a working understanding of the ERP, EPM, CRM, HR, BI, and related platforms supporting Finance — sufficient to connect business needs with the appropriate technical experts and to translate operational needs into clear requirements.
- Coordinate initiatives involving process, system, data, or technology change, including requirements gathering, testing, validation, rollout, communication, training, and adoption.
- Identify dependencies across systems, processes, teams, and initiatives early enough for them to be addressed, and maintain visibility into commitments, decisions, and risks.
- Recognize when an issue requires a business decision and bring the appropriate leaders and subject-matter experts together to resolve it.
- Actively support responsible adoption of AI and automation across Finance by helping teams understand new capabilities, identify practical use cases, and incorporate approved tools into existing workflows — approaching emerging technology with curiosity and a willingness to experiment, learn, and adapt while recognizing appropriate governance, security, and human-review requirements.
- Translate technical concepts into understandable business language and business needs into productive discussions with technical teams.
- Help establish and maintain a structured and sustainable understanding of how Finance operates so that institutional knowledge can support process improvement, transformation, analytics, automation, and AI initiatives.
- Facilitate discovery with subject-matter experts to understand and document how important Finance processes operate in practice.
- Document and map end-to-end processes, roles, terminology, business rules, systems, dependencies, decision points, controls, and exceptions across Finance functions and information flows.
- Identify conflicting terminology, undocumented business rules, unclear ownership, process gaps, and areas where important institutional knowledge is concentrated with individual employees.
- Help establish practical standards, tools, and maintenance practices for process maps, process inventories, business glossaries, and related organizational knowledge.
- Facilitate validation of documented processes and business knowledge with the appropriate functional leaders and subject-matter experts.
- Partner with Data Strategy & Analytics to provide validated business and process knowledge that can inform semantic models, enterprise ontology, analytics, automation, and AI capabilities.
Area 2: "Cross-Functional Project Leadership & Portfolio Management"
Bullets:
- Turn loosely defined problems into structured initiatives with clear objectives, stakeholders, responsibilities, dependencies, timelines, and next steps.
- Exercise sound judgment in determining which issues can be advanced independently and which require leadership involvement, working with the Director of Data Strategy & Analytics, CFO, and appropriate functional leaders to align significant initiatives with broader Finance priorities.
- Build consensus where possible and surface competing priorities or unresolved decisions when leadership involvement is needed.
- Use ClickUp or comparable project and work-management platforms to create and maintain project plans, tasks, milestones, owners, dependencies, risks, decisions, and follow-up activities, keeping information accurate and current enough that stakeholders have reliable visibility into status and next steps.
- Develop dashboards, portfolio views, and other mechanisms that provide leadership with clear visibility across initiatives.
- Establish practical standards for project documentation, status reporting, and risk management that create accountability without introducing unnecessary administrative burden.
- Use automation and AI where appropriate to reduce manual project administration, improve reporting, identify risks, and summarize activity, preserving more time for stakeholder engagement and problem solving.
- Keep initiatives moving when responsibility crosses organizational boundaries
but rules only mention
for section headings. I'll stick to
for main sections only. For subsections, I'll use within list items. Let's craft. First, About the role: There are several paragraphs. I'll combine them into a few
tags. Paragraph 1: "Reporting to the Director of Data Strategy & Analytics, the Finance Transformation Project Manager works across four primary areas — Accounting, Financial Operations, Financial Systems, and Data Strategy & Analytics — as well as other business and technology teams as needed. The role builds relationships across these areas, identifies opportunities for improvement, connects the right people and capabilities, and coordinates initiatives that span organizational boundaries. The Chief Financial Officer serves as executive sponsor for the broader Finance transformation portfolio." Paragraph 2: "This role is expected to operate with a high degree of initiative, curiosity, independence, and judgment. The successful candidate will proactively build relationships, ask questions, identify opportunities, and help turn loosely defined problems into structured initiatives. The Director of Data Strategy & Analytics provides leadership, coaching, and guidance, while the Project Manager is expected to take ownership of navigating the organization and moving initiatives forward. Success requires exceptional communication and interpersonal skills, structured problem solving, sound judgment, organizational awareness, and the ability to influence and create momentum without relying on formal authority. The successful candidate will also be comfortable embracing new technology and using modern project-management, collaboration, automation, and AI tools as part of their day-to-day work." Paragraph 3: Company description: "Dewberry is a leading, market-facing professional services firm with more than 60 locations and 2,500 professionals nationwide. What sets us apart from our competitors are our people. At Dewberry, we seek out exceptional talent and strive to deliver the highest quality of services to our clients. Whether you’re an experienced professional or a new graduate, you’ll have the chance to collaborate with the best and brightest and work on innovative and complex projects at the forefront of the industry. Our commitment to excellence stems from our personal integrity and from other defining attributes, which we call “Dewberry at Work,” that have inspired our employees to be successful for more than a half-century." I'll keep these as separate paragraphs. Now Responsibilities: I'll create a
- with three
- items, each containing a for the area title and a nested
- for each area, each containing a nested
- . That's valid HTML. I'll do that.
Similarly for Requirements: there's a list of required items. I'll make a list.
Preferred Experience: list.
What Success Looks Like: list.
Now, remove boilerplate: "At this time, Dewberry will not sponsor a new applicant for work authorization. Dewberry is an Equal Opportunity Employer... Only recipients of an offer..." - remove.
Also remove "Job Description" at start? The posting starts with "Job Description Reporting to the Director..." - that's part of the intro.
Now, write the HTML.
I'll start with
- without nesting. I can nest