Aug 23, 2026 · 45 min · 8 segments
Why do some cybersecurity job descriptions ask for everything? In this episode, we break down how cybersecurity JDs are created and why some roles end up with unrealistic qualifications, excessive…
I think last three weeks and basically the first thing I looked at was basically the company and the requirements straight up and I saw that I almost checked all the boxes and that led me to apply.
nice
so was it like what role like was the job description about is it like for a specific role was it more for like he's just the general cyber security analyst
security operations okay yeah so basically an l2 well l2 yeah but yeah so
So, for you, it was the last three weeks, you saw a job description for security operations, there's a so-called distress level 2, and you felt like you checked most of the boxes.
Okay, that's nice.
Chinaza, what was the last time you saw a job description? How did it make you
feel? I'm going to respond to this question in two ways.
So I saw last time, a month ago, first job description I saw was for a SOC analyst, L2 as well.
Well, I checked almost all the boxes, but this brings me to the next response, which was when I checked for a security engineering job description, which is an area in cybersecurity I'm trying to devote to.
And I checked like three out of 10.
But yeah, that made, that didn't make me feel bad at all.
It just made me feel like I had so much to learn and so much midnight candles to burn to get myself to a certain level of proficiency so i could apply for those roles so that's about it yeah
fair enough i mean like because the thing is i was going to like because i was just thinking about something as well you guys were talking which is do we even feel generally that these job descriptions are a proper representation of what you actually get to do in the role.
Because like, I've seen people talk about how like, you know, like HRs or people that are recruiting, probably people that put out the job descriptions probably didn't even know anything about the role.
And then they just copy paste the thing where it's like, okay, you need like a junior level, you know, maybe so-and-so for instance, or whatever it is.
And then there's a general popular job description and you can just control, control A, control C, control V.
And you have a JT.
And you have a JD, right? So based on your experiences, do you think that it's kind of like a proper representation of what you get to do in the role itself?
I think last three weeks and basically the first thing I looked at was basically the company and the requirements straight up and I saw that I almost checked all the boxes and that led me to apply.
nice
so was it like what role like was the job description about is it like for a specific role was it more for like he's just the general cyber security analyst
security operations okay yeah so basically an l2 well l2 yeah but yeah so
So, for you, it was the last three weeks, you saw a job description for security operations, there's a so-called distress level 2, and you felt like you checked most of the boxes.
Okay, that's nice.
Chinaza, what was the last time you saw a job description? How did it make you
feel? I'm going to respond to this question in two ways.
So I saw last time, a month ago, first job description I saw was for a SOC analyst, L2 as well.
Well, I checked almost all the boxes, but this brings me to the next response, which was when I checked for a security engineering job description, which is an area in cybersecurity I'm trying to devote to.
And I checked like three out of 10.
But yeah, that made, that didn't make me feel bad at all.
It just made me feel like I had so much to learn and so much midnight candles to burn to get myself to a certain level of proficiency so i could apply for those roles so that's about it yeah
fair enough i mean like because the thing is i was going to like because i was just thinking about something as well you guys were talking which is do we even feel generally that these job descriptions are a proper representation of what you actually get to do in the role.
Because like, I've seen people talk about how like, you know, like HRs or people that are recruiting, probably people that put out the job descriptions probably didn't even know anything about the role.
And then they just copy paste the thing where it's like, okay, you need like a junior level, you know, maybe so-and-so for instance, or whatever it is.
And then there's a general popular job description and you can just control, control A, control C, control V.
And you have a JT.
And you have a JD, right? So based on your experiences, do you think that it's kind of like a proper representation of what you get to do in the role itself?
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.
