Principal Software Engineer, Core Infrastructure - Nashville

We need to output HTML fragment with sections: h3 headings for sections present: About the role? Actually the posting includes sections: "Responsibilities", "What You'll Bring", "Preferred Qualifications", "Qualifications" (but there is a disclaimer inside Qualifications). Also there is "About Us". Also there is location info: "This position is office-based and requires onsite presence in Nashville, Tennessee. Relocation assistance may be available..." That could be part of About the role? There's no explicit "About the role" heading but we can create a section maybe "About the role" with that info? The instruction: use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section ONLY when the posting has real, specific content for it. So we need to decide which sections have content. We have: - About the role: we have description of OCI, role description, location, relocation assistance. That's substantive. So we can create

About the role

with paragraphs. - Responsibilities: we have "What You'll Do" list. So

Responsibilities

with

• items. - Requirements: The posting has "What You'll Bring" which is essentially requirements. So we can map that to Requirements section. Use

  Requirements

  with list. - Qualifications: There's a "Preferred Qualifications" section and also a "Qualifications" disclaimer. The "Qualifications" heading appears but it's more of a disclaimer about immunization etc. That's not substantive qualifications; it's a disclaimer. We could either not include Qualifications section because it's just boilerplate. The instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a short

  or drop it. Also "Prefer a few substantive sections over many thin ones." The Qualifications disclaimer is not substantive; we can drop it. Preferred Qualifications is substantive; we could treat that as part of Requirements or as a separate "Preferred Qualifications" section. The instruction list includes Skills, Benefits, Pay, Schedule. Not Preferred Qualifications. But we can still include a section if we have content; but we should follow the given examples? It says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. However we should avoid creating sections like "Preferred Qualifications" if not in list? Might be okay but better to incorporate into Requirements or Skills. There's no Skills section explicitly; we could put skills under Requirements or separate Skills. The posting includes many skill items: proficiency in languages, understanding of distributed systems, etc. Those could go under Skills. But we already have Requirements covering education, experience, etc. Could split: Requirements for education/experience, Skills for technical skills. However the instruction says prefer few substantive sections over many thin ones. So maybe combine Requirements and Skills into one Requirements section. But we have a separate "Preferred Qualifications" which could be added as a sub-list under Requirements or as a separate section if we want to keep it thin? Better to incorporate into Requirements as "Preferred qualifications" bullet points. Benefits: The posting includes a detailed benefits list under "Oracle US offers a comprehensive benefits package..." That's substantive. So we need a Benefits section. Pay: The posting includes "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $114,600 - $234,600 per year. May be eligible for bonus, equity, and compensation deferral." That's pay info. So we need a Pay section. Schedule: The posting mentions "This position is office-based and requires onsite presence in Nashville, Tennessee." That's about location, not schedule. No explicit schedule info like full-time, hours. Not provided. So we should not create Schedule section. Thus sections: About the role, Responsibilities, Requirements (including What You'll Bring and Preferred Qualifications), Benefits, Pay. We must not repeat job title as heading. Not include Job ID etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove the "Qualifications Disclaimer" about immunization etc. Also remove "The role will generally accept applications..." etc. Also remove "As part of Oracle's onboarding process..." etc. Also remove "About Us" maybe? The "About Us" paragraph is somewhat promotional but could be considered part of About the role? It's about Oracle mission. Could be included in About the role as extra paragraph. But it's not strictly about the role; still could be included. However we might keep it as part of About the role to avoid extra section. The instruction: include a section ONLY when posting has real, specific content for it. The About Us is specific content about Oracle; we could include it under About the role or as its own section. But we already have About the role; we can append that paragraph there. We must not include the EEO statement etc. Now produce HTML fragment: use

  for each section heading. Use

  for prose. Use

  • for lists. We need to preserve all substantive information; do not invent or summarize away detail. Let's extract content. About the role: Original paragraphs: "Job Description Oracle Cloud Infrastructure (OCI) delivers mission-critical applications for leading enterprises worldwide. Our cloud offers hyperscale, multi-tenant services deployed across more than 50 regions globally. OCI continues to expand beyond traditional public-cloud boundaries to support dedicated, hybrid, and multicloud solutions, edge computing, and more. As a Principal Core Infrastructure Engineer, you will lead the design and evolution of foundational distributed systems behind OCI. You will build highly scalable, elastic, and fault-tolerant services for high-volume data retrieval, storage, and processing, and set the technical direction for their reliability, correctness, security, and operational readiness. This position is office-based and requires onsite presence in Nashville, Tennessee. Relocation assistance may be available in accordance with Oracle's relocation policies." We need to keep all that. Possibly split into two paragraphs: first about OCI, second about role, third about location/relocation. We'll output as

    ...

    . Responsibilities: List under "What You'll Do". Items: - Lead the design, implementation, and ongoing evolution of core distributed systems and data-plane services at hyperscale. - Define scalability, elasticity, durability, and availability requirements for owned components and ensure designs meet them. - Optimize high-throughput data paths for large-scale retrieval, storage, and processing using distributed state, replication, and synchronization patterns. - Design fault-tolerant systems that support in-service updates through redundancy, automatic failover, and recovery-oriented design. - Apply sound distributed-systems tradeoffs for network partitions and reliability, including load shedding, throttling, rate limiting, retries, and timeouts. - Establish service-level objectives, key performance indicators, telemetry, dashboards, and proactive alerting for critical systems. - Design and lead performance, load, fault-injection, and brownout testing to validate correctness, resilience, and operational readiness. - Lead production incident diagnosis and recovery, guide root-cause analysis, and mentor engineers in operational excellence. - Build and improve Infrastructure as Code and operational automation that enable safe patching, updates, rollbacks, and change management. - Apply robust security controls and remediation practices for multi-tenant cloud infrastructure, including encryption, access controls, and compliance readiness. We'll put each as
  • . Requirements: Combine "What You'll Bring" and "Preferred Qualifications". What You'll Bring items: - Bachelor's or master's degree in Computer Science, Computer Engineering, or a related field, or equivalent practical experience. - 7+ years of professional software-engineering experience, with demonstrated impact on large-scale distributed systems or cloud infrastructure. - Strong experience designing and operating highly available, scalable, fault-tolerant distributed systems. - Proficiency in one or more object-oriented or systems programming languages, such as Java, C++, C#, or Go. - Deep understanding of distributed-systems design, data structures, algorithms, operating systems, networking, and secure software-development practices. - Experience with system-level test automation, performance/load testing, reliability engineering, and production incident response. - Demonstrated experience leading or influencing technical architecture and mentoring engineers. - Strong problem-solving, communication, and cross-functional collaboration skills. Preferred Qualifications items: - Experience with Oracle Cloud, AWS, Azure, Google Cloud, or other large-scale cloud platforms. - Experience with data-plane platforms, distributed storage, microservices, replication, state management, or high-throughput data processing. - Experience defining SLOs, building observability systems, and operating services in a 24x7 production environment. - Experience with Infrastructure as Code, service automation, security controls, and compliance requirements for cloud infrastructure. We'll combine into one list under Requirements. Benefits: List from "Oracle US offers a comprehensive benefits package which includes the following:" then bullet 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 - 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 need to keep all that. Some items are long sentences; we can keep as
  • with the full text. Pay: Text: "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $114,600 - $234,600 per year. May be eligible for bonus, equity, and compensation deferral. 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." We'll put that as a

    under Pay section. We should not include the "Oracle US offers a comprehensive benefits package..." under Pay; that's Benefits. Now ensure we didn't include any boilerplate: remove the "Qualifications Disclaimer" paragraph, remove "The role will generally accept applications..." paragraph, remove "As part of Oracle's onboarding process..." paragraph, remove "About Us" maybe we incorporated into About the role; but we need to check if we included About Us text. We didn't include it yet. Should we? The About Us paragraph: "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