Technical screening questions
Ask for one example per question and listen for specifics.
- How do you troubleshoot a site that lost connectivity? A good answer: Layered approach: physical, link, routing and then application.
- Explain how BGP and OSPF differ. A good answer: Exterior versus interior routing and typical use.
- How do you plan a network change? A good answer: Change window, rollback and testing.
- How do you design a VPN for a remote site? A good answer: Tunnel type, authentication and failover.
- Which certifications and equipment have you worked with? A good answer: Named platforms and certification levels.
Quick screening questions
Use these when you have only a few minutes.
- Largest network you supported?
- Walk me through troubleshooting packet loss.
- Which certifications do you hold?
What separates the levels
Match the level to the requirement before you submit.
- Junior: monitors and supports with runbooks.
- Mid: configures and troubleshoots independently.
- Senior: designs networks and leads migrations.
Red flags
Any of these is a reason to probe further.
- Only help-desk network support.
- Cannot describe a routing protocol.
- No change-management practice.
Tools you should hear mentioned
A network engineer with real experience usually names several of these without prompting.
- Cisco or Juniper
- Palo Alto or Fortinet firewalls
- BGP and OSPF
- VLANs and VPNs
- Network monitoring tools
- Wireshark
Run the call well
Ask for the last project first, then dig into the second or third question. Take notes on versions, team size and outcomes, and record them with the submission so the vendor’s later technical interview does not surprise you.
Frequently asked questions
How long should a network engineer screening call take?
Fifteen to twenty minutes is enough to cover the project, three technical questions and availability, rate and work authorization.
Do recruiters need to know the technology?
Working vocabulary is enough. Use the sourcing guide for the role and listen for specifics instead of judging technical depth yourself.