Digital Workplace Architect

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job description. First, job title: DIGITAL WORKPLACE ARCHITECT. Not to repeat as heading. We need to extract sections. The posting includes: - Job Details: Full Time / Part Time: Full Time, FLSA Classification: Exempt, Business Unit: Corporate, Reports to: Senior Director, Enterprise Applications, Travel Requirement: No. This is metadata; we can fold into a short

or drop. Probably we can include a short paragraph summarizing these details. - Job Description: paragraphs describing role. - Essential job functions list: bullet points under Microsoft 365 Architecture & Strategy, SharePoint Online, Content & Knowledge Architecture, Microsoft 365 Copilot & AI Enablement, Governance, Security, Compliance & Risk, Engineering, Automation & Operational Excellence. - Other Duties: note about job description not comprehensive. - Requirements: bullet list of requirements. - Preferred Qualifications: bullet list. - Select Values and Guiding Principles: list of values (W, A, T, E, R). Might be considered as "Skills"? Not exactly. Could be part of "Qualifications"? Might be considered as "Skills" or "Values". The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content. - Compensation Information: "Compensation is competitive and commensurate with experience." That's vague; we should not create Pay section unless posting actually states them. It says "Compensation is competitive and commensurate with experience." That's not specific; we should not create Pay section because it's not specific numbers. So we omit Pay. - Benefits: "Top Tier Benefits Medical, dental, vision, coverage in addition to life and disability insurance plans. Paid Vacation Days and Paid Holidays. Retirement and Savings (401K) Plan." That's specific benefits; we can create Benefits section. - Schedule: "Monday – Friday, 8am-5pm." That's schedule; we can create Schedule section. - Physical Demands and Exposures: maybe not needed; could be omitted or folded into About the role? Probably we can include in About the role or drop. The instruction: remove boilerplate, duplicated lines, application instructions. Physical demands maybe not boilerplate but not required heading. Could be part of About the role. - Select Values and Guiding Principles: maybe part of Skills or Qualifications. Could be a separate section "Skills"? But we have heading Skills; we could put those values there. However they are not skills per se but values. Could be considered as "Qualifications"? Might be better to include them under "Skills" as they are guiding principles. But we need to preserve all substantive information; we can include them as a

under Skills heading. - About the role: we can summarize the job description paragraph(s) that describe owning Microsoft 365 ecosystem etc. That's substantive. - Responsibilities: we can list the essential job functions as bullet list under Responsibilities. - Requirements: bullet list of requirements. - Qualifications: bullet list of preferred qualifications. - Skills: maybe we can include the values and guiding principles, also maybe mention proficiency with PowerShell, Microsoft Graph etc. But those are already in Requirements. Could still include them under Skills but might duplicate. Better to put values under Skills. - Benefits: as above. - Schedule: Monday-Friday 8am-5pm. - Pay: omit. Now we need to output only HTML fragment, no markdown fences. We need to use

