A working plan, from opening the role to growing in it

Build a better cyber hiring plan.

For recruiters, talent acquisition, HR, and managers hiring cyber talent. Work through these questions with someone who understands the job. Leave with a role brief, an interview plan, and promises you can keep after the offer.

Printing opens a PDF of the answers currently on this page. The download is always blank: six US Letter pages, with fillable fields and room to write by hand.

Answers stay in this tab. We do not submit or save them. Save your completed PDF before leaving or refreshing.

Start with the work. Answer what you know; record an owner for anything still to confirm. The first four sections build your hiring plan. The last two set expectations for life on the team.

1. Build the hiring plan · Page 1

01Define the work

Agree on the problem this hire will solve before choosing credentials or writing filters.

A title is a starting point. Adjust the level after agreeing on scope.

Name who can explain the work and who can approve this brief.

Choose the expectation at hire, with the support you can actually provide.

Name the work that is missing or the problem the team needs to solve.

Use an action, a work product, and a way to recognize useful work.

Clarify responsibilities that belong to another team and when to escalate.

1. Build the hiring plan · Page 2

02Set realistic entry requirements

Separate the skills needed on arrival from what the team will teach.

Describe two or three observable abilities, with the expected level of help.

Connect each learning need to a person, time, tools, or practice opportunity.

Where will we accept evidence of those abilities?

Select every route you will consider. Ask what the person actually contributed.

Confirm an actual requirement before putting it into an automatic rejection rule.

Record the obligation or essential work it supports, and any accepted equivalent.

Pay range, location, hours, on-call or travel, and any confirmed access requirements.

1. Build the hiring plan · Page 3

03Design the screen and work sample

Give the recruiter a useful question and the technical reviewer a consistent way to inspect the work.

Use a plain-language prompt. State what to pass to the technical reviewer.

Use fictional or sanitized material. Name the input and the work product.

Choose a primary format; arrange an equivalent option when needed.

Include preparation and every stage, not just the interview itself.

Give everyone the same policy and comparable access.

Describe observable signs of readiness for this level, including sound escalation.

1. Build the hiring plan · Page 4

04Agree on decisions and candidate care

Make the process predictable for candidates and keep reviewers focused on the same evidence.

Probe the person’s choices, uncertainty, contribution, and response to a change.

Separate missing evidence from demonstrated gaps. Explain how a candidate can clarify.

Recruiting coordinates; a person qualified in the work judges technical evidence.

Name the contact, expected sequence, and when someone will update them.

Include an accommodation contact and alternatives to public portfolios or event access.

Choose a process before meeting candidates.

2. Make onboarding promises · Page 5

05Commit to support after the offer

Agree now on the support you will describe to candidates and deliver to the new employee.

Name the manager, buddy or mentor, and backup contact.

Include access, a safe practice environment, supervised work, and initial priorities.

Specify the resource, owner, and when it is available. Leave unapproved promises open.

Keep relevant skill evidence, agreed support, and the dated job description. Limit access.

Choose a starting schedule and adapt it to the role.

Look at work, ask for the employee’s context, and fix unmet commitments.

3. Keep expectations visible · Page 6

06Plan growth and job-description changes

Give employees a way to see, discuss, and prepare for changes in the role.

Name an accessible location, version/date convention, and document owner.

Record the reason, effective date, workload and level implications, and learning support.

Name the work, evidence, reviewer, and a fair opportunity to demonstrate it.

Provide a review conversation and a place for corrections and unresolved differences.

Compare hiring expectations with actual work and the support delivered.

Use open questions to assign follow-up work, not to invent commitments.

Example role levels are adapted from the Security Titles framework. The plans and teaching grades are written by Hire-In-Cyber. This workbook helps people agree on a process; it does not automatically score or rank candidates.