Staff Systems Engineer

We need to output HTML fragment with sections: About the role? Actually we have "Who We Are" (company description) and "Job Summary", "What you will do", "What you will bring to SmithRx", "Nice to Have", "What SmithRx Offers You", "Plano, TX Pay Range". We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We must include sections only when posting has real specific content. We need to map content to appropriate headings. We have: - Who We Are: company description. Could be "About the role"? Actually "About the role" is typical heading for role description. But we have "Job Summary". Could map to "About the role" or "Job Summary". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should use those exact headings when appropriate. Thus: - About the role: could contain "Who We Are" + "Job Summary"? Probably "About the role" includes company description and role summary. We'll put both. - Responsibilities: "What you will do" list. - Requirements: "What you will bring to SmithRx" (experience, etc.) maybe also "Nice to Have" could be separate but we could combine into Requirements? But we have separate headings for Qualifications, Skills. Could split: Requirements = mandatory experience; Qualifications = maybe education? Not present. Skills = technical skills. But we can follow typical: Requirements = experience; Skills = technical skills; Qualifications = certifications? However we have "Nice to Have" separate. Could treat "Nice to Have" as optional qualifications. We need to avoid filler headings. So we should only create sections where we have content. We have content for: - About the role (company description + job summary) - Responsibilities (what you will do) - Requirements (what you will bring) - Skills (maybe we can extract technical skills from requirements) - Benefits (What SmithRx Offers You) - Pay (Plano, TX Pay Range) We could also have Schedule? Not present. We must not create sections with placeholder text. Thus produce:

About the role

Who We Are: 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: 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.

Then Responsibilities: list bullet points from "What you will do". We'll create

• each. Then Requirements: list bullet points from "What you will bring to SmithRx" (the experience list). Could be bullet list. Then Skills: maybe we can extract technical skills from that list? But we could also treat "Nice to Have" as Skills? However we have separate heading Skills. Could put technical skills like Microsoft Stack, Vendor Infrastructure Leadership, CloudPC & Virtualization Mastery, Advanced Automation & Integration, Lifecycle & Asset Management Governance, Heterogeneous Environment Oversight, Regulated Environment Expertise, Executive & Strategic Mindset. Those are more like qualifications/skills. But we already used Requirements for experience. Could split: Requirements = experience (8+ years etc). Skills = technical mastery list. Qualifications = maybe certifications? Not present. Nice to Have could be extra skills. We need to avoid filler. So we can create Skills section with bullet list of technical skills. We also have Benefits section: list benefits from "What SmithRx Offers You". We'll bullet. Pay section: include pay range. We must not repeat job title as heading. We must not include Job ID etc. We must not include boilerplate like EEO etc (not present). We must output only HTML fragment. Let's craft. Be careful to preserve all substantive information. Do not invent or summarize away detail. Must keep all details. We need to include all points from "What you will bring to SmithRx": list of experience items. We'll bullet each. Also "Nice to Have": we could include as part of Skills or separate section? Could create a separate section "Preferred Qualifications" but not in allowed headings. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could put Nice to Have under Qualifications or Skills. Since Qualifications is allowed, we can put Nice to Have there. But we also have Skills heading. Let's assign: - Requirements: mandatory experience (8+ years etc) - Qualifications: Nice to Have items (certifications, iPaaS, networking knowledge) - Skills: technical mastery list (Microsoft Stack, Vendor Infrastructure Leadership, CloudPC & Virtualization Mastery, Advanced Automation & Integration, Lifecycle & Asset Management Governance, Heterogeneous Environment Oversight, Regulated Environment Expertise, Executive & Strategic Mindset) But we also have "Mastery of Microsoft Stack" etc which are also skills. Could be under Skills. Thus: Requirements: experience bullet list. Qualifications: Nice to Have bullet list. Skills: technical mastery bullet list. Check if we have any content for Qualifications besides Nice to Have. Not really. So we will create Qualifications section with Nice to Have items. Now Benefits: list from "What SmithRx Offers You". We'll bullet each benefit. Pay: include pay range. Now ensure we don't create empty sections. Let's extract details. From "Who We Are": we have paragraph. From "Job Summary": we have paragraph. Combine them under About the role. Now Responsibilities: list each bullet from "What you will do". Let's extract: - 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. Now Requirements (experience): list bullet points from "What you will bring to SmithRx": - 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. - 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. Now Qualifications (Nice to Have): - 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). Now Skills: maybe we could treat the technical mastery list as skills, but we already used many of those in Requirements. To avoid duplication, we could move those technical mastery items to Skills, and keep Requirements as just the experience years and maybe some high-level categories. But the instruction says preserve ALL substantive information; we can duplicate? Better not duplicate. We need to decide a logical split. We could treat