Network Development Engineer , GCNA-D , AWS Internet Edge
Amazon Web Services (AWS) · Seattle, WA · 1 mo ago
ConsultingFull-time
We need to output HTML fragment with sections: headings using for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions.
We need to parse the description and extract sections.
Let's identify content:
- Description paragraph: intro about role, GCNA, etc. This could be "About the role" maybe.
- "Key job responsibilities": list of responsibilities.
- "A day in the life": more details.
- "About The Team": description of team.
- "About AWS": includes Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance, EEO/Accommodations (but we must remove EEO boilerplate). However we need to keep substantive info: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. The EEO/Accommodations is boilerplate; we should remove.
- "Basic Qualifications": list.
- "Preferred Qualifications": list.
- Pay: "The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location. Amazon also offers comprehensive benefits including health insurance ... 401(k) matching, paid time off, and parental leave. Learn more about our benefits at ..."
- Then location: "USA, WA, Seattle - 136,000.00 - 184,000.00 USD annually"
- Benefits: described in that paragraph.
Thus we have sections: About the role (intro), Responsibilities (Key job responsibilities + A day in the life maybe combined), Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Skills (maybe not explicit separate; but we could embed skills in qualifications; but we need to include a Skills section only if posting has real specific content for it. There's no separate skills list; but we could treat qualifications as skills? However instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include only those with real content. So we can include About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Possibly Schedule? Not mentioned. No schedule specifics besides "Work in a 24x7 team on call rotation, with ability to drive into workplace for critical events/needs." That's schedule info (on-call rotation). Could be considered schedule. But we need to see if we should create a Schedule section only if posting has real specific content. It does mention "Work in a 24x7 team on call rotation, with ability to drive into workplace for critical events/needs." Also "Sit at the computer during scheduled work hours with appropriate breaks". That's schedule info. So we could include Schedule section with that content.
But we must not create sections with filler/placeholder text. So we need to ensure we have actual content.
Let's extract each.
**About the role**: The initial paragraphs before "Key job responsibilities". Let's capture:
"Do you like to design, operate, and implement networks of large scale? Would you like your work to play a key role to support all aspects of connectivity to/from Amazon and the outside world, as well as the connectivity between Amazon’s data centers and services to design and architect innovation so networks are fail-proof, infinitely scale and grow? The AWS GCNA (Global Connectivity and Network Availability) Organization is looking for a Network Development Engineer to join our EDGE team. Network Development Engineers partner with our broader Infrastructure organization on configurations standards and tools, and collaborate with Systems and Software Engineers to ensure fast, smooth roll-out of new designs and products, and also deploy and sustain networking software tools. AWS GCNA (Global Connectivity and Network Availability) is the backbone that connects the global AWS network. Focused on managing the internet traffic that allows users to access their information and applications regardless of where they are in the world. GCNA is responsible for building and designing a complex backbone network that allows internet traffic to flow efficiently between data centers and customers. If you like to work with new technologies, optimizing existing technology, and have experience participating in network/systems support for a large-scale enterprise or service provider environment, we would like to meet you. Your work will play a key role in driving the stability and sustainability of next-generation IP networks. You’ll join a diverse team of software, hardware, and network engineers, supply chain specialists, security experts, operations managers, and other vital roles. You’ll collaborate with people across AWS to help us deliver the highest standards for safety and security while providing seemingly infinite capacity at the lowest possible cost for our customers. And you’ll experience an inclusive culture that welcomes bold ideas and empowers you to own them to completion."
That's substantive.
**Responsibilities**: Combine "Key job responsibilities" and "A day in the life". Let's extract bullet-like sentences.
Key job responsibilities list:
- Network Development Engineers perform high quality network and/or systems operations, deployments, scaling, technology refresh, sustaining engineering, best practices application, optimization, internal/external customer interactions, and produce appropriate technical documentation.
- Create and implement changes on the network according to our change management standards.
- Work closely with our automation teams in defining the tools that allows us to scale at higher volume.
- Lead network projects in the areas of networking sustaining engineering, network deployment/implementation, network scaling, technology refresh, best practices application, and/or network optimization.
- Maintain Amazon Web Services’ next generation networks for significant AWS customers by providing critical network support to diagnose, mitigate impact, and resolve large-scale networking events.
- Operate and troubleshoot network routing, interconnectivity, platforms, performance, and configurations issues; including necessary low-level application interaction, Unix systems, and new age networking software tools.
- Drive and support innovation from Top of Rack to the Network Border, and everything in between.
- Partner with our broader Network/Infrastructure organization in the areas of network engineering, configurations standards, and tools.
- Work closely with our Network/Systems/Software Engineering teams to ensure fast, smooth roll-out of new designs and products, as well as, assist with deployment and sustaining of networking software tools.
- Maintain standards across the networking toolset and ensure that we are fully compliant to those standards and policies.
- Deliver simple, sustainable, and repeatable solutions and processes.
- Collaborate with the highest tier escalation engineers/resolvers.
- Create and review documentation and process regarding network implementation/deployments, recurring issues, new standard operating procedures, knowledge transfer material, etc.
A day in the life:
- Engineers in the GCNA-D organization have a wide range of responsibilities: we evolve routing policy, implement traffic engineering solutions, grow our peering footprint, secure the “front door” from bad actors on the Internet, and architect the hardware platforms and network design to support any Amazon product that needs to reach end-users worldwide.
- Our infrastructure moves terabits of traffic to and from the Internet at any given moment, and represents one of the largest edge surface areas in the world, requiring complex solutions to ensure that capacity always stays ahead of demand.
- To accomplish that, our engineers develop automation, write software, and work with a wide range of partner teams to continually improve and automate our Internet connectivity in areas such as capacity delivery, configuration deployment, impairment detection, and traffic optimization.
- Internet Edge engineers make decisions on both a day-to-day and long-term strategic basis, which carry a large amount of responsibility and impact across all of Amazon’s products.
- Work in a 24x7 team on call rotation, with ability to drive into workplace for critical events/needs.
- Manage customers during problem resolution and operating efficiently under pressure.
- Sit at the computer during scheduled work hours with appropriate breaks while maintaining a high level of alertness and attention to detail.
- Travel to data center/network sites and Amazon/customer offices as needed.
We can combine into a single
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions.
We need to parse the description and extract sections.
Let's identify content:
- Description paragraph: intro about role, GCNA, etc. This could be "About the role" maybe.
- "Key job responsibilities": list of responsibilities.
- "A day in the life": more details.
- "About The Team": description of team.
- "About AWS": includes Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance, EEO/Accommodations (but we must remove EEO boilerplate). However we need to keep substantive info: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. The EEO/Accommodations is boilerplate; we should remove.
- "Basic Qualifications": list.
- "Preferred Qualifications": list.
- Pay: "The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location. Amazon also offers comprehensive benefits including health insurance ... 401(k) matching, paid time off, and parental leave. Learn more about our benefits at ..."
- Then location: "USA, WA, Seattle - 136,000.00 - 184,000.00 USD annually"
- Benefits: described in that paragraph.
Thus we have sections: About the role (intro), Responsibilities (Key job responsibilities + A day in the life maybe combined), Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Skills (maybe not explicit separate; but we could embed skills in qualifications; but we need to include a Skills section only if posting has real specific content for it. There's no separate skills list; but we could treat qualifications as skills? However instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include only those with real content. So we can include About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Possibly Schedule? Not mentioned. No schedule specifics besides "Work in a 24x7 team on call rotation, with ability to drive into workplace for critical events/needs." That's schedule info (on-call rotation). Could be considered schedule. But we need to see if we should create a Schedule section only if posting has real specific content. It does mention "Work in a 24x7 team on call rotation, with ability to drive into workplace for critical events/needs." Also "Sit at the computer during scheduled work hours with appropriate breaks". That's schedule info. So we could include Schedule section with that content.
But we must not create sections with filler/placeholder text. So we need to ensure we have actual content.
Let's extract each.
**About the role**: The initial paragraphs before "Key job responsibilities". Let's capture:
"Do you like to design, operate, and implement networks of large scale? Would you like your work to play a key role to support all aspects of connectivity to/from Amazon and the outside world, as well as the connectivity between Amazon’s data centers and services to design and architect innovation so networks are fail-proof, infinitely scale and grow? The AWS GCNA (Global Connectivity and Network Availability) Organization is looking for a Network Development Engineer to join our EDGE team. Network Development Engineers partner with our broader Infrastructure organization on configurations standards and tools, and collaborate with Systems and Software Engineers to ensure fast, smooth roll-out of new designs and products, and also deploy and sustain networking software tools. AWS GCNA (Global Connectivity and Network Availability) is the backbone that connects the global AWS network. Focused on managing the internet traffic that allows users to access their information and applications regardless of where they are in the world. GCNA is responsible for building and designing a complex backbone network that allows internet traffic to flow efficiently between data centers and customers. If you like to work with new technologies, optimizing existing technology, and have experience participating in network/systems support for a large-scale enterprise or service provider environment, we would like to meet you. Your work will play a key role in driving the stability and sustainability of next-generation IP networks. You’ll join a diverse team of software, hardware, and network engineers, supply chain specialists, security experts, operations managers, and other vital roles. You’ll collaborate with people across AWS to help us deliver the highest standards for safety and security while providing seemingly infinite capacity at the lowest possible cost for our customers. And you’ll experience an inclusive culture that welcomes bold ideas and empowers you to own them to completion."
That's substantive.
**Responsibilities**: Combine "Key job responsibilities" and "A day in the life". Let's extract bullet-like sentences.
Key job responsibilities list:
- Network Development Engineers perform high quality network and/or systems operations, deployments, scaling, technology refresh, sustaining engineering, best practices application, optimization, internal/external customer interactions, and produce appropriate technical documentation.
- Create and implement changes on the network according to our change management standards.
- Work closely with our automation teams in defining the tools that allows us to scale at higher volume.
- Lead network projects in the areas of networking sustaining engineering, network deployment/implementation, network scaling, technology refresh, best practices application, and/or network optimization.
- Maintain Amazon Web Services’ next generation networks for significant AWS customers by providing critical network support to diagnose, mitigate impact, and resolve large-scale networking events.
- Operate and troubleshoot network routing, interconnectivity, platforms, performance, and configurations issues; including necessary low-level application interaction, Unix systems, and new age networking software tools.
- Drive and support innovation from Top of Rack to the Network Border, and everything in between.
- Partner with our broader Network/Infrastructure organization in the areas of network engineering, configurations standards, and tools.
- Work closely with our Network/Systems/Software Engineering teams to ensure fast, smooth roll-out of new designs and products, as well as, assist with deployment and sustaining of networking software tools.
- Maintain standards across the networking toolset and ensure that we are fully compliant to those standards and policies.
- Deliver simple, sustainable, and repeatable solutions and processes.
- Collaborate with the highest tier escalation engineers/resolvers.
- Create and review documentation and process regarding network implementation/deployments, recurring issues, new standard operating procedures, knowledge transfer material, etc.
A day in the life:
- Engineers in the GCNA-D organization have a wide range of responsibilities: we evolve routing policy, implement traffic engineering solutions, grow our peering footprint, secure the “front door” from bad actors on the Internet, and architect the hardware platforms and network design to support any Amazon product that needs to reach end-users worldwide.
- Our infrastructure moves terabits of traffic to and from the Internet at any given moment, and represents one of the largest edge surface areas in the world, requiring complex solutions to ensure that capacity always stays ahead of demand.
- To accomplish that, our engineers develop automation, write software, and work with a wide range of partner teams to continually improve and automate our Internet connectivity in areas such as capacity delivery, configuration deployment, impairment detection, and traffic optimization.
- Internet Edge engineers make decisions on both a day-to-day and long-term strategic basis, which carry a large amount of responsibility and impact across all of Amazon’s products.
- Work in a 24x7 team on call rotation, with ability to drive into workplace for critical events/needs.
- Manage customers during problem resolution and operating efficiently under pressure.
- Sit at the computer during scheduled work hours with appropriate breaks while maintaining a high level of alertness and attention to detail.
- Travel to data center/network sites and Amazon/customer offices as needed.
We can combine into a single - list.
**Requirements**: Basic Qualifications:
- 4+ years of major internet routing protocols experience
- 4+ years of working in a Linux/Unix environment experience
- 4+ years of automation scripting using Python, Bash, Shell and/or Perl experience
We could phrase as list items.
**Qualifications**: Preferred Qualifications:
- Senior or Lead Engineer experience at other organizations.
- Expert-level certifications (e.g. CCIE, JNCIE) a plus.
- Expert-level scripting and or automation skills in a network environment.
- Software development/programming skills are a plus.
**Skills**: Not explicitly separate; but we could treat the qualifications as skills. However we already have Requirements and Qualifications. The instruction says we can include Skills section if posting has real specific content for it. There's no separate skills list; but we could embed skills in qualifications. Better to omit Skills section if no explicit content.
**Benefits**: The paragraph about benefits: "Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave. Learn more about our benefits at https://amazon.jobs/en/benefits."
Also earlier: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That's compensation but could be part of Pay.
We'll create Benefits section with that list.
**Pay**: The base salary range: "USA, WA, Seattle - 136,000.00 - 184,000.00 USD annually". Also mention sign-on payments and RSUs. Also "Final compensation will be determined based on factors including experience, qualifications, and location."
We'll include Pay section with that info.
**Schedule**: The schedule info: "Work in a 24x7 team on call rotation, with ability to drive into workplace for critical events/needs." Also "Sit at the computer during scheduled work hours with appropriate breaks while maintaining a high level of alertness and attention to detail." Also maybe "Travel to data center/network sites and Amazon/customer offices as needed." That's more about travel but could be schedule. We'll include schedule items.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll structure:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Benefits
...
Pay
...
Schedule
- ...
...
We must ensure we don't include any boilerplate like EEO, etc. Also remove duplicated lines. Ensure we preserve all substantive info.
Let's craft the content precisely.
**About the role** paragraph: We'll copy the paragraph exactly as given, but maybe we need to ensure no extra fluff. We'll keep as is.
**Responsibilities** list items: We'll combine both sets. Ensure we don't duplicate. Let's list each unique item.
From Key job responsibilities:
1. Perform high quality network and/or systems operations, deployments, scaling, technology refresh, sustaining engineering, best practices application, optimization, internal/external customer interactions, and produce appropriate technical documentation.
2. Create and implement changes on the network according to our change management standards.
3. Work closely with our automation teams in defining the tools that allows us to scale at higher volume.
4. Lead network projects in the
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
...
Pay
...
Schedule
- ... ...