Special Coverage Series

Network Computing

Special Coverage Series

Commentary


4 Must-Ask Interview Questions for Network Engineers

If you’re looking to hire a network engineer (or be hired as one), here are four job interview questions that I’ve asked, and three you shouldn’t bother with. These questions will help you figure out what a candidate does and doesn’t know.

I enjoy being on an interview panel for networking candidates. My job is usually to be the technical heavy. I need to determine what the candidate knows, what the candidate doesn't know, and what I think he or she could figure out. I rely on four questions to get at this information. But first, here are some things I don't spend time on.

Trivia. I rarely get into a trivia competition with a candidate because it proves very little. If candidates recently passed a certification exam, they might have a head full of arcane networking facts, but what's really important is what they can do with their knowledge. A trivia contest won't tell you that.

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

Tell me about your ideal job. I don't care about this one, either. The ideal job doesn't exist, so if candidates want to work in the tree where the elves make cookies, they're going to be disappointed. Besides, candidates might feel pressured to answer with words they think you want to hear, which makes it a pointless exercise.

Are you a team player? This is a silly question. Of course they'll say yes, no matter the reality. I honestly don't care if they work by themselves as long as they follow standard procedure and do what's been asked of them.

And now, here are four questions that I have asked.

1. Can you draw a diagram on the whiteboard of a network you've worked on, and explain it to me? This might be the only question I ask in the interview, depending on how it goes. For the right candidate, this will tell me everything I need to know.

How did the diagram start? From the center out? Or from the edge in? Or did it seem a bit random? This tells me how clear the network was in the candidate's mind, and the way that he or she thought about it.

How does the diagram look? Is it a horrible disaster of overlapping shapes and lines, or is it easy to read? I don't mind if candidates have to re-draw. That just tells me they care about what their diagram is communicating, which is a good thing.

How well does the candidate explain the diagram? This is where it gets interesting, because as the explanation moves forward, you can probe the candidate to find out what they really know. Oh, so that's the core switch. Was there one core switch or two? Or more? Did you run a first-hop redundancy protocol on those switches? Why or why not? What routing protocol did you run in your core? OSPF? Oh, then tell me about how your areas were laid out. Oh, so that's the edge of your wide area network, I see. What routing protocols did your carrier support? You say you ran VoIP across your network. Tell me how you handled congestion on slow links to preserve call quality.

You say your network design was meant to help with PCI compliance. Fair enough. Pretend I'm an auditor and walk me through the various subnets, firewalls and security policies that are in place related to PCI.

The diagram lets you explore the candidate's knowledge. It's a fair question even for entry- and mid-level candidates. If an entry-level candidate draws one switch and then shrugs his shoulders apologetically, you can find out how well he knows that switch. Did you provision ports? What did the standard switch port template look like? Why was command X used? What did you do to stop CDP advertisements from leaving unused ports? And so on.

Next: More Questions

 1 | 2  | Next Page »


Related Reading



Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Network Computing further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | Please read our commenting policy.
 

Editor's Choice

Research: 2014 State of Server Technology

Research: 2014 State of Server Technology

Buying power and influence are rapidly shifting to service providers. Where does that leave enterprise IT? Not at the cutting edge, thatís for sure: Only 19% are increasing both the number and capability of servers, budgets are level or down for 60% and just 12% are using new micro technology.
Get full survey results now! »

Vendor Turf Wars

Vendor Turf Wars

The enterprise tech market used to be an orderly place, where vendors had clearly defined markets. No more. Driven both by increasing complexity and Wall Street demands for growth, big vendors are duking it out for primacy -- and refusing to work together for IT's benefit. Must we now pick a side, or is neutrality an option?
Get the Digital Issue »

WEBCAST: Software Defined Networking (SDN) First Steps

WEBCAST: Software Defined Networking (SDN) First Steps


Software defined networking encompasses several emerging technologies that bring programmable interfaces to data center networks and promise to make networks more observable and automated, as well as better suited to the specific needs of large virtualized data centers. Attend this webcast to learn the overall concept of SDN and its benefits, describe the different conceptual approaches to SDN, and examine the various technologies, both proprietary and open source, that are emerging.
Register Today »

Related Content

From Our Sponsor

How Data Center Infrastructure Management Software Improves Planning and Cuts Operational Cost

How Data Center Infrastructure Management Software Improves Planning and Cuts Operational Cost

Business executives are challenging their IT staffs to convert data centers from cost centers into producers of business value. Data centers can make a significant impact to the bottom line by enabling the business to respond more quickly to market demands. This paper demonstrates, through a series of examples, how data center infrastructure management software tools can simplify operational processes, cut costs, and speed up information delivery.

Impact of Hot and Cold Aisle Containment on Data Center Temperature and Efficiency

Impact of Hot and Cold Aisle Containment on Data Center Temperature and Efficiency

Both hot-air and cold-air containment can improve the predictability and efficiency of traditional data center cooling systems. While both approaches minimize the mixing of hot and cold air, there are practical differences in implementation and operation that have significant consequences on work environment conditions, PUE, and economizer mode hours. The choice of hot-aisle containment over cold-aisle containment can save 43% in annual cooling system energy cost, corresponding to a 15% reduction in annualized PUE. This paper examines both methodologies and highlights the reasons why hot-aisle containment emerges as the preferred best practice for new data centers.

Monitoring Physical Threats in the Data Center

Monitoring Physical Threats in the Data Center

Traditional methodologies for monitoring the data center environment are no longer sufficient. With technologies such as blade servers driving up cooling demands and regulations such as Sarbanes-Oxley driving up data security requirements, the physical environment in the data center must be watched more closely. While well understood protocols exist for monitoring physical devices such as UPS systems, computer room air conditioners, and fire suppression systems, there is a class of distributed monitoring points that is often ignored. This paper describes this class of threats, suggests approaches to deploying monitoring devices, and provides best practices in leveraging the collected data to reduce downtime.

Cooling Strategies for Ultra-High Density Racks and Blade Servers

Cooling Strategies for Ultra-High Density Racks and Blade Servers

Rack power of 10 kW per rack or more can result from the deployment of high density information technology equipment such as blade servers. This creates difficult cooling challenges in a data center environment where the industry average rack power consumption is under 2 kW. Five strategies for deploying ultra-high power racks are described, covering practical solutions for both new and existing data centers.

Power and Cooling Capacity Management for Data Centers

Power and Cooling Capacity Management for Data Centers

High density IT equipment stresses the power density capability of modern data centers. Installation and unmanaged proliferation of this equipment can lead to unexpected problems with power and cooling infrastructure including overheating, overloads, and loss of redundancy. The ability to measure and predict power and cooling capability at the rack enclosure level is required to ensure predictable performance and optimize use of the physical infrastructure resource. This paper describes the principles for achieving power and cooling capacity management.