Principal Software Engineer, Platform

Oracle · Nashville, TN · 1 mo ago

Engineering$105k–$235k/yrFull-time

We need to output HTML fragment with sections: About the role (maybe description), Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay, Schedule. Only include sections that have real content. We need to parse the job description. First, we have a description paragraph: "Job Description Oracle Cloud Infrastructure (OCI) delivers mission-critical applications..." That's about the role. So we can have

About the role

with paragraphs. Then Responsibilities: bullet list under "What You'll Do". We'll create

for each bullet. Then Requirements: The "What You'll Bring" section includes degree, years experience, etc. That's qualifications. Could be under
Requirements
or
Qualifications
. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose either Requirements or Qualifications. Since there is a "Qualifications" heading later (Preferred Qualifications). We could combine both required and preferred under Qualifications. But we need to avoid filler. We'll include a Qualifications section with required and preferred bullet lists. Also there is a "Qualifications Disclaimer:" paragraph about US based roles etc. That's not really a qualification but legal. Might be considered boilerplate; we should remove cookie/navigation/legal/EEO etc. The disclaimer about immunization etc might be considered legal boilerplate; we should remove. Also the "Range and benefit information provided..." is about Pay and Benefits. We'll extract Pay and Benefits. Pay: "US: Hiring Range in USD from: $104,500 - $234,600 per year. May be eligible for bonus, equity, and compensation deferral." That's pay info. Benefits: list of benefits after "Oracle US offers a comprehensive benefits package which includes the following:" then bullet list. Schedule: The posting mentions "This position is office-based and requires onsite presence in Nashville, Tennessee." Also maybe "Relocation assistance may be available". That's about location, not schedule. No explicit schedule like full-time, part-time. There's mention of vacation accrual etc but that's benefits. No explicit schedule. So we should not create Schedule section unless stated. There's no schedule info like "Full-time" etc. So omit. Skills: Could be derived from "Proficiency in one or more object-oriented or systems programming languages, such as Java, C++, C#, or Go." etc. Could be a Skills section. But we could also include under Qualifications. The instruction says prefer a few substantive sections over many thin ones. We could combine skills into Qualifications. But we have a separate Skills heading allowed. Might be better to include Skills section with bullet list of technical skills: Java, C++, C#, Go, distributed systems, APIs, middleware, etc. However we need to avoid inventing. We can extract from "Proficiency in one or more object-oriented or systems programming languages, such as Java, C++, C#, or Go." and "Strong experience designing highly available, scalable distributed systems and evolving production APIs or platform interfaces." and "Deep understanding of distributed-systems fundamentals, object-oriented design, data structures, algorithms, and secure software-development practices." Also "Experience with microservices, SDKs, RESTful APIs, containers, cloud-native deployments, or developer-platform products." etc. That's a lot; could be a Skills section. But we also have a Qualifications section that includes required and preferred qualifications. Might be redundant to have both Qualifications and Skills. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid having both Qualifications and Skills. We can include both if they have substantive content. We need to avoid filler like "commensurate with experience". Not present. We need to remove boilerplate: EEO, equal-opportunity, scam-warning, navigation, cookie, legal. The "Qualifications Disclaimer:" about immunization etc is legal; we should remove. Also the paragraph about "Range and benefit information provided in this posting are specific to the stated locations only" is part of Pay/Benefits but we can keep the pay and benefits info; the sentence about specificity can be dropped as filler? It's not substantive; we can drop. Also the paragraph about "The role will generally accept applications for at least three calendar days..." is application instructions; remove. Also the "About Us" paragraph is company description; could be considered boilerplate but it's substantive about Oracle. Might be okay to keep as part of About the role? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Us" is not explicitly listed to remove, but it's more marketing. Might be okay to keep as part of About the role? However we already have About the role from the job description. The "About Us" could be considered extra but not boilerplate. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it if it's substantive. But we already have a description of OCI and role. The About Us is more generic about Oracle. Could be considered part of About the role? Might be okay to include as another paragraph under About the role. We need to output only HTML fragment, no /, no markdown. Let's structure:
About the role

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 Platform Software Engineer, you will shape the platform foundations that allow OCI services and their consumers to work together reliably at scale. You will lead cross-team initiatives involving APIs, middleware, runtimes, integration frameworks, and developer tooling—setting technical direction while delivering durable solutions that improve consistency, compatibility, and developer experience. This position is office-based and requires onsite presence in Nashville, Tennessee. Relocation assistance may be available in accordance with Oracle's relocation policies.

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 the second paragraph includes EEO statement? Actually it includes accommodation request and disability inclusion; that's not EEO but could be considered part of company statement. It's not explicitly prohibited. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. The accommodation request is not EEO; it's about accessibility. Might be okay. However the paragraph also includes "Oracle is an Equal Employment Opportunity Employer..." later; that is EEO boilerplate and must be removed. We'll need to remove that later paragraph. Thus we should split: keep the first part about Oracle's mission up to "volunteer programs." Then stop before the EEO line. The EEO line: "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." That's EEO boilerplate; remove. Thus About the role section will have two paragraphs: first the OCI description and role; second the mission statement up to volunteer programs. Now Responsibilities: we need to list each bullet from "What You'll Do". Let's extract: - Lead the design, development, and evolution of backend platform services, APIs, middleware, runtimes, and integration frameworks used across OCI. - Define and drive API versioning, lifecycle, deprecation, and safe-rollout strategies that protect downstream consumers. - Establish reusable patterns for interoperability, multi-tenant scale, resilience, and secure software development across multiple services. - Drive shared observability practices, including service-level objectives, error budgets, monitoring, and capacity planning. - Diagnose and resolve complex cross-service issues; lead durable remediation and compatibility-safe migration plans. - Influence architecture and technical decisions across teams through design reviews, code reviews, technical guidance, and hands-on engineering. - Create migration guides, adoption playbooks, documentation, and examples that make platform capabilities straightforward to adopt. - Mentor engineers and raise the quality of designs, code, operational practices, and technical decision-making across the organization. We'll put each as
. Now Qualifications: We have required qualifications (What You'll Bring) and Preferred Qualifications. We'll combine into a Qualifications section with two sublists? Could just list all bullet points under one
- under Qualifications. Now Skills: Could extract technical skills: Java, C++, C#, Go; distributed systems; APIs; middleware; runtimes; integration frameworks; microservices; SDKs; RESTful APIs; containers; cloud-native deployments; developer-platform products; SLOs; error budgets; observability; capacity planning; API interoperability; backward compatibility; migrations; platform-adoption; mentoring; improving engineering practices. But many overlap with qualifications. Might be redundant. Perhaps better to not include Skills section to avoid thin sections. The instruction says prefer a few substantive sections over many thin ones. So we could omit Skills and keep Qualifications covering skills. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Now Benefits: list from "Oracle US offers a comprehensive benefits package which includes the following:" then bullet list. Let's extract each bullet: - 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

Principal Software Engineer, Platform

About the role

Requirements

Qualifications

About the role

Similar jobs