Home · Interview questions · Network Engineer

Network Engineer interview questions

Network engineer interviews test your grasp of the fundamentals and your ability to troubleshoot in order, layer by layer.

What interviewers look for

Fundamentals. OSI, routing and switching.
Troubleshooting. Working through layers calmly.
Change safety. Planning changes and rollbacks.

How the interview usually runs

Recruiter call.
Technical interview.
Whiteboard or lab troubleshooting.
Team interview.

Stages vary by company, so ask the recruiter what to expect before you start preparing.

8 Network Engineer interview questions, and how to answer them

1. Two hosts in different VLANs can't talk.

What they want to see: Troubleshooting.

How to answer: Check VLANs, trunks, inter-VLAN routing and ACLs.

2. How does OSPF work?

What they want to see: Routing.

How to answer: Explain neighbours, link states and cost.

3. OSPF or BGP?

What they want to see: Design.

How to answer: Interior against exterior routing, with use cases.

4. What happens with STP in a loop?

What they want to see: Layer 2.

How to answer: It blocks redundant paths to prevent broadcast storms.

5. How do you troubleshoot packet loss?

What they want to see: Method.

How to answer: Use ping, traceroute and interface counters, layer by layer.

6. How does NAT work?

What they want to see: Fundamentals.

How to answer: It translates private to public addresses, and tracks sessions.

7. How do you plan a risky change?

What they want to see: Safety.

How to answer: Use a change window, tested rollback and timed reload.

8. What is SD-WAN?

What they want to see: Staying current.

How to answer: It routes traffic by policy across several links.

A sample answer

How do you troubleshoot packet loss?

I start by finding where it begins with traceroute or MTR. In one case, loss started at a branch switch. Interface counters showed CRC errors on one port. A patch cable had been damaged. I replaced it, confirmed the counters stopped rising and added monitoring on interface errors.

A made-up example to show the structure. Use your own experience and real numbers.

Common mistakes

Guessing instead of working through layers.
Changes with no rollback.
Vendor commands but no concepts.
Ignoring documentation.

Practise this out loud

Run a mock interview for a Network Engineer role. Questions change every time, you answer by voice or typing, and each answer gets a score with feedback.

Start a free mock interview See how Ghostpilot works

Frequently asked questions

Is CCNA still worth it?

It's widely recognised and useful, particularly early in your career.

Do network engineers need automation skills?

Increasingly, yes. Python and Ansible are a real advantage.