for section headings. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We must not repeat job title as heading. We must not put Job ID/requisition numbers as headings (none present). We must preserve ALL substantive information; do not invent or summarize away detail. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to remove EEO statements etc. The posting includes a lot of EEO and legal text at the end: "Select Water Solutions is an equal opportunity employer..." etc. Also Clean Air Act, E-Verify etc. Those are boilerplate; we should remove them. Also "Other Duties Please note this job description is not designed to cover or contain a comprehensive listing..." that's boilerplate; we can drop that. Also "Select Values and Guiding Principles W: Working Safe A: Accountability T: Teamwork E: Excellence R: Respect" we keep. Now let's extract substantive content. Job Details paragraph: "Full Time / Part Time: Full Time FLSA Classification: Exempt Business Unit: Corporate Reports to: Senior Director, Enterprise Applications Travel Requirement: No". We'll make a short

  maybe. Job Description paragraph: "Select Water’s Digital Workplace Architect owns the organization’s Microsoft 365 collaboration and productivity ecosystem, including SharePoint Online, Teams, Microsoft 365 Copilot, Microsoft Search, and Power Platform governance. This role establishes secure, scalable standards for collaboration, AI enablement, automation, records, external sharing, and workforce productivity." That's prose; we can put under About the role. Then essential job functions list: we have headings within the description: Microsoft 365 Architecture & Strategy, SharePoint Online, Content & Knowledge Architecture, Microsoft 365 Copilot & AI Enablement, Governance, Security, Compliance & Risk, Engineering, Automation & Operational Excellence. Each has bullet points. We need to output a list under Responsibilities. Should we preserve the subheadings? The instruction: use

  • for any list of duties/requirements/benefits. It didn't forbid subheadings inside list items. We could include the heading as part of the
  • text. Eg:
  • Microsoft 365 Architecture & Strategy: Own the Microsoft 365 collaboration roadmap, reference architectures, technical standards, and lifecycle strategy. Architect secure, scalable solutions across SharePoint Online, Teams, Microsoft Search, Copilot, and approved integrations.
  etc. We need to preserve all detail; we can include the subheadings as part of the list items. Now Requirements: bullet list: - Bachelor’s degree in Computer Science, Information Systems, Cybersecurity, Engineering, or related discipline; equivalent experience considered. - Demonstrated hands-on experience architecting, administering, engineering, and supporting enterprise Microsoft 365 solutions, including SharePoint Online, Teams, Microsoft 365 Copilot, and Power Platform governance. - Strong knowledge of SharePoint information architecture, permissions, search, content management, governance, and site lifecycle. - Ability to translate business requirements into practical architectures, technical standards, implementation plans, and operating models. - Proficiency with PowerShell and working knowledge of Microsoft Graph, APIs, integration patterns, and automation. - Excellent communication, facilitation, prioritization, influence, and execution skills. We'll put under Requirements heading. Preferred Qualifications: - Experience in a publicly traded, regulated, industrial, energy, utilities, or field-operations environment. - Experience establishing centers of excellence, champion programs, citizen-developer guardrails, or enterprise adoption programs. - Relevant Microsoft certifications such as MS-102, SC-100, SC-400, or current Microsoft Copilot and AI credentials. We'll put under Qualifications heading. Skills: we have values: W: Working Safe, A: Accountability, T: Teamwork, E: Excellence, R: Respect. Also maybe we could include "Excellent communication, facilitation, prioritization, influence, and execution skills" but that's already in Requirements. We'll just list values. We could also include "Proficiency with PowerShell and working knowledge of Microsoft Graph, APIs, integration patterns, and automation" but that's already in Requirements. To avoid duplication, we can keep only values under Skills. Benefits: "Medical, dental, vision, coverage in addition to life and disability insurance plans. Paid Vacation Days and Paid Holidays. Retirement and Savings (401K) Plan." We'll make a
  with each benefit as
  • . Schedule: "Monday – Friday, 8am-5pm." We'll put as

    maybe. Now About the role: we need to include the prose describing role. Could also include the Job Details paragraph? Might be better to include Job Details in About the role or separate? The instruction: About the role heading for section headings (e.g. About the role, Responsibilities...). So we can put a short paragraph summarizing the role and maybe include the job details. We'll create About the role

    containing: "Select Water’s Digital Workplace Architect owns the organization’s Microsoft 365 collaboration and productivity ecosystem, including SharePoint Online, Teams, Microsoft 365 Copilot, Microsoft Search, and Power Platform governance. This role establishes secure, scalable standards for collaboration, AI enablement, automation, records, external sharing, and workforce productivity. The position is full-time, exempt, reports to the Senior Director, Enterprise Applications, and requires no travel." That preserves details. Now we need to ensure we don't include any boilerplate like "Select Values and Guiding Principles" heading; we just list values under Skills. We must not include headings for sections that have no real specific content. We have About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule. Pay omitted. Now we need to output only HTML fragment. Let's craft:

    About the role

    Select Water’s Digital Workplace Architect owns the organization’s Microsoft 365 collaboration and productivity ecosystem, including SharePoint Online, Teams, Microsoft 365 Copilot, Microsoft Search, and Power Platform governance. This role establishes secure, scalable standards for collaboration, AI enablement, automation, records, external sharing, and workforce productivity. The position is full-time, exempt, reports to the Senior Director, Enterprise Applications, and requires no travel.

    Responsibilities

    • Microsoft 365 Architecture & Strategy: Own the Microsoft 365 collaboration roadmap, reference architectures, technical standards, and lifecycle strategy. Architect secure, scalable solutions across SharePoint Online, Teams, Microsoft Search, Copilot, and approved integrations.
    • SharePoint Online, Content & Knowledge Architecture: Serve as the primary technical authority for SharePoint Online architecture, administration, and modernization. Design information architecture, hub structures, taxonomy, metadata, content types, search, permissions, and provisioning standards. Govern SharePoint site creation, ownership, external sharing, guest access, and lifecycle standards. Lead content migration and modernization efforts while keeping content organized, discoverable, secure, and governed.
    • Microsoft 365 Copilot & AI Enablement: Lead readiness, governance, architecture, and adoption for Microsoft 365 Copilot. Assess permissions hygiene, oversharing risk, search quality, retention controls, and compliance readiness before AI enablement. Define standards for Copilot usage, AI-enabled solutions, enterprise search, approved connectors, and future agent governance. Partner with stakeholders to prioritize high-value AI use cases while balancing innovation, security, governance, and business value.
    • Governance, Security, Compliance & Risk: Partner with Cybersecurity, Legal, Compliance, Internal Audit, and Records Management to define and enforce governance. Design controls for least-privilege administration, access reviews, external collaboration, guest access, and permissions governance. Own Power Platform governance standards and identify security, operational, legal, privacy, and governance risks.
    • Engineering, Automation & Operational Excellence: Use PowerShell, Microsoft Graph, APIs, administrative portals, and automation to improve governance, reporting, maintenance, and operations. Perform discovery, design, configuration, testing, deployment, troubleshooting,