Network Engineer Interview
Questions & Answers

OSI model top-down or bottom-up: ping (Layer 3 reachability), traceroute (path and latency), telnet/nc to the specific port (Layer 4 connectivity), then application-level checks. Check interface status, routing table, firewall rules, and security groups. In cloud environments, check VPC peering routes, security groups, and NACLs — the most common connectivity issue is a missing security group rule, not a routing problem.

Border Gateway Protocol is the routing protocol of the internet — it manages how packets are routed between autonomous systems (networks under independent administrative control). Use BGP for multi-homed internet connectivity (two ISPs for redundancy), SD-WAN deployments, and cloud connectivity (AWS Direct Connect, Azure ExpressRoute all use BGP). BGP is a path-vector protocol that selects routes based on attributes (AS-path, local preference, MED) rather than just shortest path.

No single points of failure: redundant switches with spanning tree or ECMP, redundant uplinks (LAG/LACP), redundant WAN connections to different ISPs. Out-of-band management so you can access devices when the in-band network is down. Network segmentation with VLANs to contain broadcast domains and limit blast radius of failures. Document the design and test failover scenarios before they are needed in production.

Functionally similar — both route packets between subnets using IP. Difference: Layer 3 switches use ASICs for hardware-accelerated switching at line rate, optimised for intra-datacenter routing between VLANs at high speed. Routers use software-based routing engines, better suited for complex routing policies, WAN interfaces, NAT, VPN termination, and flexible protocol support. In a datacenter, L3 switches handle east-west traffic; routers handle north-south (internet) traffic.

Zero Trust architecture: authenticate every connection regardless of network location, micro-segmentation to limit lateral movement, network access control (NAC) to verify device compliance before granting access. IDS/IPS for threat detection, NetFlow or IPFIX analysis for anomaly detection. DNS filtering to block malicious domains. The perimeter is gone — modern network security assumes breach and limits the blast radius rather than keeping attackers out.

Structure your answer as a 60-second professional narrative: where you have been (your background), what you have done (your strongest achievement), and where you are going (why this role). Lead with your most relevant experience, not your entire career history. End with why you are excited about this specific opportunity.

Choose a genuine weakness that you have actively worked to improve. The structure is: name the weakness → show self-awareness of its impact → describe the concrete step you took to address it → show the improvement. Never say "I work too hard" — interviewers recognise this as evasion and it damages your credibility.

Use the STAR method (Situation, Task, Action, Result) but add a fifth element: what you learned. Choose a real failure, not a disguised success. Show you can take responsibility without making excuses, and demonstrate that the lesson changed your behaviour in a specific, verifiable way.

Be honest but constructive. Acceptable reasons: seeking greater scope, new challenge, skills you can not develop in the current role, or company-level changes (restructuring, direction shift). Never speak negatively about your current employer or manager — it signals you will do the same to the prospective employer in future conversations.

Describe the conflict specifically, show that you sought to understand the other person's perspective, and explain the resolution approach you took. Interviewers are assessing your emotional intelligence and whether you escalate or resolve. Avoid stories where you were right and they were wrong — choose a story where both parties grew.

Describe your specific prioritisation system: impact × urgency matrix, stakeholder alignment, or a specific tool or process you use. Then give an example where you applied it under real pressure. Show that your system is systematic rather than reactive, and that you communicate proactively when priorities change.

Choose an achievement that is specific, measurable, and relevant to the role. Lead with the result ("I reduced our error rate by 40% in 90 days"), then explain the context, challenge, and what you specifically did that drove the result. Show your ownership and impact, not just your team's work.

Be honest about your ambitions while showing that this role is a genuine step in that direction — not a stopgap. Hiring managers want to invest in people who will grow with the organisation. Show that your 5-year goal requires the specific skills and experience this role provides, making your ambition an asset for both sides.

Research before the interview and make the answer specific: cite their product, a recent company development, something about their culture or team, or a professional aspect of this particular role that matches your goals. Generic answers ("I love your values") signal you did not do the research. Specific answers signal genuine interest.

Always have 3–5 questions prepared. Ask about the biggest challenge in this role, what success looks like in the first 90 days, how the team operates, and the interviewer's own experience at the company. Never ask about salary, benefits, or holidays in a first interview. Questions show interest, strategic thinking, and that you care enough to have done research.