Interview questions by role

Network engineer interview questions

Network engineer interviews combine a technical check of fundamentals (the OSI model, TCP and UDP, subnetting, VLANs, routing protocols, DNS and DHCP) with stories from real work: an outage you handled, a change you planned, and how you troubleshoot methodically under pressure.

Interviewers want to hear that you understand why things work, not just which commands to type, and that you respect change control on live networks.

Mock Interview Copilot practice room: an AI interviewer asks a follow-up question while the candidate's spoken answer and pace appear in the transcript
Practising answers out loud in Mock Interview Copilot: the interviewer follows up when an answer is vague, and your pace and pauses are measured.

How the interview usually runs

A typical process is a recruiter or HR screen, then a technical interview with senior network engineers, sometimes followed by a practical: a subnetting exercise, a whiteboard diagram, a lab task or a troubleshooting scenario on a topology. Junior roles focus on fundamentals and certifications such as CCNA; senior roles add design, routing protocols such as OSPF and BGP, security, cloud networking and leading changes.

Technical questions usually go one layer deeper than you expect. If you say you configured VLANs, expect to be asked how traffic gets between them; if you mention OSPF, expect questions about how neighbours form or why a route isn't appearing. Say clearly when you're reasoning rather than remembering.

The behavioural side is about trust: interviewers look for engineers who plan changes, keep a rollback plan, communicate during outages and write things down.

Common questions and what the interviewer is checking

  1. Walk me through what happens when a user types a web address and presses enter.

    What they are checking: Layered understanding: the DNS lookup, ARP and the default gateway, the TCP handshake, TLS, HTTP, and routing in between. A good answer stays in order and goes deeper wherever the interviewer asks.

  2. What is the difference between TCP and UDP, and when would you use each?

    What they are checking: Connection-oriented and reliable versus connectionless and lightweight, with sensible examples such as web traffic versus voice calls or DNS queries.

  3. How would you subnet this address range for four departments of different sizes?

    What they are checking: Comfort with CIDR and working it through on paper, starting with the largest subnet, and staying calm doing maths in front of people.

  4. Users on one VLAN can't reach a server on another. How do you troubleshoot it?

    What they are checking: A layer-by-layer method: physical link, VLAN assignment and trunking, the routing interface between VLANs, ACLs or firewall rules, and testing from both ends.

  5. Explain how OSPF (or BGP) chooses a route.

    What they are checking: Real understanding over memorised terms: link state and cost for OSPF, path attributes and policy for BGP, and what would stop a route being learned at all.

  6. Tell me about a network outage you were involved in.

    What they are checking: Calm incident handling: how it was detected, how you isolated the cause, who you kept informed, how service was restored and what changed afterwards.

  7. How do you plan and carry out a change on production network equipment?

    What they are checking: Change control discipline: a written plan, impact assessment, approval, a maintenance window, checks before and after, a tested rollback and saved configurations.

  8. Tell me about a change that didn't go to plan.

    What they are checking: Honesty and judgement: recognising failure quickly, rolling back rather than improvising on a live network, and the lesson you applied next time.

  9. How do you document a network?

    What they are checking: Current diagrams, IP address management, configuration backups and runbooks, and an understanding of why documentation matters when someone else is on call.

How to structure a strong answer

Answer technical questions from the bottom up and state your assumptions out loud. For outage and change stories, use STAR, but make the Action the longest part: your method, your checks and your communication.

Example answer

Tell me about a network outage you were involved in.

At a distribution company with three sites, staff at one warehouse suddenly lost access to the stock system mid-morning, while head office was fine. I was the on-call engineer. I confirmed the site's internet connection was up, so it wasn't the line itself, then checked the site-to-site VPN tunnel to head office and found it repeatedly dropping and failing to re-establish.

The logs showed it had started just after maintenance work by the internet provider for that area, and the site's public IP address had changed. Our head office firewall was still configured for the old address. I updated the peer address, with my manager's approval by phone because it was an emergency change, and the tunnel came straight back up. Pickers were working again in about forty minutes, and I sent the warehouse manager an update every fifteen minutes while it was down.

Afterwards I logged the emergency change properly, raised a change to move that site to a static IP address, and added the provider's maintenance notices to our team calendar so we'd see the next one coming.

Mistakes to avoid

Frequently asked questions

What technical questions are asked in a network engineer interview?

Fundamentals come up most: the OSI model, TCP versus UDP, subnetting, VLANs and trunking, how routing works, DNS and DHCP, and often a routing protocol such as OSPF or BGP. Expect troubleshooting scenarios too, and questions on firewalls and increasingly on cloud networking.

Do I need a CCNA for a network engineer interview?

It is commonly listed for junior roles and shows you know the fundamentals, but employers weigh practical experience heavily. If you don't have it, home lab or simulator work that you can describe in detail helps.

How should I answer a networking question I don't know?

Say what you do know, reason out loud about how you'd find out, and name the command or tool you'd use to check. Interviewers respect a clear method far more than a confident guess.

What is change control and why do interviewers ask about it?

It is the process of planning, approving, scheduling and reviewing changes to live systems, including a rollback plan. Because one network change can take a whole site offline, interviewers want evidence you follow it even under time pressure.