Jobs · Tennessee

Senior Manager, Network Development Engineering

Oracle · Nashville, TN · 1 mo ago
$146k–$306k/yrFull-time
We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no boilerplate, no EEO, etc. Must not create sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes Pay: "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $146,300 - $306,400 per year. May be eligible for bonus, equity, and compensation deferral." So we have Pay info. Benefits: they list a comprehensive benefits package. So Benefits section is present. Schedule: not mentioned explicitly; there is "May telecommute." That's not schedule. No explicit schedule like full-time, part-time. So we should not create Schedule section. Skills: maybe we can include under Qualifications? The instruction says use headings for sections like Skills if present. The posting includes Preferred Qualifications and Qualifications sections. We could combine them into Qualifications. Or we could separate Requirements vs Qualifications. The posting has "Preferred Qualifications" and "Qualifications Disclaimer". Actually there is a "Qualifications Disclaimer:" then later "Range and benefit information..." then "Oracle US offers a comprehensive benefits package..." then later "About Us". There's also a "Preferred Qualifications" bullet list. There's also a "Qualifications" heading? Actually after Responsibilities, there is "Preferred Qualifications". Then after that, there is "Qualifications Disclaimer:" which is a note about US based roles. Then later there is "Range and benefit information..." then benefits. Then later "The role will generally accept applications..." etc. Then "About Us". Then EEO etc. We need to strip boilerplate: EEO, equal-opportunity, scam-warning, legal, navigation, cookie, duplicated lines, application instructions. Also remove "The role will generally accept applications for at least three calendar days..." that's application instruction? Probably remove. Also remove "As part of Oracle's onboarding process..." that's maybe boilerplate? It's about identity verification; might be considered boilerplate but it's substantive? It's about requirement; but it's likely part of EEO/legal. Safer to remove. Also remove "Only Oracle brings together..." etc (About Us) maybe keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." About Us is not boilerplate; it's descriptive. Could keep. However we must not create sections with filler. We have content for About the role (the initial paragraphs). Responsibilities (list). Preferred Qualifications (list). Qualifications Disclaimer (maybe we can incorporate into Qualifications? It's a disclaimer about US based roles; could be considered legal boilerplate; maybe remove). The benefits and pay are present. So sections: About the role (maybe we call it About the role? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use About the role heading for the introductory description. Responsibilities heading for the list. Qualifications heading for Preferred Qualifications (maybe also include Qualifications Disclaimer? but we can skip disclaimer). Benefits heading for benefits list. Pay heading for pay range. Skills? Not explicitly separate; we could embed skills within Qualifications. But we could create Skills heading if we want to list skills from Preferred Qualifications. However instruction: Prefer a few substantive sections over many thin ones. So maybe combine Qualifications and Skills into one Qualifications section. But we have both Preferred Qualifications and Qualifications Disclaimer; we can just put Preferred Qualifications under Qualifications. We'll not include Skills separate. Thus output:

About the role

At Oracle Cloud Infrastructure (OCI), we build the future of the cloud for Enterprises as a diverse team of creators and inventors. We act with the speed and attitude of a startup while maintaining the scale, reliability, and customer focus of one of the world’s leading enterprise software companies. Values are OCI’s foundation and how we deliver excellence. We are committed to the greater good in our products and our actions. We are constantly learning and taking opportunities to grow our careers and ourselves. We challenge each other to stretch beyond our past to build our future. You are the builder here. You will be part of a team of highly motivated and talented engineers and leaders, empowered to drive innovation across one of the world’s largest cloud networks. OCI Networking is looking for a Senior Manager to lead a Network Development Engineering team responsible for supporting the design, deployment, automation, and operations of Oracle Cloud Infrastructure’s global network environment. The organization develops and supports network fabrics and systems through a combination of deep networking expertise and software-driven automation required to operate cloud infrastructure at massive scale. OCI’s network includes hundreds of thousands of network devices supporting millions of servers connected through dedicated backbone infrastructure and the Internet. This role provides leadership across network engineering, lifecycle management, automation, architecture, operations, and strategic technology initiatives while building and developing a high-performing engineering organization.

Responsibilities

  • Support the design, deployment, and operations of a large-scale global Oracle Cloud Infrastructure (OCI) environment.
  • Develop and support network fabric and systems using protocol-level networking knowledge and programming skills.
  • Support intensive automation required to operate production environments.
  • Lead engineering efforts supporting a global network footprint consisting of hundreds of thousands of network devices and millions of servers connected through dedicated backbone infrastructure and the Internet.
  • Participate in network lifecycle management through build and upgrade projects.
  • Collaborate with program/project managers to define milestones and deliverables.
  • Use existing procedures and tools to safely execute network changes.
  • Develop new procedures as needed.
  • Serve as technical lead for team projects.
  • Contribute to and help drive network technology roadmaps and long-term infrastructure strategy.
  • Lead development of new runbooks and methods of procedure.
  • Mentor and develop engineers while fostering a culture of technical excellence, innovation, and continuous learning.
  • Participate in network solution and architecture design.
  • Drive the delivery of engineering features, platform enhancements, and infrastructure improvements.
  • Participate in operational rotations as primary or secondary.
  • Provide break-fix support for events.
  • Serve as an escalation point for event remediation.
  • Lead post-event root cause analysis.
  • Champion automation initiatives that improve scalability, consistency, and operational efficiency across the organization.
  • Develop scripts to automate routine tasks for the team and business unit.
  • Serve as SME on software development projects for network automation.
  • Support network vendor software bug fixes.
  • Collaborate with network vendor technical account teams and internal Quality Assurance teams to drive bug resolution.
  • May telecommute.
  • Assist in qualifying new firmware and/or operating systems.
  • May lead network engineers and technical leaders responsible for the design, deployment, automation, and operation of OCI’s global network infrastructure.

Qualifications

  • 8+ years of experience supporting large-scale cloud, service provider, or hyperscale network environments.
  • 3+ years of engineering management or technical leadship capacity, with experience leading network engineering, network development, or infrastructure engineering teams.
  • Strong technical expertise in networking protocols, cloud networking, datacenter networking, network fabrics, and large-scale distributed systems.
  • Experience supporting AI/ML, GPU, HPC, and high-performance network environments.
  • Experience with network automation, software development, scripting, and infrastructure automation technologies.
  • Experience leading network deployment, lifecycle management, and operational improvement initiatives.
  • Experience driving hiring, onboarding, mentoring, and performance management of engineering teams.
  • Strong understanding of network architecture, design, and operational best practices.
  • Excellent organizational, verbal, and written communication skills.
  • Demonstrated ability to influence technical strategy, product roadmaps, and engineering priorities.
  • Strong leadership skills with the ability to build high-performing teams and drive execution across multiple organizations.

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

US: Hiring Range in USD from: $146,300 - $306,400 per year. May be eligible for bonus, equity, and compensation deferral.

We must ensure no boilerplate like "Range and benefit information provided in this posting are specific to the stated locations only". We included that implicitly in Pay section. Might need to include that sentence? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the sentence "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $146,300 - $306,400 per year. May be eligible for bonus, equity, and compensation deferral." That is substantive. So we should include that full sentence. Let's adjust Pay section to include that sentence exactly. Thus Pay

Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $146,300 - $306,400 per year. May be eligible for bonus, equity, and compensation deferral.

We should also maybe keep the note about Oracle maintains broad salary ranges etc. That is also substantive. The paragraph after the range includes: "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." That's also substantive. Should we keep? Yes, preserve all substantive info. So include that as well. Also the benefits description we already captured. So

Similar jobs