Sr Staff Endpoint Architect

We need to output HTML fragment with sections: h3 headings for sections present: About the role? The posting includes "Position Overview" and "Key Responsibilities", "Qualifications", "Compensation & Benefits Details". Also maybe "Additional Information" (Preferred Qualifications). We should not repeat job title. Use

for each section heading. Use

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

  for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO etc. The posting includes some generic statements at start: "WD is building the infrastructure..." That's part of company description; we can keep as prose under maybe "About the role" or "Position Overview". The "Position Overview" section is present. We need to decide sections: "Position Overview" could be under

  About the role

  or

  Position Overview

  . The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map to those standard headings. Use "About the role" for position overview. Use "Responsibilities" for key responsibilities. Use "Qualifications" for required qualifications. Possibly also "Preferred Qualifications" could be under "Qualifications" or separate "Skills"? But we can include "Preferred Qualifications" as part of Qualifications maybe as a subsection? However instruction: only include a section when posting has real, specific content for it. We have content for Preferred Qualifications. Could create a separate section "Preferred Qualifications" but not in the list of examples; but we could still use

  Preferred Qualifications

  as it's a heading. The examples are not exhaustive; they said e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can add other headings if needed. Safer to include "Preferred Qualifications" as its own heading. Also "Compensation & Benefits Details" could be split into "Pay" and "Benefits". The posting includes salary range description and benefits list. We should create "Pay" section for salary range details, and "Benefits" section for benefits list. Also maybe "Schedule" not present, so omit. We must not include filler like "commensurate with experience". The posting includes salary range description with many factors; that's substantive. We'll keep. We need to remove duplicated lines, boilerplate like "Note: No amount of pay is considered to be wages..." That's part of compensation details; it's substantive? It's a note about compensation; we can keep. We must not include application instructions, EEO etc. There's none. Now structure:

  About the role

  WD is building the infrastructure behind the AI-driven data economy... (the initial paragraph) plus Position Overview paragraph(s). We'll combine. Then

  Responsibilities

  We need to list responsibilities as
  • . The responsibilities are bullet points under "Key Responsibilities" with sub-bullets. We'll flatten? Probably each bullet as
  • . Could keep sub-bullets as nested
    . But instruction: use
    • for any list of duties/requirements/benefits. It doesn't forbid nesting. We'll keep top-level bullets as
    • and if there are sub-bullets we can also nest
      • . That's fine. We need to preserve all substantive information; not summarize away. So we need to include all bullet points. Let's extract responsibilities: Key Responsibilities Endpoint Strategy and Architecture • Define the enterprise endpoint strategy, reference architecture, and modernization roadmap across Apple and Windows platforms. • Develop a persona-based device strategy that aligns endpoint selection with job responsibilities, business workflows, application requirements, security, mobility, and employee experience. • Lead assessments of applications, workflows, peripherals, and technical dependencies to identify appropriate Mac and Windows use cases. • Develop a data-driven roadmap for expanding Mac adoption across qualified employee personas and business functions. • Establish standards for endpoint hardware, operating systems, identity, applications, security, compliance, connectivity, and lifecycle management. • Evaluate emerging Apple, Microsoft, digital employee experience, automation, and AI capabilities for enterprise use. • Present technical recommendations, investment priorities, risks, and progress to technology and business leadership. Apple and Windows Platform Engineering • Architect and modernize Apple device management using Jamf Pro, Microsoft Intune, Apple Business Manager, Automated Device Enrollment, and modern Apple management frameworks. • Architect Windows management using Microsoft Intune, Windows Autopilot, Microsoft Configuration Manager, Entra ID, and related cloud-management technologies. • Design secure zero-touch provisioning, application delivery, configuration, compliance, recovery, replacement, and decommissioning experiences for both platforms. • Define the appropriate use of Jamf, Intune, Configuration Manager, co-management, and cloud-native management within the endpoint ecosystem. • Establish operating-system testing, patching, upgrade, enforcement, exception, and vulnerability-response strategies. • Architect identity capabilities using Entra ID, Platform SSO, Windows Hello for Business, Conditional Access, passwordless authentication, and certificates. • Define endpoint security standards covering FileVault, BitLocker, privileged access, endpoint protection, data protection, recovery keys, local accounts, and device compliance. • Engineer scalable application packaging, deployment, updating, and retirement for macOS and Windows applications. • Provide senior technical leadership for complex endpoint, identity, security, application, and management-platform issues. Application Readiness and Device Adoption • Establish a device eligibility framework that identifies the appropriate endpoint platform for each employee persona and business use case. • Maintain cross-platform application catalogs identifying supported, conditional, incompatible, and remediation-required applications. • Partner with application owners and vendors to address compatibility, licensing, authentication, performance, and supportability requirements. • Develop solutions for platform-specific dependencies using SaaS alternatives, browser-based applications, modernization, virtualization, Windows 365, Azure Virtual Desktop, or remote application delivery. • Lead pilots and phased deployments to validate application readiness, security, supportability, and employee experience. • Develop repeatable migration approaches for user data, applications, identity, settings, collaboration tools, and peripherals. • Partner with Change Management, Communications, Learning, and Support teams to develop adoption campaigns, training, and migration guidance. Automation and Modern Endpoint Operations • Build an automation-first engineering practice using PowerShell, Bash, Zsh, Python, Microsoft Graph, Jamf APIs, REST APIs, and orchestration platforms. • Automate provisioning, application deployment, configuration, compliance, remediation, patching, inventory, reporting, and lifecycle management. • Establish source control, peer review, testing, release management, rollback, and documentation standards for endpoint engineering. • Use endpoint telemetry and digital employee experience data to proactively identify reliability, performance, compliance, and user-experience issues. • Develop self-service and self-healing capabilities that improve employee productivity and reduce support demand. • Explore the responsible use of AI and intelligent automation for troubleshooting, compliance analysis, proactive remediation, and endpoint operations. Operational Readiness and Technical Leadership • Ensure Global Service Desk and deskside teams are prepared to support Apple and Windows platforms at enterprise scale. • Define support models, escalation paths, diagnostic workflows, knowledge requirements, and engineering-to-operations handoffs. • Identify recurring incidents and engineer permanent, scalable solutions. • Maintain architecture diagrams, engineering standards, technical decisions, operational procedures, and support documentation. • Mentor endpoint engineers, lead technical design reviews, and establish consistent engineering practices. • Influence cross-functional architecture, security, application, and investment decisions without relying on direct authority. Now Qualifications: Required Qualifications bullet list. We'll extract each bullet. Required Qualifications • 10+ years of experience in endpoint engineering, workplace technology, enterprise infrastructure, or related discipline. • Extensive experience architecting and supporting Apple and Windows endpoints in a large, complex, or global enterprise. • Demonstrated experience leading an endpoint modernization, Mac adoption, cloud-management, or device-transformation initiative. • Deep expertise with Jamf Pro and strong experience with Microsoft Intune, Windows Autopilot, and Microsoft Configuration Manager. • Hands-on experience with Apple Business Manager, Automated Device Enrollment, and Apple application management. • Advanced knowledge of macOS and Windows architecture, security, configuration, deployment, and troubleshooting. • Strong experience with Entra ID, Platform SSO, Windows Hello for Business, Conditional Access, certificates, and passwordless authentication. • Advanced automation skills using PowerShell and at least one of the following: Bash, Zsh, Python, Microsoft Graph, Jamf APIs, or REST APIs. • Experience implementing enterprise security baselines, encryption, endpoint protection, privileged-access controls, and compliance policies. • Experience assessing employee personas, business workflows, application compatibility, and device requirements. • Strong knowledge of enterprise networking, including Wi-Fi, VPN, DNS, proxies, certificates, and Zero Trust. • Ability to translate business requirements into architecture, roadmaps, execution plans, and measurable outcomes. • Strong communication, documentation, stakeholder management, and technical leadership skills. • Experience developing device standards, total-cost-of-ownership models, technical pilots, migration programs, and employee enablement. • Familiarity with AI-assisted endpoint operations and self-healing capabilities. Preferred Qualifications bullet list. We'll include under

        Preferred Qualifications

        . Now Compensation & Benefits Details: we need Pay and Benefits sections. Pay: includes paragraph about salary range determination and range statement. We'll put that as

        . Benefits: list of benefits. We'll extract benefits paragraph: "We offer a comprehensive package of benefits including paid vacation time; paid sick leave; medical/dental/vision insurance; life, accident and disability insurance; tax-advantaged flexible spending and health savings accounts; employee assistance program; other voluntary benefit programs such as supplemental life and AD&D, legal plan, pet insurance, critical illness, accident and hospital indemnity; tuition reimbursement; transit; the Applause Program; employee stock purchase plan; and the WD Savings 401(k) Plan." We'll make

        • each benefit separated by semicolons? Could split but better to keep as one
        • with the whole list? The instruction: use
          • for any list of duties/requirements/benefits. So we should split each benefit into separate
          • . Let's parse: - paid vacation time - paid sick leave - medical/dental/vision insurance - life, accident and disability insurance - tax-advantaged flexible spending and health savings accounts - employee assistance program - other voluntary benefit programs such as supplemental life and AD&D, legal plan, pet insurance, critical illness, accident and hospital indemnity - tuition reimbursement - transit - the Applause Program - employee stock purchase plan - the WD Savings 401(k) Plan We'll keep as separate items. Now also there is note about pay not considered wages etc. That's part of Pay section maybe as a

            . Now we need to ensure we don't include any boilerplate like "Note: No amount of pay is considered to be wages or compensation until such amount is earned, vested, and determinable." That's part of compensation details; we can keep. Now produce HTML fragment. We'll start with

            About the role

            ...

            We need to include the initial paragraph: "WD is building the infrastructure behind the AI-driven data economy. As AI scales, so does data. Every interaction, every model, every system generates data that must be stored, managed, and made accessible over time. That’s where we come in. We combine deep engineering expertise with global-scale manufacturing to deliver the storage systems that make AI possible, powering hyperscale data centers, cloud platforms, and enterprise infrastructure worldwide. This isn’t theoretical work. It’s real systems, at real scale, people solving some of the hardest challenges in technology today. We’re looking for people who want to build, solve