Senior Power Platform Functional Consultant
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info; remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the job posting content.
Key sections:
- Intro paragraph: "Your Journey at Crowe Starts Here: ..." up to "Join us at Crowe and embark on a career where you can help shape the future of our industry." This is general description; could be placed as a
before sections.
- "Job Description: What It Means To Be a Consultant ..." This is a description of consultant role. Could be part of "About the role" or separate? The posting includes "About the role:" heading later. The earlier part is generic consultant description; we could treat it as part of "About the role" or maybe as a separate "Overview". But we need to follow headings: we can have
About the role
and include the content from both the generic consultant description and the specific Senior Power Platform Functional Consultant description.
- Responsibilities: The bullet list after "The Senior Power Platform Functional Consultant will perform the following responsibilities:" includes items: Lead client discovery..., Translate..., Configuring..., Serve..., Analyze..., Develop..., Manage..., Use..., Support... That's a list.
- Basic Qualifications: list: Bachelor's degree required. 4+ years of relevant experience... Hands-on experience... Strong writing... Ability to handle multiple projects concurrently. Availability to work Pacific Time.
- Preferred Skills: list: Microsoft D365, Power Platform, or AI certifications; Public-sector, government, or other highly regulated industry experience; Experience working in Agile/Scrum software-delivery environments; Experience mentoring or reviewing the work of junior staff.
- What Success Looks Like: description paragraph; could be part of "Responsibilities" or separate "Expectations". Might be considered as part of role description; but we can include as a separate section maybe "Success Profile". However headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "What Success Looks Like" could be considered part of Responsibilities or maybe "Requirements". But we can incorporate into Responsibilities or About the role. The instruction: Prefer a few substantive sections over many thin ones. So we could combine "What Success Looks Like" into About the role or Responsibilities.
- Values paragraph: "We expect the candidate to uphold Crowe’s values..." This is values; could be part of About the role or maybe omitted as boilerplate? It's substantive but not a list. Could be included in About the role.
- Application deadline: "The application deadline for this role is 09/23/2027." This is metadata; we could fold into a short maybe under About the role or separate? Not a heading.
- Work authorization statement: "In compliance with federal law..." etc. That's boilerplate legal; should be removed per instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So remove that.
- Wage range: "The wage range for this role takes into account..." and "A reasonable estimate of the current range is $83,300.00 - $164,900.00 per year." This is Pay info; we should include a Pay section with that range. However instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state wage range, so we can include Pay section.
- Benefits: "Our Benefits: Your exceptional people experience starts here..." then description about benefits, career coach, etc. This is Benefits section; we should include Benefits heading with that content.
- Schedule: Not mentioned; no schedule info. So we should not create Schedule section.
- Requirements: Could be Basic Qualifications; we could have Requirements heading with Basic Qualifications. Or Qualifications heading. The allowed headings include Requirements and Qualifications. We need to decide. Usually Requirements = basic qualifications; Qualifications = preferred skills? But we have both Basic Qualifications and Preferred Skills. Could map Basic Qualifications to Requirements, Preferred Skills to Skills. Or we could have Qualifications for both basic and preferred. But we have separate headings: Requirements, Qualifications, Skills. We need to use them appropriately.
We have Basic Qualifications (mandatory) and Preferred Skills (preferred). Could put Basic Qualifications under
Requirements
and Preferred Skills under Skills
. Or we could put Basic Qualifications under Qualifications and Preferred Skills under Skills. The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose.
We need to avoid filler/placeholder text. Ensure we don't create sections with only generic placeholder like "commensurate with experience". We have real content.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the posting, except boilerplate removed.
We need to output only HTML fragment, no /, no markdown fences.
Thus final HTML will have series of headings with
or
- as appropriate.
Let's extract content precisely.
Intro paragraph (before Job Description):
"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 can keep that as a
(maybe as an intro). Not a heading.
Then "Job Description: What It Means To Be a Consultant At Crowe Consulting is a dynamic business focused on solving problems for our clients and serving our core markets through innovative solutions. As technology and AI continue to reshape the consulting landscape, we are looking for individuals who are curious, adaptable, and eager to learn. At Crowe, consultants are expected to build both technical and transferable skills, think critically, and use technology to solve real business problems. In this role, you will continuously learn, collaborate across teams, and explore how tools, including emerging AI capabilities, can improve efficiency, insights, and client outcomes. As you grow, you’ll also begin to take ownership of client relationships, contribute to account strategy, and support the delivery of high-impact work. Developing a sense of account leadership, including understanding client needs, ensuring delivery excellence, and building trusted partnerships, is part of what sets successful consultants apart. Success in this role comes from a growth mindset, strong communication skills, advanced critical thinking, and the ability to navigate new challenges with confidence."
We can incorporate this into About the role.
Then "About the role: The Senior Power Platform Functional Consultant will combine strong business analysis, consulting, and Microsoft technology skills to help clients improve business processes and solve complex operational challenges through digital innovation and automation. As a member of Crowe's Enterprise Innovation & Automation (EI&A) team, the Senior Functional Consultant will work as part of cross-functional teams of Crowe and client resources to design and implement business solutions using AI-first automation solutions on Microsoft Dynamics 365, Power Platform, and related Microsoft technologies. This role is intended for an experienced functional consultant who can independently lead requirements and design activities, translate business objectives into actionable solution requirements, configure sophisticated D365 and Power Platform solutions, manage functional workstreams, and serve as a trusted liaison between client stakeholders and technical delivery teams. The Senior Power Platform Functional Consultant will perform the following responsibilities:"
Then list responsibilities.
After responsibilities list, we have "Basic Qualifications:" then list.
Then "Preferred Skills:" then list.
Then "What Success Looks Like:" paragraph.
Then "We expect the candidate to uphold Crowe’s values of Care, Trust, Courage, and Stewardship. These values define who we are. We expect all of our people to act ethically and with integrity at all times."
Then "The application deadline for this role is 09/23/2027." (keep as short p)
Then "In compliance with federal law..." (remove boilerplate)
Then "Crowe is not sponsoring for work authorization at this time." (maybe also boilerplate? It's about work authorization; could be considered legal; but it's a statement about sponsorship. Might be considered boilerplate; but it's substantive? It's about work authorization; could be kept as short p? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is legal/work authorization; likely considered boilerplate. Safer to remove.
Then "The wage range for this role takes into account the wide range of factors that are considered in making compensation decisions including but not limited to skill sets; experience and training; licensure and certifications; and other business and organizational needs. The disclosed range estimate has not been adjusted for the applicable geographic differential associated with the location at which the position may be filled. At Crowe, it is not typical for an individual to be hired at or near the top of the range for their role and compensation decisions are dependent on the facts and circumstances of each case. A reasonable estimate of the current range is $83,300.00 - $164,900.00 per year."
We need to keep the wage range info; we can summarize as a
under Pay section: "The wage range for this role is estimated at $83,300.00 - $164,900.00 per year." But we must preserve ALL substantive information; we cannot summarize away detail? The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." Summarizing might be considered summarizing away detail? However we can keep the full sentences but maybe we can keep them as is. The instruction about Pay section: we should not create Pay section unless posting actually states them. It does state wage range; we can include the full text as a
under Pay.
But we might need to keep the explanation about factors, geographic differential, not typical to hire at top, etc. That's substantive. So we should keep it.
Thus Pay section
containing that paragraph.
Then "Our Benefits: Your exceptional people experience starts here. At Crowe, we know that great people are what makes a great firm. We care about our people and offer employees a comprehensive total rewards package. Learn more about what working at Crowe can mean for you! How You Can Grow: We will nurture your talent in an inclusive culture that values diversity. You will have the chance to meet on a consistent basis with your Career Coach that will guide you in your career goals and aspirations. Learn more about where talent can prosper! More about Crowe: Crowe provides professional services through two separate entities: Crowe LLP delivers audit and attest services, and Crowe Advisory LLC provides tax, advisory, consulting, and other nonattest services. The Crowe Global network consists of more than 300 independent accounting and advisory services firms in more than 150 countries around the globe, making it one of the largest accounting networks
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info; remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the job posting content. Key sections: - Intro paragraph: "Your Journey at Crowe Starts Here: ..." up to "Join us at Crowe and embark on a career where you can help shape the future of our industry." This is general description; could be placed as a
before sections. - "Job Description: What It Means To Be a Consultant ..." This is a description of consultant role. Could be part of "About the role" or separate? The posting includes "About the role:" heading later. The earlier part is generic consultant description; we could treat it as part of "About the role" or maybe as a separate "Overview". But we need to follow headings: we can have
About the role
and include the content from both the generic consultant description and the specific Senior Power Platform Functional Consultant description. - Responsibilities: The bullet list after "The Senior Power Platform Functional Consultant will perform the following responsibilities:" includes items: Lead client discovery..., Translate..., Configuring..., Serve..., Analyze..., Develop..., Manage..., Use..., Support... That's a list. - Basic Qualifications: list: Bachelor's degree required. 4+ years of relevant experience... Hands-on experience... Strong writing... Ability to handle multiple projects concurrently. Availability to work Pacific Time. - Preferred Skills: list: Microsoft D365, Power Platform, or AI certifications; Public-sector, government, or other highly regulated industry experience; Experience working in Agile/Scrum software-delivery environments; Experience mentoring or reviewing the work of junior staff. - What Success Looks Like: description paragraph; could be part of "Responsibilities" or separate "Expectations". Might be considered as part of role description; but we can include as a separate section maybe "Success Profile". However headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "What Success Looks Like" could be considered part of Responsibilities or maybe "Requirements". But we can incorporate into Responsibilities or About the role. The instruction: Prefer a few substantive sections over many thin ones. So we could combine "What Success Looks Like" into About the role or Responsibilities. - Values paragraph: "We expect the candidate to uphold Crowe’s values..." This is values; could be part of About the role or maybe omitted as boilerplate? It's substantive but not a list. Could be included in About the role. - Application deadline: "The application deadline for this role is 09/23/2027." This is metadata; we could fold into a shortmaybe under About the role or separate? Not a heading. - Work authorization statement: "In compliance with federal law..." etc. That's boilerplate legal; should be removed per instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So remove that. - Wage range: "The wage range for this role takes into account..." and "A reasonable estimate of the current range is $83,300.00 - $164,900.00 per year." This is Pay info; we should include a Pay section with that range. However instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state wage range, so we can include Pay section. - Benefits: "Our Benefits: Your exceptional people experience starts here..." then description about benefits, career coach, etc. This is Benefits section; we should include Benefits heading with that content. - Schedule: Not mentioned; no schedule info. So we should not create Schedule section. - Requirements: Could be Basic Qualifications; we could have Requirements heading with Basic Qualifications. Or Qualifications heading. The allowed headings include Requirements and Qualifications. We need to decide. Usually Requirements = basic qualifications; Qualifications = preferred skills? But we have both Basic Qualifications and Preferred Skills. Could map Basic Qualifications to Requirements, Preferred Skills to Skills. Or we could have Qualifications for both basic and preferred. But we have separate headings: Requirements, Qualifications, Skills. We need to use them appropriately. We have Basic Qualifications (mandatory) and Preferred Skills (preferred). Could put Basic Qualifications under
Requirements
and Preferred Skills underSkills
. Or we could put Basic Qualifications under Qualifications and Preferred Skills under Skills. The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose.
We need to avoid filler/placeholder text. Ensure we don't create sections with only generic placeholder like "commensurate with experience". We have real content.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the posting, except boilerplate removed.
We need to output only HTML fragment, no /, no markdown fences.
Thus final HTML will have series of headings with
or
- as appropriate.
Let's extract content precisely.
Intro paragraph (before Job Description):
"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 can keep that as a
(maybe as an intro). Not a heading. Then "Job Description: What It Means To Be a Consultant At Crowe Consulting is a dynamic business focused on solving problems for our clients and serving our core markets through innovative solutions. As technology and AI continue to reshape the consulting landscape, we are looking for individuals who are curious, adaptable, and eager to learn. At Crowe, consultants are expected to build both technical and transferable skills, think critically, and use technology to solve real business problems. In this role, you will continuously learn, collaborate across teams, and explore how tools, including emerging AI capabilities, can improve efficiency, insights, and client outcomes. As you grow, you’ll also begin to take ownership of client relationships, contribute to account strategy, and support the delivery of high-impact work. Developing a sense of account leadership, including understanding client needs, ensuring delivery excellence, and building trusted partnerships, is part of what sets successful consultants apart. Success in this role comes from a growth mindset, strong communication skills, advanced critical thinking, and the ability to navigate new challenges with confidence." We can incorporate this into About the role. Then "About the role: The Senior Power Platform Functional Consultant will combine strong business analysis, consulting, and Microsoft technology skills to help clients improve business processes and solve complex operational challenges through digital innovation and automation. As a member of Crowe's Enterprise Innovation & Automation (EI&A) team, the Senior Functional Consultant will work as part of cross-functional teams of Crowe and client resources to design and implement business solutions using AI-first automation solutions on Microsoft Dynamics 365, Power Platform, and related Microsoft technologies. This role is intended for an experienced functional consultant who can independently lead requirements and design activities, translate business objectives into actionable solution requirements, configure sophisticated D365 and Power Platform solutions, manage functional workstreams, and serve as a trusted liaison between client stakeholders and technical delivery teams. The Senior Power Platform Functional Consultant will perform the following responsibilities:" Then list responsibilities. After responsibilities list, we have "Basic Qualifications:" then list. Then "Preferred Skills:" then list. Then "What Success Looks Like:" paragraph. Then "We expect the candidate to uphold Crowe’s values of Care, Trust, Courage, and Stewardship. These values define who we are. We expect all of our people to act ethically and with integrity at all times." Then "The application deadline for this role is 09/23/2027." (keep as short p) Then "In compliance with federal law..." (remove boilerplate) Then "Crowe is not sponsoring for work authorization at this time." (maybe also boilerplate? It's about work authorization; could be considered legal; but it's a statement about sponsorship. Might be considered boilerplate; but it's substantive? It's about work authorization; could be kept as short p? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is legal/work authorization; likely considered boilerplate. Safer to remove. Then "The wage range for this role takes into account the wide range of factors that are considered in making compensation decisions including but not limited to skill sets; experience and training; licensure and certifications; and other business and organizational needs. The disclosed range estimate has not been adjusted for the applicable geographic differential associated with the location at which the position may be filled. At Crowe, it is not typical for an individual to be hired at or near the top of the range for their role and compensation decisions are dependent on the facts and circumstances of each case. A reasonable estimate of the current range is $83,300.00 - $164,900.00 per year." We need to keep the wage range info; we can summarize as a
under Pay section: "The wage range for this role is estimated at $83,300.00 - $164,900.00 per year." But we must preserve ALL substantive information; we cannot summarize away detail? The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." Summarizing might be considered summarizing away detail? However we can keep the full sentences but maybe we can keep them as is. The instruction about Pay section: we should not create Pay section unless posting actually states them. It does state wage range; we can include the full text as a
under Pay. But we might need to keep the explanation about factors, geographic differential, not typical to hire at top, etc. That's substantive. So we should keep it. Thus Pay section
containing that paragraph. Then "Our Benefits: Your exceptional people experience starts here. At Crowe, we know that great people are what makes a great firm. We care about our people and offer employees a comprehensive total rewards package. Learn more about what working at Crowe can mean for you! How You Can Grow: We will nurture your talent in an inclusive culture that values diversity. You will have the chance to meet on a consistent basis with your Career Coach that will guide you in your career goals and aspirations. Learn more about where talent can prosper! More about Crowe: Crowe provides professional services through two separate entities: Crowe LLP delivers audit and attest services, and Crowe Advisory LLC provides tax, advisory, consulting, and other nonattest services. The Crowe Global network consists of more than 300 independent accounting and advisory services firms in more than 150 countries around the globe, making it one of the largest accounting networks