Senior End User Computing (EUC) Engineer

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, etc. Also remove application instructions. Must not create sections with filler like "commensurate with experience". Pay is given: $74.00 - $84.00/hr; W2 contract, no PTO, no Benefits. ACA-compliant supplemental package available for enrollment. So we have Pay and Benefits info. Benefits: "no PTO, no Benefits. ACA-compliant supplemental package available for enrollment." That's specific enough to include Benefits section. Schedule? Not mentioned. So omit Schedule. We need sections: About the role (description), Responsibilities (list of duties), Requirements (essential requirements), Qualifications (preferred qualifications?), Skills (maybe combine? but we can separate). The posting includes "Description:" which is about role. Then bullet-like paragraphs for responsibilities (multiple paragraphs). Then "The essential requirements of the job include:" list. Then "Preferred Qualifications:" list. Also there is mention of "Strong expertise in..." etc part of essential requirements. We'll need to parse. We must use

for section headings. Use

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

  for prose. We need to preserve all substantive info. So we need to capture the description paragraphs, responsibilities bullet points (the sections after "In this role, you will have the opportunity to:" which includes subheadings like EUC Strategy & Architecture, Modern Workplace Transformation, Platform Engineering & Endpoint Management, Identity, Security & Compliance Integration, Application Delivery & User Experience, Operational Excellence & Governance, Stakeholder Engagement & Leadership). Those are responsibilities. We'll need to turn each bullet into

