Broaden what counts as experience.
A candidate may have done the work in a lab, a competition, a previous career, or a community project. Ask them to explain their contribution.
Find evidence beyond job titlesA practical guide for recruiters & hiring managers
Find skills in labs, competitions, community work, and previous careers. Agree on what the job needs, then use that evidence from the first screen to promotion.
Free to read, use, and share. No signup.
From
Verified Security LLC.

Bring these three ideas to your next hiring conversation.
A candidate may have done the work in a lab, a competition, a previous career, or a community project. Ask them to explain their contribution.
Find evidence beyond job titlesDefine what someone must demonstrate on day one and what the team can teach. Use consistent questions and a short, relevant work sample.
Build a consistent assessmentGive the employee and manager a shared starting point. Track growth by skill and make changes to job expectations visible.
See the hiring-to-growth exampleUse this in your next intake meeting
Good intentions don’t make a process consistent. When every interviewer brings a different test, candidates are trying to pass a person instead of demonstrate a skill.
A referral can open a door. It shouldn’t set a lower bar, or make an unfamiliar candidate invisible. Give both a fair opportunity to show what they can do.
Trivia, pet questions, and “I’d have a beer with them” measure different things. Agree on the work and what a good response looks like before anyone interviews.
A degree or certification can show a foundation. It cannot, by itself, show how someone handles an unfamiliar problem in your environment today.
Career changers & nontraditional paths
Some candidates have been building, breaking, investigating, and learning for years outside their paid work. A résumé’s employment and education sections may tell you very little about that practice.
Hack The Box and TryHackMe activity, capture-the-flag (CTF) write-ups, home labs, and personal projects can make otherwise invisible practice visible. Ask candidates to walk through a problem, explain their choices, and respond to a change in the scenario.
Cyber competitions make room for people to demonstrate skills before they have the matching job title. Send recruiters to events and competition communities where they can discuss that work with the people doing it.
Volunteering, speaking, teaching workshops, and running conference events are valid sources of experience. A talk can show how someone explains technical ideas; coordinating an event can show planning, teamwork, and follow-through. Ask what they owned, what they produced, and how they handled problems. Use that evidence to assess the skills the job needs.
Technical credentials such as Zero-Point Security’s Red Team Operator certification (CRTO), or work from specialist training such as MalDev Academy, can open a useful discussion about applied skills. Connect the evidence to the role you are filling.
Ask for examples of explaining complex issues, handling competing priorities, documenting decisions, and learning unfamiliar systems. Let candidates draw on their whole working life, then assess how those strengths translate to this job.
Use the same role-specific standards for work, labs, and community contributions. Ask about the person’s contribution beyond the event name, score, or badge. Offer an equivalent work sample to candidates without event access, public profiles, or paid training.
A better place to recruit
Send cyber recruiters to competitions instead of another college job fair. Spend that recruiting day meeting people who are defending systems, investigating evidence, and explaining what they found.
Bring a hiring manager who understands the work. Arrange access with the organizers through recruiting sessions, volunteering, or sponsorship, and save conversations for appropriate breaks and debriefs. Online events and regional competitions count, too.
Choose an event to see skills to explore and questions to ask.
Ask how they kept services running, prioritized incidents, and coordinated a defense while meeting business needs.
Visit CCDCExplore scoping, technical findings, report writing, and how they explained risk and remediation to a client.
Visit CPTCDiscuss critical infrastructure defense and the tradeoffs involved in keeping a system secure and usable.
Visit DOE CyberForce CompetitionUse a participant’s Scouting Report to start a conversation about specific skills. Ask them to explain a solve and what they learned from a challenge they could not finish.
Visit National Cyber LeagueLook at challenge work, practice, and teamwork. Ask how the participant approached an unfamiliar problem and improved between attempts.
Visit US Cyber GamesExplore technical depth and collaboration across specialties. Follow the regional team and qualifying communities as well as the international competition.
Visit ICCAsk about reverse engineering, vulnerability research, exploitation, and defense. Discuss the tools, decisions, or write-ups the person contributed to their team.
Visit DEF CON CTFPast participation can still reveal investigative skill. Ask how they recovered and interpreted evidence, documented their method, and supported their conclusions. This is a past challenge, not a current event listing.
Visit DC3 Digital Forensics Challenge historyRecruiting and the hiring manager need a shared definition of good work. Use these four steps to turn that agreement into a process candidates can understand.
Name the decisions, tasks, and outcomes. Separate what someone must demonstrate on day one from what you can teach. Challenge requirements that don’t earn their place.
Use a short, realistic exercise and consistent prompts. Publish the time commitment, tools, AI policy, and assessment criteria. Offer accessible ways to participate.
Train interviewers on shared standards. Record observations independently, then discuss disagreements. Treat an untested skill as unknown, not as a failure.
Connect recruiting HR, the hiring manager, and employee development. Carry relevant skill evidence into onboarding, with the employee able to see the baseline and help shape the next steps.
Use the workbook with one open roleNext: keep the record after hiring
From candidate to colleague
Recruiting learns about a person. Employee development should be able to build on that learning. Keep the hiring baseline, show growth by skill, and make changing job expectations visible.
A fictional alert, a small log bundle, and a clear handoff. The candidate separates facts from assumptions and explains when to escalate.
Review several supervised investigations together. Keep the original baseline and add dated evidence of what the employee can now do.
Compare repeated work with the published expectations for the next role. Discuss demonstrated strengths and the opportunities still needed to show readiness.
Illustrative example. The milestones describe observable work in this role; they are not a universal rating scale.
Look back at what you got right, what you missed, and which interview signals proved useful on the job.
See your job description, its changes, your progress against it, and the evidence needed for the next level.
Connect recruitment and development through relevant evidence, shared definitions, and agreed review points.
Keep the fundamentals. Refresh the scenarios, tools, and expectations. A hiring exercise should reflect the work you need done now.
Build your hiring planABET’s computing criteria call for current content and continuous improvement. Making that happen takes institutional support. Approval delays, university politics, gaps in instructors’ current practical experience, and resistance to change can all slow curriculum updates. Faculty may also worry that a change could jeopardize accreditation, especially when older interpretations of the rules persist.
Give instructors the time, training, and practitioner partnerships to keep labs aligned with today’s tactics, techniques, and tools. For hiring, assess the work a candidate can demonstrate today and how they continue learning, wherever they started. Source
Capture-the-flag challenges can reveal useful skills. Ask how the person investigated, what they tried, why it worked, and how they would communicate the finding. A leaderboard position alone doesn’t tell the whole story.
Choose the exercise for the job: an alert investigation, a cloud access review, a scoped offensive lab, or a risk recommendation. Not every cyber role is a hacking contest.
If AI is part of the job, define how candidates may use it and give them equivalent access. Ask what they accepted, what they rejected, and how they verified the result.
Use fictional data and a live follow-up with a changed assumption. Assess reasoning, verification, and ownership of the answer. State any unaided portion in advance.
Put it to work
Start with one role, one realistic task, and a clear definition of good work. Carry the skill evidence and agreed support into onboarding and development reviews.
Open the cyber hiring workbookFill it in online, try an example, or download the blank PDF. No signup.
We distinguish research findings from our recommendations. These sources inform the approach; they do not validate a proprietary Hire-In-Cyber assessment or guarantee a hiring outcome.
MIT News: The power of weak ties in gaining new employment (2022). The LinkedIn experiment studied how connections affect job mobility. It measured job mobility through connections, not the share of tech jobs filled through referrals or the competence of the people hired. It is not a cybersecurity-specific hiring study.
U.S. Office of Personnel Management: Structured interviews. OPM describes predetermined questions and shared rating standards. We recommend applying that structure to role-relevant cyber interviews and reviewing the process over time.
ABET: Computing accreditation criteria, 2025–2026. The criteria call for up-to-date computing topics and continuous improvement, while leaving room for institutions to choose courses. They also call for faculty development and institutional support.
Our concern is the gap between those expectations and day-to-day practice. Approval processes, university politics, limited time to refresh practical skills, and fear of jeopardizing accreditation can hinder updates. Older interpretations of the rules can persist even when the standards support change. Help instructors understand their options and give them the resources to act on them.
The examples and workbook are starting points to adapt and pilot for a specific role. Check whether the process measures the work, provides equitable access, and leads to useful decisions.