The BGP Interview Questions That Actually Get Asked (and How to Answer Them)

Border Gateway Protocol appears in almost every network engineering interview, and in many cloud and infrastructure engineering interviews as well. It is a topic where interviewers reliably separate candidates who understand the mechanism from candidates who can only recite the name.

The most common BGP question at entry level is path selection. If you cannot walk through the full decision process — weight, local preference, AS path length, origin code, MED, eBGP over iBGP, lowest router ID — without looking it up, you are not ready for a panel. The question is not whether you can list the attributes. It is whether you can explain why each one exists and what happens when two paths are equal on all attributes above it.

At senior level, the question often shifts to design. You might be asked to build a BGP policy architecture for a multi-region network: how do you prevent route leaks, enforce prefix limits, use communities to signal traffic intent, or design around a route reflector cluster without creating a single point of failure? These questions test whether you have operated BGP at scale, not just studied it.

Route leaks are another recurring topic. Interviewers want to know both what a route leak is mechanically — a prefix being advertised to a peer that should not receive it — and what the controls are: prefix length limits, AS path validation, RPKI, IRR filtering, community-based policy, and NO_EXPORT. A candidate who can only name RPKI without explaining what it validates and what it does not catch will struggle.

One thing many candidates miss: BGP convergence is intentionally slow, and understanding why matters. The Minimum Route Advertisement Interval, route dampening, and BFD-assisted fast failure detection all exist for different reasons. If an interviewer asks about BGP convergence behaviour under link failure, they expect you to know the difference between fast detection and fast advertisement.

The framing that helps most in these interviews is to answer in three layers: what the mechanism is, what the operational consequence is, and what you would observe or change if something were wrong. That structure demonstrates both depth and practical experience — which is exactly what senior panels are evaluating.

BGP is not a topic you pass by memorising the twelve-step decision algorithm. You pass it by being able to explain the algorithm, apply it to a real topology, and diagnose what happens when a route does not appear where you expect it.

More from the blog