Network Administrator interview questions and how to answer them
A network administrator interview is mostly about one thing: can they trust you with production gear at the worst possible moment. Expect a mix of fundamentals, a troubleshooting scenario or two, and questions about how you behave when the whole office is down. Here's what they ask, why, and what a good answer sounds like.
What happens in each round
- 1
Recruiter or HR screen
What happens
Whether your experience matches the gear they run, whether you can do on-call, and whether you hold the certification the posting mentions. Keep it short and name the vendors you've actually worked with.
- 2
Technical interview with the network or IT lead
What happens
Your fundamentals: subnetting, VLANs, routing, DHCP, DNS and firewall rules. They'll usually hand you a broken scenario and listen to the order you'd check things in.
- 3
Hands-on or whiteboard exercise
What happens
Some teams give you a lab in Packet Tracer, a config to read, or a diagram to fix. They care less about speed and more about whether you explain what you're doing and why.
- 4
Hiring manager and team fit
What happens
How you handle an outage, how you talk to users who aren't technical, how you document, and whether you follow change control instead of cowboying fixes in at lunchtime.
Questions you're likely to get
1.Walk me through how you'd troubleshoot a user who says they have no network access.
Why they ask
It's the most common ticket you'll get, and your order of operations shows whether you think in layers or just guess.
How to answer
- Start with scope: is it one user, one floor or everyone
- Check the physical side first: link light, cable, the switch port status
- Confirm the IP address, gateway and DNS the machine actually received
- Ping the gateway, then something outside, then test name resolution separately
- Look at the switch port for errors, the wrong VLAN or a port security violation
2.What's a VLAN, and why would you use one here?
Why they ask
VLANs are everyday work for a network administrator. They want to hear you connect the concept to a real reason, not recite a definition.
How to answer
- A VLAN splits one physical switch into separate broadcast domains
- Give real uses: keeping guest Wi-Fi away from staff, putting phones or cameras on their own segment
- Mention trunk ports carrying several VLANs between switches and access ports for end devices
- Say that traffic between VLANs goes through a router or firewall, which is where you apply rules
3.A department says the network is slow. How do you figure out what's going on?
Why they ask
Slow is vaguer than down, and it tests whether you use monitoring data or just go on what the loudest user says.
How to answer
- Ask what's slow: one app, the internet, file shares, or everything
- Check interface utilization and errors in the monitoring tool, such as SolarWinds or PRTG
- Look for a saturated uplink, duplex mismatch or a port throwing CRC errors
- Use Wireshark or a flow tool to see what's eating the bandwidth
- Rule out the application or server before blaming the network
4.How do DHCP and DNS work together when a laptop joins the network?
Why they ask
A lot of network tickets turn out to be DHCP or DNS. They want to know you can tell the two apart under pressure.
How to answer
- Describe the DHCP exchange: the laptop asks, the server offers, the laptop requests, the server confirms
- Explain that DHCP hands out the address, gateway and DNS servers
- Mention DHCP relay or an IP helper when the server sits on another VLAN
- Show you know the symptoms: a self-assigned address points to DHCP, pinging by IP but not by name points to DNS
5.Tell me about a time you caused an outage or a change went wrong.
Why they ask
Everyone who's touched a production network has broken something. They want honesty and proof you learned a habit from it.
How to answer
- Pick a real mistake, such as a wrong ACL or a trunk you pruned too far
- Say how you noticed and how fast you rolled it back
- Explain who you told and how you communicated during the outage
- Name the habit you changed, like saving a backup config first or using a scheduled reload
6.How would you set up remote access for staff working from home?
Why they ask
VPN access is a big chunk of the job and a common security gap. They want to see you think about both usability and risk.
How to answer
- Name the approach you've used, such as a client VPN on the firewall
- Tie authentication to Active Directory and add multi-factor sign-in
- Decide on split tunnel versus full tunnel and explain the tradeoff
- Limit what VPN users can reach with firewall rules and groups
- Mention logging and how you'd remove access when someone leaves
7.How do you decide whether a firewall rule request should be approved?
Why they ask
Firewall requests come in constantly, and a network administrator who approves everything is a risk.
How to answer
- Ask what the business need is and who owns the request
- Keep the source, destination and port as narrow as the need allows
- Put it through change control and document it with a ticket number in the rule description
- Review old rules on a schedule so temporary access doesn't become permanent
8.What's your experience with wireless, and how would you fix a spot with bad coverage?
Why they ask
Wireless complaints are constant, and they want to see if you understand it beyond rebooting the access point.
How to answer
- Mention the controller or dashboard you've used, like Meraki or a Cisco wireless controller
- Talk about a site survey or a heat map before you move or add access points
- Cover channel overlap and interference, not just signal strength
- Check whether the problem is too few access points or too many clients on one
9.How do you keep network documentation up to date?
Why they ask
Stale diagrams make every outage longer. This tells them whether you'll leave the next person better off.
How to answer
- Say where you keep diagrams and records, such as Visio, draw.io, NetBox or a wiki
- Update documentation as part of closing a change, not as a separate project
- Keep config backups automated so you always have a known good copy
- Give an example of documentation that saved time during an incident
10.The main internet circuit goes down during business hours. What do you do?
Why they ask
This is the outage scenario. They're listening for calm, order and communication as much as technical steps.
How to answer
- Confirm it's the circuit and not your edge firewall or router
- Check whether failover to the backup link kicked in
- Open a ticket with the carrier and have the circuit ID ready
- Tell leadership and the help desk what's down and when you'll update them next
- Afterward, write up the cause and whether the failover needs work
11.How do you stay current with networking?
Why they ask
Gear, firmware and security threats keep changing, and they want someone who keeps learning without being told to.
How to answer
- Mention a home lab or a lab tool like Packet Tracer or EVE-NG
- Name a certification you hold or are working toward, such as the CCNA
- Follow vendor security advisories for the gear you run
- Give one specific thing you learned recently and used at work
Mistakes that sink good candidates
Saying you'd make a change on production gear without a backup or a rollback plan
Bluffing on a protocol you don't know instead of saying how you'd find out
Blaming users, vendors or the last admin for every problem in your stories
Showing no interest in documentation or change control because they slow you down
Need more Network Administrator interviews to prep for?
HeroApply applies to Network Administrator jobs that match you, every day. 164 jobs are open today.