Microsoft Dynamics 365 Finance Functional Implementation Manager
Crowe · Burlington, VT · 1 mo ago
$102k–$204k/yrFull-time
We need to produce HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented or summarized away detail. Remove boilerplate (cookie/navigation/legal/EEO etc). Must not include filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes a wage range: $102,400.00 - $204,100.00 per year. So Pay section can be included. Benefits: there is a section "Our Benefits: ..." with description of benefits. So Benefits section can be included. Schedule: there is mention "Flexible work environment with predictable, project-based travel (25%–50%)." That's schedule info (travel). So Schedule can be included.
We need sections: About the role (there is "About The Role" heading). Responsibilities: there is "What You Will Lead And Influence" which is responsibilities. Requirements: there is "Experience That Makes You Successful (Must-Have)" and also "Preferred Experience". Qualifications: maybe combine with Requirements? The instruction says use headings for those categories if content exists. We have qualifications like Bachelors degree required, etc. Could put under Requirements. But we also have "Preferred Experience". Could be under Requirements or Qualifications. We'll decide: Use Requirements for must-have, Preferred maybe also under Requirements or separate? Could create Qualifications for education/certifications. But we must not create thin sections. Let's see content:
- About The Role: paragraph describing role expansion, seeking experienced Microsoft Dynamics 365 Finance Consultant, opportunity to lead solution architecture, influence transformation initiatives, work with finance and ops leaders.
- Responsibilities: "What You Will Lead And Influence": bullet list of duties: architect and lead end-to-end D365 Finance solutions; advise senior stakeholders; set solution direction; lead functional design; participate in quality reviews; contribute to methodologies; engage in team-building.
- Requirements: "Experience That Makes You Successful (Must-Have)": list: Bachelors degree required; 4+ years hands-on D365 Finance implementation leadership or equivalent ERP delivery experience; proven track record delivering complex full-lifecycle D365 Finance projects; strong functional expertise across core finance and operational modules; ability to lead solution architecture; excellent communication skills; demonstrated ability to manage priorities, produce high-quality work products, lead engagements with minimal oversight.
- Preferred Experience: list: Prior consulting experience; manufacturing or distribution environments; metals industry exposure; strong functional expertise across operational modules (Procurement, Inventory, etc.); experience with complementary ISV solutions; D365 certifications; CPA, CMA, CFA a plus.
We could combine both under Requirements (must-have) and maybe a separate "Preferred Qualifications" but not required heading. Since we have headings list includes Qualifications, Skills, Benefits, Pay, Schedule. We could put qualifications under "Qualifications" (education, certifications). Skills could be under "Skills" (communication, critical thinking, etc). But we must not create thin sections. Let's see if we have enough for each.
Qualifications: Bachelors degree required, D365 certifications, CPA/CMA/CFA a plus. That's maybe enough.
Skills: Strong functional expertise across modules, ability to lead solution architecture, excellent communication skills, ability to manage priorities, etc. Could be under Skills.
But we also have "Experience That Makes You Successful (Must-Have)" which is more experience than skills. Could be under Requirements.
We need to avoid duplication. Let's structure:
.
Requirements: we have must-have list. We'll turn each bullet.
Qualifications: we have preferred experience, certifications, education maybe but education already in must-have. We'll include preferred items.
Skills: we have functional expertise, communication, critical thinking, etc.
Benefits: we have the benefits paragraph.
Pay: we have wage range paragraph.
Schedule: we have flexible work environment with travel.
Now we must ensure we don't include filler like "commensurate with experience". Not present.
We must not include duplicated lines. Ensure we don't repeat same bullet.
Let's extract exact text for each piece.
Opening journey paragraph:
"Your Journey at Crowe Starts Here: At Crowe, you can build a meaningful and rewarding career. With real flexibility to balance work with life moments, you’re trusted to deliver results and make an impact. We embrace you for who you are, care for your well-being, and nurture your career. Everyone has equitable access to opportunities for career growth and leadership. Over our 80-year history, delivering excellent service through innovation has been a core part of our DNA across our audit, tax, and consulting groups. That’s why we continuously invest in innovative ideas, such as AI-enabled insights and technology-powered solutions, to enhance our services. Join us at Crowe and embark on a career where you can help shape the future of our industry."
We'll keep as is.
About The Role paragraph:
"Crowe’s Metals & Materials Consulting practice is expanding, and we are seeking an experienced Microsoft Dynamics 365 Finance Consultant to help shape the future of our D365 practice. This role offers the opportunity to lead solution architecture, influence major transformation initiatives, and work directly with finance and operations leaders across manufacturing and distribution organizations. If you want meaningful impact, autonomy, and a clear path to practice leadership, this is a strategic career opportunity—not just another consulting role."
We'll keep.
Responsibilities bullet points from "What You Will Lead And Influence":
- Architect and lead end-to-end D365 Finance solutions that deliver measurable outcomes for mid-market and enterprise clients.
- Advise senior stakeholders, including CFOs and Operations leaders, to define requirements and design transformation roadmaps.
- Set solution direction and guide delivery teams to ensure projects meet scope, quality, and client expectations.
- Lead functional design, feature optimization, data integrity, and user experience improvements to maximize platform value.
- Participate in quality reviews and steer project teams through design, prototyping, and deployment phases.
- Contribute to Crowe’s methodologies, accelerators, and best practices; mentor team members; and support the growth of our D365 offering.
- Engage in team-building and internal initiatives, leveraging non-client time for personal development and practice enhancement.
We'll keep each as .
Requirements (Must-Have) list:
- Bachelors degree required.
- 4+ years of hands-on D365 Finance implementation leadership or equivalent ERP delivery experience.
- Proven track record delivering complex, full-lifecycle D365 Finance projects.
- Strong functional expertise across core finance and operational modules (GL, AP, AR, FA, Cash/Bank, Reporting, etc.).
- Ability to lead
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented or summarized away detail. Remove boilerplate (cookie/navigation/legal/EEO etc). Must not include filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes a wage range: $102,400.00 - $204,100.00 per year. So Pay section can be included. Benefits: there is a section "Our Benefits: ..." with description of benefits. So Benefits section can be included. Schedule: there is mention "Flexible work environment with predictable, project-based travel (25%–50%)." That's schedule info (travel). So Schedule can be included.
We need sections: About the role (there is "About The Role" heading). Responsibilities: there is "What You Will Lead And Influence" which is responsibilities. Requirements: there is "Experience That Makes You Successful (Must-Have)" and also "Preferred Experience". Qualifications: maybe combine with Requirements? The instruction says use headings for those categories if content exists. We have qualifications like Bachelors degree required, etc. Could put under Requirements. But we also have "Preferred Experience". Could be under Requirements or Qualifications. We'll decide: Use Requirements for must-have, Preferred maybe also under Requirements or separate? Could create Qualifications for education/certifications. But we must not create thin sections. Let's see content:
- About The Role: paragraph describing role expansion, seeking experienced Microsoft Dynamics 365 Finance Consultant, opportunity to lead solution architecture, influence transformation initiatives, work with finance and ops leaders.
- Responsibilities: "What You Will Lead And Influence": bullet list of duties: architect and lead end-to-end D365 Finance solutions; advise senior stakeholders; set solution direction; lead functional design; participate in quality reviews; contribute to methodologies; engage in team-building.
- Requirements: "Experience That Makes You Successful (Must-Have)": list: Bachelors degree required; 4+ years hands-on D365 Finance implementation leadership or equivalent ERP delivery experience; proven track record delivering complex full-lifecycle D365 Finance projects; strong functional expertise across core finance and operational modules; ability to lead solution architecture; excellent communication skills; demonstrated ability to manage priorities, produce high-quality work products, lead engagements with minimal oversight.
- Preferred Experience: list: Prior consulting experience; manufacturing or distribution environments; metals industry exposure; strong functional expertise across operational modules (Procurement, Inventory, etc.); experience with complementary ISV solutions; D365 certifications; CPA, CMA, CFA a plus.
We could combine both under Requirements (must-have) and maybe a separate "Preferred Qualifications" but not required heading. Since we have headings list includes Qualifications, Skills, Benefits, Pay, Schedule. We could put qualifications under "Qualifications" (education, certifications). Skills could be under "Skills" (communication, critical thinking, etc). But we must not create thin sections. Let's see if we have enough for each.
Qualifications: Bachelors degree required, D365 certifications, CPA/CMA/CFA a plus. That's maybe enough.
Skills: Strong functional expertise across modules, ability to lead solution architecture, excellent communication skills, ability to manage priorities, etc. Could be under Skills.
But we also have "Experience That Makes You Successful (Must-Have)" which is more experience than skills. Could be under Requirements.
We need to avoid duplication. Let's structure:
About the role
... (the paragraph)
Responsibilities
- ... each duty
Requirements
- ... must-have items
Preferred Qualifications
(but not in allowed list; allowed list includes Qualifications, Skills, Benefits, Pay, Schedule. "Preferred Qualifications" not allowed; we could put under Qualifications or Skills. Perhaps better to put under Qualifications (includes education, certifications, preferred experience). But we also have Skills heading. Let's decide: Use Qualifications for education/certifications/preferred experience. Use Skills for functional expertise, communication, critical thinking, leadership. Thus:Qualifications
- Bachelor’s degree required.
- D365 certifications in Finance or related modules; CPA, CMA, or CFA a plus.
- Preferred experience in Manufacturing or Distribution environments; Metals industry exposure highly valued.
- Experience with complementary ISV solutions within the D365 ecosystem.
- Prior consulting experience within a professional services environment.
Skills
- Strong functional expertise across core finance and operational modules (GL, AP, AR, FA, Cash/Bank, Reporting, etc.).
- Strong functional expertise across operational modules (Procurement, Inventory, etc.).
- Ability to lead solution architecture, translate requirements into actionable designs, and guide teams through execution.
- Excellent communication skills with experience engaging C‑suite and director‑level stakeholders.
- Demonstrated ability to manage priorities, produce high‑quality work products, and lead engagements with minimal oversight.
- Advanced critical thinking and growth mindset.
maybe. Pay: we have wage range: $102,400.00 - $204,100.00 per year. Also note about range not adjusted for geographic differential etc. We'll include that as
. Schedule: "Flexible work environment with predictable, project-based travel (25%–50%)." We'll put as
. We must not include boilerplate like EEO, legal, etc. Must remove those paragraphs. We need to ensure we preserve all substantive information. Let's extract substantive paragraphs from the posting: - Opening paragraph about journey at Crowe: "Your Journey at Crowe Starts Here: At Crowe, you can build a meaningful and rewarding career. With real flexibility to balance work with life moments, you’re trusted to deliver results and make an impact. We embrace you for who you are, care for your well-being, and nurture your career. Everyone has equitable access to opportunities for career growth and leadership. Over our 80-year history, delivering excellent service through innovation has been a core part of our DNA across our audit, tax, and consulting groups. That’s why we continuously invest in innovative ideas, such as AI-enabled insights and technology-powered solutions, to enhance our services. Join us at Crowe and embark on a career where you can help shape the future of our industry." That's substantive but maybe considered generic marketing; but it's part of posting. Should we include? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep it. However, we need to fit into sections. There's no specific heading for that; maybe we can include it under About the role? But About the role already has a heading. Could we add a paragraph before About the role? The instruction says use