• maybe grouping under subheadings? But we only have

  for section headings, not subheadings. We could keep the responsibility section as a

  with each major responsibility as
  • containing the detailed description (maybe as paragraphs inside
  • ). That's acceptable. Similarly, essential requirements list: Bachelor’s degree..., 10+ years..., Strong expertise in..., Proven experience..., Deep understanding..., Strong architectural..., Excellent communication... We'll turn each into
  • . Preferred Qualifications list: Certifications..., Experience with..., Experience working..., Familiarity... We'll turn each into
  • . Benefits: "W2 contract, no PTO, no Benefits. ACA-compliant supplemental package available for enrollment." That's a statement. We'll put in

    under Benefits heading. Pay: "$74.00 - $84.00/hr; W2 contract, no PTO, no Benefits." Actually pay already includes that. We'll put Pay section with that info. We must not repeat job title. Must not include boilerplate like EEO etc. Must not include application instructions. Also must not include the line about Primary Talent Partners being EEO etc. Remove that. Also must not include the hashtag #PTPJobs. Now craft HTML. Structure:

    About the role

    ... description paragraph(s) ...

    Responsibilities

    • ... (EUC Strategy & Architecture ...)
    • ... (Modern Workplace Transformation ...)
    • ... (Platform Engineering & Endpoint Management ...)
    • ... (Identity, Security & Compliance Integration ...)
    • ... (Application Delivery & User Experience ...)
    • ... (Operational Excellence & Governance ...)
    • ... (Stakeholder Engagement & Leadership ...)

    Requirements

    • Bachelor’s degree in information technology, Computer Science, or related field
    • 10+ years of experience in End User Computing, Workplace Engineering, or Infrastructure Architecture
    • Strong expertise in: Endpoint management (Intune, SCCM, Jamf); VDI/DaaS platforms (Azure Virtual Desktop, Citrix, VMware Horizon); Identity integration (Azure AD / Entra ID)
    • Proven experience leading enterprise-scale EUC transformation programs
    • Deep understanding of: Modern device management and co-management models; OS lifecycle management, patching, and compliance; Digital workplace and user experience optimization
    • Strong architectural, analytical, and stakeholder engagement skills
    • Excellent communication skills with the ability to connect technology decisions to business outcomes

    Qualifications

    • Certifications in: Microsoft Endpoint Manager / Intune; Azure Solutions Architect / Workplace Analytics; Citrix / VMware EUC certifications
    • Experience with: DEX tools (e.g., Nexthink, Lakeside, Aternity); Automation and scripting (PowerShell, Python); Zero Trust and endpoint security frameworks
    • Experience working in global, regulated enterprise environments
    • Familiarity with ITSM platforms (e.g., ServiceNow) for EUC service integration

    Skills

    Maybe we could combine some skills but we already have skills in Requirements and Qualifications. Could we omit Skills section? The instruction: Prefer a few substantive sections over many thin ones. We already have About, Responsibilities, Requirements, Qualifications, Pay, Benefits. That's six sections. Skills could be omitted as its content is covered. But we need to decide if we should include Skills. The posting does not have a separate "Skills" section; skills are embedded in requirements and qualifications. So we should not create a Skills section with filler. So omit Skills.

    Pay

    $74.00 - $84.00/hr; W2 contract, no PTO, no Benefits.

    Benefits

    ACA‑compliant supplemental package available for enrollment.

    We need to ensure we didn't repeat "no PTO, no Benefits" in Benefits; we already said no PTO, no Benefits in Pay. Benefits section can mention the supplemental package. That's fine. Check for any other substantive info: location: Sunnyvale, CA. Should we include location? It's part of description maybe. The About the role paragraph could include location. The initial sentence: "Primary Talent Partners has a new contract opening for a Senior End User Computing (EUC) Engineer with a multinational science and technology company in Sunnyvale, CA. This is a 2-month contract with a potential for extension." That's substantive. Should we include that in About the role? Yes. So About the role paragraph should include that. Thus About the role paragraph: "Primary Talent Partners has a new contract opening for a Senior End User Computing (EUC) Engineer with a multinational science and technology company in Sunnyvale, CA. This is a 2‑month contract with a potential for extension. The Senior End User Computing (EUC) Engineer is responsible for defining and delivering the strategy, architecture, and transformation of OpCo’s end-user computing environment. This role focuses on modern workplace technologies, endpoint management, digital experience, virtualization, mobility, identity integration, and automation—ensuring a secure, scalable, and high-performing user environment across a global enterprise. This position is part of the IT Global Infrastructure & Operations team based out of Sunnyvale." We need to preserve all substantive info. Also mention "In this role, you will have the opportunity to:" then the responsibilities. We'll capture responsibilities as list items. Make sure not to include any boilerplate like "Primary Talent Partners is an Equal Opportunity..." etc. Now produce HTML fragment only. Check for any missing info: The description also includes "This role focuses on modern workplace technologies, endpoint management, digital experience, virtualization, mobility, identity integration, and automation—ensuring a secure, scalable, and high-performing user environment across a global enterprise." We included that. Also "This position is part of the IT Global Infrastructure & Operations team based out of Sunnyvale." included. Now responsibilities list items: need to capture each bullet's content. Let's extract each: 1. EUC Strategy & Architecture - Define and own the enterprise EUC architecture roadmap spanning endpoint management, virtual desktops, mobility, collaboration, and digital experience. - Lead modernization initiatives across Windows, macOS, mobile platforms, and virtual desktop environments (VDI/DaaS). - Establish architecture principles for secure, scalable, and user-centric workplace computing aligned with enterprise IT strategy. - Drive alignment with Identity, Security, Network, and Cloud architectures to ensure cohesive end-to-end user experience. 2. Modern Workplace Transformation - Lead transformation programs such as: - Device lifecycle modernization (Autopilot / zero-touch provisioning) - UEM migration (e.g., SCCM ? Intune / modern management) - VDI/DaaS optimization (e.g., Azure Virtual Desktop, Citrix, VMware Horizon) - Enable hybrid work capabilities with seamless, secure, and high-performance user access from any location. - Drive digital employee experience (DEX) improvements through analytics, telemetry, and automation. 3. Platform Engineering & Endpoint Management - Architect and govern endpoint platforms including: - Microsoft Intune / Endpoint Manager - SCCM / Configuration Manager (co-management scenarios) - Jamf or macOS management platforms - Define standards for: - OS builds and patch management - Application packaging and deployment - Device compliance and configuration baselines - Enable automation through PowerShell, Graph API, and orchestration frameworks. 4. Identity, Security & Compliance Integration - Partner with security and identity teams to embed: - Zero Trust principles - Conditional Access and device posture enforcement - Endpoint security (Defender, EDR/XDR integration) - Ensure EUC platforms comply with enterprise security, regulatory, and data protection policies. - Drive integration with IAM platforms (Azure AD / Entra ID, MFA, SSO). 5. Application Delivery & User Experience - Architect application delivery models including: - Native install, virtualized apps, and cloud-based SaaS delivery - Optimize application performance and user experience across physical and virtual environments. - Lead self-service enablement via modern catalogs and automation. 6. Operational Excellence & Governance - Define EUC operating model, governance frameworks, and service standards. - Establish KPIs for: - Device health - User experience - Patch compliance - Service performance - Drive continuous improvement, automation, and cost optimization across EUC services. 7. Stakeholder Engagement & Leadership - Partner with Infrastructure, Security, Service Desk, and Business units to align EUC strategy with organizational goals. - Translate technical architecture into business value and measurable outcomes. - Mentor engineers and lead design reviews, technical standards, and best practices. - Communicate risks, dependencies, and roadmap progress to leadership. We'll combine each major heading into a single
  • containing the subpoints as separate sentences or maybe as
    inside
    • ? But spec says use
      • for any list of duties/requirements/benefits. It didn't forbid nested lists. But to keep simple, we can make each responsibility as a
      • with the content as sentences, using commas and semicolons. That's acceptable. We must preserve all substantive info; nested lists might be okay but not required. We'll keep as plain text inside
      • . Now Requirements list: we have items as above. Qualifications list: as above. Pay: "$74.00 - $84.00/hr; W2 contract, no PTO, no Benefits." Benefits: "ACA‑compliant supplemental package available for enrollment." Check for any other info: "Candidates must be legally authorized to work in the United States and