Principal Systems Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: About the role? There's a "Job Description" paragraph describing role. That could be "About the role". Responsibilities list present. Required Qualifications list present. Preferred Skills list present. Benefits described. Pay range given. Schedule? Not mentioned. So we include About the role, Responsibilities, Requirements (maybe "Qualifications"), Skills (Preferred Skills), Benefits, Pay. Not Schedule. We must not repeat job title as heading. Use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Qualifications Disclaimer" maybe? That's legal boilerplate; we should drop. Also remove "About Us" maybe? That's boilerplate but could be considered substantive? It's generic marketing; but instructions say remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Us" is not explicitly listed but could be considered boilerplate; but it's not EEO. However it's generic fluff; maybe we keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we keep About Us if not those categories. But we also have "About Us" section after Qualifications Disclaimer. It's marketing but not prohibited. However we also have a separate "About Us" paragraph that could be considered part of "About the role"? Might be redundant. Safer to keep it as part of About the role? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the About Us text as it's substantive (though generic). But we already have an About the role section from the Job Description paragraph. We could combine? Better to keep About the role from the Job Description paragraph, and maybe also include About Us as separate? But we only have headings for predefined list; we could add About the role heading and put the Job Description paragraph there. The About Us paragraph could be considered part of "About the role" as well, but it's about company. Might be okay to include under About the role as additional prose. However we must not create filler sections. We'll include About the role with the Job Description paragraph plus maybe the About Us paragraph? That would be mixing. Safer: Keep About the role as the Job Description paragraph only. Keep About Us as separate? Not in allowed headings list; we could omit it because it's not required heading. But we would be dropping substantive info (About Us). The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep About Us info somewhere. Since we cannot add arbitrary headings, we could incorporate it into About the role section as additional prose after the Job Description paragraph. That seems reasonable: About the role includes both role description and company overview. That preserves info. Now Responsibilities: we have a list of bullet points (each line starts with a verb). We'll put each as

