# Security talent conclusion, from the candidates viewpoint

URL: https://securitytable.ai/security-talent-conclusion-from-the-candidates-viewpoint/
Published: 2023-02-14
Duration: 2446 seconds
Season: Not supplied
Episode: Not supplied
Hosts: Chris Romeo, Izar Tarandach, Matt Coles

## Show notes and chapters

The gang continues our discussion and debate around the security talent shortage. We consider the issue from the candidate's viewpoint this time, thinking about all the different things candidates have to deal with in being hired, from years of experience, certification, and depth of the interview process. We try to draw some actionable conclusions for hiring managers because, without action, we are just part of the problem.

Follow AI Security Table:

➜ Home: [https://securitytable.ai/](https://securitytable.ai/)

➜ X: [https://x.com/AISecurityTable](https://x.com/AISecurityTable)

➜ LinkedIn: [https://www.linkedin.com/company/ai-security-table/](https://www.linkedin.com/company/ai-security-table/)

➜ YouTube: [https://www.youtube.com/@AISecurityTable](https://www.youtube.com/@AISecurityTable)

## Transcript

**Chris Romeo (0:00)**: Hey folks, welcome to another episode of The Security Table. This is Chris Romeo, and I'm joined by Tanya and Isar and Matt. And we are going to continue a conversation that we started in the previous episode. So we got into this idea of, is there a talent shortage in cybersecurity? Started unpacking who are the culprits and why there could be. A talent shortage. But one of the things that we're gonna do with this episode is we're gonna flip it around and we're gonna focus from the perspective of the person who's trying to get hired, the new graduate, the CS student that has maybe a minor in cybersecurity or somebody who's coming out of a coding bootcamp or, you know, there's cybersecurity bootcamps now too. And so I wanna think about this from their perspective. What are they experiencing? When they look into this world of cybersecurity. So Matt, let's go ahead and start with you here. What are kind of your thoughts about what is the, what's the perception for this person who's brand new and is trying to get into our industry?

**Matt Coles (1:11)**: Well, yeah, you would have to pick on me, wouldn't you? So I think it's a daunting task. So first off, let's— we can talk about a couple areas, but start with where do they even know to get started? Right? So if they're in school, you know, they may be learning word of mouth, you know, people they've been in classes with or the professors, you know, school sometimes has job boards and things like that. But otherwise, where are they going? They're going to LinkedIn, they're going to Indeed, they're going to, uh, Monster. I don't think Monster's around anymore, but you know, where do you, where do you go, right, to, to find these jobs? Um, or they have companies in mind, uh, either ones they've interned for or ones that they are just familiar with. Of course, that's the, you know, the big FAANG corporations, um, that, that everyone wants to get into, it seems. So the first problem is just finding the jobs, right? And what, what can they search on, right? How do you find the ones you're looking for? I want to remind you, you know, viewers of this podcast, of this episode in particular, in the last one we did talk about, we brought up this concept that there's, there's a lot of different types of roles in the security space. And so if you're new to the security space, how do you know what to look for? If you just do a keyword search for security, you're going to find everything from a security guard all the way up to a CISO, probably, right? And that may also exclude a whole bunch of, or may get a lot of garbage in between, right? Development roles may have security in those job descriptions and they'll show up in they'll show up in the search, but they're not security roles. They're developer roles because they're working on a security product or they have to have security knowledge or experience, or they have to, or they are security roles as developers. And so I think the first thing is there's a volume of stuff they have to get through. And let me, I'm going to throw this to Tanya actually, because I know Tanya has been involved directly with writing job descriptions for security.

**Tanya Ward (3:39)**: I'm just gonna jump in there. People like— I actually spent some time just looking at LinkedIn because I was curious about our conversation last time. And I feel like sometimes the way the job descriptions are written isn't necessarily the way it's intended to come across. It's almost like they're looking for these, you know, they're looking for these kind of super experts with these unrealistic, you know, criteria that you have to meet and not really kind of— and like even the job titles themselves, like there's very vague. It's like, you know, some of them are compliance related, some of them are security. So I think the industry could definitely do better in writing up exactly what they're looking for and making it a little bit more specific, but also, you know, really, really thinking about What are really the requirements that somebody needs to meet for somebody coming out of university? Because I was looking at it and I'm like, I've been in this industry probably like I'm the baby out of all of you. I think I've been in the industry 12 years and I'm like, I don't think I can meet some of these credentials. Like, you know, so I'm like, oh, nope, nope, nope. So yeah, I think recruiters probably need to get better trained in really how to position the roles that they need and write it in a way where it's a little bit more appealing and not so scary. And I think you had brought up an analogy, um, as our round— I think you were talking about, you know, you don't need specialist, what you call it, doctors, like a neuroscientist or a neurologist. I think sometimes we're looking for perfection and we're just like, that good enough could become just absolutely exceptional, you know. And the other thing is the security professionals are not born— like, you don't buy a pot and suddenly you have the security, you know. You may have been born, not all of us were. Anyway.

**Chris Romeo (5:36)**: Were you born a security professional? Did you just begin life and your career as a security pro?

**Izar Tarandach (5:43)**: No, I was incepted as one.

**Matt Coles (5:45)**: Like there wasn't— Wait, wait, who did that?

**Izar Tarandach (5:51)**: Who did that? And there I was.

**Matt Coles (5:53)**: No, I, as many of you, I came into this totally by accident.

**Izar Tarandach (5:59)**: And I think that if we go over most of the episodes of the AppSec podcast, we learn that a lot of the people who are leading this industry nowadays that were in there got where they were basically by accident. And I want to take a step back and point out one resource, Alyssa Miller's book, The Cybersecurity Career Guide. Right. And I think that it's a unique resource. I didn't read the whole thing. Thank God. I don't need to read the whole thing. But the part that I did look at and that caught my attention is the bit where she points out that, yes, cybersecurity is a huge thing. There's a lot of different facets and stuff. And that for somebody going in today, it's pretty scary. And that a bit of self-reflection before they go in can go a long way in telling them where they want to put their head in first. Right. I mean, I know people who started in, I don't know, governance and saw the light and moved to AppSec. And I know people who started in AppSec and moved to infrastructure and stuff like that. And everybody has that, uh, uh, flashbang moment that they notice, I prefer to do the other stuff. But Alisa actually puts a number of questions in front of the reader that helps direct them more or less where they should be going. So I, I think that for the millions and millions of people who are listening to us right now, uh, if either you are interested in a, in a job, or if you know somebody who is, or, uh, if you if you even want to point your recruiters to figuring out how those things work and how people think, I think it's a great resource. So yeah, close parenthesis. Now, what were we talking about again?

**Tanya Ward (8:06)**: We were going to explore further because that other word's And a little bit about the way these job descriptions are written up.

**Matt Coles (8:17)**: And yeah, and actually, so let me just jump in here quick. I just did this quick search on one of the recruiting sites for entry-level security roles. And the top ones I got, so this goes back to the, how do I know as a new person what I'm looking for, right? And, and marry that to the set of, of options that are available to me. Um, you know, I just did a quick search for entry-level security and I got a security analyst at the National— at the National Security Agency, as it turns out. Um, an electronic warfare, uh, technician, a floor manager at a hospital or at a hospitality group, and an unarmed security guard.

**Tanya Ward (9:03)**: Wow.

**Matt Coles (9:03)**: So as an entry level, none of those make sense.

**Izar Tarandach (9:08)**: Let me put it like this. I have a lot of hope for ChatGPT in writing, uh, writing job descriptions, right? Because I know some great recruiters and I love them dearly, but I know a lot more who will turn to me on, uh, on LinkedIn and say that they read my, my resume, they are very impressed by my experience, and they want to know if I want to be a Java embedded engineer.

**Chris Romeo (9:41)**: It's even worse though, it's entry level. So you know, entry level job.

**Izar Tarandach (9:47)**: It's not only that they have difficulty in writing, they have difficulty reading as well.

**Tanya Ward (9:54)**: So I totally agree. Totally 100%. Similar to you, I got solicited on LinkedIn and what they are presenting to me, I'm like, I don't even think that's in alignment with what I've ever been like, what I've ever done in the last 12 years. So I don't know, maybe their search engines are busted or they just, they need to train up their HR recruiters to be able to kind of really read between the lines.

**Izar Tarandach (10:23)**: It's basically, you have a computer, here, come write embedded Java.

**Chris Romeo (10:30)**: It's lazy recruiting, right?

**Tanya Ward (10:32)**: Let's call it what it is.

**Chris Romeo (10:34)**: Any of us, if we get a, if you, if any of the four of us, and I'm sure in the last month, one of us has gotten a job. I know I did. So there, I've even ticked the box. I got a job offer for an entry-level position in cybersecurity. And I'm like, oh, wait a minute. Did you, didn't even, did you, I mean, like, I'm not, I'm not, I'm not all that or anything, but I've been doing this for 25 years. I probably don't need an entry-level job, but it's lazy recruiting. They didn't, they didn't do any analysis of, they just sprayed and prayed. They said, let me, let's just send this to 5 million people and hopefully one of them will be the right candidate.

**Izar Tarandach (11:09)**: You know, I had a theory. I had a theory. I went looking for why that happened because it actually in the same week, I got 3 different Java Java entry position offers. And I went looking for what, and this was like 3 months ago. And I noticed that in 90, no, in 2009 or something like that, I took the LinkedIn Java test and failed it. Perhaps they're just being like optimistic. I learned something since then and my entry level. So, it's the only explanation that I have.

**Tanya Ward (11:47)**: I have two points. By the way, wake up, entry-level? Chris is from 0 to 25 years experience. The other one is, so my daughter, she's in her final year at university and she is working part-time for an HR recruiting company. And so, she's never really been exposed to a lot of technology. I mean, she was more into you know, mathematics and, you know, physics. And so in this job, she was actually recruiting people to go into the technology sector. And it was amazing because like she was, she was coming to me and it's like, mom, I know what a stack, like a stack developer is. I know what a front-end GUI developer, like she had never known what these concepts were. And I think a lot of the ones that actually go out, you know, in LinkedIn and looking for people are maybe just not as senior, right? They're, you know, they, and they may not, you know, be as exposed. I'm almost 98% sure exposed to security type roles and functions and where they should go.

**Izar Tarandach (12:53)**: So what I'm hearing is that now that your daughter knows all of that, she's ready for an entry position as a Java embedded.

**Chris Romeo (13:02)**: We're determined to fill that position.

**Izar Tarandach (13:05)**: She knows all the checkboxes, right?

**Tanya Ward (13:10)**: But it's fascinating. I don't think like, I mean, I mean, I don't know what HR recruiting does, what level of training. I know her company really did train her really well because she was talking about the software development lifecycle, security, even the security development lifecycle. She goes, I get what you're doing now. But I don't know if all companies do that for a 21-year-old.

**Izar Tarandach (13:31)**: So let's pull that back to security and what we were talking about. So I passed the LinkedIn entry-level thing, and now I am in front of Tanya as a candidate. To my first cybersecurity entry position. Tanya, how does that experience go? What is it that you are asking people?

**Tanya Ward (13:51)**: Oh, what would I ask? Show me your code. No, I mean, no, it's like you want to be able to understand the experience, right?

**Izar Tarandach (14:02)**: Important. That goes together with a discussion that we had a while ago. Do cybersecurity people need to know how to code?

**Tanya Ward (14:11)**: There's so many tools. Do you need, I mean, code tools?

**Izar Tarandach (14:14)**: You went straight into show me your code.

**Matt Coles (14:16)**: But this is a wide—

**Izar Tarandach (14:17)**: throw a fraudian in there.

**Matt Coles (14:19)**: You can't have a wide open conversation like this. This goes back to what role are you looking for? What role do you want and what role do you need? Exactly.

**Tanya Ward (14:25)**: Yeah.

**Izar Tarandach (14:26)**: Okay. So let's choose a role. We are interviewing somebody for an entry role in—

**Matt Coles (14:30)**: Well, let's say we're going to make them a security champion.

**Izar Tarandach (14:36)**: Security Champion as an entry role? Well, no.

**Matt Coles (14:41)**: All right, no.

**Izar Tarandach (14:41)**: Okay, we can't do that.

**Tanya Ward (14:43)**: You could, you could, but you would train them up again. Remember, security professionals are developed.

**Izar Tarandach (14:49)**: Okay, let's keep Security Champion for another day. I already see Chris thinking about it.

**Matt Coles (14:55)**: So, all right, let's start with, let's start with a role here. I'll throw out a role. Uh, let me throw out a better one this time. Um, uh, a security incident and an analyst who like looks at the SIEM. A CIEM?

**Chris Romeo (15:07)**: SOC analyst.

**Matt Coles (15:08)**: A SOC analyst. Thank you. There we go.

**Izar Tarandach (15:10)**: Okay. So Tanya, you're interviewing somebody for a SOC analyst position. What's the first thing that you ask?

**Tanya Ward (15:18)**: Do they like— How are you doing? Do you like working overtime?

**Izar Tarandach (15:23)**: No, I'm kidding.

**Chris Romeo (15:25)**: Do you have 25 years of experience?

**Tanya Ward (15:28)**: Do you have 25-year experience? I know this is, this is interesting because my brain's going off in 14 different directions because I think you want to look for practical skills like coming in. What do they know? What, you know, what, what have they learned? You have to look at also your own environment, like how do you run? How much training time are you going to take to be able to get this person operational where you need them to be? What really matters to me a lot is, to be honest, is soft skills, especially in a SOC environment. Communication is everything.

**Izar Tarandach (16:00)**: Nice, nice. Okay, so, oh yeah, I think it's a nice bizarre management questions that you, that you just started thinking about. What is the first thing you're going to ask this person?

**Tanya Ward (16:16)**: There's no wrong or right answer here, Matt.

**Izar Tarandach (16:19)**: It's like thinking, which is the right one, and there's everything else that you're going to This is what's called a lose-lose situation.

**Tanya Ward (16:29)**: Yeah, win here.

**Izar Tarandach (16:32)**: So come on, what you're going to ask them first? You have it, you just said it, you just said what you think is most important.

**Tanya Ward (16:40)**: I'm gonna defer to Matt. My brain, I've talked a lot. Matt, you're— you, you come on, come on, save the day here.

**Matt Coles (16:47)**: Well, so the first question I would, I would ask them, oh, in all seriousness here, is What in your background or your experience makes you, uh, an appropriate candidate for this role, right? There needs to be some description of that role, right? We're talking about a stock analyst. The person has to be diligent. The person has to be, uh, capable to read, to be fast, to understand things at a fast pace, and to be able to follow instructions. We're talking about entry level here.

**Chris Romeo (17:22)**: What?

**Izar Tarandach (17:22)**: That's awesome because it just took what Tanya said, the soft skills, and you put it into a framework of what is it that you've done before this, then you can bring into this.

**Tanya Ward (17:34)**: The other question is, why are you applying for this?

**Izar Tarandach (17:39)**: I know, because they need money. That's a given.

**Chris Romeo (17:42)**: Yeah. Yeah, but I mean, that— I ask this a little differently, so I get the same result, but I don't lead the witness as much. My first question to everyone I've ever interviewed, probably in the last 10 years, tell me your story.

**Tanya Ward (17:55)**: Yeah.

**Chris Romeo (17:57)**: True. I don't, because that way I don't lead them into, because I want to hear off the cuff what they want to tell me from that perspective.

**Izar Tarandach (18:04)**: Look at the difference here. Tell me your story. I'm going to tell you the things that I think are interesting about me. And I'm going to sort of mask the things that are less interesting. But the way that Matt asked, what is it that you've done before that you think you're going to carry into this? You are asking this person to look into themselves and say, okay, so I have curiosity, or I have tenacity, or I don't give too much importance to my mental health. Things like that actually are important to the job at hand.

**Tanya Ward (18:38)**: I will say the difference between Chris's, the way he asked it, and you, Matt, is I feel like that's something I can absolutely pre-canned an answer for. Like that's the type of typical interview question that you may get asked when you go for a job. Whereas Chris is like, you're sitting in there and you're waiting for all these structured, you know, questions coming at you. You may go into Indeed and look up the company and say, what are all the cybersecurity questions they ask? And then you sit down and you're ready and Chris goes, tell me your story. And it's like, boom, you know?

**Matt Coles (19:08)**: So, well, yeah, so let me, let me, it can be a diffusing situation.

**Chris Romeo (19:11)**: It can diffuse too, because it's not, it's not a scary question because I'm asking you to tell me your story. Don't tell me the story I want to hear. Don't tell me who you, and what I find in that though is I learned a lot about that candidate that they wouldn't, that they wouldn't have told me in a structured answer. Because sometimes they tell me, they tell me all kinds of things about their life that are interesting to, you know, I had one person told me that he was a motorcycle racer in his free time. And I was, and so I asked a couple of follow-up questions about what does it take to run a team? Oh, well, you know, we have to have mechanics. We have to, you know, it's like, oh, so I left that, that portion of the conversation going. This is somebody who can manage a group of 4 to 5 people pretty easily. 'Cause if you can do that in the heat of a motorcycle race, then that transfer. Now, I'm getting away from entry-level, but that was just where the illustration kind of went.

**Matt Coles (20:04)**: I was gonna say, are you, yeah, go ahead.

**Tanya Ward (20:06)**: I was gonna say maybe that question though, for people who are entry-level, it's just more, you know, it's less, you know, it just makes it easier when you're interviewed. I mean, think about a lot of these kids coming out of university. Like, it's probably their first interview, maybe second, maybe they've done a couple, maybe they haven't even. The resume hasn't even been looked at, it's been rejected. And now they've got that, you know. So, you know, it's a good lead way in that kind of shows, you know, we have to extend some grace to them as well.

**Chris Romeo (20:38)**: Like, that's one thing I always remember. It was a long time ago, but I was in that situation sitting across the table from somebody, you know, my legs shaking because I'm in this interview for the first time ever after you know, getting out of college or whatever. And so I think that's just something that we as people that are hiring entry-level folks and anybody out there who's hiring an entry-level person, you know, give them— I give them a lot more room than I would a senior candidate. I expect a senior candidate to be more, you know, on the ball, like, you know, I mean, everybody gets nervous a little bit, but—

**Izar Tarandach (21:13)**: So I'll have to take this to the next form question in these things. You're just interviewing somebody entry-level for a cybersecurity job, and now you throw the, where do you see yourself in 5 years? Uh, is, yeah, I mean, a question that says something or not, or it's just a filler.

**Chris Romeo (21:35)**: I, I think it gives you some perspective on, do, does this person have a plan for what they want to do with their career? Have they thought about it? If they come back, if somebody comes back and tells me, no, I have no idea what I want to do, then it's a tell that they haven't really thought about where they want to go and what they want to do. For me, that's how I read it.

**Tanya Ward (21:58)**: And I think that's okay. I think that's okay. There's planners in the world and there's people who are spontaneous and go with opportunities.

**Chris Romeo (22:06)**: Yeah, I mean, for me, I don't, It doesn't matter 5 years in the future. Like when I'm doing an entry-level interview, I'm trying to answer one question. Maybe two questions. Am I going to have to, you know, follow this? Is this person going to follow me around and ask me 100 questions a day? Or do they have the ability? Have I, can I see something in them that says they're going to go try to figure stuff out? And I always tell people, especially entry-level folks that are working, that work for me is I don't want you to spend, you know, I give them a metric about here's how much time you should spend before you come and ask the question. But don't just come and ask me the question. Don't ping me every 5 minutes with, oh, what do I do next? Yeah. So I mean, that's so that, but that's what I'm more, I'm like, I could, I'll take somebody who says, I don't know anything about a SOC. If they have a, if they have something in their background that makes me think they're going to figure it out, they're going to learn what they need to learn, you know, they, and they're not going to sit there and I'm not going to have to micromanage them because I don't want to micromanage anybody. From my entry level all the way up to the most senior.

**Izar Tarandach (23:10)**: Okay, so, so far we want people who are curious but know when to ask for help, resourceful, resourceful, open-minded, critical thinking, critical thinkers, and a different point of view. One of the best answers that I got for the, uh, where do you see yourself in 5 years was cybersecurity evolved at such a pace that it would be irresponsible for me to say right now that I know where I'm going to be in 5 years. I know that I'm going to spend the next 5 years looking for the next place.

**Chris Romeo (23:45)**: That's a great answer.

**Izar Tarandach (23:48)**: I like that one.

**Chris Romeo (23:50)**: They thought about it. They didn't, they didn't just, they didn't come up with that on the fly. They had pondered it and said, hey, this is where it is.

**Izar Tarandach (23:57)**: Yep.

**Matt Coles (23:59)**: Let me ask a question of all of you because I probably, uh, well, I'm not a manager, so I don't hire people on a daily basis. Uh, I've been involved with interviewing people and obviously I, uh, you know, tapped to provide, you know, expert opinion, but I don't have that direct, full, fully direct hiring experience, at least in my current role. When you are looking at an entry-level person, How long are you thinking that you're going to have this person in your team in this role? And whether you promote them or they move on to something else or they leave, what's that timeframe that you're looking at?

**Izar Tarandach (24:43)**: Let's use—

**Matt Coles (24:43)**: if you're using the SOC example, and maybe it varies by role, but you know, what's— when you're interviewing somebody, are you thinking 5 years or are you thinking 18 months?

**Tanya Ward (24:55)**: I think that's a hard question to ask. Well, because I think there's two things that you look at. Entry-level means that there's going to be some level of ramp-up time for them to be operational and independent. And so that's a hard thing to gauge. You know, normally entry-level, I think you're kind of almost, and depending on the job as well, you may expect anywhere between 3 to 12 months. So, you know, and then you want to be able to make sure that if you've trained them up, they're not going to walk out the door either, right? So, because you've invested that time, so it's— you want them to stay in your team for as long, you know, as much as possible, because, you know, you're investing in that and that development, you know. But then people— then you have to plan about what their next step is, where do they want to go. And sometimes it may mean moving away from your team and going somewhere else or trying something different because the security landscape is just so big and so many domains.

**Chris Romeo (25:57)**: What Tanya just described is one of the traits of a good leader. A good leader doesn't hold on to people because they want to. And what you just said, Tanya, is a really powerful thing. You just said you may find, you may find, you may help that person go do something else inside your company and maybe even somewhere else because there's a, there's, there's somewhere else that they need to grow. And that's, And I'm in the same boat. Like, I like to think about how am I going to help this person get to the next level? What is the next level for them? You know, and some of that comes from one-on-ones and coaching and listening to them tell me that either they don't know, and if they don't know, then I challenge them to go think about it and figure out where they want to go. If they do, then my job as your manager is to help you get there. And I'm a failure if I don't help you, if I don't knock down doors, if I don't help you get the things you need to meet your own development goals. And, you know, like Tanya said, it could be, you know, I don't think there's any one answer for a period of time. I think it's, it comes down to the complexity of the job. And, but, you know, my hope is that we bring somebody into the SOC, they're doing a great job and they're learning everything and they're growing. You know, 18 months, maybe even as early as 12 months if they're really killing it, we should be looking about what's the next thing. We should be getting them some exposure to the next thing, whether it's becoming an incident response team member or, you know, whatever, whatever the next progression is going to be coming out of the SOC in that particular company.

**Izar Tarandach (27:31)**: Which brings us to a very important aspect of this whole, are we missing talent myth? And I think that we spoke a bit about the technical side. We spoke a bit about the soft skill side. We spoke about how people get into the door. I think that each one of us, from hearing all of you, I know that you are heavily involved into this. Each one of us, to a great extent, likes the part of the job that involves mentorship.

**Tanya Ward (28:02)**: Absolutely.

**Izar Tarandach (28:03)**: And one thing that I can tell for myself is the, the past few times that I had the opportunity of mentoring someone, very quickly it stopped being move this bit to that bit and turn on this flag and start this virtual machine. And very quick it became not only the soft skills but the whole framework of being a professional building your brand, relating to other people, doing the politics of the workplace and all that, that stuff. Do you guys think that this stuff related to cyber is different from other— let me put it like this. Somebody who got to a staff engineer by writing code and somebody who got to a staff security engineer Do they need different sets of soft skills?

**Tanya Ward (29:06)**: Yes.

**Matt Coles (29:06)**: Yes, I think that they do. And I think that's because it's a nature of their work. So a developer who's writing code and working way up the ranks needs to have listening skills, critical thinking skills, the ability to pull in information like requirements and deal with schedules and things like that. And as they, obviously, if they, as they move up the ranks, they're going to be developers first. And I think a couple of us here have done this sort of work, right? We've been developers, take direction, then developers sort of provide direction, then developers operating independently or not independently, but like autonomously, I suppose. All the way up, and then up to staff engineer, where you're seen as the guru on the toolchain, or you're an expert in the language, and you're doing program leadership, and you're doing, you know, and so you have the ability to work with other engineers in your area, you have the ability to manage schedules and work with the— and manage out and up, right? You have to both manage your leadership as well as managing your other program, uh, peers, right? Whereas the, the staff cybersecurity, uh, cyber engineer— and, and I guess I have to be careful here about which role we're really talking about— but, uh, but somebody who's doing, you know, InfoSec as an example, as opposed to AppSec, um, it's a little bit different. Your requirements are coming from different places. And your peers are different. But then you need better communication skills because you're talking to people who in many cases don't want you there, right? Or you're not seen as a partner, and there's a lot of partner building. So I think the skills are— there are some overlap, but I think by and large I see that there are very specialized skills in both areas. One is more focused at how do I make this program successful, this overall, and how do I, you know, make, make the schedule on time and meet numbers and make sure our management is aware, etc. The other one is doing some of that, but really their role is also to help, uh, create this partnership and drive change and not be in the news and keep their CISO from being fired and, you know, all of that sort of stuff. And so the skill set is different, and those soft skills especially are going to be different.

**Tanya Ward (31:37)**: So you, you made— both of you are making me think about something that has really hit home to me. So most of my career I was a program manager. I was at Microsoft, and there wasn't really a lot of mentorship program for a program manager. And what I realized that I'm really drawn to, to culture. So I don't know if you know, but I used to be a pro-am bodyboarder in Ireland, so I was very much immersed in surfing culture. And then I ski patrol up in my local mountain, and we're all there every Monday working together as a team, and we support each other. And then I'm almost working in an EMS system as an EMT. But security is exactly the same. It's the first time ever where it was like, hey, you want to— you want a mentor? Like, I remember when I stepped into my first job, real, real big job in security, I think both of you were there. Like, there's this warm mentoring here to support you kind of culture that it's so like, for example, when you go to a conference, you see people you haven't seen in a while, it's like, oh, it's so good to see you. It's, it's, there's something very unique about this profession. I don't know about government, like, you know, InfoSec. I'm talking purely AppSec, um, because there's a level of just understanding of some of the pressures and the impact of what you're doing and what could go wrong. And I think there's, I mean, You know, for me, I pay it forward like all of you. But I think the mentorship aspect is that people are so willing to help. Like, if somebody— I'm sure if I went to somebody on LinkedIn and said, look, I really, really love reading your blogs around security. Would you mind maybe just mentoring me like 1 hour? You know, people are willing to do that, right? So yeah, I think that there's a lot of analogies with the military here.

**Matt Coles (33:18)**: And, you know, well, So I've never been in the military, so I can't speak about this specifically. But I think, you know, it's people who are in stressful situations together. And I guess, Tanya, you see this with being an EMT and ski patrol, right? I'm not sure about surfing, but, you know, people who, and, you know, in some past lives of work. I've been on incident response teams and customer support groups dealing with, you know, crises when they occur. And I think that that's in part where this camaraderie comes into, right? And the notion that there's a small number of us, and there's a giant development team or business, you know, business stakeholders out there, and there's a lot of pressure. And so it pulls people together and they they, um, uh, you know, that they want— are willing to support each other. I think it's also, though, in a function of the time that we live in, right? So all, all of us here, I think, have sort of grown up and, and grown into these roles starting after 9/11, right? Or, you know, after the year 2000, effectively. Although I mean, I know your history probably goes back a bit further.

**Tanya Ward (34:45)**: Another 20 years, just in case.

**Matt Coles (34:47)**: I mean, technically, I guess my first job that has security impact data also started before 2000, but I'm really talking about the stuff that's like since 2000. And not that that's a hard cutoff, but it makes it a little bit easier just to talk about. We entered a time where collaboration was good. It wasn't the the turn of the '70s, '60s, '70s, and '80s where, you know, every— everyone for themselves. And, uh, you know, you were, uh, it's— it seemed like it was a different time to how people operated. You know, it was, you know, uh, strict dress code. And, um, uh, you know, we now have— we now have the sweater culture or the— or the— or the dress-down culture. It's relaxed style. And then on top of that, now you have— oh, and oh, by the way, it's no longer illegal to do what we do, right? A lot of, uh, a lot of security was not— was, was under the, uh, you know, behind the, behind the curtain, so to speak, because some of it was, was questionable legality, right? Um, and so we entered a phase of our careers and of the industry where collaboration was okay. And so, I think that's in part, like, we are a tight-knit group. And I'll say, you know, my area specifically is product security. Product security people don't necessarily, it's sort of a subset of application security, I think. And it's an even smaller set of people. And so, I think that goes a long way to why we see what we do in terms of how people interact in the industry.

**Chris Romeo (36:25)**: I wanna come back around to your, kind of the initial question, Isar, that you asked here about, and kind of Matt's point about seeing differences. I think there's a lot of, I think there's more similarity than difference in that core set of skills. Like critical thinking is one that we've mentioned, and it was mentioned in this context. You know, just general social skills, being able to speak at a meeting where there's more than 2 people in the room. You know, I think there's a lot of, there's a lot of commonality in those things. And I think you can even extend those into other fields outside of technology. Being, you know, critical thinking is something that fits into any— it's hard to find a job, you know, where you— that was based on getting a college degree and then getting a job in the field that doesn't require critical thinking, doesn't require social skills. And so I think there's more similarity than difference.

**Izar Tarandach (37:16)**: I think that if I look at the bottom line of the— all that we spoke about in the past hour and best episode. I think that yes, we need more bodies. No, we are not doing a good job in publishing out who are these people that we need. Yes, we are able to produce these people based on them having a very easy to define set of basic qualities. Yes, we can teach on the job. Yes, people enjoy teaching on the job. And yes, if we look at the origin story of many, many, many leading people in this industry, we will find that they started in completely different things, right? And that's not a new thing. If you look at, uh, what was his name, Cliff Stoll, which you guys probably don't remember the name, But he had this great book called The Cuckoo's Egg, and it's one of the, the first ever, I think, computer security stories out there. The guy started as an astronomer, right? And he went into security because of an error of 10 cents in a bill that he got. But the point is, he started something completely different even before there was no security. So yeah, I think yes, it's not a myth that we are missing people. I think that we can solve this gap mostly with, um, tools that we already have, mostly with the approach that we already have. And the important thing now is to convince people that, uh, they can do this. Yeah, I, it's funny because sometimes I catch myself talking with, uh, friends of my son. He's 13 years old now. Well, almost 13. Almost 14 next week. And, uh, they ask, so what do you do for a living? And once upon a time it was hard to explain, but nowadays it's easy to sit down with this 14-year-old, relate to things that they read in the news all the day, or things that they experience every day. Yeah, remember that, I don't know, that thing you got on Instagram saying click here to get $1,000 in Bitcoin? Here's what's happening behind that. And they have the interest, they ask those questions, they are looking at that as a possible field to get busy at. So what was it? We, we started by saying, is it a myth that we are missing people? No, I think that it's a reality. The myth is that we can't find them. We just have to meet them.

**Chris Romeo (39:56)**: That's a heck of a way to put this together. I don't think we can add anything else.

**Tanya Ward (40:02)**: So that is just— you have to repeat it again. You always have one, one thing each podcast. Can you repeat that again? Just repeat it.

**Izar Tarandach (40:12)**: The t-shirt later on.

**Chris Romeo (40:16)**: That's really good. It's a good way to summarize and bring it all together because, you know, we don't want to just sit around and talk about problem space. We want to offer some solutions to the world. And I think people can take away, Izar, to your point here, things you just shared. There's some things that people can take away and there's some action to be done here by all the different parties that we talked about here. So why don't we leave this conversation right here and we will continue our next episode, talk to talk about something else around the security table.
