Senior Network Development Engineer, Network - Core
About the role
then... maybe combine description and "A day in the life" and "About The Team"? Might be too much but okay. But we need to avoid duplication. Could separate: About the role (overview), Responsibilities (list), Requirements (basic qualifications), Qualifications (preferred qualifications), Skills (maybe combine both? but we can list skills from qualifications). Benefits (health insurance etc). Pay (salary range). Schedule: none -> omit. We must not create empty sections. Thus output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Check if we have content for Skills: we could extract from qualifications: "8+ years of major internet routing protocols experience", "5+ years of working in a Linux/Unix environment", "3+ years of automation scripting using Python, Bash, Shell and/or Perl", "Experience working in large-scale networking environments", "Knowledge of IP networking fundamentals and extensive experience in the application of IP protocols". Preferred: "Proficient in major network technologies such as VLAN, IPv4/IPv6, MPLS, BGP, MPBGP, GRE, VXLAN, OSPF, SDN etc". Those are skills. We could put Skills section with list. Requirements maybe basic qualifications. Qualifications maybe preferred qualifications. But we need to avoid duplication: maybe Requirements = basic qualifications, Qualifications = preferred qualifications. Skills could be omitted if we think it's redundant. But we need to decide. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Requirements and Qualifications into one "Requirements" section that includes both basic and preferred? But they said sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include only those with content. Could combine Requirements and Qualifications into one? But they are separate headings; we could still include both if they have content. However we might avoid thin sections. We have substantial content for both basic and preferred qualifications, so we can keep both. Skills: we could extract specific skills like "routing protocols", "Linux/Unix", "automation scripting", "large-scale networking", "IP fundamentals", "VLAN, IPv4/IPv6, MPLS, BGP, MPBGP, GRE, VXLAN, OSPF, SDN". That's substantive enough. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Now we need to format. Use
for each section heading. Inside each section, use
for prose,
- for lists. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from the posting. Let's extract details precisely. About the role: combine the initial description paragraphs (maybe up to "Key job responsibilities"). We have: "The AWS Networking organization is hiring, and we’re looking for talented Network Development Engineers (NDE) to join our team. Within Networking, we’re confronting and solving complex and high-stake challenges. Our teams support all aspects of connectivity to/from Amazon and the outside world, as well as the connectivity between Amazon’s data centers and services. As a member of one our network engineering teams, you will play a part in designing and architecting networks that simply cannot fail, must scale infinitely, and can never constrain growth or innovation. This opportunity sits within our Network Fabric Engineering organization, where the team is responsible for designing the networks for our data center network fabric, partnering with our customers, and enabling new services and cloud-native use cases through our network. Engineers in this organization define routing policy, design and implement Traffic Engineering solutions, as well as architect the hardware platforms and network design to support internal and external connectivity. Engineers on this team make day-to-day and strategic decisions that carry a huge amount of responsibility and impact." That's the about role. We could also include "A day in the life" and "About The Team" as part of about role or separate? But we already have Responsibilities section for key job responsibilities. The "A day in the life" is more descriptive of daily activities; could be part of About the role or Responsibilities. But we already have Responsibilities list; we could add a paragraph about day in the life under About the role. Better: Keep About the role as overview (first paragraph plus maybe "A day in the life" and "About The Team"). But we must not duplicate content that appears elsewhere. The "A day in the life" includes details about working with internal partners, developing next-gen platforms, tooling ecosystems, automation, scaling capacity, durable solutions, tooling for visibility and control, automatic mitigation. That's substantive and not in responsibilities list (though somewhat overlapping). We'll include it in About the role. "About The Team" includes description of AWS Core Networking focus, building data centers, owning solutions for racks, goal to balance efficiency, performance, reliability, network size >10Pbps inter data center traffic over >1M devices worldwide, team structured to create and evolve products, providing highly available, secure, scalable network for multiple customers globally. That's also substantive. Thus About the role section can contain multiple paragraphs. Now Responsibilities: list from "Key job responsibilities": - Develop and validate new network designs. - Architect, implement, and operate large-scale networks. - Champion operational excellence in AWS networking, with responsibility for the introduction and adoption of new and evolving fabric designs based on customer needs. - Demonstrate expertise in distributed control-plane network routing designs, including their supported use cases and limitations. - Improve consistency and integration between data center access network layer and/or systems and related data center fabric (DCF) networks and/or systems. - Identify and solve ambiguous network problems, architectural or operational deficiencies. We'll put each as
- .
Now Requirements (basic qualifications):
- 8+ years of major internet routing protocols experience
- 5+ years of working in a Linux/Unix environment
- 3+ years of automation scripting using Python, Bash, Shell and/or Perl experience
- Experience working in large-scale networking environments
- Knowledge of IP networking fundamentals and extensive experience in the application of IP protocols
We'll list.
Now Qualifications (preferred qualifications):
- Proficient in major network technologies such as VLAN, IPv4/IPv6, MPLS, BGP, MPBGP, GRE, VXLAN, OSPF, SDN etc
We could also include maybe other preferred? That's it.
Now Skills: we could list specific skills derived from both sets:
- Major internet routing protocols (BGP, OSPF, etc.)
- Linux/Unix environment
- Automation scripting (Python, Bash, Shell, Perl)
- Large-scale networking environments
- IP networking fundamentals and application of IP protocols
- VLAN, IPv4/IPv6, MPLS, BGP, MPBGP, GRE, VXLAN, OSPF, SDN
- Traffic Engineering solutions
- Routing policy definition
- Hardware platform architecture
- Network design for internal/external connectivity
- Tooling for visibility and control, automation of builds, configuration deployment, scaling capacity
- Event mitigation and impact reduction
But we must not invent details; we can only include what is in posting. So we can list skills that are explicitly mentioned: "major internet routing protocols", "Linux/Unix environment", "automation scripting using Python, Bash, Shell and/or Perl", "large-scale networking environments", "IP networking fundamentals and extensive experience in the application of IP protocols", "VLAN, IPv4/IPv6, MPLS, BGP, MPBGP, GRE, VXLAN, OSPF, SDN", "Traffic Engineering solutions", "routing policy", "hardware platforms and network design", "tooling ecosystems", "automation of builds, configuration deployment, scaling of capacity", "visibility and control of traffic", "automatic mitigation of events". That's all from posting.
We'll create a
- list.
Now Benefits: from paragraph: "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." Also mention sign-on payments and RSUs? That's compensation, not benefits. But we can include sign-on payments and RSUs under Pay maybe. Benefits section: health insurance details, 401(k) matching, paid time off, parental leave. Also maybe mention "Learn more about our benefits at https://amazon.jobs/en/benefits." but that's a link; we could keep as part of benefits? It's a reference; we could include as a
with link. However instruction: remove application instructions, but this is not application instruction; it's a link to learn more about benefits. Might keep. We'll include benefits as list. Now 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