What You’ll DoAs a Senior Principal Network Reliability Engineer, you will:Provide technical leadership for the deployment, operation, and lifecycle management of OCI’s global network infrastructure.Define and drive the…
Network Engineer jobs in Seattle, WA
Network engineers design, build, and maintain the networks that connect an organization — routing, switching, wireless, firewalls, and increasingly cloud and software-defined networking.
No email, no resume, no sign-up. Save any listing below and you start anonymously.
You're signed in. Saving a listing drops it straight into your pipeline.
Open network engineer roles
12 shown of 814 · sorted by freshness
bringing cutting-edge autonomy, AI, computer vision, sensor fusion, and networking technology to the military in months, not years.ABOUT THE TEAMThe Software Platform organization is seeking a Software Engineer to join A…
feasibility of design within time and cost constraints;Work with engineers across the company to build new features at large-scale;... ...across the company’s codebases to communicate with external card networks and paym…
We Are: We are a global collective of innovators applying the New every day to improve the way the world works and lives. New doesn’t mean being ahead of the curve; new is pushing forward the curve, riding the edge where…
international boundaries.25%-30% travel is required.Key job responsibilities- Design, build, and deploy solutions on AWS alongside partner engineering teams — from proof-of-concept through customer delivery, with a focus…
the agentic era? You’re in the right place! Agentforce is the future of AI, and you are the future of Salesforce.Our Public Cloud engineering teams are responsible for innovating and maintaining a large scale distributed…
The Networking team brings together innovative ideas and technologies from network architecture, software defined networking (SDN), network... ...)- Bachelor or higher degree in computer science, electronic engineering,…
technical teams, working with some of the best and brightest engineers, architects and technical managers while also developing your... ...choices across broad use cases involving security, compute, storage networking as…
years of related experience (Required)4-7 years Related work experience. (Required)4-7 years Progressive experience in software engineering, enterprise architecture, or technology leadership across multiple products, sys…
leading Testing, Inspection and Certification company. We operate a network of over 2,500 laboratories and business facilities across 115... ...system from the ground up.As the Founding Product & Platform Engineer, you'l…
independent members of Baker Tilly International, a worldwide network of independent accounting and business advisory firms in 141 territories... ...client relationships.ResponsibilitiesMulti-cloud platform engineering a…
possible not only in your community, but around the world.HDR Engineering is currently seeking a Transmission Line Project Engineer to join... ...our authentic selves to work every day.Our eight Employee Network Groups (…
What network engineers earn in Seattle
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $35–$49 | $72k–$102k |
| Mid level | $49–$67 | $102k–$140k |
| Senior | $65–$87 | $135k–$181k |
Adjusted for the Seattle market from national ranges.
What employers ask for
The skills these listings keep naming
Interview questions worth rehearsing
With the thing the interviewer is actually listening for
Users at one site report intermittent connectivity. How do you troubleshoot?
Work the layers: physical, then switching, routing, and upstream — using monitoring data to narrow scope. Intermittent issues test patience and method, so show both.
Explain what happens at each OSI layer when a user loads a website.
Keep it crisp and accurate through the layers; this is a fluency check. Tie each layer to a real troubleshooting tool you would use there.
How would you design the network for a new office?
Ask about size and needs first, then cover segmentation, redundancy, wireless coverage, and internet failover. Mentioning documentation and future growth rounds it out.
When would you use BGP versus OSPF?
External versus internal routing in essence — explain it through where each lives in a real network you have run rather than textbook definitions alone.
Tell me about a change you made that caused an outage, and what you learned.
Everyone in networking has one. Show the discipline that came out of it: change windows, peer review, rollback configs staged in advance.
How are you using automation in network operations?
Config templating, compliance checks, or Python/Ansible scripts — even small examples count. The field is moving this way and interviewers check for the trajectory.
Resume tips that move the needle
For network engineers specifically — generic advice costs you here
State network scale: sites, users, devices, and bandwidth managed — it is the first credibility check.
List certifications prominently (CCNA, CCNP) since networking still hires heavily on them.
Name specific platforms (Cisco IOS/NX-OS, Meraki, Palo Alto, Fortinet) rather than 'networking equipment'.
Quantify reliability wins: uptime improved, outage minutes reduced, failover designs that worked when tested.
Include automation and cloud networking experience — it distinguishes you from config-only candidates.
Where this role goes
Typical progression
Applying for network engineer jobs in Seattle?
Robbi carries this page into your first day: your role, your city, your shift preference. Then it hands you a few small things each morning and keeps the pipeline honest.
Save what looks right here, then let Robbi hand you a few small things each morning and keep the follow-ups honest.