Senior Network Engineer Interview Questions and Answers

Milad Bonakdar
Author
Prepare for senior network engineer interviews with practical questions on OSPF, BGP, SD-WAN, high availability, security, QoS, automation, and troubleshooting.
Introduction
Senior network engineer interviews usually test how you reason through design and incidents, not whether you can recite commands. Be ready to explain why you would choose OSPF areas, BGP policy, SD-WAN or MPLS, segmentation, QoS, and automation controls in a real enterprise network.
Use these questions to practice concise answers: state the goal, name the trade-offs, describe the checks you would run, and connect the design to reliability, security, cost, and user impact.
Advanced Routing
1. Explain OSPF and how it works.
Answer: OSPF (Open Shortest Path First) is a link-state routing protocol.
Key Features:
- Fast convergence
- Hierarchical design (areas)
- Classless (supports VLSM)
- Metric: Cost (based on bandwidth)
OSPF Areas:
OSPF Configuration:
OSPF States:
- Down
- Init
- Two-Way
- ExStart
- Exchange
- Loading
- Full
Rarity: Very Common
Difficulty: Hard
2. How does BGP work and when would you use it?
Answer: BGP (Border Gateway Protocol) is the internet's routing protocol.
Use Cases:
- Internet service providers
- Multi-homed networks
- Large enterprises with multiple ISPs
BGP Types:
- eBGP: Between different AS (external)
- iBGP: Within same AS (internal)
BGP Configuration:
BGP Path Selection:
- Highest Weight
- Highest Local Preference
- Locally originated
- Shortest AS Path
- Lowest Origin type
- Lowest MED
- eBGP over iBGP
- Lowest IGP metric
Rarity: Common
Difficulty: Hard
3. Explain MPLS vs SD-WAN and when to use each.
Answer: MPLS (Multiprotocol Label Switching) and SD-WAN (Software-Defined WAN) are enterprise WAN technologies.
MPLS:
- Label-based packet forwarding
- Predictable performance
- Traffic engineering capabilities
- Predictable but usually higher-cost
SD-WAN:
- Software-defined overlay network
- Uses internet connections
- Application-aware routing
- Can reduce WAN cost when designed with security and monitoring
Comparison:
MPLS Configuration:
SD-WAN Architecture:
SD-WAN Policy Example:
Migration Strategy:
1. Hybrid Approach:
- Keep MPLS for critical applications
- Add SD-WAN for internet breakout
- Gradual migration
2. Full SD-WAN:
- Reduce or replace MPLS where SLA and security requirements allow
- Use multiple internet circuits
- Implement a security stack: firewall policy, encryption, segmentation, and logging
Use Cases:
Choose MPLS when:
- Strict latency, loss, or private-transport requirements
- Strong compliance or segmentation requirements
- Predictable performance critical
- Budget allows
Choose SD-WAN when:
- Cost optimization needed
- Cloud-first strategy
- Rapid deployment required
- Multiple branch locations
- Need application visibility
Rarity: Common
Difficulty: Hard
Network Design
4. Design a highly available enterprise network.
Answer: Enterprise network with redundancy:
Key Components:
1. Redundancy:
- Dual ISP connections
- Redundant routers (HSRP/VRRP)
- Redundant core switches
- Redundant links (EtherChannel)
2. HSRP Configuration:
3. Spanning Tree:
Rarity: Very Common
Difficulty: Hard
5. How do you design an enterprise wireless network?
Answer: Enterprise wireless requires careful planning for coverage, capacity, and security.
Architecture Options:
1. Controller-Based (Centralized):
Benefits:
- Centralized management
- Seamless roaming
- Consistent policies
- Easier troubleshooting
2. Controller-Less (Distributed):
- Each AP is autonomous
- Lower cost
- No single point of failure
- More complex management
Design Considerations:
1. Site Survey:
2. Channel Planning:
2.4 GHz:
- Channels: 1, 6, 11 (non-overlapping)
- 20 MHz channel width
- Better range, more interference
5 GHz:
- More channels available (25+ non-overlapping)
- 20/40/80/160 MHz channel widths
- Less interference, shorter range
3. Roaming:
802.11r (Fast Roaming):
- Pre-authentication
- Faster handoff (< 50ms)
- Better for VoIP
Configuration:
4. Security:
WPA3-Enterprise (802.1X):
Guest Network Isolation:
5. QoS for Wireless:
Capacity Planning:
Best Practices:
- 20-30% AP overlap for seamless roaming
- Separate SSIDs for different user types
- Regular spectrum analysis
- Monitor client health and performance
- Plan for growth (50% capacity buffer)
Rarity: Common
Difficulty: Medium-Hard
Network Security
6. How do you secure a network infrastructure?
Answer: For a senior role, describe security as layered controls across users, devices, network segments, applications, and the management plane:
1. Access Control Lists (ACLs):
2. Port Security:
3. VPN Configuration:
4. Network Segmentation:
- DMZ for public services
- Separate VLANs for departments
- Firewall between segments
- Least-privilege management access with AAA, MFA where supported, and TACACS+/RADIUS
- Zero Trust principles where practical: identify assets, segment critical flows, and continuously verify access
- Protected management plane with out-of-band access, SSH only, SNMPv3, centralized logging, and regular ACL/firewall reviews
Rarity: Very Common
Difficulty: Hard
Quality of Service (QoS)
7. Explain QoS and how to implement it.
Answer: QoS does not create bandwidth; it protects important traffic during congestion by classifying, marking, queuing, and shaping or policing flows.
QoS Mechanisms:
- Classification: Identify traffic
- Marking: Tag packets (DSCP, CoS)
- Queuing: Prioritize traffic
- Policing/Shaping: Control bandwidth
QoS Configuration:
DSCP Values:
- EF (46): Voice
- AF41 (34): Video
- AF31 (26): Critical data
- BE (0): Best effort
Rarity: Common
Difficulty: Medium-Hard
8. How do you automate network configuration and management?
Answer: Network automation should be treated like software delivery: use source control, templates, peer review, staged rollout, validation, backups, and rollback plans.
Automation Tools:
1. Python with Netmiko:
2. Ansible for Network Automation:
3. NETCONF/RESTCONF APIs:
4. Configuration Backup Automation:
5. Network Validation:
Benefits:
- Reduced configuration time
- Consistent configurations
- Reduced human error
- Easy rollback
- Audit trail
- Scalability
Rarity: Common
Difficulty: Medium-Hard
Advanced Troubleshooting
9. How do you troubleshoot complex network issues?
Answer: Systematic approach to complex problems:
1. Gather Information:
2. Packet Capture:
3. Network Monitoring:
4. Layer-by-Layer Troubleshooting:
- Layer 1: Physical (cables, ports)
- Layer 2: Data Link (VLANs, STP)
- Layer 3: Network (routing, IP)
- Layer 4: Transport (TCP/UDP)
- Layer 7: Application (DNS, HTTP)
5. Common Issues:
Rarity: Very Common
Difficulty: Hard
Conclusion
A strong senior answer combines protocol knowledge with operational judgment. For each topic, prepare one example from your own work: the problem, constraints, design choice, validation steps, and result.
Focus your prep on:
- Advanced routing: OSPF design, BGP policy, route manipulation, and failure behavior
- WAN strategy: MPLS, SD-WAN, cloud connectivity, migration risk, and SLA trade-offs
- Network design: Redundancy, high availability, scaling limits, and change planning
- Wireless: Capacity planning, roaming, security, and client experience
- Security: Segmentation, management-plane protection, VPNs, ACLs, logging, and Zero Trust principles
- QoS: Classification, marking, queuing, shaping, policing, and congestion behavior
- Automation: Source control, templates, validation, staged rollout, rollback, and audit trails
- Troubleshooting: Layered diagnosis, packet analysis, monitoring data, and clear incident communication
Before the interview, map each answer to a real incident, migration, or design decision you can discuss without exaggerating your role.


