$70 - $80 per hour
Job Title: Network Engineer Location: Washington, D.C. Type: Contract Model: Hybrid – Onsite and Remote Security Clearance: Active - DOD Responsibilities: Implement DISA Secure Cloud Computing Architecture (SCCA) referen…
Engineering & IT · Washington, DC
Network Engineer jobs in Washington, DC
Network engineers design, build, and maintain the networks that connect an organization — routing, switching, wireless, firewalls, and increasingly cloud and software-defined networking.
7,915
Open roles today
$35–$87/hr
Typical pay range
$121k
Median, full-time
2
Fresh in this list
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.
01
Open network engineer roles
4 shown of 7,915 · sorted by freshness
Job Description Job Description We are looking for a Network Engineer II to support enterprise network initiatives and deliver reliable engineering solutions across a diverse portfolio of programs. This long-term contrac…
volunteer time. Additional paid sick leave is also provided if required by state or local law. Summary of Position: The Network Engineer is responsible for architecture, support, routing, switching, documentation, troubl…
Job Description Job Description DCS is searching for a performance‑driven Network Engineer to support US Army programs. A focus on either Analytical, Financial, logistics, engineering, technical support and/or management…
02
What network engineers earn in Washington
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 Washington market from national ranges.
03
What employers ask for
The skills these listings keep naming
Routing and switching (BGP, OSPF)Cisco or Juniper platformsFirewalls and VPNsTCP/IP deep knowledgeWireless networkingNetwork monitoring toolsCloud networking (VPC, SD-WAN)Automation (Python, Ansible)Documentation and diagrams
04
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.
05
Resume tips that move the needle
For network engineers specifically — generic advice costs you here
01
State network scale: sites, users, devices, and bandwidth managed — it is the first credibility check.
02
List certifications prominently (CCNA, CCNP) since networking still hires heavily on them.
03
Name specific platforms (Cisco IOS/NX-OS, Meraki, Palo Alto, Fortinet) rather than 'networking equipment'.
04
Quantify reliability wins: uptime improved, outage minutes reduced, failover designs that worked when tested.
05
Include automation and cloud networking experience — it distinguishes you from config-only candidates.
06
Where this role goes
Typical progression
01
Network Technician
02
Network Engineer
03
Senior Network Engineer
04
Network Architect
Ten quiet minutes a day
Applying for network engineer jobs in Washington?
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.
Start with this search
No email, no resume, no sign-up.
Open your tracker
Everything you saved is already there.