Staff Systems Engineer

We need to output HTML fragment with sections: About the role (maybe from Job Summary?), Responsibilities (What you will do), Requirements/Qualifications (What you will bring to SmithRx), Skills (maybe Nice to Have?), Benefits (What SmithRx Offers You), Pay (Pay Range), Schedule (not present, so omit). Also include a short

for metadata like location? The posting includes location: Plano, TX. Should we include as a short paragraph? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include location in a

. Also maybe include "Who We Are" as part of About the role? The "Who We Are" is company description; could be part of About the role or separate section? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role (maybe combine Who We Are + Job Summary?), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. However we need to avoid thin sections. We have a lot of content for Responsibilities (What you will do). Requirements/Qualifications: "What you will bring to SmithRx" includes experience and skills. Could split into Requirements (experience) and Qualifications (specific skills). Nice to Have could be Skills? Actually Skills section could list both required and nice-to-have? The instruction: Use headings as examples; we can decide. Probably better: About the role (company overview + job summary), Responsibilities (What you will do), Requirements (Experience), Qualifications (Technical mastery), Skills (Nice to Have), Benefits (What SmithRx Offers You), Pay (Pay Range). Ensure we only include sections with real content. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the details from each bullet. We need to format lists with

• . For prose use

  . We must not include boilerplate like EEO etc. There's none. We must not include application instructions. We must not repeat job title. We must not include Pay/Schedule/Benefits unless posting actually states them. Pay is present: Pay Range: $136,000 USD - $160,000 USD. Benefits present. Schedule not present, so omit. We need to ensure we don't include placeholder like "commensurate with experience". Not present. Now craft HTML. First, maybe a short

  for location: Plano, TX. Then

  About the role

  with prose combining Who We Are and Job Summary. Who We Are paragraph: "SmithRx is a rapidly growing, venture-backed Health-Tech company. Our mission is to disrupt the expensive and inefficient Pharmacy Benefit Management (PBM) sector by building a next-generation drug acquisition platform driven by cutting edge technology, innovative cost saving tools, and best-in-class customer service. With hundreds of thousands of members onboarded since 2016, SmithRx has a solution that is resonating with clients all across the country. We pride ourselves for our mission-driven and collaborative culture that inspires our employees to do their best work. We believe that the U.S healthcare system is in need of transformation, and we come to work each day dedicated to making that change a reality. At our core, we are guided by our company values: Integrity: Our purpose guides our actions and gives us confidence in the path ahead. With unwavering honesty and dependability, we embrace the pressure of challenging the old and exemplify ethical leadership to create the new.Courage: We face continuous challenges with grit and resilience. We embrace the discomfort of the unknown by balancing autonomy with empathy, and ownership with vulnerability. We boldly challenge the status quo to keep moving forward—always.Together: The success of SmithRx reflects the strength of our partnerships and the commitment of our team. Our shared values bind us together and make us one. When one falls, we all fall; when one rises, we all rise." Job Summary paragraph: "SmithRx is seeking a visionary and highly strategic Staff Systems Engineer to serve as the overarching technical authority and architect for our enterprise endpoint infrastructure, vendor ecosystem, and IT asset strategy, while also serving as the senior most member of the IT team in our Plano, TX office. In this high-impact role, you will define the multi-year technology roadmap for our endpoint environments, drive organizational alignment on vendor integrations, and architect our zero-touch, modern management frameworks at scale. Operating with a security-first, compliance-driven mindset, you will set the engineering standards for our Windows and mixed-OS fleets, design cloud workspace strategies (CloudPC/AVD), and mentor engineering teams across the organization. You will partner directly with executive leadership, Security, and Compliance to ensure our infrastructure scales seamlessly while meeting stringent HIPAA and SOC 2 requirements." We can combine into one

  or multiple

  . Probably separate paragraphs for readability. Then Responsibilities: heading

  Responsibilities

  then
  with each bullet from "What you will do". Need to preserve each bullet exactly as given. List items: - Strategic Architecture & Ecosystem Vision: Serve as the architect for the enterprise Windows and modern workspace ecosystem. Define the multi-year technology roadmap, architectural standards, and security baselines for all global endpoint infrastructure. - Next-Gen Endpoint Management: Lead the strategic design, governance, and optimization of Microsoft EntraID, Microsoft Intune, and Windows Autopilot. Drive zero-touch provisioning and continuous compliance models to support rapid enterprise growth. - Vendor Strategy & Strategic Partnerships: Direct the overall vendor strategy and technical oversight for external partners. Define onboarding frameworks, evaluate enterprise-grade technologies, and align cross-functional business units to maximize vendor investments. - Virtual Workspace & Fleet Architecture: Scope, architect, and establish governance for virtual desktop infrastructures (CloudPC / Azure Virtual Desktop) and third-party remote environments, ensuring secure access for partners, contractors, and distributed teams. - Asset & Governance Strategy: Establish total lifecycle governance, hardware refresh strategies, and SaaS asset management frameworks. Partner with Finance and Operations to optimize hardware asset investments and licensing footprints. - Enterprise Automation Frameworks: Lead the push toward an automation-first culture by architecting scalable automation frameworks (PowerShell, Python, APIs) to streamline identity lifecycle workflows, systems orchestration, and complex endpoint remediations. - Architectural Escalation & Root Cause Leadership: Act as the ultimate technical escalation point for complex enterprise incidents. Lead systemic root-cause analyses (RCAs) and implement long-term structural preventions across the IT ecosystem. - Security Alignment & Regulatory Compliance: Partner as a core peer with Security and Compliance leadership to ensure all endpoint and cloud strategies align with HIPAA, SOC 2, and zero-trust frameworks. Architect robust IAM controls and conditional access policies. - Mentorship & Engineering Standards: Set technical standards, author high-level architecture designs (ADRs/runbooks), and actively mentor IT support and engineering teammates to raise the technical bar across the organization. - High-Availability Leadership: Serve as a technical consultant and escalation point for major incidents, ensuring resilient high availability across all business-critical operations. We need to keep the exact phrasing. Then Requirements: heading

  Requirements

  maybe for experience: "Experience: 8+ years of progressive experience in Systems Engineering, Enterprise Architecture, or IT Infrastructure Operations, with a proven track record of architectural leadership in high-growth, SaaS-driven, or regulated environments." We could also include other experience items? The "What you will bring to SmithRx" includes many bullet points each starting with a bold label. Those could be considered Qualifications. Let's split: Requirements = Experience (years). Qualifications = the mastery items. But we could also combine Requirements and Qualifications into one section? The instruction says we can use those headings; better to separate if content distinct. Thus:

  Requirements

  Experience: 8+ years of progressive experience in Systems Engineering, Enterprise Architecture, or IT Infrastructure Operations, with a proven track record of architectural leadership in high-growth, SaaS-driven, or regulated environments.

  Qualifications

  • Mastery of Microsoft Stack: Deep architectural expertise in Windows OS, Microsoft EntraID, Intune, dynamic groups, conditional access strategies, and zero-touch Autopilot deployments at scale.
  • Vendor Infrastructure Leadership: Demonstrated ability to manage strategic vendor partnerships, establish vendor selection and onboarding frameworks, and influence cross-functional technical decisions.
  • CloudPC & Virtualization Mastery: Proven expertise architecting, deploying, and governing CloudPC (Windows 365), Azure Virtual Desktop (AVD), or VDI environments for remote and third-party workforces.
  • Advanced Automation & Integration: Advanced scripting proficiency (PowerShell, Python) with experience utilizing REST APIs and iPaaS platforms to automate complex, cross-system IT processes.
  • Lifecycle & Asset Management Governance: Experience designing end-to-end asset governance models, enterprise hardware standards, and SaaS portfolio management strategies.
  • Heterogeneous Environment Oversight: Broad operational and architectural understanding of multi-platform environments (macOS/Apple Business Manager, Jamf/Kandji, Google Workspace, Okta).
  • Regulated Environment Expertise: Extensive experience designing infrastructure compliant with HIPAA, SOC 2, ISO 27001, or equivalent regulatory frameworks.
  • Executive & Strategic Mindset: Strong strategic vision, organizational agility, and the ability to articulate complex technical architecture directly to C-level executives and key business stakeholders.
  Then Skills: heading

  Skills

  for Nice to Have. Nice to Have bullets: - Enterprise-level certifications (e.g., Microsoft Certified: Enterprise Administrator Expert, Microsoft Certified: Cybersecurity Architect Expert, CISSP). - Proven experience implementing modern iPaaS/workflow platforms for enterprise identity lifecycle automation. - High-level knowledge of enterprise networking topology (Ubiquiti, zero-trust network access/ZTNA, SD-WAN) and cloud-first identity systems (Okta, Entra ID). We'll put each as
  • . Then Benefits: heading

    Benefits

    with content from "What SmithRx Offers You:" list. We need to preserve all items: "Highly competitive wellness benefits including Medical, Pharmacy, Dental, Vision, and Life Insurance and AD&D Insurance", "Flexible Spending Benefits", "401(k) Retirement Savings Program", "Short-term and long-term disability", "Discretionary Paid Time Off", "Paid Company Holidays", "Wellness Benefits", "Commuter Benefits", "Paid Parental Leave benefits", "Employee Assistance Program (EAP)", "Well-stocked kitchen in office locations", "Professional development and training opportunities". Also later they mention "time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance and 401(k)". But we should not duplicate; we need to preserve all substantive information, but avoid duplication. The list already includes many; the later sentence repeats some. We should include the list as given, maybe combine but not duplicate. Safer to include the list exactly as in "What SmithRx Offers You:" and then maybe also include the later sentence? That would duplicate. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not invented, but it's redundant. Might be okay but better to avoid duplication. We'll include the list from that section; the later sentence is essentially a summary; we could omit as it's repetitive. However it's still substantive info (mentions mental health support). The list didn't mention mental health support explicitly; but "Wellness Benefits" may encompass. To be safe, we could include the later sentence as additional detail, but ensure not to duplicate exact same phrases. We'll add a