A practical guide for recruiters & hiring managers

Cyber experience is bigger than a job title.

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.

A rough translucent crystal among dark stones, with its inner structure revealed by light.
A candidate a job-title filter could miss 17 years teaching.
A senior security analyst within a year.
Read the career-change story

The short version

Bring these three ideas to your next hiring conversation.

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 titles

Agree on the work before screening.

Define 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 assessment

Keep the evidence after the offer.

Give the employee and manager a shared starting point. Track growth by skill and make changes to job expectations visible.

See the hiring-to-growth example

Use this in your next intake meeting

Four questions for the hiring manager

  1. What three outcomes will this person own?
  2. What must they demonstrate on day one, and what can we teach?
  3. What evidence will we accept from work, labs, competitions, or community contributions?
  4. How will we carry that baseline into onboarding and review it with the employee?

Put the answers in the hiring workbook

Where good candidates get filtered out.

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.

The network advantage

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.

The interview lottery

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.

The credential shortcut

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

Look for skills beyond the job title.

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.

Give recruiters more places to look.

Explore the work behind the profile.

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.

Meet people where they practice.

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.

Count community contributions as experience.

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.

Make previous careers part of the conversation.

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

Go where the work is happening.

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.

Where to find demonstrated skills

Choose an event to see skills to explore and questions to ask.

  • CCDCCollegiate Cyber Defense Competition

    Ask how they kept services running, prioritized incidents, and coordinated a defense while meeting business needs.

    Visit CCDC
  • CPTCCollegiate Penetration Testing Competition

    Explore scoping, technical findings, report writing, and how they explained risk and remediation to a client.

    Visit CPTC
  • DOE CyberForce CompetitionU.S. Department of Energy

    Discuss critical infrastructure defense and the tradeoffs involved in keeping a system secure and usable.

    Visit DOE CyberForce Competition
  • National Cyber LeagueIndividual and team challenges

    Use 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 League
  • US Cyber GamesCyber sport and talent development

    Look at challenge work, practice, and teamwork. Ask how the participant approached an unfamiliar problem and improved between attempts.

    Visit US Cyber Games
  • ICCInternational Cybersecurity Challenge

    Explore technical depth and collaboration across specialties. Follow the regional team and qualifying communities as well as the international competition.

    Visit ICC
  • DEF CON CTFCapture the Flag

    Ask about reverse engineering, vulnerability research, exploitation, and defense. Discuss the tools, decisions, or write-ups the person contributed to their team.

    Visit DEF CON CTF
  • DC3 Digital Forensics ChallengeHistorical competition experience

    Past 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 history

Agree on the work before you screen.

Recruiting 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.

  1. Define the job people will actually do.

    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.

    A usable role scorecard
  2. Give candidates a fair chance to show it.

    Use a short, realistic exercise and consistent prompts. Publish the time commitment, tools, AI policy, and assessment criteria. Offer accessible ways to participate.

    A relevant work sample
  3. Compare evidence before opinions.

    Train interviewers on shared standards. Record observations independently, then discuss disagreements. Treat an untested skill as unknown, not as a failure.

    A decision you can explain
  4. Keep the record after the offer.

    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.

    A shared starting point

Use the workbook with one open roleNext: keep the record after hiring

From candidate to colleague

Keep the skill record after the offer.

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.

Incident triage · Illustrative shared record

Start with what
the work showed.

A fictional alert, a small log bundle, and a clear handoff. The candidate separates facts from assumptions and explains when to escalate.

Job description v1.0 · At hireTriage routine alerts with guidance. Document findings and escalate within the team’s playbook.

Visible to the employee and manager

Investigation
Guided practiceFinds relevant evidence; needs prompts to test alternative explanations.
Communication
Independent on routine workWrites a clear, actionable handoff in the exercise.
Hiring hypothesis
“Strong written communication. Likely to become independent in routine triage with practice.”

Handoff: Preserve the observed evidence, the expectations, and the support promised. Review the hypothesis after onboarding.

Incident triage · Illustrative shared record

Make growth visible and revisit the hiring baseline.

Review several supervised investigations together. Keep the original baseline and add dated evidence of what the employee can now do.

Job description v1.1 · Change recordedAdded routine cloud alerts after training. Employee and manager reviewed the change and agreed on support.

Progress against the current role

Investigation
Guided → Independent on routine workChecks alternative explanations across three reviewed investigations.
Communication
Original strength confirmedHandoffs are consistently usable by the next analyst.
Manager learning
“The communication assessment held up. Investigation developed faster than I expected.”

Employee view: See the old and new expectations, add examples or context, and agree on the next development step.

Incident triage · Illustrative shared record

Show what the next
level asks of them.

Compare repeated work with the published expectations for the next role. Discuss demonstrated strengths and the opportunities still needed to show readiness.

Job description v2.0 · Proposed next levelOwn ambiguous investigations, improve triage guidance, and coach others. Current-role expectations remain visible.

Readiness is specific to each skill

Investigation
Evidence for the next role is emergingOwns ambiguous cases; needs a broader set of examples for review.
Communication
Meets the next role’s expectationCoaches a colleague and improves the team’s handoff guidance.
Shared next step
Agree on a stretch assignment, the support available, and a review date. Carry that record into the next promotion cycle.

No moving goalposts: Date and explain changes. Review past work against the expectations that applied at the time.

Illustrative example. The milestones describe observable work in this role; they are not a universal rating scale.

For hiring managers

Look back at what you got right, what you missed, and which interview signals proved useful on the job.

For employees

See your job description, its changes, your progress against it, and the evidence needed for the next level.

For recruitment and employee development

Connect recruitment and development through relevant evidence, shared definitions, and agreed review points.

Keep your assessments current.

Keep the fundamentals. Refresh the scenarios, tools, and expectations. A hiring exercise should reflect the work you need done now.

Build your hiring plan

Help educators keep pace with the work.

ABET’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

A CTF flag is the start of a conversation.

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.

Assess judgment when AI is part of the work.

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

Use this on your next open role.

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 workbook

Fill it in online, try an example, or download the blank PDF. No signup.

Bring your hiring partner into the conversation

Send a useful starting point.

Forward this guide before the next role intake. Pick one hiring habit to change together, then use the workbook to make the agreement concrete.

A message you can adapt

Before we open the next cyber role, can we use this guide to agree on the work, the evidence we’ll accept, and what we can teach? It covers career changers, labs and competitions, community contributions, consistent assessments, and growth after hiring: https://hireincyber.com/

Need help applying the guide?Optional consulting through Verified Security LLC

Get help with your hiring process.

Bring a role you struggle to fill, an interview process you don’t trust, or a promotion standard nobody can explain. We’ll help you make it concrete.

Discuss your hiring process

Email sales@verifiedsecurityllc.com

What we can work on together

  • Hiring process reviewFind where requirements, screens, and interviews lose useful evidence.
  • Assessment and interviewer trainingBuild role-specific exercises and teach teams to evaluate them consistently.
  • The handoff from recruiting to developmentConnect skill baselines, versioned job descriptions, employee feedback, and promotion criteria.
About Verified Security LLC
The thinking behind the approachSources, context, and limits

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.

  1. Networks influence access to opportunities.

    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.

  2. Consistency is something you design.

    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.

  3. Keeping curriculum current takes institutional support.

    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.