Reading a post from 2012 like this it's shocking how quickly the ladder has been pulled up in all computer careers, but I suppose it's not as bad as the ladder pull from the dotcom bubble to 2012 where you could previously land a career "knowing HTML".
Surely "knowing HTML != you're hired" after dotcom bust was not so much a ladder pull as a regression to mean from an unprecedented employment boom?
As for today, there was a shock from end of ZIRP and now AI.
On the AI side I guess one could read it as a ladder pull but it feels more structural to me? The entire field is in an existential crisis while we try to figure out what our jobs are now, what hiring criteria we should use, how work should be organised and what products might even be valuable anymore.
For boutique security specifically I can't say if it was difficult or easy to get hired in 2012, sort of both? The hardest part was figuring out where the ladder even was. It was hidden round the back of the building, next to the loading docks where people smoke. The hiring path was quietly "game recognise game", i.e, you learn & hack stuff in a safe way and people already doing that recognise that you can do the job. Certificates never mattered - that's not what anyone was looking for (by the time someone can certify you to do it, it's not really hacking anymore). I don't really see that changing.
Marking this as 2012 would help. It’s a fun read in a nostalgic, pre-ai kind of way, where emphasizing that developers should use bcrypt wasn’t standard practice.
I'm often asked how to turn a security-related interest or hobby into a job. For the longest time, I'd say pretty much the same thing written here: get a book, do some research, build some projects, talk to people in industry. I've been going to DEF CON for about 25 years now, so I've had this conversation countless times.
But in 2026, tptacek says it best in the comments here: At this point, who knows?
Are we still telling kids to learn programming languages to become software developers? Perhaps system design is a more reasonable skill set.
That said, because this is the time to say it: security is still important, and it's not -- and shouldn't be -- fully automated.
The toolchain is changing just like it always has. I remember when interpreted languages replaced compiled ones, and people said that interpreters solved security. Then people went from writing their own codebases to implementing frameworks, and people said it solved security.
Barracuda Networks posters at every airport stated "Security Solved."
As long as people take risks, security is important. Now we just need to focus on designing resilient systems instead of finding bugs and vulns on the code-level. LLMs can do that part for us.
I hire for incident response roles. Honestly, despite how much has changed this is still the way to do it for us. You need to be versed in many things and more importantly, interested enough to not feel entirely stressed out when things hit the fan.
As for AI it’s been great for things like log review but those were already pretty low skill requirements. We haven’t had much luck past that.
Yes -- I was keen to hear what tptacek had to say about breaking into the industry in the age of LLMs and 0-days being discovered by the dozen for pennies.
tptacek may disagree, but this needs an update considering how much has changed both with AI and the economies of scale AI brings to the discipline.
I'm anticipating "the fundamentals are crucial," and as much as I want to agree, I think practical realities show us otherwise. We're at a point where all someone needs to know is how to AI-program-manage and how to glean enough about the discipline (or any discipline at this point) from AI to be dangerous enough in the field. To be a builder, breaker, or defender wearing any color hat of their choosing... that's it, really.
it would be interesting to know what tptacek's thoughts are in the age of 'agents' violating vulnerabilities willy-nilly ? if his thoughts of getting into application security still apply.
what the incentives are since hacking seems to be no longer a crime given how many hacking incidents have gone unpunished.
Now would be a very weird time to write any kind of an authoritatively-sounding "here's how to break into software engineering" or "here's how to break into infosec".
On some level, nothing has changed - you still get noticed and hired the same way as before, the companies are still pretty much the same - but I just wouldn't have the confidence to tell anyone "hey kid, this is how it's going to look three years from now". It's not that I think these roles are going away, but there's a good chance they're going to be a lot less interesting (and not as well-paying) when it's all said and done.
As for today, there was a shock from end of ZIRP and now AI.
On the AI side I guess one could read it as a ladder pull but it feels more structural to me? The entire field is in an existential crisis while we try to figure out what our jobs are now, what hiring criteria we should use, how work should be organised and what products might even be valuable anymore.
For boutique security specifically I can't say if it was difficult or easy to get hired in 2012, sort of both? The hardest part was figuring out where the ladder even was. It was hidden round the back of the building, next to the loading docks where people smoke. The hiring path was quietly "game recognise game", i.e, you learn & hack stuff in a safe way and people already doing that recognise that you can do the job. Certificates never mattered - that's not what anyone was looking for (by the time someone can certify you to do it, it's not really hacking anymore). I don't really see that changing.
But in 2026, tptacek says it best in the comments here: At this point, who knows?
Are we still telling kids to learn programming languages to become software developers? Perhaps system design is a more reasonable skill set.
That said, because this is the time to say it: security is still important, and it's not -- and shouldn't be -- fully automated.
The toolchain is changing just like it always has. I remember when interpreted languages replaced compiled ones, and people said that interpreters solved security. Then people went from writing their own codebases to implementing frameworks, and people said it solved security.
Barracuda Networks posters at every airport stated "Security Solved."
As long as people take risks, security is important. Now we just need to focus on designing resilient systems instead of finding bugs and vulns on the code-level. LLMs can do that part for us.
As for AI it’s been great for things like log review but those were already pretty low skill requirements. We haven’t had much luck past that.
I'm anticipating "the fundamentals are crucial," and as much as I want to agree, I think practical realities show us otherwise. We're at a point where all someone needs to know is how to AI-program-manage and how to glean enough about the discipline (or any discipline at this point) from AI to be dangerous enough in the field. To be a builder, breaker, or defender wearing any color hat of their choosing... that's it, really.
it's a decade+ old document. i dont think it needs anything, other than a notice of its publication date.
at this point, much more than an update would be required to be up to date
what the incentives are since hacking seems to be no longer a crime given how many hacking incidents have gone unpunished.
On some level, nothing has changed - you still get noticed and hired the same way as before, the companies are still pretty much the same - but I just wouldn't have the confidence to tell anyone "hey kid, this is how it's going to look three years from now". It's not that I think these roles are going away, but there's a good chance they're going to be a lot less interesting (and not as well-paying) when it's all said and done.