Principal Network Developer (Automation, Border Gateway Protocol Routing)
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists
- Use
for prose
- Do NOT repeat job title as heading (not provided anyway)
- Do NOT put Job ID/requisition numbers as headings (none present)
- Preserve ALL substantive information
- Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions)
- Include section ONLY when real specific content exists
- Never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Prefer few substantive sections over many thin ones
- Output ONLY HTML fragment, no /, no markdown code fences
Now, let's parse the content:
The posting starts with "Archer is collaborating with Oracle to connect them with exceptional professionals for this role." This seems like a recruiter note, maybe boilerplate? Could be considered minor metadata. I'll fold into a short
or drop. Since it's not substantive about the role, I'll drop it.
"About The Team" - this is a heading. Then "Join OCI’s NRB team! Lead network expansion, automation, and our AI infrastructure at a global scale. Drive the future of cloud networking!" This is prose.
"Description" - heading? The text says "Description" then a paragraph about NRB team responsibilities. That's prose.
"Responsibilities" - heading, then a list of bullet points (each line starting with a verb). Should be
- .
"Qualifications" - heading, then a mix: first a disclaimer about US roles, then salary range, then benefits package details, then career level. This section includes pay and benefits info. According to rules, I should include Pay and Benefits sections only if posting actually states them. The posting does state salary range and benefits. However, the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. But also "Prefer a few substantive sections over many thin ones." The Qualifications section currently includes requirements (experience, skills) and also pay/benefits. I could split into separate sections: Requirements (or Qualifications), Pay, Benefits. But the heading "Qualifications" is used for both. The rules suggest using headings like "Requirements", "Qualifications", "Skills", "Benefits", "Pay". The posting has "Qualifications" heading and then lists experience/skills, then disclaimer, then pay range, then benefits. I think I should separate: keep "Qualifications" for the experience/skills part, then create "Pay" and "Benefits" sections for the respective content. However, the rules say "include a section ONLY when the posting has real, specific content for it". The posting has specific pay range and benefits. So I should include them.
But note: the disclaimer about immunization/drug testing is also part of qualifications? Might be boilerplate. The rules say remove EEO/equal-opportunity boilerplate. That disclaimer might be considered legal boilerplate. However, it's specific to US-based roles. Might keep as a short
under Qualifications? But the rules say remove EEO/equal-opportunity boilerplate. That disclaimer is about immunization/occupational health mandates and drug testing. That's not EEO, but it's legal compliance. Might be considered boilerplate. I'll include it as a short paragraph under Qualifications? Or drop? The rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". This is legal boilerplate. I'll drop it.
The salary range and benefits are specific and substantive. I'll create separate sections for Pay and Benefits.
Also "Career Level - IC4" is minor metadata, fold into a short
or drop. I'll include as a short paragraph maybe under Qualifications or separate.
Now, the experience/skills list under Qualifications: they are bullet points? In the text, they are separated by line breaks but not bullet points. They are sentences. I'll convert to
- for each distinct requirement.
Let's list them:
- Experience working in a large ISP or cloud provider environment.
- Exposure to commodity Ethernet hardware (Broadcom/Mellanox), protocol experience with BGP/OSPF/IS-IS, TCP, IPv4, IPv6, DNS, DHCP, MPLS.
- Experience with networking protocols such as TCP/IP, VPN, DNS, DHCP, and SSL.
- Experience with Internet peering and inter-domain networking.
- Experience with scripting or automation and datacenter design – Python preferred, but must demonstrate knowledge in a scripting or compiled language.
- Experience with automation systems, framework design/use and deployment.
- Experience with network modeling and programing – YANG, OpenConfig, NETCONF.
- Knowledge of network security design, system performance characterization and testing.
- Knowledge of data flow and telemetry design, deployment and operation.
- Excellent judgment in influence for product roadmap direction, features, and priorities.
- Excellent organizational, verbal, and written communication skills.
That's 11 items. Good for a list.
Now, the responsibilities list: each line is a responsibility. I'll make each a
- .
Now, structure:
About the Team
Join OCI’s NRB team! Lead network expansion, automation, and our AI infrastructure at a global scale. Drive the future of cloud networking!
Description
The Network Region Build (NRB) team is responsible for deploying greenfield infrastructure, establishing network connectivity for new (Oracle Cloud Infrastructure) OCI regions, and enabling compute connectivity for child sites. This includes building and managing data center fabrics, edge networks, backbone, fiber metro networks, and supporting multi-cloud initiatives. NRB provides operational support during build phases and oversees network and server rack adds, decommissions, and capacity expansions. The team also drives automation, process improvements, and tool development in collaboration with Network Automation to enhance efficiency. This role involves designing, deploying, and operating large-scale global cloud networks. It requires a deep understanding of network protocols and programming skills to support automation at scale. As OCI's cloud network spans a global footprint, this role supports a vast infrastructure of network devices and millions of connected servers across dedicated backbone and internet-based connectivity.
Responsibilities
- Participate in Network lifecycle management through network build and/or upgrade projects.
- Collaborate with program/project managers to develop milestones and deliverables.
- Will primarily use existing procedures and tools to develop and safely execute network change. However, may have to develop new procedures from time to time.
- Serve as technical lead for team projects.
- Contributes to the development of roadmap issues.
- Leads development of new runbooks and method of procedures.
- Mentors junior engineers.
- Participates in network solution and architecture design process.
- Responsibility for developing standalone features.
- Participate in operational rotations as either primary or secondary.
- Provide break-fix support for events.
- Serve as escalation point for event remediation.
- Lead post-event root cause analysis.
- Coordinate with networking automation services for the development and integration of support tooling.
- Frequently develops scripts to automate routine tasks for team and business unit.
- Serves as SME on software development projects for network automation.
- Supports network vendor software bug fixes.
- Collaborate with network vendor technical account team and internal Quality Assurance team to drive bug resolution and assist in the qualification of new firmware and/or operating systems.
Qualifications
- Experience working in a large ISP or cloud provider environment.
- Exposure to commodity Ethernet hardware (Broadcom/Mellanox), protocol experience with BGP/OSPF/IS-IS, TCP, IPv4, IPv6, DNS, DHCP, MPLS.
- Experience with networking protocols such as TCP/IP, VPN, DNS, DHCP, and SSL.
- Experience with Internet peering and inter-domain networking.
- Experience with scripting or automation and datacenter design – Python preferred, but must demonstrate knowledge in a scripting or compiled language.
- Experience with automation systems, framework design/use and deployment.
- Experience with network modeling and programing – YANG, OpenConfig, NETCONF.
- Knowledge of network security design, system performance characterization and testing.
- Knowledge of data flow and telemetry design, deployment and operation.
- Excellent judgment in influence for product roadmap direction, features, and priorities.
- Excellent organizational, verbal, and written communication skills.
Pay
US Hiring Range: $102,300 to $209,500 per annum. May be eligible for bonus and equity. Oracle maintains broad salary ranges for its roles 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.
Benefits
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 for salaried (non-overtime eligible) positions; Accrued Vacation for others. For employees working at least 35 hours per week, vacation accrual rate is 13 days annually for first three years and 18 days annually thereafter. Vacation accrual prorated for employees working 20-34 hours per week. Employees working fewer than 20 hours per week not eligible for vacation.
- 11 paid holidays
- Paid sick leave: 72 hours upon date of hire, refreshes each calendar year, unused balance carries over up to 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
Career Level
IC4
But the rules say "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it." Career Level is minor metadata. I'll fold into a short
maybe under Qualifications or separate. I'll include as a short paragraph at the end.
Also, the posting includes "The role will generally accept applications for at least three calendar days
for prose - Do NOT repeat job title as heading (not provided anyway) - Do NOT put Job ID/requisition numbers as headings (none present) - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) - Include section ONLY when real specific content exists - Never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment, no /, no markdown code fences Now, let's parse the content: The posting starts with "Archer is collaborating with Oracle to connect them with exceptional professionals for this role." This seems like a recruiter note, maybe boilerplate? Could be considered minor metadata. I'll fold into a short
or drop. Since it's not substantive about the role, I'll drop it. "About The Team" - this is a heading. Then "Join OCI’s NRB team! Lead network expansion, automation, and our AI infrastructure at a global scale. Drive the future of cloud networking!" This is prose. "Description" - heading? The text says "Description" then a paragraph about NRB team responsibilities. That's prose. "Responsibilities" - heading, then a list of bullet points (each line starting with a verb). Should be
- .
"Qualifications" - heading, then a mix: first a disclaimer about US roles, then salary range, then benefits package details, then career level. This section includes pay and benefits info. According to rules, I should include Pay and Benefits sections only if posting actually states them. The posting does state salary range and benefits. However, the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. But also "Prefer a few substantive sections over many thin ones." The Qualifications section currently includes requirements (experience, skills) and also pay/benefits. I could split into separate sections: Requirements (or Qualifications), Pay, Benefits. But the heading "Qualifications" is used for both. The rules suggest using headings like "Requirements", "Qualifications", "Skills", "Benefits", "Pay". The posting has "Qualifications" heading and then lists experience/skills, then disclaimer, then pay range, then benefits. I think I should separate: keep "Qualifications" for the experience/skills part, then create "Pay" and "Benefits" sections for the respective content. However, the rules say "include a section ONLY when the posting has real, specific content for it". The posting has specific pay range and benefits. So I should include them.
But note: the disclaimer about immunization/drug testing is also part of qualifications? Might be boilerplate. The rules say remove EEO/equal-opportunity boilerplate. That disclaimer might be considered legal boilerplate. However, it's specific to US-based roles. Might keep as a short
under Qualifications? But the rules say remove EEO/equal-opportunity boilerplate. That disclaimer is about immunization/occupational health mandates and drug testing. That's not EEO, but it's legal compliance. Might be considered boilerplate. I'll include it as a short paragraph under Qualifications? Or drop? The rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". This is legal boilerplate. I'll drop it. The salary range and benefits are specific and substantive. I'll create separate sections for Pay and Benefits. Also "Career Level - IC4" is minor metadata, fold into a short
or drop. I'll include as a short paragraph maybe under Qualifications or separate. Now, the experience/skills list under Qualifications: they are bullet points? In the text, they are separated by line breaks but not bullet points. They are sentences. I'll convert to
- for each distinct requirement. Let's list them: - Experience working in a large ISP or cloud provider environment. - Exposure to commodity Ethernet hardware (Broadcom/Mellanox), protocol experience with BGP/OSPF/IS-IS, TCP, IPv4, IPv6, DNS, DHCP, MPLS. - Experience with networking protocols such as TCP/IP, VPN, DNS, DHCP, and SSL. - Experience with Internet peering and inter-domain networking. - Experience with scripting or automation and datacenter design – Python preferred, but must demonstrate knowledge in a scripting or compiled language. - Experience with automation systems, framework design/use and deployment. - Experience with network modeling and programing – YANG, OpenConfig, NETCONF. - Knowledge of network security design, system performance characterization and testing. - Knowledge of data flow and telemetry design, deployment and operation. - Excellent judgment in influence for product roadmap direction, features, and priorities. - Excellent organizational, verbal, and written communication skills. That's 11 items. Good for a list. Now, the responsibilities list: each line is a responsibility. I'll make each a
- .
Now, structure:
About the Team
Join OCI’s NRB team! Lead network expansion, automation, and our AI infrastructure at a global scale. Drive the future of cloud networking!
Description
The Network Region Build (NRB) team is responsible for deploying greenfield infrastructure, establishing network connectivity for new (Oracle Cloud Infrastructure) OCI regions, and enabling compute connectivity for child sites. This includes building and managing data center fabrics, edge networks, backbone, fiber metro networks, and supporting multi-cloud initiatives. NRB provides operational support during build phases and oversees network and server rack adds, decommissions, and capacity expansions. The team also drives automation, process improvements, and tool development in collaboration with Network Automation to enhance efficiency. This role involves designing, deploying, and operating large-scale global cloud networks. It requires a deep understanding of network protocols and programming skills to support automation at scale. As OCI's cloud network spans a global footprint, this role supports a vast infrastructure of network devices and millions of connected servers across dedicated backbone and internet-based connectivity.
Responsibilities
- Participate in Network lifecycle management through network build and/or upgrade projects.
- Collaborate with program/project managers to develop milestones and deliverables.
- Will primarily use existing procedures and tools to develop and safely execute network change. However, may have to develop new procedures from time to time.
- Serve as technical lead for team projects.
- Contributes to the development of roadmap issues.
- Leads development of new runbooks and method of procedures.
- Mentors junior engineers.
- Participates in network solution and architecture design process.
- Responsibility for developing standalone features.
- Participate in operational rotations as either primary or secondary.
- Provide break-fix support for events.
- Serve as escalation point for event remediation.
- Lead post-event root cause analysis.
- Coordinate with networking automation services for the development and integration of support tooling.
- Frequently develops scripts to automate routine tasks for team and business unit.
- Serves as SME on software development projects for network automation.
- Supports network vendor software bug fixes.
- Collaborate with network vendor technical account team and internal Quality Assurance team to drive bug resolution and assist in the qualification of new firmware and/or operating systems.
Qualifications
- Experience working in a large ISP or cloud provider environment.
- Exposure to commodity Ethernet hardware (Broadcom/Mellanox), protocol experience with BGP/OSPF/IS-IS, TCP, IPv4, IPv6, DNS, DHCP, MPLS.
- Experience with networking protocols such as TCP/IP, VPN, DNS, DHCP, and SSL.
- Experience with Internet peering and inter-domain networking.
- Experience with scripting or automation and datacenter design – Python preferred, but must demonstrate knowledge in a scripting or compiled language.
- Experience with automation systems, framework design/use and deployment.
- Experience with network modeling and programing – YANG, OpenConfig, NETCONF.
- Knowledge of network security design, system performance characterization and testing.
- Knowledge of data flow and telemetry design, deployment and operation.
- Excellent judgment in influence for product roadmap direction, features, and priorities.
- Excellent organizational, verbal, and written communication skills.
Pay
US Hiring Range: $102,300 to $209,500 per annum. May be eligible for bonus and equity. Oracle maintains broad salary ranges for its roles 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.
Benefits
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 for salaried (non-overtime eligible) positions; Accrued Vacation for others. For employees working at least 35 hours per week, vacation accrual rate is 13 days annually for first three years and 18 days annually thereafter. Vacation accrual prorated for employees working 20-34 hours per week. Employees working fewer than 20 hours per week not eligible for vacation.
- 11 paid holidays
- Paid sick leave: 72 hours upon date of hire, refreshes each calendar year, unused balance carries over up to 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
Career Level
IC4
But the rules say "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it." Career Level is minor metadata. I'll fold into a short
maybe under Qualifications or separate. I'll include as a short paragraph at the end. Also, the posting includes "The role will generally accept applications for at least three calendar days