Responsibilities Own the Software Requirements Specification with program stakeholders as requirements evolve. Write real-time C++ control software for motors, actuators, and sensors in multi-axis motion-control systems.…
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 775 · sorted by freshness
Senior Embedded Software Engineer: Autonomous Heavy-Lift Vehicle OCI · St. Louis, MO · On-site Mon–Thu · Start Dec 2026/Jan 2027 US citizenship required (no clearance needed) There are no hydraulics. About 16 electric mo…
cloud environments that allow even the best companies to move faster, all while having some fun! About the job: As a Solutions Engineer, you will be responsible for supporting our Mid-Enterprise customers, reporting to t…
Platforms that help Mission Critical Software Ship Securely and Reliably. Join Esri`s Professional Services organization and help engineer the CI/CD platforms, automation and infrastructure supporting secure software del…
Coach and develop junior SAs (L3–L5) on technical depth, customer engagement, and use case prioritization Contribute to Field Engineering thought leadership through customer-facing content, workshops, and community engag…
computing, cloud, and edge-native architecture ~ Knowledge implementing zero trust, cross domain services, and securing classified networks ~ Professional experience architecting, implementing, and administrating enterpr…
computing, cloud, and edge-native architecture ~ Knowledge implementing zero trust, cross domain services, and securing classified networks ~ Professional experience architecting, implementing, and administrating enterpr…
computing, cloud, and edge-native architecture ~ Knowledge implementing zero trust, cross domain services, and securing classified networks ~ Professional experience architecting, implementing, and administrating enterpr…
Senior Firewall Engineer Technical Lead Remote in USA | 12-month contract | 1 opening About the role We are looking for... ...tasks to two project engineers, and work closely with the client's network security engineerin…
RentalandAlamo Rent A Carbrands through its integrated global network ofindependent regional subsidiaries. Enterprise Mobility and its... ...to assist in defining the architecture Collaborates with engineers and other ar…
designing, implementing, supporting, and improving enterprise network infrastructure. Strong knowledge of TCP/IP, IPv4/IPv6, DNS... ...Incorporate security and compliance requirements into network engineering and operati…
be at the forefront of these efforts. This position requires an Engineer to collaborate with a talented team within Digital and... ...software applications development, relational databases, and server / network infrastr…
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.