Role: Senior Software Engineer – Network Services / Proxy Development Employment: Contract Location: St. Louis, MO Skills: Strong hands-on development experience in Go or C is mandatory. - Candidates without demonstrated…
Network Engineer jobs in St. Louis, MO
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 403 · sorted by freshness
year Requirements: Bachelors degree in computer science, engineering, or a related discipline, or equivalent professional experience... ...organization. Deep knowledge of infrastructure security, including network securi…
SAP PMMO/GPD Solution Architect Employer: Inabia Solutions & Consulting Inc. Client: Aerospace & Defense organization Location: Remote, with periodic travel to St. Louis, MO Duration: Up to 12 months Pay: $80–$85 per hou…
scalability, and cost efficiency* Collaborate with security, networking, and operations teams to ensure deployments meet compliance,... ...runbooksRequirements* Bachelor's degree in Computer Science, Engineering, or a re…
About this role:Wells Fargo is seeking a Principal Engineer for the Wealth Investment Management Technology (WIMT) Platform Engineering... ...an advisor to leadership to develop or influence applications, network, inform…
Salary: $65,000 - 80,000 per year Requirements: We look for three or more years of hands-on experience supporting business networks; MSP experience is preferred. We need strong working knowledge of TCP/IP, DNS, DHCP, NAT…
development, enhancement, and ongoing optimization of a complex enterprise ServiceNow platform. This role will focus on platform engineering, workflow automation, release management, configuration management, and AI-driv…
stage of your career. Try new things, learn new skills and discover what you excel at—all from Day One.Job DescriptionThe Automation Engineer tests, creates, implements and supports robotics process and desktop automatio…
solutions powered by AI agents and decision-support platforms. Acting as the bridge between client stakeholders, product teams, and engineers, you will map current-state operations and co-create the future-state AI-nativ…
By owning your opportunity at GDIT, you are helping us ensure today is safe and tomorrow is smarter. Our work depends on a Sr. Network Engineer with TS/SCI security clearance and willing to take CI Polygraph in joining o…
can’t turn into opportunity. GDIT is seeking a Cyber Systems Engineer III – ECDS (Cross Domain Engineer) to support our Intelligence... ...experience as a Cyber Engineer across application, system, and network cybersecur…
Position Overview We are seeking a highly skilled Field Service Engineer to install, commission, maintain, and troubleshoot industrial material handling and process equipment at customer manufacturing facilities across N…
What network engineers earn in St. Louis
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $25–$36 | $53k–$75k |
| Mid level | $36–$50 | $75k–$103k |
| Senior | $48–$64 | $99k–$133k |
Adjusted for the St. Louis 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 St. Louis?
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.