Penetration Testing The Dev Interview: Attacks to Ace Interviews and Defenses to Build Better Teams
summary
Shows how interview heuristics get exploited and how to fix them: resumes with action verbs double callbacks, adding a degree gives ~20–40% lift and Monday sends 5x callbacks, so story-driven bullets and seven polished anecdotes become the real assets. Phone screens are hijacked by voice cues (smile, mirroring, clarifying questions, a brief stall). Take-home tests require 3–5x polishing, mimic the company stack and a 15–20 minute follow-up note. Defenses: 30/60/90 outcomes, discard or score resumes, use structured rubrics and two independent graders.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:13Learning the hard way
- 2:26Attack the interview!
- 3:18What is the goal of the hiring process?
- 8:48Our attack vector: stories!
- 10:42Resume Be the feminist librarian.
- 18:38Take-home test "Does this look like my work?"
- 20:39Scorecard
- 29:32Call-to-arms! Which 1 vulnerability will you plug?
related talks
56mBuilding An Effective Application Penetration Testing Team
39mAutomating myself out of a job...
33mWorking with penetration testers as a developer
25mWhen words become attacks: prompt injection through a technical writing lens
35mBreaking Boundaries with Adversarial Testing
20mHow to Use Your Vulnerabilities to Train Your Developers on Security
56mAttacking AI
44mApplication Security: Everything we know is wrong