Sr. Practice Architect, Cloud

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. First, there is a preamble: "Why You’ll Love Softchoice ..." which is about company culture. Could be "About the role"? Actually "Why You’ll Love Softchoice" is about company. Could be "About the role"? Not exactly. The posting includes sections: "The Impact You Will Have", "What You'll Do", "What You'll Bring To The Table", "Compensation", "Why You’ll Love Working Here", "Inclusion & Equal Opportunity Employment", "Our Commitment To Your Experience", "Job Requisition ID". Also there is "Compensation" with pay range. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. - About the role: Could be "The Impact You Will Have" and maybe "Why You’ll Love Softchoice"? But "About the role" likely describes the role. The posting includes "The Impact You Will Have" describing role impact. Also "What You'll Do" is responsibilities. So we can put About the role as a summary of role impact. Use content from "The Impact You Will Have". Also maybe include "Why You’ll Love Softchoice"? That's more about company, not role. Probably not needed. - Responsibilities: from "What You'll Do". That's a list of bullet points (though not bullet formatted but paragraphs). We need to extract list items. The text includes multiple paragraphs each starting with a bold heading? Actually they are headings like "Technical Leadership & Expertise", "Methodology & Best Practice Development", etc. Each has sentences. We can treat each as a list item? The instruction: Use

