Senior Power Platform Functional Consultant

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Qualifications?), Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove generic fluff like "Your Journey at Crowe Starts Here" maybe considered boilerplate? It's part of description but not specific to role? It's generic company marketing. Probably we should keep only job description content. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep the substantive parts: About the role paragraph, responsibilities list, basic qualifications, preferred skills, what success looks like (maybe could be part of responsibilities or separate? Could be a section like "What Success Looks Like" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content accordingly. We have: - About the role: paragraph after "About the role:" includes description of Senior Power Platform Functional Consultant role. - Responsibilities: bullet list after "The Senior Power Platform Functional Consultant will perform the following responsibilities:" includes many items. - Basic Qualifications: list after "Basic Qualifications:" includes Bachelor's degree required, 4+ years experience, hands-on experience with Microsoft D365 and/or Power Platform preferred, strong writing and interpersonal communication skills, ability to handle multiple projects concurrently, availability to work Pacific Time. - Preferred Skills: list after "Preferred Skills:" includes Microsoft D365, Power Platform, or AI certifications, public-sector/government/regulated industry experience, experience working in Agile/Scrum, experience mentoring or reviewing work of junior staff. - What Success Looks Like: could be considered part of Responsibilities or maybe a separate section but not in allowed headings. Could be omitted? But we must preserve ALL substantive information. If we cannot create a heading not in list, we could incorporate that content into existing sections, maybe under Responsibilities or a new "Qualifications"? But "What Success Looks Like" is more about expectations, could be placed under "Responsibilities" as additional bullet points? However it's not a responsibility but success criteria. Could be placed under "Requirements" maybe? But better to add a section "What Success Looks Like" is not allowed; we must not create headings outside allowed list. So we need to embed that content somewhere else, maybe under "Responsibilities" as additional bullet points, or under "Qualifications" as extra bullet. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should only use those headings? It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect we use those exact headings when appropriate. It doesn't forbid other headings, but says use h3 for section headings (e.g. list). Probably we should stick to those. So we need to fit all content into those sections. We have Benefits: paragraph after "Our Benefits:" includes description of benefits but not specific list. It says "Our Benefits: Your exceptional people experience starts here.... We care about our people and offer employees a comprehensive total rewards package. Learn more about what working at Crowe can mean for you!" That's vague, no specific benefits listed. According to rule: never create Benefits section unless posting actually states them. It does state they offer a comprehensive total rewards package but not specifics. Might be considered not specific enough? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state they offer benefits, but not details. Might be considered stating them (they say they offer a comprehensive total rewards package). However they also say "Learn more about what working at Crowe can mean for you!" which is a link. This is vague. I'd argue we should not create a Benefits section because no concrete benefits listed. But we could include a short paragraph under Benefits if we want to preserve the statement. The rule: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The benefits statement is vague but not placeholder like "commensurate with experience". It's a statement that they offer benefits. Might be considered real content. I'd include a Benefits section with that paragraph. Pay: they give wage range: $83,300.00 - $164,900.00 per year. That's specific. So we should include Pay section. Schedule: not mentioned. No schedule info. So we should not include Schedule. Now we need to output HTML fragment only, no /, no markdown fences. We'll structure:

About the role

... paragraph ...

Responsibilities

• ...
...

Requirements

Maybe we put Basic Qualifications under Requirements. Or we could have Requirements and Qualifications separate. The basic qualifications are requirements. Preferred skills could be under Skills. So:

Requirements

• Bachelor's degree required.
• 4+ years of relevant experience in business analysis, software implementation, digital transformation, or related technology consulting.
• Hands-on experience with Microsoft Dynamics 365 and/or Power Platform preferred.
• Strong writing and interpersonal communication skills.
• Ability to handle multiple projects concurrently.
• Availability to work Pacific Time.

Skills

• 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

We also have "What Success Looks Like" content. Where to put? Could be under Responsibilities as additional bullet points, or maybe under Requirements as expectations. I'd add as bullet points under Responsibilities (makes sense). Let's extract that paragraph: "What Success Looks Like: A successful Senior Power Platform Functional Consultant is able to independently lead client discovery and functional design activities, convert ambiguous business needs into well-defined solution requirements, use AI-first tools to configure sophisticated business capabilities, and provide clear direction to both client stakeholders and technical team members. The individual will consistently produce high-quality work, anticipate and communicate delivery risks, contribute reusable knowledge to the EI&A practice, support the development of junior staff, and help clients implement Microsoft solutions that are usable, maintainable, and aligned with their business objectives. 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." We can add these as bullet points under Responsibilities (or maybe a separate section but not allowed). I'll add as bullet points under Responsibilities after the existing responsibilities list. Now Benefits: we have paragraph: "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: ..." That's a lot of fluff. The substantive part: "We care about our people and offer employees a comprehensive total rewards package." Also "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." That's about growth. Might be considered benefits? It's more about development. Could be placed under Benefits? But we have no specific benefits like health insurance etc. The rule: only create Benefits if posting actually states them. It does state they offer a comprehensive total rewards package and mention career coach. That's somewhat specific. I'd include a Benefits section with those statements. Pay: we have wage range. Now we need to remove boilerplate: The initial fluff "Your Journey at Crowe Starts Here: ..." and many paragraphs about Crowe's history, innovation, etc. Also the "In compliance with federal law..." etc. Also the EEO statements, etc. Also the "Crowe is not sponsoring for work authorization at this time." etc. Also the "Please visit our webpage..." etc. Also the "As independent members..." etc. Also the "Crowe LLP and Crowe Advisory LLC..." etc. All that is boilerplate/legal/EEO. Must remove. We must preserve all substantive information: that includes the role description, responsibilities, qualifications, skills, success looks like, benefits, pay. Also maybe the "Availability to work Pacific Time." is a requirement. Now we need to ensure we don't repeat job title as heading. The job title is "Senior Power Platform Functional Consultant". We must not put that as heading. We already didn't. Now produce HTML. Let's craft the About the role paragraph: combine the two paragraphs after "About the role:" up to before responsibilities. Original: "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." We'll put that in

. Now Responsibilities list: items: - Lead client discovery, requirements, and solution design sessions. - Translate business objectives into clear user stories, functional requirements, process flows, and solution designs. - Configuring Microsoft D365 and Power Platform functionality to implement business-driven forms, entities, view, relationships, business rules, and workflows. - Serve as the functional liaison between client stakeholders and technical teams, ensuring business needs are accurately reflected in the solution. - Analyze business processes and recommend practical opportunities for improvement, automation, and application of AI. - Develop and execute functional testing, support User Acceptance Testing, and ensure solutions align with approved requirements. - Manage assigned functional workstreams, including deliverables, timelines, dependencies, risks, and communication with project leadership. - Use approved AI tools throughout project delivery to improve the quality, speed, and effectiveness of analysis, documentation, configuration, and testing. - Support client adoption through demonstrations, training, knowledge transfer, and clear documentation. Then add success looks like bullets: - Independently lead client discovery and functional design activities. - Convert ambiguous business needs into well-defined solution requirements. - Use AI-first tools to configure sophisticated business capabilities. - Provide clear direction to both client stakeholders and technical team members. - Consistently produce high-quality work. - Anticipate and communicate delivery risks. - Contribute reusable knowledge to the EI&A practice. - Support the development of junior staff. -