Staff Systems Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to extract sections: Who We Are (company description) could be "About the role"? Actually "About the role" is usually a summary of the role. The posting includes "Job Summary:" which is a summary of the role. So we can put that under
About the role
with prose.
Then "What you will do:" is responsibilities. So Responsibilities
with list.
Then "What you will bring to SmithRx:" includes experience and qualifications. Could be split into Requirements and Qualifications? The instruction says we can have Requirements, Qualifications, Skills sections. We need to decide based on content. The "What you will bring to SmithRx:" includes Experience, Mastery of 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 qualifications/requirements. Could be under Requirements
or Qualifications
. Since they are qualifications, maybe use Qualifications. But we also have "Nice to Have:" which could be Skills? Actually nice to have are additional qualifications/skills. Could be under Skills
for nice-to-have. Or we could combine.
We also have "What SmithRx Offers You:" which includes benefits. So we need Benefits section. Also Pay Range is given: "$136,000 USD - $160,000 USD". So we need Pay section. Schedule not mentioned, so we should not create Schedule section.
We must not include filler like "commensurate with experience". Not present.
We need to remove boilerplate: "Who We Are:" includes mission etc. That's substantive. Keep.
We need to preserve all substantive information. So we need to include the mission description etc.
We need to format as HTML fragment only, no or . Use headings,
for prose,
- for lists.
We need to decide how to structure lists: For responsibilities, each bullet is a sentence starting with a bold heading? In the text, responsibilities are listed as headings like "Strategic Architecture & Ecosystem Vision:" then description. We could treat each as a list item with the heading as strong text inside
- . Similarly for qualifications.
We need to preserve all detail, not summarize.
Let's extract sections:
Who We Are: (company description) - we can put under About the role? Actually About the role is usually role summary. But we have Job Summary separate. The "Who We Are" is company overview. Could be placed under About the role? Might be better to treat as About the company, but instructions only list certain headings; we can use About the role for role summary, and maybe we can incorporate company description into that? But we must preserve all substantive information; we could add a
under About the role that includes both company description and job summary? However the instruction says use headings for sections like About the role, Responsibilities, etc. It doesn't forbid adding extra paragraphs under those headings. So we can put company description under About the role as prose, then job summary also there? Might be mixing.
Alternatively, we could create a section "About the company" but not in allowed headings. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but it says use those for section headings (e.g.) implying we should stick to those. Safer to use only those headings. So we need to map content to those headings.
We have:
- About the role: could contain Job Summary and maybe company description? But company description is not about the role. However we could still put it there as part of context. The instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid adding extra info.
Thus we can put under About the role: a paragraph describing the company (Who We Are) and then the Job Summary.
Alternatively, we could split: About the role = Job Summary; and we could add another heading like "About the company" but not allowed. Better to keep to allowed headings.
Thus:
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 each bullet.
We need to capture each responsibility heading and its description.
Responsibilities list:
- 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'll put each as - with maybe for the heading.
Then Requirements/Qualifications: The "What you will bring to SmithRx:" list.
We could split into Requirements (mandatory) and Nice to Have (preferred). The instruction allows Requirements, Qualifications, Skills sections. We could treat the main list as Requirements, and Nice to Have as Skills.
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.
- 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 Mind
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to extract sections: Who We Are (company description) could be "About the role"? Actually "About the role" is usually a summary of the role. The posting includes "Job Summary:" which is a summary of the role. So we can put that under
About the role
with prose. Then "What you will do:" is responsibilities. SoResponsibilities
with list. Then "What you will bring to SmithRx:" includes experience and qualifications. Could be split into Requirements and Qualifications? The instruction says we can have Requirements, Qualifications, Skills sections. We need to decide based on content. The "What you will bring to SmithRx:" includes Experience, Mastery of 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 qualifications/requirements. Could be underRequirements
orQualifications
. Since they are qualifications, maybe use Qualifications. But we also have "Nice to Have:" which could be Skills? Actually nice to have are additional qualifications/skills. Could be underSkills
for nice-to-have. Or we could combine. We also have "What SmithRx Offers You:" which includes benefits. So we need Benefits section. Also Pay Range is given: "$136,000 USD - $160,000 USD". So we need Pay section. Schedule not mentioned, so we should not create Schedule section. We must not include filler like "commensurate with experience". Not present. We need to remove boilerplate: "Who We Are:" includes mission etc. That's substantive. Keep. We need to preserve all substantive information. So we need to include the mission description etc. We need to format as HTML fragment only, no or . Useheadings,
for prose,
- for lists. We need to decide how to structure lists: For responsibilities, each bullet is a sentence starting with a bold heading? In the text, responsibilities are listed as headings like "Strategic Architecture & Ecosystem Vision:" then description. We could treat each as a list item with the heading as strong text inside
- . Similarly for qualifications.
We need to preserve all detail, not summarize.
Let's extract sections:
Who We Are: (company description) - we can put under About the role? Actually About the role is usually role summary. But we have Job Summary separate. The "Who We Are" is company overview. Could be placed under About the role? Might be better to treat as About the company, but instructions only list certain headings; we can use About the role for role summary, and maybe we can incorporate company description into that? But we must preserve all substantive information; we could add a
under About the role that includes both company description and job summary? However the instruction says use headings for sections like About the role, Responsibilities, etc. It doesn't forbid adding extra paragraphs under those headings. So we can put company description under About the role as prose, then job summary also there? Might be mixing. Alternatively, we could create a section "About the company" but not in allowed headings. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but it says use those for section headings (e.g.) implying we should stick to those. Safer to use only those headings. So we need to map content to those headings. We have: - About the role: could contain Job Summary and maybe company description? But company description is not about the role. However we could still put it there as part of context. The instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid adding extra info. Thus we can put under About the role: a paragraph describing the company (Who We Are) and then the Job Summary. Alternatively, we could split: About the role = Job Summary; and we could add another heading like "About the company" but not allowed. Better to keep to allowed headings. Thus:
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 each bullet. We need to capture each responsibility heading and its description. Responsibilities list: - 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'll put each as - with maybe for the heading.
Then Requirements/Qualifications: The "What you will bring to SmithRx:" list.
We could split into Requirements (mandatory) and Nice to Have (preferred). The instruction allows Requirements, Qualifications, Skills sections. We could treat the main list as Requirements, and Nice to Have as Skills.
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.
- 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 Mind