• for any list of duties/requirements/benefits. So we need to convert duties into list items. We can break each duty paragraph into a
• . Might be okay. - Requirements: Could be from "What You'll Bring To The Table" which lists qualifications/experience. Also "This role requires at least 10 years experience...". So we can put requirements there. - Qualifications: Might be similar to Requirements. But we should not duplicate. Perhaps we can put Requirements as experience, Qualifications as education/certifications? Not given. Could combine. But we need to only include sections with real content. We could include Requirements and Qualifications both if we have distinct content. The posting mentions "Deep expertise in Microsoft Azure solutions. Proven experience architecting and delivering complex Microsoft solutions for enterprise customers. Cowork, Skills building and deployment Strong track record in methodology development, technical leadership, and innovation. Excellent communication, collaboration, and stakeholder management skills. Experience working with Microsoft and global partners. Commitment to continuous learning and professional growth. This role requires at least 10 years experience in a technical field (ideally with Microsoft technologies)". That's more like qualifications/skills. Could treat as Requirements (experience) and Skills (specific skills). Let's see. - Skills: Could extract specific skills: Microsoft Azure, solution architecture, methodology development, technical leadership, communication, collaboration, stakeholder management, working with Microsoft/global partners, continuous learning. Could list as
  . - Benefits: The posting includes "Softchoice offers a comprehensive and competitive benefit plan to all full-time employees, which includes: Health and Wellbeing: Medical and Dental Care, Employee & Family Assistance Program Financial Benefits: RRSP/DPSP Retirement Savings Plan with Company Matching, Life and Disability Insurance Paid Time Off: Vacation and Sick Leave, Holidays, Parental Leave, Volunteer Days, Bereavement Leave Additional Perks: Employee Discount Program". That's benefits. - Pay: Compensation section includes salary range and target incentives. So we need Pay section. - Schedule: Not mentioned. No schedule info. So we should not include Schedule. We also need to avoid boilerplate like EEO, legal, accommodation, etc. Remove those. We also need to not repeat job title as heading. Not needed. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details. We need to output only HTML fragment, no /, no markdown fences. We'll produce sections in order: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. Possibly Qualifications if we have distinct content. But we might combine Requirements and Qualifications; but better to separate if we have content for each. Let's see if we can extract qualifications: maybe education, certifications not mentioned. So we may not have Qualifications content. So we skip Qualifications. Requirements: we have experience requirement (10 years). Also maybe "Deep expertise...". That could be requirements. Skills: we can list specific skills. Let's craft content. About the role: Use "The Impact You Will Have" paragraph: "The Microsoft Cloud Platform Practice Architect is a senior technical leader within the Microsoft Practice, responsible for driving excellence in the design, delivery, and evolution of solutions leveraging Microsoft Cloud technologies. This role is pivotal in shaping methodologies, developing best practices, supporting offerings, and engaging with high-value customers to ensure transformative business outcomes." We could also include a bit from "Why You’ll Love Softchoice"? Not needed. Responsibilities: list each duty area. From "What You'll Do": - Technical Leadership & Expertise: Serve as a subject matter expert in Microsoft Cloud (Azure) technologies (including Frontier partner/Foundary and IQ workloads); Stay ahead of emerging trends, ensuring the practice adopts and evangelizes the latest Microsoft innovations.; Lead the integration of cloud capabilities into solution delivery models, transforming customer workflows and outcomes. - Methodology & Best Practice Development: Coordinate the development, documentation, and continuous improvement of methodologies and best practices for Microsoft Azure solutions.; Collaborate with architects, engineers, and product managers to ensure consistency and quality across all engagements.; Champion internal enablement, fostering a culture of learning and innovation. - Offerings Development & Enablement: Support the creation and evolution of Microsoft Azure offerings, working closely with product management and delivery teams.; Act as “Customer Zero” for new technologies, piloting and refining offerings before broad rollout.; Provide presales support, solution architecture, and technical leadership for strategic opportunities. - High-Value Customer Engagement: Engage directly with key strategic customers as a trusted advisor, guiding their Microsoft transformation journeys.; Lead solution workshops, architecture reviews, and executive briefings for high-impact engagements.; Ensure customer satisfaction and measurable business impact through delivery excellence. - Collaboration & Advocacy: Partner with Microsoft and other strategic partners to co-create solutions and drive joint success.; Represent Softchoice/WWT at industry events, sharing thought leadership and promoting best practices.; Advocate for continuous improvement and early adoption of emerging technologies. We need to keep the content exactly, not summarizing. We'll keep each bullet as a sentence or phrase. Might be long but okay. Requirements: from "What You'll Bring To The Table" and the experience requirement. We could list: - Deep expertise in Microsoft Azure solutions. - Proven experience architecting and delivering complex Microsoft solutions for enterprise customers. - Strong track record in methodology development, technical leadership, and innovation. - Excellent communication, collaboration, and stakeholder management skills. - Experience working with Microsoft and global partners. - Commitment to continuous learning and professional growth. - At least 10 years experience in a technical field (ideally with Microsoft technologies). We'll put as
  • . Skills: Could list specific skills: Microsoft Azure, solution architecture, methodology development, technical leadership, communication, collaboration, stakeholder management, working with Microsoft/global partners, continuous learning, presales support, customer engagement, etc. But many overlap with requirements. To avoid duplication, maybe we can treat Skills as technical skills: Microsoft Azure (including Frontier partner/Foundary and IQ workloads), solution architecture, presales support, etc. But we risk duplication. However instruction: preserve ALL substantive information; do NOT invent or summarize away detail. If we split responsibilities, requirements, skills, we may duplicate content across sections, but that's okay as long as we don't lose info. However we should avoid repeating same sentences verbatim? Not prohibited. But better to keep distinct. We could assign: - Requirements: experience and qualifications (10 years, expertise, proven experience, track record, commitment). - Skills: specific technical skills: Microsoft Azure (including Frontier partner/Foundary and IQ workloads), solution architecture, presales support, methodology development, technical leadership, communication, collaboration, stakeholder management, working with Microsoft/global partners. But there is overlap. Might be okay. Alternatively, we could skip Skills section and put all under Requirements. But we need to include Skills only if posting has real specific content for it. The posting does mention skills explicitly: "Excellent communication, collaboration, and stakeholder management skills." Also "Deep expertise in Microsoft Azure solutions." So we can treat those as skills. Thus we can have both Requirements (experience) and Skills (skill sets). Let's do that. Requirements: list items: - At least 10 years experience in a technical field (ideally with Microsoft technologies). - Proven experience architecting and delivering complex Microsoft solutions for enterprise customers. - Strong track record in methodology development, technical leadership, and innovation. - Commitment to continuous learning and professional growth. Skills: list items: - Deep expertise in Microsoft Azure solutions (including Frontier partner/Foundary and IQ workloads). - Excellent communication, collaboration, and stakeholder management skills. - Experience working with Microsoft and global partners. - Ability to serve as a subject matter expert in Microsoft Cloud (Azure) technologies. - Ability to lead integration of cloud capabilities into solution delivery models. - Ability to coordinate development, documentation, and continuous improvement of methodologies and best practices. - Ability to support creation and evolution of Microsoft Azure offerings. - Ability to act as “Customer Zero” for new technologies. - Ability to provide presales support, solution architecture, and technical leadership. - Ability to engage directly with key strategic customers as a trusted advisor. - Ability to lead solution workshops, architecture reviews, and executive briefings. - Ability to partner with Microsoft and other strategic partners to co-create solutions. - Ability to represent Softchoice/WWT at industry events, sharing thought leadership. - Ability to advocate for continuous improvement and early adoption of emerging technologies. But many of these are basically responsibilities rephrased as abilities. Might be too much duplication. However we need to preserve all substantive information; we could just put the responsibilities as list under Responsibilities, and not duplicate under Skills. Then Skills could be just the explicit skill mentions: "Deep expertise in Microsoft Azure solutions", "Excellent communication, collaboration, and stakeholder management skills", "Experience working with Microsoft and global partners". That seems reasonable. Thus: Skills: - Deep expertise in Microsoft Azure solutions (including Frontier partner/Foundary and IQ workloads). - Excellent communication, collaboration, and stakeholder management skills. - Experience working with Microsoft and global partners. Now Benefits: we have list. Pay: we have compensation range. Now we need to output HTML. Structure:

    About the role

    The Microsoft Cloud Platform Practice Architect is a senior technical leader within the Microsoft Practice, responsible for driving excellence in the design, delivery, and evolution of solutions leveraging Microsoft Cloud technologies. This role is pivotal in shaping methodologies, developing best practices, supporting offerings, and engaging with high-value customers to ensure transformative business outcomes.

    Responsibilities

    • Serve as a subject matter expert in Microsoft Cloud (Azure) technologies (including Frontier partner/Foundary and IQ workloads); Stay ahead of emerging trends, ensuring the practice adopts and evangelizes the latest Microsoft innovations.; Lead the integration of cloud capabilities into solution delivery models, transforming customer workflows and outcomes.
    • Coordinate the development, documentation, and continuous improvement of methodologies and best practices for Microsoft Azure solutions.; Collaborate with architects, engineers, and product managers to ensure consistency and quality across all engagements.; Champion internal enablement, fostering a culture of learning and innovation.
    • Support the creation and evolution of Microsoft Azure offerings, working closely with product management and delivery teams.; Act as “