Principal Software Engineer, Platform - Nashville
Oracle · Nashville, TN · 1 mo ago
Engineering$105k–$235k/yrFull-time
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. We must not repeat job title as heading. Remove boilerplate, navigation, EEO, etc. Keep substantive info.
We need to parse the job description.
Key sections:
- About the role: The description includes introductory paragraph: "Job Description Oracle Cloud Infrastructure (OCI) delivers mission-critical applications...". That's about the role? Actually it's about OCI and the role. Could be "About the role". We'll include that as a paragraph.
- Responsibilities: The "What You'll Do" list.
- Requirements: The "What You'll Bring" list (education, experience, etc.)
- Qualifications: There's a "Preferred Qualifications" list. Also there is a "Qualifications Disclaimer" but that's boilerplate; we can ignore. The "Qualifications" heading maybe includes both required and preferred? The posting has "What You'll Bring" (requirements) and "Preferred Qualifications". We could combine under "Requirements" and "Qualifications"? The instruction says use headings for sections like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content goes where.
We have:
- Responsibilities: bullet list.
- Requirements: education, experience, skills (languages, distributed systems, etc.)
- Preferred Qualifications: additional experience.
- Skills: maybe we can extract skills from requirements: proficiency in Java, C++, C#, Go; understanding of distributed systems, OOP, data structures, algorithms, secure software dev; leading/influencing architecture; judgment, ownership, communication.
But we could also put those under Requirements.
- Benefits: detailed list of benefits.
- Pay: salary range $104,500 - $234,600 per year, plus bonus, equity, compensation deferral.
- Schedule: The position is office-based and requires onsite presence in Nashville, Tennessee. Relocation assistance may be available. That's schedule/location info. Not exactly schedule but we can put under Schedule: office-based, onsite presence in Nashville, TN; relocation assistance may be available.
We should not include boilerplate like "Range and benefit information provided in this posting are specific to the stated locations only", etc. But we can keep the salary range and benefits.
We need to avoid filler like "commensurate with experience". Not present.
We must not include duplicated lines.
We must not include application instructions, EEO, etc.
We must not include "About Us" maybe? The instruction says use heading "About the role". The "About Us" section is more about company; could be considered "About the role"? Might be okay to include as About the role? But we already have introductory paragraph about OCI and role. The "About Us" is more generic company marketing; could be considered boilerplate? It's not required but could be included as part of About the role? The instruction: "Prefer a few substantive sections over many thin ones." So we could combine the introductory paragraph and About Us into About the role? But About Us is not about the role. Might be considered filler. Safer to include only the introductory paragraph as About the role.
Thus sections:
.
Requirements: from "What You'll Bring": education, experience, etc. We'll list.
Qualifications: maybe "Preferred Qualifications". We'll list.
Skills: maybe we can extract skills: proficiency in Java, C++, C#, Go; deep understanding of distributed-systems fundamentals, OOP, data structures, algorithms, secure software-development practices; leading/influencing architecture; judgment, ownership, communication. But these are already in Requirements. Could create Skills section separate but might be thin. Better to put them under Requirements.
Benefits: list of benefits.
Pay: salary range and bonus/equity/compensation deferral.
We must not include sections with filler like "not specified". We have all.
Now we need to ensure we don't repeat content.
Let's extract precise text.
From posting:
Intro paragraph before Responsibilities: "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 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."
That's the About the role content.
Now Responsibilities bullet list:
- 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.
Now Requirements (What You'll Bring):
- 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 backend, platform, or cloud services.
- Strong experience designing highly available, scalable distributed systems and evolving production APIs or platform interfaces.
- Proficiency in one or more object-oriented or systems programming languages, such as Java, C++, C#, or Go.
- Deep understanding of distributed-systems fundamentals, object-oriented design, data structures, algorithms, and secure software-development practices.
- Demonstrated experience leading or influencing architecture and technical design across teams.
- Strong judgment in ambiguous environments, a high degree of ownership, and clear written and verbal communication skills.
Preferred Qualifications:
- Experience with microservices, SDKs, RESTful APIs, containers, cloud-native deployments, or developer-platform products.
- Experience defining or operating SLOs, error budgets, observability standards, and capacity plans.
- Experience with API interoperability, backward compatibility, migrations, or platform-adoption programs.
- Experience mentoring engineers and improving engineering practices across multiple teams.
Now Benefits list (from Oracle US offers a comprehensive benefits package which includes the following:):
- 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
Now Pay: "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $104,500 - $234,600 per year. May be eligible for bonus, equity, and compensation deferral."
We'll extract: Hiring Range in USD from: $104,500 - $234,600 per year. May be eligible for bonus, equity, and compensation deferral.
Now Schedule: "This position is office-based and requires onsite presence in Nashville, Tennessee. Relocation assistance may be available in accordance with Oracle's relocation policies."
Now we need to output HTML fragment with headings and
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Remove boilerplate, navigation, EEO, etc. Keep substantive info.
We need to parse the job description.
Key sections:
- About the role: The description includes introductory paragraph: "Job Description Oracle Cloud Infrastructure (OCI) delivers mission-critical applications...". That's about the role? Actually it's about OCI and the role. Could be "About the role". We'll include that as a paragraph.
- Responsibilities: The "What You'll Do" list.
- Requirements: The "What You'll Bring" list (education, experience, etc.)
- Qualifications: There's a "Preferred Qualifications" list. Also there is a "Qualifications Disclaimer" but that's boilerplate; we can ignore. The "Qualifications" heading maybe includes both required and preferred? The posting has "What You'll Bring" (requirements) and "Preferred Qualifications". We could combine under "Requirements" and "Qualifications"? The instruction says use headings for sections like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content goes where.
We have:
- Responsibilities: bullet list.
- Requirements: education, experience, skills (languages, distributed systems, etc.)
- Preferred Qualifications: additional experience.
- Skills: maybe we can extract skills from requirements: proficiency in Java, C++, C#, Go; understanding of distributed systems, OOP, data structures, algorithms, secure software dev; leading/influencing architecture; judgment, ownership, communication.
But we could also put those under Requirements.
- Benefits: detailed list of benefits.
- Pay: salary range $104,500 - $234,600 per year, plus bonus, equity, compensation deferral.
- Schedule: The position is office-based and requires onsite presence in Nashville, Tennessee. Relocation assistance may be available. That's schedule/location info. Not exactly schedule but we can put under Schedule: office-based, onsite presence in Nashville, TN; relocation assistance may be available.
We should not include boilerplate like "Range and benefit information provided in this posting are specific to the stated locations only", etc. But we can keep the salary range and benefits.
We need to avoid filler like "commensurate with experience". Not present.
We must not include duplicated lines.
We must not include application instructions, EEO, etc.
We must not include "About Us" maybe? The instruction says use heading "About the role". The "About Us" section is more about company; could be considered "About the role"? Might be okay to include as About the role? But we already have introductory paragraph about OCI and role. The "About Us" is more generic company marketing; could be considered boilerplate? It's not required but could be included as part of About the role? The instruction: "Prefer a few substantive sections over many thin ones." So we could combine the introductory paragraph and About Us into About the role? But About Us is not about the role. Might be considered filler. Safer to include only the introductory paragraph as About the role.
Thus sections:
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.
But note we already used location in Schedule maybe. We could keep location in About the role or Schedule. The instruction says Schedule section only if posting actually states them. The posting states "This position is office-based and requires onsite presence in Nashville, Tennessee. Relocation assistance may be available". That's about schedule/location. So we could put that under Schedule. Then About the role could be just the description of OCI and role without location. Let's split. About the role: description of OCI and role responsibilities high-level. Schedule: office-based, onsite presence in Nashville, TN; relocation assistance may be available. Now Responsibilities: list from "What You'll Do". We'll convert each bullet to headings and - for lists,
for prose.
We must not include any markdown fences.
We'll produce something like:
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.
Schedule
This position is office-based and requires onsite presence in Nashville, Tennessee. Relocation assistance may be available in accordance with Oracle's relocation policies.
Responsibilities
- 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 rem
for prose. We must not include any markdown fences. We'll produce something like:
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.
Schedule
This position is office-based and requires onsite presence in Nashville, Tennessee. Relocation assistance may be available in accordance with Oracle's relocation policies.
Responsibilities
- 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 rem