Technical screening questions
Ask for one example per question and listen for specifics.
- How do you scope an engagement? A good answer: Authorization, rules of engagement and timelines.
- How do you test authentication? A good answer: Common flaws and testing methods.
- How do you rate a finding? A good answer: Impact, likelihood and a framework such as CVSS.
- How do you explain a vulnerability to developers? A good answer: Reproduction steps and practical fixes.
- Which certifications do you hold? A good answer: Specific credentials and practical exam experience.
Quick screening questions
Use these when you have only a few minutes.
- Walk me through how you test a web application.
- How do you write a finding so developers can fix it?
- What is your scope and authorization process before testing?
What separates the levels
Match the level to the requirement before you submit.
- Junior: supports tests.
- Mid: leads web or network tests.
- Senior: leads engagements and methodology.
Red flags
Any of these is a reason to probe further.
- Runs scanners only.
- No reports to show.
- Unclear about authorization.
Tools you should hear mentioned
A penetration tester with real experience usually names several of these without prompting.
- Burp Suite
- Nmap
- Metasploit
- OWASP guidance
- Scripting
- Reporting templates
Run the call well
Ask for the last project first, then dig into the second or third question. Take notes on versions, team size and outcomes, and record them with the submission so the vendor’s later technical interview does not surprise you.
Frequently asked questions
How long should a penetration tester screening call take?
Fifteen to twenty minutes is enough to cover the project, three technical questions and availability, rate and work authorization.
Do recruiters need to know the technology?
Working vocabulary is enough. Use the sourcing guide for the role and listen for specifics instead of judging technical depth yourself.