Job Title: Network Developer
Location: Remote
Duration: Long-term
Location: Remote
Duration: Long-term
Job Description:
The team is looking for Network Developer Engineer to solve challenging high-level networking problems, deliver new capabilities, and continue to scale our platform to meet the increasing needs of our customers world-wide. The ideal candidate has strong technical background in computer networking, network cloud architecture, tier1-3 internet routing, and systems-level programming experience.
The team is looking for Network Developer Engineer to solve challenging high-level networking problems, deliver new capabilities, and continue to scale our platform to meet the increasing needs of our customers world-wide. The ideal candidate has strong technical background in computer networking, network cloud architecture, tier1-3 internet routing, and systems-level programming experience.
Candidates who enjoy challenging, performance sensitive environments, have deep analytical skills along with the ability to lead cross functional technical teams, provide structured documentation to senior leaderships, and provide detailed scope and solutions to business critical problems will find the Oracle Edge Services team to be inline with their interests. Candidates must be highly collaborative, creative, analytical, and have the ability to thrive in fast-paced environments.
Responsibilities:
Engineering remote transit for constrained markets
Engineering remote transit for scaling
Engineering of EDGE POP backhaul
Engineering of free peers between regions
Cost vs. performance (e.g. latency)
Capacity offloading mechanisms
DDOS clean traffic circuit and route policy efficiencies
Provide design for redundancy in high capacity to low capacity regions
Solve challenges with redundancy factoring
Provide study/date on peak versus P99 traffic demand to optimize needed transit vs. customer traffic demand
Focus on peering design with how to offset demand from Internet Transit
Clear rules on how to drive local geo region peering vs. inter-region peering
Design should include single point / localized peers vs. global peers, and policies such as Anycast (DNS) distribution.
Downstream connectivity engineering efficiencies
Build tools and automation frameworks for routine engineering tasks.
Failure handling mechanisms
Work with org to learn to identify internet weather events and measure impact
Engineering visibility improvements by region
Engineering visibility improvements by ISP
Engineering visibility improvements by PNI/IX/Peering
Engineering visibility improvements across all regions
Policy best practices for RPKI and IRR entries
Manage addressing allocations
Engineering remote transit for constrained markets
Engineering remote transit for scaling
Engineering of EDGE POP backhaul
Engineering of free peers between regions
Cost vs. performance (e.g. latency)
Capacity offloading mechanisms
DDOS clean traffic circuit and route policy efficiencies
Provide design for redundancy in high capacity to low capacity regions
Solve challenges with redundancy factoring
Provide study/date on peak versus P99 traffic demand to optimize needed transit vs. customer traffic demand
Focus on peering design with how to offset demand from Internet Transit
Clear rules on how to drive local geo region peering vs. inter-region peering
Design should include single point / localized peers vs. global peers, and policies such as Anycast (DNS) distribution.
Downstream connectivity engineering efficiencies
Build tools and automation frameworks for routine engineering tasks.
Failure handling mechanisms
Work with org to learn to identify internet weather events and measure impact
Engineering visibility improvements by region
Engineering visibility improvements by ISP
Engineering visibility improvements by PNI/IX/Peering
Engineering visibility improvements across all regions
Policy best practices for RPKI and IRR entries
Manage addressing allocations
