Subnetting, VLANs, and Routing — Why These 3 Decide Your First Networking Interview
A founder with 25+ years explains why subnetting, VLANs, and routing are the three pillars every fresher must master before stepping into any networking interview. Common mistakes, how interviewers test depth, and what to practice.
About the Networkers Home Engineering Team
Our content is written by industry practitioners with hands-on experience in enterprise environments. We don't write theory — we share what actually works in production.
The Three Pillars of Every Networking Interview
I have been training network engineers since 2000. I hold CCIE #22239. I have built production-grade products — QuickZTNA and QuickSDWAN — that run in real enterprise and ISP environments. Over 25 years and more than 47,000 students, I have watched thousands of interviews unfold. I have debriefed hiring managers at companies across India. And I can tell you with absolute certainty: every single networking interview for freshers begins and ends with three topics — subnetting, VLANs, and routing.
These are not just three topics among many. They are the three filters that determine whether the interviewer takes you seriously or wraps up in five minutes. If you cannot subnet quickly, the conversation dies right there. If your VLAN understanding is limited to "it segments broadcast domains," you have given a textbook answer that every other candidate also gave. If you cannot explain how a router makes a forwarding decision or why a particular route was selected over another, you have shown that you studied for the exam but never worked on a network.
This is not my opinion. This is a pattern I have observed across hundreds of hiring rounds at companies like Barracuda Networks, Infosys, Cisco, Ruckus Networks, Palo Alto Networks, and Fortinet. The interviewers at these companies are practitioners — they build and manage networks daily. They can tell within the first three questions whether a candidate has real understanding or memorized definitions.
The Five-Minute Rule
Subnetting: The Speed Test
Subnetting is the single most tested topic in networking interviews. Not because it is the most complex — it is not. But because it reveals something that no other question can reveal in under 60 seconds: whether you genuinely understand binary addressing or whether you memorized a subnet chart the night before.
Here is how the test typically works. The interviewer gives you an IP address with a prefix length — say, 172.16.45.130/26 — and asks you to determine the network address, broadcast address, usable host range, and number of usable hosts. They watch how you approach it. Do you start drawing a table? Do you hesitate and ask for paper? Or do you immediately recognize that a /26 means a block size of 64, that the third interesting octet is the fourth octet, that 130 falls in the 128-191 range, and that the network is 172.16.45.128, broadcast is 172.16.45.191, and usable hosts are 129-190? The speed at which you arrive at the answer tells the interviewer whether subnetting is second nature to you or a formula you look up.
The common subnet sizes you must be able to handle instantly: /24 (256 addresses, 254 usable), /25 (128 addresses, 126 usable), /26 (64 addresses, 62 usable), /27 (32 addresses, 30 usable), /28 (16 addresses, 14 usable), /29 (8 addresses, 6 usable), /30 (4 addresses, 2 usable — point-to-point links). You should also be comfortable with supernetting — /19, /20, /21 — because interviewers test whether you can think in both directions.
The Mental Math Approach
- Know the powers of 2 cold: 2, 4, 8, 16, 32, 64, 128, 256. These are your block sizes. If someone says /27, you should instantly think "32 addresses per subnet" without calculating.
- Find the interesting octet: /25 to /30 means the fourth octet is interesting. /17 to /24 means the third octet is interesting. /9 to /16 means the second octet. Identify which octet changes across subnets.
- Divide and locate: Take the value in the interesting octet and determine which block it falls into. For 172.16.45.130 with /26 (block size 64): 0, 64, 128, 192 — the value 130 falls in the 128 block. Network address: 172.16.45.128. Next subnet starts at 192, so broadcast is 191.
- Practice with variety: Do not just practice /24 and /26. Practice /19 (block size of 8192, interesting octet is the third). Practice /13 (block size of 524288, interesting octet is the second). Range matters.
The methodology is simple. The execution requires practice — daily practice. I tell every student the same thing: spend 15 minutes every morning doing subnetting drills. Pick random IP addresses and prefix lengths, calculate the network, broadcast, and range in your head, then verify. Within 2-3 weeks, it becomes reflexive. Within a month, you can subnet any address in under 10 seconds without paper. That is the speed interviewers expect.
What Interviewers Actually Watch
VLANs: Beyond the Definition
"A VLAN is a logical grouping of devices that segments a broadcast domain." Every candidate says this. It is correct. It is also completely insufficient. When an interviewer asks "What is a VLAN?" they are not testing whether you know the definition. They are opening a conversation to probe how deeply you understand Layer 2 segmentation, trunk behavior, and inter-VLAN communication. The definition is the starting line, not the finish line.
Here is the depth you need. You should be able to explain the difference between an access port and a trunk port — not just "an access port carries one VLAN and a trunk port carries multiple," but what happens at the frame level. On a trunk port, how is the VLAN identified? 802.1Q inserts a 4-byte tag into the Ethernet frame header, with a 12-bit VLAN ID field that allows up to 4094 VLANs. On an access port, the frame is untagged because the switch already knows which VLAN it belongs to based on the port assignment. This level of detail shows you understand the mechanism, not just the label.
Native VLAN — The Trap Question
"What is the native VLAN and why does it matter?" This is asked in almost every interview. The native VLAN is the VLAN whose traffic is sent untagged on a trunk link. By default, it is VLAN 1. The security implication: if an attacker sends untagged frames on a trunk port, they land in the native VLAN. This is the basis of VLAN hopping attacks. You should know that best practice is to change the native VLAN to an unused VLAN and explicitly tag all traffic. If you can explain the security reasoning behind native VLAN configuration, you have separated yourself from 90% of candidates.
Inter-VLAN Routing — The Layer 2/Layer 3 Bridge
"Can two VLANs communicate without a router?" The answer is no — by definition. VLANs are separate broadcast domains, and communication between different broadcast domains requires Layer 3 routing. This can be achieved through router-on-a-stick (a single router interface with subinterfaces, each assigned to a VLAN), a Layer 3 switch with SVIs (Switch Virtual Interfaces), or a dedicated router with separate physical interfaces per VLAN. You should be able to explain all three methods and know when each is appropriate. In modern enterprise networks, Layer 3 switches with SVIs are the standard approach for inter-VLAN routing.
Real-World VLAN Design
Interviewers at enterprise companies often ask: "Design a VLAN structure for a small office with four departments." They want to hear you think through it — a data VLAN for each department, a management VLAN for switch management, a voice VLAN if IP phones are deployed, a native VLAN set to something unused, trunk links between switches with only the necessary VLANs allowed (VLAN pruning). If you can walk through this design and explain each decision, you have demonstrated practical understanding that goes far beyond what CCNA exam preparation covers.
I have seen candidates who can recite VLAN theory perfectly but freeze when asked "What commands would you use to configure a trunk port and verify which VLANs are allowed?" If you have never typed switchport mode trunk, switchport trunk allowed vlan, and show interfaces trunk on an actual switch — or at minimum in GNS3/EVE-NG — the interviewer will know. The gap between theory and practice is visible in the first 30 seconds of a configuration question.
The VLAN Depth Test
Routing: The Decision-Making Logic
Routing is where interviewers separate candidates who understand networking from candidates who memorized a study guide. Because routing is fundamentally about decision-making — how does a router decide where to send a packet? — the questions reveal whether you can think through network behavior or only repeat definitions.
Start with the routing table. Every candidate should be able to read a routing table and explain what each entry means. When you see a line like O 10.1.2.0/24 [110/20] via 192.168.1.1, 00:05:32, GigabitEthernet0/1, you should immediately recognize: O means OSPF-learned route, 10.1.2.0/24 is the destination network, 110 is the administrative distance, 20 is the OSPF metric (cost), 192.168.1.1 is the next-hop address, and GigabitEthernet0/1 is the exit interface. If you cannot parse this quickly, you need more lab time.
Understanding the routing table is more important than memorizing configuration commands. Commands can be looked up. The logic of route selection cannot be faked. When a router receives a packet destined for 10.1.2.50, it performs a longest prefix match — the most specific route wins. If the table has both 10.1.0.0/16 and 10.1.2.0/24, the /24 wins because it is more specific. If two routes have the same prefix length but different sources (say, one OSPF and one static), administrative distance determines the winner — static (AD 1) beats OSPF (AD 110). If both routes have the same AD and prefix length, the routing protocol metric breaks the tie.
Static vs Dynamic Routing
You should know when to use each and why. Static routing is appropriate for small networks, default routes, and stub networks. Dynamic routing (OSPF, EIGRP) is necessary when the network is large enough that manually maintaining routes is impractical, or when redundancy and automatic failover are required. The interview question "When would you use static routing over OSPF?" tests whether you understand trade-offs, not just definitions.
OSPF Basics for Freshers
For CCNA-level interviews, you need to understand: OSPF is a link-state protocol that uses Dijkstra's algorithm to compute shortest paths. It forms neighbor adjacencies through hello packets (default 10 seconds on broadcast networks). It uses areas for scalability — Area 0 is the backbone, and all other areas must connect to it. Common adjacency failures: hello/dead timer mismatch, area ID mismatch, authentication mismatch, MTU mismatch, network type mismatch. Being able to list these from memory shows lab experience.
Default Routes
A default route (0.0.0.0/0) is the route of last resort — it matches any destination that does not have a more specific match in the routing table. Interviewers ask: "What happens if a router has no default route and receives a packet for a destination not in its table?" The answer: the packet is dropped, and an ICMP Destination Unreachable message is sent back. Simple question, but candidates who have never seen this behavior in a lab often give vague answers.
Route Selection Logic
The decision hierarchy: (1) Longest prefix match first — always. (2) If prefix length is equal, lowest administrative distance wins. (3) If AD is equal, lowest metric wins. (4) If everything is equal, load balancing may occur (equal-cost multi-path). This hierarchy is the foundation of every routing question. If you understand it deeply, you can reason through any scenario the interviewer throws at you.
One of the most revealing interview questions is: "You have a router with a static route to 10.0.0.0/8 via next-hop A and an OSPF-learned route to 10.0.1.0/24 via next-hop B. A packet arrives for 10.0.1.50. Which path does it take?" Many candidates say the static route because it has a lower AD. The correct answer is next-hop B via OSPF, because the /24 route is more specific than the /8 route. Longest prefix match always wins, regardless of administrative distance. This question alone eliminates a significant percentage of candidates.
The BGP Question for Freshers
What Interviewers Actually Ask
Let me share the types of questions I have seen from actual interview rounds at companies where our students have been placed. These are not hypothetical — they are drawn from real debrief conversations with hiring managers and students over the past several years.
The "Configure This" Questions
"Here is a topology with two switches and a router. Configure VLANs 10 and 20 on the switches, set up trunking between them, and configure inter-VLAN routing on the router using subinterfaces." This tests your hands-on ability. If you have done this in the lab, you can walk through it methodically — create VLANs, assign access ports, configure trunk links, create subinterfaces with dot1Q encapsulation, assign IP addresses. If you have only read about it, you will miss details like enabling the physical interface before creating subinterfaces, or specifying the encapsulation type.
The "Explain Why" Questions
"Why would you use OSPF instead of static routes in a network with 15 routers?" "Why does STP exist and what problem does it solve?" "Why is the default gateway necessary even though the destination might be on the same physical network but a different VLAN?" These questions test conceptual understanding. The interviewer wants to hear reasoning, not definitions. "OSPF provides automatic route convergence if a link fails — with static routes in a 15-router network, I would need to manually update routes on multiple routers every time a topology change occurs, which is error-prone and slow."
The Troubleshooting Scenarios
"A host on VLAN 10 cannot ping a host on VLAN 20. Both can ping their default gateway. Walk me through your troubleshooting." This is where lab experience becomes obvious. A practiced candidate says: "I would check the routing between the two SVIs or subinterfaces — is inter-VLAN routing configured correctly? I would verify with show ip route that routes for both subnets exist. I would check if any ACLs are blocking traffic. I would verify the trunk configuration between switches carries both VLANs using show interfaces trunk." An unpracticed candidate gives a vague answer about "checking connectivity."
The Subnet Design Questions
"You have been given 10.10.0.0/16 and need to create subnets for five departments: Engineering (120 hosts), Sales (50 hosts), HR (25 hosts), Management (10 hosts), and a point-to-point WAN link. Design an efficient subnetting scheme." This tests whether you can apply subnetting to a real-world requirement. You need to allocate the right prefix lengths — /25 for Engineering, /26 for Sales, /27 for HR, /28 for Management, /30 for the WAN link — and you need to assign them without overlap. Candidates who practiced subnetting only with isolated questions often struggle when they need to design a complete addressing plan from scratch.
Gagan, who was placed at Barracuda Networks as a Network Engineer after completing his CCNA, has spoken about this directly — he credits his lab practice for his interview performance. When Barracuda's interviewers asked him configuration and troubleshooting questions, he could answer with the specificity that only comes from having done it repeatedly on real equipment. He did not recite theory. He described what he had actually configured and debugged.
Gopal came from Nagpur with determination to break into networking. He mastered subnetting, VLANs, and routing through daily practice — not just study, but hands-on lab work every single day. When Movate interviewed him, his practical depth made all the difference. He could subnet in his head, configure VLANs and trunking from memory, and explain routing decisions clearly. He was placed at Movate, outperforming candidates with engineering degrees who had the same CCNA but less practical depth.
The pattern continues at every level. Vedant from Chhattisgarh deepened his networking knowledge and was placed at RUCKUS Networks with a 10+ LPA package. Kalyan Kumar from Bidar was placed at NTTDATA — his depth in routing protocols and troubleshooting methodology made the difference. In the security domain, Urvish from Ahmedabad was placed at Tribastion Technologies, while Legasri from Tamil Nadu secured a 6+ LPA placement at Xpheno. Abhishek from Bangalore got placed at Unisys Global Services India. Every one of these placements traces back to the same root: deep mastery of subnetting, VLANs, and routing as the foundation that everything else builds upon.
The Interviewer's Perspective
The Practice Framework
Knowing what to study is not the same as knowing how to practice. Most students understand that subnetting, VLANs, and routing are important. The problem is they study these topics passively — reading notes, watching videos, highlighting text. That approach builds familiarity, not competence. Competence comes from structured, active practice with measurable progress.
Here is the framework I have refined over 25 years of training. It works for students with engineering backgrounds and for students like Gopal, now at Movate, who came from Nagpur. The framework does not depend on your background. It depends on your discipline.
Interview-Ready Practice Framework
Subnetting Drills (15 min/day)
Pick 10 random IP/prefix combinations daily. Calculate network address, broadcast, usable range, and number of hosts — in your head. Verify with a calculator. Track your speed. Target: under 10 seconds per question within 3 weeks.
VLAN Lab Sessions (1 hour, 3x/week)
Configure VLANs, assign access ports, set up trunk links, change the native VLAN, implement inter-VLAN routing using both router-on-a-stick and Layer 3 SVIs. Break the configuration deliberately — remove a trunk allowed VLAN, misconfigure the native VLAN — and diagnose the symptoms.
Routing Labs (1 hour, 3x/week)
Build multi-router topologies. Configure static routes, then replace them with OSPF. Introduce link failures and observe convergence. Read the routing table after every change and explain to yourself why each route is there. Practice default route injection and verify reachability.
Integrated Scenarios (2 hours/week)
Combine all three: design a network with multiple VLANs, proper subnetting, inter-VLAN routing via OSPF, and verify end-to-end connectivity. Then break something and fix it using only show and debug commands. This simulates interview lab exercises.
Mock Interview Questions (30 min, 2x/week)
Have a peer or mentor ask you interview questions while you answer aloud. Practice explaining your troubleshooting approach verbally. If you cannot explain it clearly out loud, you do not understand it deeply enough.
Common Practice Mistakes to Avoid
- 1.Watching labs instead of doing labs: Watching someone configure OSPF on YouTube is not practice. You must type the commands yourself, see the output, make mistakes, and fix them. Passive consumption creates false confidence.
- 2.Only practicing what works: Most students configure a topology, see it work, and move on. Real learning happens when you break it. Misconfigure a trunk, mismatch OSPF timers, use the wrong subnet mask — then diagnose and fix without erasing and starting over.
- 3.Skipping subnetting drills because "I already know it": Knowing how to subnet and being able to subnet quickly under pressure are two different things. Interview anxiety slows your thinking. The only counter is practice deep enough that the skill is automatic.
- 4.Ignoring verbal practice: You may understand routing perfectly in your head but struggle to explain it clearly when an interviewer asks. Practice explaining concepts aloud. Record yourself. Listen back. Clear verbal articulation is a skill that requires separate practice.
This framework requires roughly 8-10 hours per week of focused practice. That is not casual studying — it is deliberate, structured work. But within 6-8 weeks of following it consistently, the difference in interview readiness is dramatic. Students who follow this approach consistently clear technical rounds within their first few interviews. Students who skip the practice and rely on theory struggle for months.
Our CCNA course in Bangalore builds this framework directly into the curriculum. Students practice on real Cisco equipment — not just simulations — and the lab component is structured around the exact progression described above: fundamentals first, then integration, then troubleshooting under pressure. The online CCNA course provides the same structured approach with remote lab access.
The Lab Hours Benchmark
Watch: Placement Stories & Technical Tutorials
Watch students who mastered these fundamentals and see how subnetting, VLANs, and routing are taught and practiced at Networkers Home:
Frequently Asked Questions
How to prepare subnetting for networking interviews?
Practice until you can subnet in your head within seconds. Interviewers often give a /26 or /19 and expect you to calculate the network address, broadcast, and usable range without paper. Speed and accuracy matter more than memorizing formulas.
What VLAN questions are asked in networking interviews?
Common questions: What is a VLAN trunk? Difference between access and trunk port? What is native VLAN? How does inter-VLAN routing work? Can two VLANs communicate without a router? Interviewers test whether you understand the concept or just memorized definitions.
How deep should routing knowledge be for freshers?
For CCNA-level interviews: understand static routing, OSPF single-area configuration, default routes, and basic route selection. You don't need BGP depth as a fresher, but understanding why routing protocols exist and how they make decisions is essential.
What are the most common networking interview mistakes?
The top three: (1) Not being able to subnet quickly, (2) Confusing Layer 2 and Layer 3 concepts, (3) Giving textbook answers without practical context. Interviewers want to hear 'I configured this in the lab' not 'I read this in the book.'
Related Training Programs
If you want structured guidance on mastering subnetting, VLANs, and routing with real equipment and placement support:
CCNA Course in Bangalore
Hands-on CCNA training with real Cisco equipment, structured lab sessions covering subnetting, VLANs, routing, and interview preparation.
CCNA Online Video Course
Remote-access labs with the same curriculum, covering all three pillars with practical exercises and troubleshooting scenarios.
Everything in this article is free and actionable. You can build your subnetting speed, deepen your VLAN understanding, and develop routing intuition using the practice framework above — whether or not you train with us. The methodology works regardless of where you study. If you do want a structured environment with real Cisco equipment, daily lab access, and placement preparation built around these exact fundamentals, explore the CCNA course details and make your own informed decision.
Subnetting, VLANs, and routing are not just interview topics. They are the foundation of every network you will ever build, manage, or troubleshoot. Master them once, and they serve you for your entire career.
— Vikas Swami
