Microsoft Power Platform Senior Technical Consultant

We need to output HTML fragment with sections: About the role? The posting includes description of responsibilities etc. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes responsibilities (the bullet list of expectations), requirements/qualifications (Bachelor's degree etc), skills (maybe "You're great at..."), benefits (Benefits section). Pay: they mention "competitive pay with and performance-based bonus." That's vague but they mention competitive pay and performance-based bonus. That is specific enough? It says "competitive pay with and performance-based bonus." It's a bit awkward but indicates pay. Should we include Pay section? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. They do state pay: "competitive pay with and performance-based bonus." So we can include Pay section with that sentence. Schedule: not mentioned, so omit. We need to remove boilerplate like EEO etc. Also remove "HSO is an Equal Opportunity Employer." Also remove "Sound interesting? If so, you’ll have…" maybe part of qualifications? Actually that leads into qualifications. We'll keep qualifications. We need to preserve all substantive info. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to decide sections: About the role (maybe intro paragraph), Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay. Could combine Requirements and Qualifications? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include. Probably include About the role (short intro), Responsibilities (the bullet list of expectations), Requirements (education/experience etc), Skills (You're great at...), Benefits, Pay. We must not repeat job title as heading. So no heading for Platform Senior Technical Consultant. We need to output only HTML fragment. Let's extract content. Intro: "As a Platform Senior Technical Consultant you can expect to…" then list of expectations (multiple sentences). That's responsibilities. We can put About the role: maybe a brief paragraph summarizing role? Could use the first sentence as About the role: "As a Platform Senior Technical Consultant you can expect to work as a core member of delivery teams on large, complex client engagements, or serve as the technical lead on smaller or more focused implementations". But that's part of responsibilities. However we can still have About the role as a short paragraph: maybe combine first two sentences? But we must not invent content. We'll keep About the role as a paragraph that includes the introductory sentence(s) before the bullet list? The original text: "As a Platform Senior Technical Consultant you can expect to… Work as a core member of delivery teams on large, complex client engagements, or serve as the technical lead on smaller or more focused implementationsTake end-to-end responsibility for the delivery of technical capabilities at the solution, feature, and user story levelServe, based on engagement needs, as:Lead Developer, designing and supervising the development of Power Platform solutionsSolution Developer, building high-quality applications, automations, and integrationsTechnical Consultant, advising on enterprise platform topics such as governance, security, ALM, architecture, and user empowermentDesign, build, and deliver Power Platform solutions including Power Apps (canvas and model-driven), Power Automate, Dataverse, and related Azure servicesTranslate business and functional requirements into scalable, secure, and maintainable technical designsCollaborate closely with functional consultants, solution architects, and client stakeholders to ensure solutions align with business goals and platform best practicesSupport client-facing consulting services including cloud assessments, technical workshops, and co-design sessionsEnsure adherence to Power Platform best practices, security standards, governance models, and compliance requirementsGuide clients through application lifecycle management (ALM), environment strategy, and deployment pipelinesContribute to successful solution adoption through technical enablement, documentation, and knowledge transferContinuously develop and deepen your technical expertise and share knowledge internally through mentoring, best practices, reusable assets, and intellectual property" That's a long run-on. We can split into bullet list for responsibilities. Thus About the role could be a short paragraph: maybe "As a Platform Senior Technical Consultant, you will work as a core member of delivery teams on large, complex client engagements or serve as the technical lead on smaller implementations." That's derived from the text. It's not invented; it's directly from the text. Good. Then Responsibilities: list bullet items. Let's extract bullet items from that block: - Work as a core member of delivery teams on large, complex client engagements, or serve as the technical lead on smaller or more focused implementations - Take end-to-end responsibility for the delivery of technical capabilities at the solution, feature, and user story level - Serve, based on engagement needs, as: - Lead Developer, designing and supervising the development of Power Platform solutions - Solution Developer, building high-quality applications, automations, and integrations - Technical Consultant, advising on enterprise platform topics such as governance, security, ALM, architecture, and user empowerment - Design, build, and deliver Power Platform solutions including Power Apps (canvas and model-driven), Power Automate, Dataverse, and related Azure services - Translate business and functional requirements into scalable, secure, and maintainable technical designs - Collaborate closely with functional consultants, solution architects, and client stakeholders to ensure solutions align with business goals and platform best practices - Support client-facing consulting services including cloud assessments, technical workshops, and co-design sessions - Ensure adherence to Power Platform best practices, security standards, governance models, and compliance requirements - Guide clients through application lifecycle management (ALM), environment strategy, and deployment pipelines - Contribute to successful solution adoption through technical enablement, documentation, and knowledge transfer - Continuously develop and deepen your technical expertise and share knowledge internally through mentoring, best practices, reusable assets, and intellectual property We need to format as

  • . For nested list (Serve, based on engagement needs, as: with subitems) we can either keep as a single li with sub-ul. That's okay. Now Requirements/Qualifications: The posting says: "You’ll have… Bachelor's degree in Computer Science, Information Systems, or a related field (or equivalent work experience) 4+ years of technical experience in consulting or customer settings working with Microsoft Cloud technologies such as Power Platform or Dynamics 365 CE, Azure, or Microsoft 365 application development, integration, and / or infrastructure solutions A strong sense of ownership, autonomy, and accountability for your work The ability to work independently, translate goals into action, and own outcomes while collaborating effectively with others A passion for Microsoft cloud technologies, particularly Power Platform, Azure, and Microsoft 365 Strong client-facing skills, empathy, and the ability to guide clients through ambiguity and complex challenges Demonstrated experience delivering production-grade Power Platform solutions, including Canvas and model-driven apps, Power Automate flows, Integrations using connectors, APIs, or custom services The drive and self-sufficiency to work independently, translate goals into action, own the success of your area of work, support and seek support from colleagues when needed" We can split into Requirements (education, experience) and Qualifications (soft skills). But we can just have one Requirements section with bullet list. Let's create bullet list: - Bachelor's degree in Computer Science, Information Systems, or a related field (or equivalent work experience) - 4+ years of technical experience in consulting or customer settings working with Microsoft Cloud technologies such as Power Platform or Dynamics 365 CE, Azure, or Microsoft 365 application development, integration, and/or infrastructure solutions - Strong sense of ownership, autonomy, and accountability for your work - Ability to work independently, translate goals into action, and own outcomes while collaborating effectively with others - Passion for Microsoft cloud technologies, particularly Power Platform, Azure, and Microsoft 365 - Strong client-facing skills, empathy, and the ability to guide clients through ambiguity and complex challenges - Demonstrated experience delivering production-grade Power Platform solutions, including Canvas and model-driven apps, Power Automate flows, integrations using connectors, APIs, or custom services - Drive and self-sufficiency to work independently, translate goals into action, own the success of your area of work, support and seek support from colleagues when needed Now Skills: "You’re great at…" list: - Working closely with clients to understand their pain points, challenges, and goals - Gathering important information through requirements gathering, participating or conducting workshops and interviews with key stakeholders to gather and document detailed business requirements, ensuring a clear understanding of client needs - Developing strong technical, analytical, presentation, documentation, and communication skills - Building trusted relationships with clients, partners, and internal stakeholders - Prioritizing work, managing dependencies, and clearly communicating commitments - Working effectively in highly collaborative, cross-functional teams - Solving complex technical and business problems with creative, pragmatic solutions - Learning new technologies and concepts quickly and applying them effectively - Coaching and mentoring other consultants and developers to raise overall delivery quality - Developing your own technical expertise, and share that expertise with your colleagues as a mentor or producer of best practices and intellectual property - When asked, providing technical pre-sales support to sellers and their clients when needed (e.g. technical presentations to clients, development and presentation of demos, preparation of design and proposal documentation, etc.); note this is not the primary job function, and pre-sales assignments will be made based on technical expertise required by the pursuit - Working in a highly collaborative team environment, solving complex problems with creative solutions - Promoting the mission and Shared Values of our company We can keep as bullet list. Benefits: The posting says: "Benefits We offer competitive pay with and performance-based bonus. Our employees also enjoy unlimited paid time off and a flexible and affordable benefits program designed to help you be and stay well, including: medical, dental & vision coverage, flexible spending accounts, health reimbursement account, and a 401(k) plan with a company match. Additionally, you’ll have the benefit of working alongside enthusiastic and energetic teammates in a dynamic and thriving environment." We need Benefits section: list bullet items. - Competitive pay with performance-based bonus - Unlimited paid time off - Flexible and affordable benefits program including: - Medical, dental & vision coverage - Flexible spending accounts - Health reimbursement account - 401(k) plan with company match - Working alongside enthusiastic and energetic teammates in a dynamic and thriving environment Pay section: The posting also mentions pay in Benefits but we already have pay in benefits. However rule says create Pay section only if posting actually states them. It does state competitive pay with performance-based bonus. We could still include Pay section with that sentence, but we already have it in Benefits. To avoid duplication, maybe we include Pay section with that sentence and Benefits section without pay? But the Benefits paragraph includes pay as part of benefits. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine pay into Benefits and not create separate Pay section. However they said never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits, so we can have Benefits section. Pay is also stated but we could omit Pay section to avoid thin section. I'd combine pay into Benefits. Thus we will have sections: About the role, Responsibilities, Requirements, Skills, Benefits. We need to use

    for each section heading. Let's craft HTML. We'll output:

    About the role

    As a Platform Senior Technical Consultant, you will work as a core member of delivery teams on large, complex client engagements or serve as the technical lead on smaller implementations.

    Responsibilities

    • Work as a core member of delivery teams on large, complex client engagements, or serve as the technical lead on smaller or more focused implementations
    • Take end-to-end responsibility for the delivery of technical capabilities at the solution, feature, and user story level
    • Serve, based on engagement needs, as: