Technical interview guide

Network Troubleshooting

Systematically isolating where in the stack a connectivity problem actually lives, instead of guessing.

Read: 45 min
Practice MCQs: 25
Interview QA: 25
Edition: v4
Editorial status: Reviewed
Relevant for: Network Engineer

Scope: Current Wireshark, tcpdump, Linux iproute2/ss/tc/ethtool, IETF host/TCP/ICMP/PMTUD/DNS/TLS references reviewed 2026-09-04.

Interview QA

Treat each question like a live interview question: answer out loud first (structure, assumptions, tradeoffs), then open the model answer to spot gaps and rehearse a tighter follow-up.

Curated: 2026-10-05 · Written: 2026-10-05 · Reviewed: 2026-10-03

QA-1

Scope an intermittent network incident.

QA-2

Map an end-to-end packet path for diagnosis.

QA-3

Diagnose failed ARP or NDP resolution.

QA-4

Troubleshoot a route that appears present but traffic fails.

QA-5

Use DNS bypass tests without drawing false conclusions.

QA-6

Separate connect, TLS, and application failures.

QA-7

Locate packet loss using TCP sequence evidence.

QA-8

Diagnose a slow TCP stream with window and queue data.

QA-9

Troubleshoot certificate failures affecting one client cohort.

QA-10

Run a Path MTU investigation.

QA-11

Interpret captures in the presence of offloads.

QA-12

Diagnose a p99 latency regression.

QA-13

Troubleshoot low transfer throughput systematically.

QA-14

Diagnose and mitigate bufferbloat.

QA-15

Investigate intermittent failures through a stateful middlebox.

QA-16

Plan a safe multi-point packet capture during an incident.

QA-17

How do you distinguish between asymmetric routing and a unidirectional link failure when troubleshooting intermittent TCP connection drops?

QA-18

How do you isolate whether high latency is caused by network queueing delay versus propagation delay or endpoint processing latency?

QA-19

How do you troubleshoot BGP route flapping and isolate whether the trigger is physical layer instability, hold-time expiration, or policy misconfiguration?

QA-20

Validate packet-loss evidence under high traffic.

QA-21

Build a network incident evidence timeline.

QA-22

Design network troubleshooting telemetry.

QA-23

Close a network incident with engineering evidence.

QA-24

Diagnose dual-stack failures affecting only some clients.

QA-25