Jobs · Engineering · Tennessee

Senior Software Engineer, Core Infrastructure - Nashville

Oracle · Nashville, TN · 1 mo ago
Engineering$79k–$210k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Qualifications), Benefits, Pay, Schedule maybe. We must only include sections that have real specific content. The posting includes: - About the role: description paragraph at start: "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 put that as

About the role

with

. - Responsibilities: bullet list under "What You'll Do". We'll make

  • . - Requirements: there is "What You'll Bring" list (education, experience). Also "Preferred Qualifications". Also "Qualifications Disclaimer" etc. We'll combine into Requirements section maybe with sub-sections? But we should only have sections for real content. Could have "Requirements" containing required qualifications, and maybe "Preferred Qualifications" as separate? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements and Qualifications separate. We'll put required qualifications under Requirements, preferred under Qualifications. - Benefits: there is a long list of benefits. We'll put under Benefits. - Pay: 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." That's pay info. So we include Pay. - Schedule: there is "This position is office-based and requires onsite presence in Nashville, Tennessee. Relocation assistance may be available..." That's schedule/location info. Could be Schedule? It mentions office-based, onsite presence. Not exactly schedule but we can treat as Schedule/Location. The instruction says include Schedule section only if posting actually states them. It does state office-based and onsite presence. So we can include Schedule. We must not include boilerplate like EEO, legal, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove application instructions (like "The role will generally accept applications for at least three calendar days..."). We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from responsibilities, qualifications, benefits, pay, schedule. We must not repeat job title as heading. The job title is "Senior Core Infrastructure Engineer". Not to be used as heading. We must not put Job ID/requisition numbers as headings. We must output only HTML fragment, no /, no markdown fences. Let's extract content. About the role: The first paragraph(s) before Responsibilities: "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 Senior Core Infrastructure Engineer, you will build and operate the foundational distributed systems behind OCI. You will develop scalable, resilient components for high-volume data retrieval, storage, and processing, with a focus on correctness, security, observability, and dependable operation at global scale. This position is office-based and requires onsite presence in Nashville, Tennessee. Relocation assistance may be available in accordance with Oracle's relocation policies." Note: The last two sentences about office-based and relocation could go to Schedule section, but they are also part of About the role. However we might want to keep them in Schedule. The instruction: "Prefer a few substantive sections over many thin ones." We could keep them in About the role, but then Schedule would be empty or just location? Actually schedule section could contain office-based and onsite presence and relocation assistance. That's substantive. So we could move those sentences to Schedule. But then About the role would lose those details. However we could keep them in About the role as part of role description; still we can have Schedule separate with those details. The instruction says preserve ALL substantive information; we can duplicate? It didn't forbid duplication but better to avoid duplication. We could keep them in Schedule and not repeat in About the role. Let's see if About the role still has enough content without those sentences. The first part about OCI and role responsibilities is enough. Thus About the role: OCI description and role building foundational distributed systems etc. We'll keep that. Now Responsibilities: list under "What You'll Do". Let's extract bullet points: - Design, implement, test, and optimize components of large-scale distributed systems and data-plane services. - Build for horizontal and vertical scale, using distributed state, replication, synchronization, and high-volume data-processing patterns. - Strengthen service reliability through redundancy, automatic failover, recovery-oriented design, retries, circuit breakers, and timeouts. - Develop and execute performance, load, and fault-injection tests to validate scalability, correctness, availability, and operational readiness. - Create dashboards, alarms, telemetry, runbooks, and automation that proactively detect issues and accelerate recovery. - Diagnose production issues, participate in on-call rotations and incident response, and contribute to root-cause analyses and durable corrective actions. - Develop infrastructure automation and Infrastructure as Code (IaC) for safe maintenance, troubleshooting, patching, updates, and rollbacks. - Apply strong security controls—including encryption, access controls, and vulnerability remediation—in multi-tenant environments. We'll put each as
  • . Now Requirements (required qualifications): from "What You'll Bring": - Bachelor's or master's degree in Computer Science, Computer Engineering, or a related field, or equivalent practical experience. - 4+ years of professional software-development experience; advanced degree holders may have fewer years of experience. - Proficiency in at least one object-oriented or systems programming language, such as Java, C++, C#, or Go. - Experience building or operating scalable, highly available distributed systems or cloud infrastructure. - Experience with system-level testing and automation, including performance, load, reliability, or fault-injection testing. - Understanding of distributed-systems concepts, data structures, algorithms, operating systems, networking, and secure software-development practices. - Strong debugging, problem-solving, communication, and cross-functional collaboration skills. We'll put as
    • . Now Qualifications (preferred): from "Preferred Qualifications": - Experience with cloud platforms, such as Oracle Cloud, AWS, Azure, or Google Cloud. - Experience with data-plane platforms, distributed storage, microservices, state management, replication, or large-scale data processing. - Experience with observability, incident management, Infrastructure as Code, and production service operations. - Familiarity with compliance requirements and security controls for cloud infrastructure. We'll put as
      • . Now 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'll put each as
      • . Note the vacation description is long; we can keep as a single
      • with that sentence. Now Pay: "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." We'll put as

        maybe. 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." We'll put as

        . We must not include boilerplate like "The role will generally accept applications for at least three calendar days from the posting date or as long as the job remains posted." etc. Also remove "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." That's a qualification disclaimer; maybe we could include it under Requirements? It's a disclaimer about compliance; but it's still substantive? It's about immunization etc. Might be considered boilerplate? It's a legal requirement. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is a legal disclaimer about immunization/drug testing. Might be considered legal boilerplate; better to remove. Also remove "As part of Oracle's onboarding process and consistent with applicable law, US-based employees are required to complete identity verification, which involves the collection and processing of their biometric information. Accommodations to this requirement may be granted following an individualized assessment." That's also legal; remove. Also remove "About Us" section and everything after that (including EEO). So we stop before About Us. Now we need to output HTML fragment with headings

        and content. Structure:

        About the role

        ...

        Responsibilities

        • ...
        • ...

        Requirements

          ...

        Qualifications

          ...

        Benefits

          ...

        Pay

        ...

        Schedule

        ...

        Make sure no extra whitespace? It's fine. Now craft the HTML. Let's write the About the role paragraph: combine the first sentences excluding office-based/relocation. "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 Senior Core Infrastructure Engineer, you will build and operate the foundational distributed systems behind OCI. You will develop scalable, resilient components for high-volume data retrieval, storage, and processing, with a focus on correctness, security, observability, and dependable operation at global scale." Now Responsibilities list as above. Now Requirements list. Now Qualifications list. Now Benefits list: need to capture each bullet. Let's list them: - 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 -

Similar jobs

Software Engineer, Senior

Torch Technologies, Inc.Laughlin AFB, TX· 1 mo ago
Engineeringapply on starfish.wd501.myworkdayjobs.com

Software Engineer, Senior

Booz Allen HamiltonFort Meade, MD· 3 mo ago
Engineering$87k–$198k/yrapply on careers.boozallen.com

Software Engineer, Senior

Booz Allen HamiltonNellis AFB, NV· 3 mo ago
Engineering$87k–$198k/yrapply on careers.boozallen.com