Systems Engineer II, Healthcare IT
- . For prose use
. We need to avoid repeating job title as heading. Not include Job ID. We need to output only HTML fragment. Let's craft. First, About the role: combine introductory paragraphs up to On-Call Responsibility? Might be considered role description. We'll include all paragraphs before "Key job responsibilities". That includes description of team, role, on-call responsibility. We'll keep as prose (maybe multiple
). Ensure we keep all details. Then Responsibilities: list from "Key job responsibilities". We'll extract each bullet. Let's list them: - Own the operational health, availability, and performance of a fleet of over 7,000 healthcare endpoints (Windows, macOS, iOS, Android) - Build reusable automation and tooling that scales fleet operations: device provisioning, patching, compliance enforcement, and configuration management - Serve as an excellent diagnostician: interpret logs, understand dependencies, and root-cause failures across endpoint, identity, and network systems - Provide tier 3 support for production healthcare endpoint infrastructure, resolving complex escalations from field teams - Integrate device management platforms (MDM), identity providers (Active Directory, SAML/SSO), and operational tooling through scripting and APIs - Identify and remediate operational and security risks across the fleet; participate in security compliance reviews and vulnerability management - Build monitoring, alerting, dashboards, and metrics reporting for device health, patch compliance, login latency, and fleet-wide anomalies - Support specialized device fleet infrastructure including image tuning, patching, and monitoring - Drive operational excellence initiatives that demonstrate measurable improvements in reliability, compliance, or support burden - Create and review SOPs, runbooks, and operational documentation; drive engineering and operational best practices - Participate in a 24x7 on-call rotation for critical infrastructure services We need to keep all. Then Requirements (Basic Qualifications): - Bachelor's degree in Systems Engineering, Computer Science, or related field or relevant work experience - 4+ years of site reliability engineering (SRE), systems engineering, systems administration, DevOps, security administration, or network administration experience - Experience with a scripting language such as PowerShell, Python, Bash, Perl, Ruby or similar - Knowledge of networking protocols such as HTTP(S), DNS, and TCP/IP - Experience in systems administration (Windows/MacOS) Then Qualifications (Preferred Qualifications): - Experience designing and developing scripts to automate operational burdens and reviewing scripting changes to ensure they meet the standards for maintainability, scalability and security - Experience working in 24/7 production environment - Experience with service-oriented architecture and web services - AWS Certification (Cloud Technologist, Solutions Architect, SysOps Administrator, Developer), or equivalent Microsoft Certification such as Microsoft Certified: Windows Server Administrator Associate, Microsoft 365 Certified: Endpoint Administrator Associate, or equivalent. Then Skills: maybe we can extract from qualifications and responsibilities: scripting languages, networking protocols, systems administration, automation, MDM, identity providers, monitoring, etc. But to avoid duplication, maybe we can just list skills that are not already covered? However instruction says preserve ALL substantive information; we can't omit any. If we put skills separately, we might duplicate content already in Requirements/Qualifications. But duplication is allowed? It says do not repeat the job title as a heading and do not put Job ID as headings — fold minor metadata into a short
or drop it. It doesn't forbid duplication of content across sections, but we should avoid unnecessary duplication? It says preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to not duplicate unnecessarily. However we could treat Skills as a summary of key technical skills: scripting, networking, systems admin, automation, MDM, identity, monitoring, cloud, etc. That might be derived from existing content but not verbatim duplication. Might be okay. But maybe we can skip Skills section and incorporate skills into Requirements/Qualifications. However instruction says we can use those headings; we can choose to include Skills if we have content. We have content: experience with scripting language, knowledge of networking protocols, experience in systems administration, experience designing scripts, experience with 24/7 production, experience with SOA/web services, certifications. That's basically the qualifications. So Skills may be redundant. Safer to omit Skills section to avoid thin sections? But we have enough content for Skills; but it's basically same as qualifications. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we should combine Skills into Requirements/Qualifications and not have a separate Skills section. Let's decide to omit Skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Check if we have Benefits: yes. Pay: yes. Now we need to format. We'll produce:
About the role
... paragraphs ...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
... benefits description ...
Pay
The base salary range for this position is $104,500.00 - $160,000.00 USD annually. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location.
We need to ensure we preserve all substantive info from benefits: health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave. Also mention link to learn more about benefits (we can keep as part of prose). Should we keep the link? It's not boilerplate? It's a link to benefits page; it's substantive. We'll include. Now About the role prose: need to include all details from intro paragraphs and on-call responsibility. Let's craft a concise but complete paragraph(s). We'll break into maybe two paragraphs for readability. Paragraph 1: Healthcare IT powers technology delivery across One Medical's nationwide clinic network and Amazon Pharmacy's fulfillment operations. Our team owns the engineering, deployment, management, patching, and support of healthcare endpoints once they reach the field, ensuring clinicians and pharmacy staff have reliable, secure technology that stays out of their way so they can focus on patients. As a Systems Engineer on the Healthcare IT team, you will own the operational health of a fleet of over 7,000 endpoints spanning Windows, macOS, iOS, and Android across hundreds of clinic and fulfillment center locations. You will use technology to solve difficult operational problems: keeping devices patched, compliant, and performant at scale, root-causing failures across endpoint, identity, and network systems, and building the automation that lets a talented team operate a large fleet. You will serve as tier 3 support for on-site technology teams, owning the escalation path for complex endpoint infrastructure issues that require deep technical investigation. This is