# Updated Resume # Current Location # Work Authorization # LinkedIn Id Job Title: Embedded Software Engineer Location: Minneapolis, MN (Onsite) Duration: Long term Education/Experience Required: ~ Bachelor s Degree...
Network Engineer jobs in Minneapolis, MN
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 1,324 · sorted by freshness
already have the following set of skills. Familiarity with network services (web servers, databases, DNS, etc.) Experience maintaining... ...groups with over 4500 active users spanning the sciences, engineering, life sci…
IDR is seeking a Senior IT Solutions Architect to join one of our top clients for an opportunity in Minneapolis, Minnesota . In this role, you will provide end-to-end solution architecture leadership for major initiative…
technical and client teams to design scalable SAP solutions that drive measurable business outcomes. Apply a Forward Deployment Engineering (FDE) mindset to rapidly translate business challenges into executable solutions…
Job Description Job Description Job Title: Embedded Software Engineer Job Description We are seeking a talented Embedded Software... ...who drive scale, innovation and speed to market. With a network of almost 20,000 con…
Job Description Job Description Job Summary We are looking for an experienced Senior Network Engineer to help support and grow our current and future client base. In this role, you'll assess clients' current operations a…
security, and responsible AI considerations. Collaborate with engineering and business teams to assess emerging technologies and... ...cloud computing, systems engineering, infrastructure, security, networking, or data a…
Below is specific information for you to consider about this position. Job Title: Systems Engineer - Enterprise Infrastructure (2026-2027) and Requisition ID number: 104764 Close Date: 11:59 PM on 07/22/2020 Organization…
Job Description Job Description Description: Position Summary: The Senior Network Engineer will develop, implement, and support network services and solutions for consulting clients. This position will build a customer-f…
and support functions across the globe, your journey at Tennant can take you places you never expected. Senior Principal System Engineer - New Product Development Tennant Company is a recognized leader in designing, manu…
connected -- and a lot smarter. We’re looking for an Embedded Software Engineer who’ll be responsible for the development of software for the adoption and integration of smart home networking technologies for the SmartTh…
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 Minneapolis
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $28–$40 | $59k–$84k |
| Mid level | $40–$55 | $84k–$114k |
| Senior | $53–$71 | $110k–$148k |
Adjusted for the Minneapolis 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 Minneapolis?
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.