I am exploring creating job descriptions and qualifications centered around entry level infosec roles, like pentesting. I am very conscious of unrealistic job reqs & want to avoid common pitfalls. What are some go-to resources? @shehackspurple @AlyssaM_InfoSec @marigalloway
6
3
1
15
@RachelRecruitin might have some good tips
1
3
First is the diff between entry-level and junior bc entry-level should mean just that, they come in with no exp / no skills. Most teams actually want someone JR who has demonstrated interest with studies or home lab or CTFs as examples. Which are you targeting? (thx TD💜)
1
4
Thank you for the clarification! These discussions are really showing this is a distinction I had not considered (which makes me really glad I asked the original question!). My target currently is junior level.
3
4
So entry level can be up to 3 years of experience.
2
2
I would disagree with this. Anything over a year, IMHO, is no longer entry level. That's now Junior. I'd have a really hard time creating a JD that said 1-3 years experience and call it entry level.
2
1
6
Its what NSA says. Every org is different.
1
2
If it’s common to think entry level is up to three years experience, then no wonder it’s so hard to break into security; they’re up against people with experience. If we want to end the labor shortage in infosec, we have to hire people with NO experience. Call it what you want.

Feb 21, 2022 · 4:02 PM UTC

1
1
It’s been my main frustration in cybersecurity workforce development for the last 6 yrs. I also don’t think that a career pivoter has zero exp. Industry knowledge & biz exp are already an advantage compared to recent grads. But biz has an ageism problem IMHO.
1
5
I pivoted into security in my 40s. It was really hard to get a foot in the door. And I had 14 years of full stack web dev experience. That’s why I pay it forward by hiring first-timers; I’ve been there and it is way harder than it should be.
1
4