Senior Core Infrastructure Engineer (Nashville, TN)

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Also remove "About Us" maybe? The instruction says include a section ONLY when posting has real specific content. The posting includes location, relocation assistance, onsite, description of team, responsibilities, must-have skills, qualifications, benefits, pay range, schedule (onsite 5 days/week). Also maybe "About the role" could be the initial description before responsibilities. We'll need to parse. We need sections: - About the role: could be the introductory paragraph(s) describing the team and role. That includes location, relocation assistance, onsite, description of App Configuration Service team building OCI platform service, etc. That is substantive. - Responsibilities: there is a "Key Responsibilities" section with many bullet points. We'll need to convert to

• . - Requirements: maybe the "MUST-HAVE SKILLS" section qualifies as Requirements. Could also be Skills. The instruction says use headings for Requirements, Qualifications, Skills. We need to decide mapping. The posting has "MUST-HAVE SKILLS:" which is skills. Also "Qualifications Disclaimer:" then some text about US based roles, immunization, etc. Then "Range and benefit information provided..." then benefits. Then "Oracle US offers a comprehensive benefits package..." So we have Benefits and Pay. We also have schedule: "Location: Nashville, TN — onsite 5 days/week." So schedule is onsite 5 days/week. We need to include Pay section: they gave hiring range $79,200 - $209,500 per year, may be eligible for bonus and equity. That's specific. We need Benefits section: list of benefits. We need Qualifications: maybe the "Qualifications Disclaimer:" plus the text about US based roles etc. But that seems more like a disclaimer. However there is also "Qualifications" heading in the posting? Actually they have "Qualifications Disclaimer:" then a paragraph. That could be considered Qualifications. We'll include that as Qualifications section. We need Skills: the MUST-HAVE SKILLS list. We need to avoid filler like "commensurate with experience". Not present. We need to remove boilerplate: EEO, equal opportunity, scam warning, etc. At the end there is a lot of EEO statement. Remove that. Also remove "The role will generally accept applications..." etc (application instructions). Also remove "As part of Oracle's onboarding process..." etc (maybe not boilerplate but could be considered part of qualifications? It's about identity verification; might be considered part of qualifications? It's a requirement for US-based employees. Might be considered part of Qualifications? But it's more about onboarding. The instruction says remove application instructions, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines. The identity verification part might be considered legal/boilerplate? It's about compliance with law. Might be considered boilerplate. Safer to remove it. Also remove "About Us" section? That's more marketing; could be considered boilerplate? It's not strictly EEO but could be considered fluff. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "About Us" is substantive? It's generic marketing. Might be considered boilerplate but not explicitly listed. However it's not about the role. I'd lean to remove it as it's not specific to the role. The instruction: "Prefer a few substantive sections over many thin ones." So we could omit About Us. Thus sections: About the role, Responsibilities, Requirements (maybe we treat MUST-HAVE SKILLS as Skills, and Qualifications as the disclaimer), Skills, Benefits, Pay, Schedule. We need to ensure we don't repeat content. Let's extract content. Location paragraph: "Location: Nashville, TN — onsite 5 days/week. Relocation assistance is available; this is not a remote position." Then description: "The App Configuration Service team is building a new OCI platform service for application configuration and feature flighting. The team will enable OCI services to safely, consistently, and reliably manage dynamic configuration, targeted feature rollouts, experimentation, and emergency kill switches across distributed cloud environments. The team owns the end-to-end platform: service APIs, control plane, globally distributed configuration evaluation path, SDKs and self-service tooling, security and access controls, auditability, observability, and the operational model required for a Tier-0 service. As a greenfield team, we are also building and operating in an AI-first way—using AI-assisted development, automation, and intelligent operational workflows to improve how we design, build, test, review, document, release, and run the service. This gives engineers the opportunity to shape both a high-impact cloud platform and modern AI-enabled engineering practices from the ground up." That's About the role. Responsibilities: The bullet list under "Key Responsibilities". We'll need to capture each bullet. Let's list them: System Design & Architecture - System Scalability: - Implements and contributes to the development for components of distributed systems that support horizontal and vertical scaling including leveraging distributed state management tools. - Optimizes code and/or systems for large-scale data processing in large-scale systems. - Implements scalability requirements for assigned components and reviews implementation of team members. - Leverages components of data plane platforms to handle large-scale data retrieval, storage, and processing. - Implements performance and load testing. System Design & Architecture - System Reliability Design: - Collaborates with team to build fault-tolerant components capable of withstanding in-service updates by implementing redundancy, replication, and automatic failover mechanisms. - Applies recovery oriented computing principles to design components that effectively handle service disruptions. - Implements retry mechanisms, circuit breakers, and timeouts to help handle network unreliability. System Design & Architecture - System Reliability Performance: - Implements tests and alarm configurations to proactively detect and address issues/failures. - Supports efforts to recover from failures by drafting and executing runbooks and operational procedures. - Builds and customizes dashboards, telemetry systems, and alerting mechanisms to monitor component health. System Design & Architecture - Correctness / Availability: - Designs and implements functional requirements and testing for assigned features within an existing system. - Implements tests scenarios (e.g., fault-injection, brown-out) to evaluate system correctness. - Implements standard data replication and synchronization techniques to maintain data integrity and availability. Operational Troubleshooting & Incident Management: - Diagnoses, debugs, and resolves issues in system components to support ongoing operation. - Implements basic strategies to prevent interruptions, ensuring no maintenance windows are required for customers and users when resolving issues. - Designs and implements automation scripts and tooling used to troubleshoot operational issues. - Participates in operational support rotations, assisting in incident responses and root cause investigations. Compliance & Security: - Applies advanced security measures to protect data and applications in multi-tenant environments, including encryption and access controls. - Implements remediation plans to continuously improve security. - Collaborates with the team to ensure cloud infrastructure complies with relevant industry standards and regulations and that documentation is up-to-date Automation & Change Management: - Maintains automation scripts and tools (e.g., Infrastructure as Code (IaC)) for managing cloud infrastructure. - Adheres to change management plans for patching, updating, and rolling back applications. We'll need to output as
  • items. Could group under headings? The instruction: use

    for section headings,

    • for any list of duties/requirements/benefits, and

      for prose. So for Responsibilities we can have a

      Responsibilities

      then a
      with all the bullet items as
      • . No need to preserve subheadings like "System Design & Architecture - System Scalability:" as separate headings because they'd be extra sections; but we could keep them as part of the
      • text. That's fine. Now Requirements: The posting has "Qualifications Disclaimer:" and then some text about US based roles etc. That could be Qualifications. But we also have "MUST-HAVE SKILLS:" which is Skills. The instruction says we have separate headings for Requirements, Qualifications, Skills. We need to decide what goes where. Maybe Requirements = the "MUST-HAVE SKILLS:"? But they also have Skills heading. Actually they used "MUST-HAVE SKILLS:" which is clearly skills. So Skills = that list. Requirements could be the "Qualifications Disclaimer:" plus maybe the earlier description of experience? But that's more like qualifications. However the posting also has a paragraph after "Qualifications Disclaimer:" that mentions immunization etc. That's not really qualifications but more a disclaimer. Could treat as Qualifications. But we also have a paragraph earlier: "5+ years of professional software development experience, with a record of delivering production-quality distributed systems, platform services, or developer tools." That's part of MUST-HAVE SKILLS list. So Skills covers that. Thus Requirements might be empty? We could omit Requirements section if no specific content besides what's already in Skills. But we need to follow instruction: include a section ONLY when posting has real specific content. If we don't have distinct Requirements content, we omit it. Thus sections: About the role, Responsibilities, Skills, Qualifications, Benefits, Pay, Schedule. Now extract Skills list: MUST-HAVE SKILLS: - 5+ years of professional software development experience, with a record of delivering production-quality distributed systems, platform services, or developer tools. - Strong programming skills in one or more modern languages such as Java, Go, C++, C#, Python, or similar. - Experience designing APIs, data models, and service architectures with attention to scalability, availability, security, and operability. - Solid understanding of cloud-native systems, including containers, orchestration, CI/CD, infrastructure automation, or release engineering concepts. - Demonstrated ownership: you can drive work from problem definition through design, implementation, launch, and ongoing operation. - Clear written and verbal communication skills, and the ability to collaborate effectively across engineering disciplines. - Strong understanding of distributed-systems fundamentals, including consistency tradeoffs, failure handling, concurrency, and resilient service design. - Experience with code review, automated testing, and CI/CD practices. Now Qualifications: The "Qualifications Disclaimer:" paragraph: "Disclaimer: Certain U.S. based or U.S. customer or client-facing roles may be required to comply with applicable requirements, such as immunization/occupational health mandates, and/or drug testing requirements." Then after that there is "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $79,200 - $209,500 per year. May be eligible for bonus and equity. Oracle maintains broad salary ranges for its roles in order to account for variations in knowledge, skills, experience, market conditions and locations, as well as reflect Oracle's differing products, industries and lines of business. Candidates are typically placed into the range based on the preceding factors as well as internal peer equity." That seems more about Pay and Benefits. Actually the pay range is there. So we need to separate Pay from Qualifications. Thus Qualifications section could just be the disclaimer about immunization etc. That's specific content. Now Benefits: The paragraph after "Oracle US offers a comprehensive benefits package which includes the following:" then list. Let's extract benefits list: - 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 -