Lock it Down Podcast

The episode contains some substantive ideas - particularly the time-travel interview technique and the distinction between credentials vs. practical problem-solving under pressure - but these insights are undermined by repetitive circling, incomplete thoughts, and filler. Lucas frequently restarts sentences, loses his train of thought ("from the book, which it just escaped my brain now"), and restates the same core point multiple times without deepening it. A 10-minute format with a sponsor break leaves little room for density, and the conversation doesn't accumulate novel claims per minute.

“people um, who can still get uh, locked and um, be unable to actually uh, execute properly under pressure”

“individuals with specific traits of ownership and accountability who tend to understand uh, that practical problem solving under pressure is uh, more important uh, than, than having those certificates”

The core argument - hire for practical skills and ownership over credentials - is well-trodden in tech hiring discourse and not contrarian or particularly fresh. The time-travel interview technique is the most original element but is under-explained and presented as a personal innovation without deeper structure or evidence. The final point about compliance shaping talent pools is reasonable but brief and intuitive rather than counterintuitive.

“we tend to focus too much on credentials and especially certification”

“I play a Bit of a role play during my interviews and I recommend to my other colleagues here at LLI to do this exactly the same. What we do is we travel the timeline”

Lucas Lisevsky is a founder/CEO of a consultancy with stated experience building tech teams in regulated industries (healthcare, finance, PE), which is relevant to the topic. However, the transcript provides limited evidence of operating at significant scale or achieving measurable outcomes. He speaks from experience but remains somewhat vague about the scope and impact of his work, and his rambling delivery undermines confidence in his expertise.

“CEO and founder of LL Informatics, a consultancy that builds and rescues complex systems for enterprises and PE backed firms”

“my background is in building uh, scalable tech teams for enterprises in highly regulated industries such as healthcare, finance, private equity”

The episode lacks concrete examples, named companies, specific metrics, timelines, or quantified outcomes. References to GDPR, EU AI Act, and clinical trial data are regulatory name-drops rather than case examples. The interview technique is described but not illustrated with a real candidate interaction or outcome. The advice remains largely abstract and anecdotal ('in my practical experience') without hard evidence.

“we see gdpr, we see EU act, right, AI act”

“in situations where um, there is um, an aspect of data leakage importance or prevention or sort of a situation where in clinical trials patient data is on the line”

Jordan's questions are straightforward setup questions that allow Lucas space to answer, but there is minimal pushing, follow-up, or productive friction. When Lucas loses his train of thought or becomes vague (e.g., the forgotten book reference, the unclear explanation of 'lockage'), Jordan does not press for clarity or specific examples. The host accepts hand-wavy answers and moves to the next topic rather than drilling down, resulting in a soft interview rather than a substance-driven conversation.

“Kind uh, of getting into the meat of the topic today. What common pitfalls do you think security leaders fall into when hiring?”

“And you touched on this a little bit in your answer. But what actually predicts success in technical and security adjacent roles?”