Jobs · Engineering · Tennessee

Senior Platform Software Engineer - Kubernetes

Oracle · Nashville, TN · 1 mo ago
Engineering$93k–$210k/yrFull-time
We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. Must include only sections with real specific content. We need to parse the job description. Content: - Intro paragraph: "Are you passionate about Kubernetes, cloud-native technologies, and open source software? ..." This is about the role. Could be "About the role". Use

About the role

then

...

. - Responsibilities: The posting says "Responsibilities" then a line break then "Required qualifications:" Actually after "Responsibilities" there is no bullet list; it directly goes to "Required qualifications:" So responsibilities section may be empty? Actually there is no list of responsibilities given; they just say "As a Senior Platform Software Engineer, you will be part of a team..." That's more about role. There's no explicit responsibilities list. So we should not create a Responsibilities heading if no specific content. - Required qualifications: list of items after "Required qualifications:" includes Bachelor’s degree..., 3+ years..., Strong programming skills..., Experience designing APIs..., Solid understanding..., Demonstrated ownership..., Clear written... That's a list. So we can make a section

Requirements

(or Qualifications?). The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we have Requirements and Qualifications separate. Usually "Required qualifications" could go under Requirements. "Preferred qualifications" could go under Qualifications. Or we could combine. But we need to follow instruction: use those headings when content exists. So we can have:

Requirements

with ul list of required qualifications.

Qualifications

with ul list of preferred qualifications. - Skills: Not explicitly listed as separate; but we could infer from required qualifications includes programming skills etc. But we should not invent. There's no separate "Skills" section. So skip. - Benefits: The posting includes "Oracle US offers a comprehensive benefits package which includes the following:" then a list. So we can have

Benefits

with ul list. - 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: $92,500 - $209,500 per year. May be eligible for bonus and equity." That's pay info. So we can have

Pay

with p containing that sentence. - Schedule: Not mentioned. No schedule info. So skip. - About Us: There's a section "About Us" after qualifications disclaimer etc. That's not exactly "About the role". But we already have About the role from intro. The "About Us" is more company description. Could we treat as About the role? Already used. Could we add another section like "About the company"? Not in allowed headings. So we may ignore or incorporate into About the role? But we should not repeat heading. The instruction: Use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not limited to those? It says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should not add About Us heading. We can incorporate that paragraph into About the role maybe? But About the role already has intro. Could add another paragraph under same heading? It's okay to have multiple

under same heading. So we can add the About Us paragraph as another

under About the role. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. At end there is EEO statement, accommodation request, etc. Remove those. Also remove "Qualifications Disclaimer: Certain U.S. based..." that's legal; maybe keep? It's a disclaimer about immunization etc. That's legal boilerplate; should remove. Also remove "The role will generally accept applications for at least three calendar days..." that's application instruction; remove. Also remove "As part of Oracle's onboarding process..." that's legal; remove. Also remove "Only Oracle brings together..." that's About Us but we kept. We need to preserve all substantive information. So keep the benefits list, pay range, required qualifications, preferred qualifications, about role/intro, about us. Now construct HTML. Structure:

About the role

Are you passionate about Kubernetes, cloud-native technologies, and open source software? Do you enjoy solving complex engineering challenges at scale? Join Oracle Cloud Infrastructure (OCI) and help build the next generation of cloud-native services that power enterprise workloads around the world. As a Senior Platform Software Engineer, you will be part of a team focused on enhancing the Kubernetes experience on OCI. You will design, develop, and deliver innovative solutions that help customers deploy, manage, and scale applications using modern cloud-native technologies. Your work will directly contribute to strategic initiatives such as Kubernetes cluster lifecycle management, infrastructure automation, and open-source projects that simplify running workloads on OCI. You'll collaborate with talented engineers across OCI to build reliable, scalable, and secure distributed systems while contributing to the broader Kubernetes and CNCF ecosystem. This is an opportunity to work on impactful projects, influence technical direction, and solve challenging problems that affect customers at a global scale. We're looking for engineers who are curious, collaborative, and passionate about building high-quality software. If you thrive in a fast paced environment, enjoy taking ownership, and want to help shape the future of cloud infrastructure, we'd love to hear from you.

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.

But note the accommodation request line is maybe considered EEO/boilerplate? It's about accommodation for disability; could be considered EEO? Might be borderline. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. The accommodation request line is part of EEO? It's about accommodation; might be considered EEO. Safer to remove that line. Also the sentence about "We’re committed to including people with disabilities..." is also EEO. So we should remove those sentences. Keep the rest about Oracle's mission. Thus 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 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'll keep that. Now Requirements section:

Requirements

  • Bachelor’s degree in Computer Science, Engineering, or a related technical field, or equivalent practical experience.
  • 3+ 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.
Qualifications section (preferred):

Qualifications

  • Experience in one or more of the following areas is a plus: Application deployment platforms, continuous delivery, GitOps, artifact management, or developer platform engineering.
  • Large-scale distributed systems, multi-tenant cloud services, control planes, or workflow orchestration.
  • Site reliability engineering, production incident response, observability, or capacity and performance engineering.
  • Security engineering, identity and access management, policy-as-code, supply-chain security, or compliance automation.
  • with each bullet. But the original had "Experience in one or more of the following areas is a plus." then bullet list. We'll keep as separate bullet? Could combine but okay. Now Benefits section:

    Benefits

    • 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
    Pay section:

    Pay

    Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $92,500 - $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.

    We could keep the extra explanation about ranges; it's substantive. Schedule: none. Now ensure we didn't include any boilerplate like "Qualifications Disclaimer", "

Similar jobs