Interview kit · 2026
Penetration Tester interview questions
A curated set of 8 questions for technical and behavioural rounds with penetration testers. Tap any card for what to listen for.
Interview prep
Questions to ask a penetration tester
Grouped by area. Pick 3–4 per round; calibrate as a panel after each candidate.
3
Maximum rounds
Top penetration testers drop out of processes longer than 3 rounds. Run a 30-min intro, a technical deep-dive, and a final with team & leadership - no take-homes longer than 2 hours.
Skills to probe in penetration tester interviews
4 core · 4 nice to have
Core stack
Nice to have
Python
BashInterviewing tips
The penetration tester hiring playbook
Penetration Tester specialist or generalist - which should you hire?
The honest answer depends on the half-life of your penetration tester surface area. If you expect to keep investing in Burp Suite and Metasploit work over the next 18-24 months, a specialist penetration tester will out-deliver a generalist on day-30 throughput and stakeholder confidence.
If your team is under ten people, or penetration tester responsibilities are spread across two or three roles already, hire a strong generalist who has shipped this work in anger at least twice. The cross-disciplinary pattern recognition will pay for itself the first time priorities collide.
On Haystack we surface both - filtered by whether the candidate self-identifies as a penetration tester specialist and verified against their last two roles. Expect to pay around £65k–£90k for a mid-level UK hire, scaling toward £95k–£135k for senior.
What strong penetration testers actually bring
A great penetration tester is not the one with the longest CV - it is the one who has owned a hard Burp Suite call and changed how they work because of how it landed. Across the engineering hires we have placed in 2025-2026, the same patterns keep showing up.
- Active mentorship of at least one other penetration tester or adjacent role - usually a junior - within the first quarter.
- Versioned, observable penetration tester work - measurable outputs, structured logs of decisions, and a clear rollback path on every change.
- Documented trade-off notes on the calls they made, including the option they rejected and why.
- An opinion on what NOT to do with Burp Suite, backed by an example where adding it would have hurt the team.
Red flags when interviewing penetration testers
Every discipline has its own pattern of plausible-sounding answers that fall apart in production. For penetration testers, these are the patterns that most often correlate with a six-month regret hire on the employer side.
- Cannot name a single penetration tester project where they removed scope rather than added it.
- Defines "senior penetration tester" purely by years of experience, not by the scope of decisions they own.
- Lists Burp Suite on the CV but cannot describe a single trade-off they hit in production - all framework, no friction.
- Treats the penetration tester role as a job title rather than a problem to solve - no opinion on what they would change about how the discipline is typically practised.
A sample take-home for penetration tester candidates
When teams ask us how to evaluate a penetration tester beyond a CV and a chat, we recommend a 90-minute paid take-home that mirrors real work, not a trivia quiz. The brief below is one we have refined with employers hiring across engineering teams.
Give the candidate a small, intentionally imperfect artefact tied to "run black-box and grey-box pentests". Their task is to add a second capability - tied to "write actionable, prioritised reports" - while keeping existing behaviour intact. Then grade in three parts.
- Correctness: the new work satisfies the brief and at least one edge case the candidate flags themselves.
- Judgement: did they refactor, wrap or work around the existing imperfection? Any of the three is fine - we are listening for the reasoning, not the verdict.
- Communication: a short written note explaining what they would do differently with another week, what they noticed about Burp Suite, Metasploit and Web AppSec, plus working exposure to Cloud Pentest, Mobile Pentest and Python, and the assumptions they made along the way.
What to expect in the first 30 days from a Haystack penetration tester hire
By week one, the new penetration tester should have shipped a small, low-risk artefact to production or a stakeholder - a docs fix, a small process change, a first review on someone else's work. The goal is to validate the loop, not to ship anything heroic.
By week two, the penetration tester is shadowing the active workstreams, attending standups in observe-mode, and asking pointed questions about why specific decisions were made. If they are not asking those questions, the hire is going to plateau.
By day 30, they own one cleanly-scoped slice of the penetration tester surface area, have published a public ramp-up doc, and are the named point of contact for stakeholders inside that slice. Every Haystack employer gets a structured onboarding template, so you are not reinventing the playbook each hire.
Keep exploring
Related interview kits
Same format. Different role.
Other Engineering kits
Skip the cold sourcing for penetration testers
Haystack matches you with vetted, interview-ready candidates so your interviews start with the right people.