Picture a 250-person distributor with 5 branch offices that loses its only network administrator in March. The recruiter sends 9 resumes. Among them, 6 list a CCNA and 2 list CompTIA Network+. The last lists a CCNP and asks for about $134,000, while the budget says $100,000. The hiring manager can’t tell which of the 9 could fix a flapping trunk at 2 a.m., or whether the CCNA dates on the resumes are still valid. This scenario is invented for illustration and doesn’t describe a real company or candidate.
This post covers what certifications prove and how to build a practical test that fits a mid-size company. It draws on Cisco’s certification FAQ, CompTIA’s Network+ page, Juniper’s learning portal, the Bureau of Labor Statistics and a SIOP summary of a 2022 hiring-validity study. I also used 3 third-party pages, flagged where they appear, and every exam vendor here sells the exams it describes. Exam details change often, so confirm them with the vendor before you write a job posting. Ask counsel to review any assessment you plan to use.
TL;DR
- Certifications screen for knowledge, and tests screen for skill. A CCNA or Network+ shows a candidate studied for a proctored exam, and Cisco’s FAQ lists the CCNA at $300. Neither proves the person can diagnose your network. Use certifications to build a shortlist, check the issue date and exam version, and let a practical test make the decision.
- Run a 60-minute troubleshooting lab with a weighted rubric. Score diagnosis, fix, verification, documentation and communication on a 100-point scale you set before you meet candidates. In my invented example a 70-point cutoff separates candidates who scored 80 and 79 from a third at 69. Limit finalists to 4, which keeps reviewer time near 20 hours, or about $1,500 at an invented $75 an hour.
- Weight the whole process rather than a single credential. A SIOP summary of Sackett and colleagues (2022) reports corrected validities of .42 for structured interviews, .40 for job knowledge tests and .33 for work samples. Pair a structured interview with the lab and give certification a small weight. BLS puts administrator median pay at $99,130 and architect pay at $134,050, so match the level to the role.
Define the role before the credential list
Start with the work, because “network engineer” covers jobs that share little beyond the title. Before choosing credentials, compare the role with how an IT staffing agency defines infrastructure and networking talent for the level you actually need. At a 250-person company it may mean racking switches, managing a firewall, renewing a carrier contract and answering help desk escalations. At a larger firm it can mean designing a campus fabric and never touching a cable.
List the 6 to 8 tasks the person will do in the first 90 days, then rank them by how often they happen and how much damage a mistake does. A migration of 5 branch offices to a new carrier calls for routing and VPN work. A monthly firewall rule review calls for security judgment. Those tasks, rather than a certification name, set the practical test later in this post, so keep the list where the whole interview panel can see it and compare each candidate against it.
What a certification proves, and what it doesn’t
- It proves the candidate passed a proctored exam. A third-party CCNA page describes a 120-minute exam at $300 that includes multiple-choice, drag-and-drop and hands-on simulation items, and Cisco’s FAQ confirms the $300 price. Passing shows study discipline and a baseline vocabulary. It doesn’t show how the person behaves with a half-documented network, a carrier that won’t return calls and a manager asking for an estimate of when service will return.
- It carries a date, and the date matters. The same third-party page says CCNA lasts 3 years, and Juniper says its certifications are valid for 3 years. A CCNA earned in 2019 may have lapsed unless the person recertified. Ask for the credential ID or a verification link, check the issue and expiry dates and ask which exam version the person took. CompTIA’s page says the current Network+ exam usually retires about 3 years after launch, with 2027 estimated.
- It says little about your equipment. Vendor exams test vendor platforms, and BLS notes that employers may require certification in the specific products they use. A person with a Juniper credential can learn Cisco commands, and the reverse holds too, but ramp time is a cost to price in. Compare the credential’s platform with your inventory before you decide how much weight it earns in your process. Write the platform names from your inventory into the posting so candidates can self-select before the screen.
- It can’t carry the decision alone. I found no public study showing that a particular networking certification predicts job performance, and the PrepForCerts page says Cisco doesn’t publish pass rates. Treat a credential as a way to shorten the pile, then test the skills of your first-90-day list names. A candidate with no credential and a strong lab result deserves the same interview as a candidate with 3 logos. The lab exists to close that gap.
Credential levels and exam facts at a glance
The table puts the entry and associate credentials side by side, using vendor pages where I could and a third-party page where Cisco’s own pages left gaps. Cisco’s certification FAQ lists prices but no exam durations, so the CCNA duration and the forward-only rule come from a third-party site, and I couldn’t confirm them on a Cisco page. Cells marked not stated mean the page I read didn’t say. Exam prices and versions change, so confirm each figure before you set a requirement in a job posting.
| Credential | Format and length | Price | Other facts |
| Cisco CCST Networking | Not stated | $125 (Cisco FAQ) | Entry level per the FAQ |
| Cisco CCNA 200-301 | 120 minutes; multiple-choice, drag-and-drop and simulations (third-party page) | $300 (Cisco FAQ) | 3-year validity per third-party page; Cisco’s passing score and question count aren’t published per that page |
| CompTIA Network+ N10-009 | Up to 90 questions in 90 minutes; multiple-choice and performance-based | Not stated on the page | Passing score 720 on a 100 to 900 scale; recommended A+ plus 9 to 12 months of experience |
| Juniper JNCIS-ENT JN0-352 | 65 multiple-choice questions in 90 minutes | Not stated | Requires JNCIA-Junos; valid for 3 years; passing score not specified |
A pair of details in the table needs a flag. CompTIA lists a maximum of 90 questions, so the count can vary between candidates. The CCNA row leaves out an unofficial passing estimate of about 825 out of 1,000 that the third-party page offers as a community figure, because Cisco doesn’t publish a pass mark on the pages I read. That page also gives a “100-plus items” estimate with no source. I didn’t read the JNCIA-Junos page, so the table says nothing about it beyond the prerequisite.
Professional and expert credentials
Cisco CCNP. Cisco’s FAQ lists a CCNP core exam at $400 and concentration exams at $300 each, which makes a CCNP at least $700 in exam fees if it’s a core exam plus a single concentration. The PrepForCerts page describes that structure, but the Cisco FAQ doesn’t spell it out, so confirm it. Add the $300 CCNA and the ladder costs $1,000 in exam fees. Ask a CCNP holder which concentration they passed, since the PrepForCerts page names Enterprise, Security and Data Center tracks that cover different work.
Cisco CCIE. The FAQ lists the CCIE lab at $1,600 at a testing facility, $1,900 for a mobile kit and $1,600 for bring-your-own-device. It gives no duration and no separate price for a written exam. PrepForCerts describes an 8-hour hands-on lab, but that page is a practice-test site that doesn’t quote Cisco, and its update date (February 15, 2026) precedes its own check date (September 8, 2026). Adding the CCNA, a CCNP core exam, a single concentration and the lab gives $2,600 in listed exam fees, though Cisco’s FAQ doesn’t say which steps a CCIE candidate must take.
Juniper JNCIE-ENT. Juniper’s page describes a 6-hour hands-on lab in which you build an enterprise network of multiple routers and switches, with objectives in system management, Layer 2 and Layer 3 switching, EVPN and class of service. The wider Juniper enterprise routing and switching certification track places JNCIS-ENT between JNCIA-Junos and JNCIP-ENT. It requires JNCIP-ENT, lists exam code JPR-946 and states a 3-year validity. Lab-based credentials come closest to a practical test, though they test a single vendor’s platform in a lab built by someone else.
Vendor-neutral versus vendor-specific
CompTIA’s Network+ page recommends A+ and 9 to 12 months of hands-on experience as a junior network administrator or support technician, and says the credential prepares people for jobs in technical support, network operation and system administration. That framing puts Network+ at the junior or support end of the ladder. It fits a help desk escalation role or a first network job, and it fits a candidate who has worked on several vendors’ gear. It doesn’t claim to prove skill on your platform.
Vendor-specific credentials fit when your inventory is mostly 1 vendor. BLS says certifications come from vendors and vendor-neutral providers, and that employers may require certification in the products they use. If you run Cisco switches and a Juniper firewall, name both in the posting and rank them. For a mixed estate, compare the candidate’s background against the broader roles covered by VALiNTRY’s information technology staffing solutions and weight the practical test more heavily than the logo, because a person who has configured both platforms will often ramp faster than a person who holds a single high-level credential.
Reading a certification claim on a resume
- Check the status before the interview. Ask for a credential ID or verification link and compare the dates with the resume. I didn’t review each vendor’s verification tool, so I confirmed the method with the vendor. A resume that says “CCNA certified” with no year may describe an exam passed long ago. Ask for the year and for what the person did with the knowledge in their last role, then write the answer in your notes.
- Ask what recertification looked like. A third-party page says a CCNA holder can renew with 30 Continuing Education credits, a retake or a higher-level exam, while Cisco’s FAQ lists 2 pathways but gives no credit counts. The mismatch means you shouldn’t assume a number. Ask the candidate how they renewed and which pathway they used. A person who renewed through a higher exam studied recently, and a person who let it lapse may simply have changed roles.
- Separate “studying for” from “holds.” Resumes mix completed credentials with planned ones. Ask for the exam date and the score report if the person has it, and note that CompTIA publishes a passing score of 720 on a 100 to 900 scale while Cisco’s pass mark isn’t published on the pages I read. A candidate who is honest about a plan to sit a CCNP next quarter has told you something useful about motivation.
- Probe with a scenario, not a definition. Ask the candidate to walk through a recent outage, what they checked first and what they got wrong. This kind of technical screening is also central to how specialized tech recruiters evaluate IT candidates beyond resume keywords. A person who earned a credential and can’t describe a fault they fixed has memorized material, and that’s a signal for the lab. A person without a credential who describes a clear method has given you a reason to keep going.
Practical test formats worth considering
Configuration build. Jobicy’s interview-prep page describes a 3-hour assignment to set up routers and switches, VLANs and trunking, IP addressing and routing in a simulated network, scored on correct configuration, documentation and efficiency. A similar assessment approach appears in VALiNTRY’s description of how tech recruitment firms assess candidate skills through technical tests and scenario-based questions. It fits a role that deploys new sites. The page promotes its own mock interview product and gives no weights or pass thresholds, so I’d treat its tasks as a menu rather than a standard.
Troubleshooting lab. The same page lists a timed 2-hour troubleshooting scenario with steps, a resolution report, root cause analysis and prevention recommendations, and it lists no scoring criteria for that task. I’d shorten it to 60 minutes with 5 planted faults, roughly 12 minutes each, and ask the candidate to talk through each diagnosis. This format tests the skill you’ll use most often, which is finding what broke under time pressure, and it’s the format I score in the rubric below.
Design review or audit. Jobicy also describes a 4-hour security audit simulation with a report and a presentation. For a senior hire I’d cut that to a 45-minute read of a network diagram with a deliberate flaw, such as a single uplink on a core switch, and ask the candidate to list risks and fixes in order. It suits architects and leads more than administrators, and it works without a lab, which makes it easy to run remotely.
A scoring rubric you can copy
Set the rubric before you see a single candidate. The table scores the 60-minute troubleshooting lab on 100 points. Diagnosis gets 35, the fix gets 25, verification gets 15, documentation gets 15 and communication gets 10. The 3 candidates and their scores are invented. The cutoff is 70, and all of the numbers were totaled in code. Notice that candidate B has the best fix score and still misses the cutoff, because B fixed faults without checking the result or writing anything down.
| Criterion | Max | Candidate A | Candidate B | Candidate C |
| Diagnosis | 35 | 30 | 24 | 33 |
| Fix | 25 | 20 | 25 | 15 |
| Verification | 15 | 10 | 5 | 12 |
| Documentation | 15 | 12 | 6 | 14 |
| Communication | 10 | 8 | 9 | 5 |
| Total | 100 | 80 | 69 | 79 |
Candidates A and C clear the cutoff by 10 and 9 points, and they fail in different ways. A fixes more faults while C diagnoses better and communicates poorly. Which of them you’d hire depends on the role. If the person will work alone at night, A’s fix rate matters more. If the person will brief managers after outages, C needs coaching on communication. The rubric doesn’t make the choice for you, but it forces the panel to say why.
Calibrate the rubric before you use it. Score the pilot run together, line by line, and write down why each criterion earned its points. If 2 reviewers differ by more than 10 points on the same recording or the same run, tighten the anchors until they agree within a few points. A rubric that 2 reviewers apply the same way is worth more than a clever lab that nobody can score consistently.
Where practical tests go wrong
The usual failure is length. Jobicy’s tasks run 2 to 4 hours, and a finalist with a job may decline a 4-hour exercise and take another offer. The second failure is a rubric that exists only as a feeling. Jobicy’s rubrics are qualitative and give no scoring scales, and 2 reviewers can watch the same candidate and disagree by 20 points without anchors. Put the weights on paper, score independently, and then compare notes before you talk to each other.
The third failure is a test that measures trivia, such as a command that a candidate would look up in 10 seconds on the job. Let candidates use documentation, because your engineers will. The fourth is a lab that doesn’t resemble your network. If your branches run a single router model and 3 VLANs, test on that pattern. The fifth is unequal treatment, so give every finalist the same faults, the same time and the same help. Ask counsel whether your assessment needs an accommodation process and a record of how you score.
A last failure sits in the debrief. A candidate who solves 3 faults in 20 minutes and then stalls on the fourth has shown a different profile than a candidate who solves all 5 slowly. Record time per fault rather than the total alone, so the panel can see where each person got stuck. Those notes make the debrief concrete and give you a fair basis for follow-up questions on the areas where scores were weak.
Setting up the test environment
- Use a virtual lab you can reset. Juniper’s JNCIE-ENT page lists virtual switch, firewall and router images with version numbers, which shows virtual labs are standard practice for vendor exams. Build or borrow an emulated lab with the same device types you run. Snapshot the working state and the broken state, so every candidate starts from identical conditions and a reviewer can restore the lab in minutes between sessions. Test the reset before the first candidate arrives.
- Write the fault list and an answer key. Plant 5 faults of mixed difficulty, such as a wrong VLAN on a trunk, an incorrect subnet mask, a missing route, a duplex mismatch and a blocked port. For firewall-heavy roles, compare the skills you test with the types of responsibilities handled by cybersecurity staffing candidates so the lab doesn’t ignore access control and network security judgment. For each fault, write the symptom the candidate sees, the root cause and an acceptable fix.
- Pilot the test with a current employee. Ask an engineer or a trusted outside contractor to take the lab cold, and time them. If a person who knows your network can’t finish in 60 minutes, the lab is too long or the faults are too obscure. Fix the lab before candidates see it. Record the pilot’s score and use it to sanity-check your cutoff, not to set the bar at a level that only your best engineer reaches.
- Observe and record. Have the candidate share a screen and talk through each step, with 2 reviewers watching and scoring on separate sheets. Keep the command history if your tool saves it. Candidates who narrate show how they think, and candidates who stay silent give you less to score on communication. Tell everyone in advance that narration is part of the score, so nobody is surprised. Keep each reviewer’s sheet until the decision closes.
Wrapping the lab in a structured interview
Why structure matters. A SIOP summary of the revised personnel-selection research reports mean operational validities of .42 for structured interviews, .40 for job knowledge tests and .33 for work samples. The summary is practitioner-oriented rather than peer-reviewed, and the interview estimates vary widely around the mean. The gap between the interview and the work sample is .09, which is small enough that I wouldn’t rank either above the other.
How to build the interview. Write 6 to 8 questions from your first-90-days list, ask every candidate the same questions in the same order and score each answer on a 1 to 5 scale with written anchors. VALiNTRY’s IT interview questions hub includes role-specific network administrator questions that can help you keep the interview tied to actual troubleshooting work. Include a behavioral question about an outage and a situational question about a failed change window.
How to combine the pieces. Use certification as a screen, the lab as the main skill signal and the interview for judgment and communication. Take notes during each part, score immediately afterward and discuss only after everyone has submitted scores. If the lab and the interview disagree sharply, ask the candidate a follow-up question about the area where they differed. I found no published validity figure for networking labs specifically, so treat the .33 work-sample figure as a general estimate.
Pay and market context
BLS reports a 2025 median of $99,130 for network and computer systems administrators and $134,050 for computer network architects, a gap of $34,920. Its current profile for computer network architects also describes them as network engineers who design and deploy data communication networks. Administrator employment is projected to decline 4 percent from 2025 to 2035, while architect employment is projected to grow 8 percent over the same period.
Read those numbers carefully. The pages I read have no occupation titled network engineer, so the title you’re hiring for may span both groups, and your market may pay above or below a national median. In the invented scenario, a $100,000 budget sits close to the administrator median, while the CCNP holder’s $134,000 request sits at the architect median. That tells you the candidate is pricing a different job than the role you posted, so test for the job you described.
Use the medians as a sanity check rather than a quote. VALiNTRY’s information technology salary hub also separates Network Administrator pay by experience tier and explains how certifications, location and work model affect compensation. Ask your recruiter for 3 recent offers for similar roles, set a range before the first interview and keep it the same for every candidate, so the rubric rather than the salary ask drives the shortlist.
Weighted scoring for finalists
Weights keep a high-credential candidate from winning on logos. The table uses invented weights of 10 for certification, 40 for the practical lab, 35 for the structured interview and 15 for references, and invented 0 to 100 scores for 3 finalists. Candidate Z holds the strongest credential and finishes last, because a lab score of 55 earns only 22 of the 40 lab points. Candidate Y has no standout credential and wins. The weighted totals are 69.5, 78.25 and 63.5, computed in code.
| Component | Weight | Candidate X | Candidate Y | Candidate Z |
| Certification | 10 | 90 | 50 | 100 |
| Practical lab | 40 | 60 | 85 | 55 |
| Structured interview | 35 | 70 | 80 | 60 |
| References | 15 | 80 | 75 | 70 |
| Weighted total | 100 | 69.5 | 78.25 | 63.5 |
The weights are a judgment call, and the ranking can flip. In a sensitivity check using the same invented scores, moving the weights to 30 for certification, 20 for the lab, 35 for the interview and 15 for references gives X 75.5, Z 72.5 and Y 71.25. Y drops from first to last. That’s the reason to fix the weights before you meet candidates, write the reasoning down and keep the numbers out of the room until each reviewer has scored.
What testing costs
- Reviewer time is the main cost. In the invented plan, 2 reviewers spend 2.5 hours each per finalist on setup, observation and scoring, which is 5 reviewer-hours. At an invented $75 an hour that’s $375 per finalist, or $1,500 for 4 finalists. The total comes to 20 reviewer-hours. Compare that with your own estimate of what a mis-hire or a long vacancy costs, and decide whether a smaller panel or a shorter lab fits your budget.
- Candidate time is a cost too. The invented plan asks each finalist for 90 minutes, which is 60 minutes in the lab and 30 minutes of debrief. That’s 6 hours across 4 finalists, and it’s easier to ask for than a 3-hour take-home. If you ask for more, expect drop-off. I found no public data on drop-off rates for networking tests, so watch your own numbers and adjust. Say the time up front.
- Credentials have costs that you may be asked to share. Cisco’s FAQ puts the CCNA at $300, the CCNP core at $400 and each concentration at $300, which is $1,000 along the ladder, and the CCIE lab at $1,600 more, which makes $2,600 before any written fee if a candidate took every step. If you require a credential, decide whether you’ll reimburse the exam and the renewal. A policy written before the offer avoids an awkward negotiation after it.
- Decide what a retest costs. If a candidate fails by 2 points, you need to decide whether to allow a second attempt. Set the rule in advance, apply it to everyone and keep the answer key private. A retest on a different lab form costs another round of reviewer time, so budget for it only for roles where the market is thin. Record each decision so the next search starts with better data.
A hiring process you can run next week
Week 1: Lock the role and the rubric. Write the first-90-days task list, choose the 5 faults and set the weights. Use VALiNTRY’s IT job descriptions hub to compare Network Administrator responsibilities and technologies before you finalize the posting. Draft the posting with the platforms you run and state whether a credential is required or preferred. Decide who sits on the panel and who owns the answer key.
Week 2: Screen the pile. In an invented funnel of 40 applicants, 40 percent list a relevant credential, which gives 16. A 20-minute phone screen using 3 of your structured questions passes 75 percent of those, which leaves 12. Take the best 4 on screen results, including at least 1 without a credential if their answers justify it. Verify each credential’s date and exam version before the interview, and note anything that doesn’t match.
Week 3: Lab, interview and decision. Schedule each finalist for a 60-minute lab and a 30-minute debrief on the same day, with 2 reviewers scoring separately. Run the structured interview in the same block or on the next day. Score independently, total the weighted sheet and meet once to compare. Make the offer within a few days of the last interview, record why you chose the winner and keep the sheets for your next search.
After the offer. Keep the first-90-days list and the rubric, because they double as an onboarding plan. VALiNTRY’s engineer candidate hub likewise treats interview coordination and post-offer onboarding as connected parts of the hiring process. Compare the new hire’s lab scores with their first-quarter performance, and note which parts of the rubric predicted ramp-up. Review the process after 6 months, adjust the weights and update the fault list so it doesn’t leak.
FAQs
Which certification matters most for a network engineer?
It depends on your equipment and the level of the role. For junior and support roles, CompTIA’s Network+ page recommends A+ plus 9 to 12 months of experience, and for Cisco shops the CCNA is the common associate credential, listed at $300 by Cisco. For senior roles, BLS says employers may require certification in the products they use. I found no public study ranking certifications by job performance, so choose by platform and test the skills.
Is a CCNA enough to hire someone as a network engineer?
Only for a role that matches what a CCNA covers, and only if the person can show it in a lab. The third-party page I used describes a 120-minute exam with multiple-choice, drag-and-drop and simulation items, and Cisco doesn’t publish a pass mark on the pages I read. A CCNA suggests baseline knowledge. Use a practical test to learn whether the person can troubleshoot your network, and confirm that the credential is still valid.
How long should a practical test be?
I’d keep it to 60 minutes of lab time plus a 30-minute debrief for finalists. Jobicy’s tasks run 2 to 4 hours, which is long for a candidate who has a job, and its rubrics give no weights. A shorter lab with 5 planted faults, an answer key and a 100-point rubric produces comparable scores. Pilot the lab with a current engineer first, and ask counsel to review your process.
How do I verify a certification?
Ask the candidate for the credential ID or verification link, then confirm the issue date, the expiry date and the exam version with the vendor. I didn’t review each vendor’s verification tool, so I can’t tell you how each tool works. Cisco and Juniper certifications are described as valid for 3 years, so a credential with no recent date deserves a question about renewal. If a candidate can’t produce either, treat the claim as unverified and say so in the notes.
What’s the cost of a Cisco certification path?
Cisco’s FAQ lists the CCNA at $300, the CCNP core exam at $400, each concentration exam at $300 and the CCIE lab at $1,600 at a testing facility. A CCNA plus a CCNP core and a single concentration is $1,000 in exam fees, and adding the lab makes $2,600 before any written exam, which the FAQ doesn’t price. Prices exclude tax and may change, so confirm them with Cisco. Always check the current price page before you budget.
What does CompTIA Network+ cover?
CompTIA’s page lists deploying wired and wireless devices, documentation and change management, virtualization and cloud concepts, monitoring for high availability, securing networks and diagnosing issues with tools. The N10-009 exam has up to 90 questions in 90 minutes, mixes multiple-choice with performance-based items and uses a 720 passing score on a 100 to 900 scale. The page doesn’t list a price or a renewal period. Ask the candidate which of these areas they used in their last role.
What’s the difference between a structured and an unstructured interview?
A structured interview asks every candidate the same job-related questions and scores them against written anchors. An unstructured interview varies by candidate and relies on the interviewer’s impression. A SIOP summary of Sackett and colleagues (2022) reports a corrected validity of .42 for structured interviews and doesn’t report unstructured ones. The estimates vary widely around the mean, so confirm your approach with counsel. Use a rubric with written anchors for each answer, and train the panel to follow it.
Should I pay candidates for a practical test?
Keep the test short enough that the question rarely arises. A 60-minute lab with a 30-minute debrief is a smaller task than a 3-hour take-home, and I found no public guidance on paying finalists for networking tests. If you want a longer exercise, such as a multi-hour build, ask counsel about pay and about who owns the work. Tell candidates in advance what the test covers and how you’ll score it.