• . Requirements: we have Required Qualifications list. We'll put as
• . Also we have Bachelor's degree etc. We'll include. Skills: Preferred Skills list. We'll put as
• . Benefits: list of benefits. We'll put as
• . Pay: we have range: "US: Hiring Range in USD from: $79,900 - $187,000 per year. May be eligible for bonus and equity." We'll put as

  . We must not include headings with filler like "commensurate with experience". Not present. We must not include Schedule section. We must not include Job ID/requisition numbers. We must not include boilerplate like "Qualifications Disclaimer", "The role will generally accept applications..." etc. Those are application instructions or legal; we drop them. Also drop "Accommodations to this requirement may be granted..." etc. That's legal; drop. Also drop "Only Oracle brings together..." etc (About Us) we kept inside About the role. We must output only HTML fragment, no /, no markdown fences. Let's craft. Structure:

  About the role

  We are seeking a technical operations leader to join the AI Infra Operations team as a Principal Systems Engineer supporting GPU infrastructure in Oracle Cloud Infrastructure (OCI). In this role, you will lead the development and maintenance of automation and operational tooling for GPU fleets across multiple regions, ensuring high availability. You will collaborate closely with engineering and operations teams to build robust automation, observability, and reliability solutions while continuously improving GPU operations. Only Oracle brings together the data, infrastructure, applications, and expertise to power everything from industry innovations to life-saving care. And with AI embedded across our products and services, we help customers turn that promise into a better future for all. Discover your potential at a company leading the way in AI and cloud solutions that impact billions of lives. True innovation starts when everyone is empowered to contribute. That’s why we’re committed to growing a workforce that promotes opportunities for all with competitive benefits that support our people with flexible medical, life insurance, and retirement options. We also encourage employees to give back to their communities through our volunteer programs. We’re committed to including people with disabilities at all stages of the employment process. If you require accessibility assistance or accommodation for a disability at any point, let us know by emailing accommodation-request_mb@oracle.com or by calling 1-888-404-2494 in the United States. Oracle is an Equal Employment Opportunity Employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, national origin, sexual orientation, gender identity, disability and protected veterans’ status, or any other characteristic protected by law. Oracle will consider for employment qualified applicants with arrest and conviction records pursuant to applicable law.

  But note: The last part about EEO is boilerplate; we should remove EEO/equal-opportunity boilerplate. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. So we must drop those lines. Also the accommodation request line maybe not EEO but it's about accommodation; could be considered part of EEO? It's about disability accommodation; might be considered EEO-related. Safer to remove that as well. Also the line about Oracle is an Equal Employment Opportunity Employer etc. Remove. Thus About the role should contain only the substantive role description and maybe the generic marketing about Oracle (the "Only Oracle brings together..." paragraph). That paragraph is not EEO; it's marketing. We'll keep that. Thus About the role paragraph: "We are seeking a technical operations leader to join the AI Infra Operations team as a Principal Systems Engineer supporting GPU infrastructure in Oracle Cloud Infrastructure (OCI). In this role, you will lead the development and maintenance of automation and operational tooling for GPU fleets across multiple regions, ensuring high availability. You will collaborate closely with engineering and operations teams to build robust automation, observability, and reliability solutions while continuously improving GPU operations. Only Oracle brings together the data, infrastructure, applications, and expertise to power everything from industry innovations to life-saving care. And with AI embedded across our products and services, we help customers turn that promise into a better future for all. Discover your potential at a company leading the way in AI and cloud solutions that impact billions of lives. True innovation starts when everyone is empowered to contribute. That’s why we’re committed to growing a workforce that promotes opportunities for all with competitive benefits that support our people with flexible medical, life insurance, and retirement options. We also encourage employees to give back to their communities through our volunteer programs. We’re committed to including people with disabilities at all stages of the employment process." We might keep the last sentence about including people with disabilities; it's not EEO boilerplate but a statement of commitment; could be kept. Now Responsibilities: list each bullet. We need to ensure we capture all responsibilities lines: - Build and maintain automation and operational tooling for OCI GPU infrastructure across multiple geographic regions. - Drive collaboration with software engineers, hardware teams, and operations partners to maintain a highly available GPU fleet. - Build and improve monitoring, alerting, and diagnostics for GPU fleet health, performance, capacity, and utilization using tools such as Grafana. - Serve as the senior escalation point for complex GPU host and repair issues - Participate in incident response and root-cause analysis to remove blockers affecting GPU capacity, availability, and regional deployments. - Continuously improve AI2 Ops processes, GPU fleet automation, and OCI region build readiness. - Participate in on-call rotations and provide support for critical infrastructure issues. - Document operational procedures, automation workflows, troubleshooting guides, and runbooks. - Build and improve AI agents, ensuring safe rollout, execution and monitoring. - Mentor and guide junior engineers in operational best practices, provide senior technical support, and drive constant improvement. Make sure each ends with period. Now Required Qualifications list: - 8+ years of software operations or infrastructure automation experience with strong proficiency in Python and Bash. - Expert Linux administration experience, particularly Ubuntu and Oracle Linux, in large-scale production environments. - Strong understanding of distributed systems, including peer-to-peer, node-to-node, and service-to-service communication patterns. - Strong data-center and host-lifecycle experience, including provisioning, validation, repair workflows, hardware replacement, and fleet recovery. - Strong problem-solving and troubleshooting skills. - Excellent communication and teamwork skills. - Experience with observability tooling, including metrics, logging, dashboards, and alerting. - Experience with AI agents and tooling - Experience leading on-call operations and incident response. - Bachelor's degree in Computer Science, Engineering, or a related field, or equivalent practical experience. Note: "Experience with AI agents and tooling" line missing period; we can add. Now Preferred Skills list: - Hands-on experience with GPU infrastructure, including NVIDIA and AMD based systems, and familiarity with GPU shapes or instance families. - Experience operating or automating GPU, compute, or other large-scale cloud infrastructure. Now Benefits list: we need to capture all benefits described. From text: - Medical, dental, and vision insurance, including expert medical opinion - Short term disability and long term disability - Life insurance and AD&D - Supplemental life insurance (Employee/Spouse/Child) - Health care and dependent care Flexible Spending Accounts - Pre-tax commuter and parking benefits - 401(k) Savings and Investment Plan with company match - Paid time off: Flexible Vacation is provided to all eligible employees assigned to a salaried (non-overtime eligible) position. Accrued Vacation is provided to all other employees eligible for vacation benefits. For employees working at least 35 hours per week, the vacation accrual rate is 13 days annually for the first three years of employment and 18 days annually for subsequent years of employment. Vacation accrual is prorated for employees working between 20 and 34 hours per week. Employees working fewer than 20 hours per week are not eligible for vacation. - 11 paid holidays - Paid sick leave: 72 hours of paid sick leave upon date of hire. Refreshes each calendar year. Unused balance will carry over each year up to a maximum cap of 112 hours. - Paid parental leave - Adoption assistance - Employee Stock Purchase Plan - Financial planning and group legal - Voluntary benefits including auto, homeowner and pet insurance We should keep each as
• . Some are sentences; we can keep as is. Now Pay: we have "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $79,900 - $187,000 per year. May be eligible for bonus and equity. Oracle maintains