How to write a penetration tester resume summary
Say what kind of testing you do, for whom and how much of it, with one result, in two or three sentences. Use the word "authorised".
- Junior penetration tester (entry level)
- Junior penetration tester with two years of authorised web application and internal network testing for client engagements. Has worked on 26 scoped assessments and found 9 critical issues.
- Senior penetration tester (mid level)
- Senior penetration tester with seven years of authorised application, cloud and Active Directory testing. Leads assessments for a consultancy's financial clients and has delivered about 120 reports.
- Principal penetration tester (senior)
- Principal penetration tester with 14 years of authorised testing for banks, insurers and retailers. Leads a team of 11 and has delivered more than 300 client reports.
| Instead of | Write |
|---|---|
| Passionate ethical hacker who loves breaking into systems. | Penetration tester with seven years of authorised application and cloud testing, leading assessments for financial clients and delivering about 120 reports. |
Words like "hacker" and "breaking into" make a hiring manager wonder about permission. "Authorised" in the first line settles it.
Summary or objective?
Anyone with testing work behind them, including an internship or supervised placement, should use a summary.
Graduates and career changers can write an objective, for example: "Cybersecurity graduate seeking a junior penetration testing role; completed 40 lab machines and wrote two practice reports in a client format."
Resume headline examples
Testing roles are often split between web, network, cloud and red team work, so put your areas next to your title.
- Junior Penetration Tester | Web, network, Burp Suite, reporting (Entry)
- Senior Penetration Tester | Application, cloud, Active Directory (Mid)
- Application Security Tester | OWASP, APIs, Burp Suite Professional (Web)
- Principal Penetration Tester | Red team, assurance, team leadership (Senior)
Experience bullets that show results
Give the scope of each test and what you found, then what the client fixed. Keep client details out.
| Instead of | Write |
|---|---|
| Performed penetration tests. | Completed 26 scoped web application and internal network assessments for clients under signed rules of engagement. |
| Found vulnerabilities. | Found a broken access control flaw in a payments API exposing 18,000 customer records, reported it within an hour, and saw it fixed in two days. |
| Wrote reports. | Cut report turnaround from 10 working days to 6 by standardising templates and evidence capture. |
| Helped clients fix issues. | Retested fixes for 85% of critical findings within 30 days, giving clients proof of closure for audits. |
| Pushed clients to fix faster. | Cut the median time to fix critical findings from 48 days to 19 by agreeing severity targets with engineering leads. |
| Did web tests. | Led 18 web application tests a year, finding 12 critical issues that clients fixed before launch. |
| Trained the team. | Built an internal lab and training plan that took four junior testers to OSCP within a year. |
Missing a number? Write a bracket now, such as "cut the run from [X] to [Y] minutes", and check the figure in your team's dashboards or tickets before you send. A bracket you can't fill means the bullet needs rewriting.
Bullet ideas by area
Bullets for the work most often hired for. Swap in your figures where the brackets are and keep only the work you have done.
Scope and authorisation
- Agreed scope, test windows and emergency contacts with [X] clients, with [Y] out-of-scope incidents
- Built a [tool] that checks targets against the scope list, preventing out-of-scope scanning on [X] engagements
Findings and reporting
- Found [X] critical and [Y] high-severity issues across [Z] assessments, each with a reproducible proof of concept
- Delivered [X] reports with [CVSS or other rating] and fix guidance, reviewed by [role] before release
Fixes and leadership
- Retested [X] fixes and confirmed [Y] as closed within [Z] days
- Trained [X] testers on [reporting or method] and reviewed [Y] reports
Engagements
- Led [X] [type] tests a year with [Y] critical findings
- Cut report turnaround from [X] to [Y] days with [template or tool]
Skills and keywords for a penetration tester resume
Sort the tools and standards by testing area, and keep only those you could use on a scoped engagement this week.
Testing
Web and API testing, Internal network testing, Active Directory, Cloud assessments, Red team operations
Tools
Burp Suite, Nmap, Metasploit, BloodHound, Impacket, NetExec, Nessus
Standards
OWASP Top 10, OWASP ASVS, MITRE ATT&CK, CVSS, NIST SP 800-115
Languages
Python, Bash, PowerShell, SQL
Practices
Scoping, Rules of engagement, Report writing, Retesting
Matching the penetration tester job description
Ads stress an area: web, network, cloud, mobile or red team. Lead with engagements in that area.
Name the tools and methods the ad lists, such as Burp Suite or Active Directory attacks, where you've used them.
If the ad mentions reporting or clients, lead with report quality and client results.
Certifications and how to list them
No licence is needed. Some testing employers ask for OSCP, and Security+ is a common baseline for security jobs. Many employers prefer candidates with security certification. Put engagement and report bullets first and the certificate after.
| Credential | Earned | In progress |
|---|---|---|
| OffSec Certified Professional (OSCP)OffSec | OffSec Certified Professional (OSCP), OffSec, [year] | PEN-200 course in progress; exam scheduled for [month year] |
| CompTIA Security+CompTIA | CompTIA Security+, CompTIA, [year] | Exam scheduled for [month year] |
- OffSec Certified Professional (OSCP): A 24-hour proctored exam: you exploit and report on live lab systems, including three standalone machines and an Active Directory set. OSCP doesn't expire; OSCP+ lasts three years. OffSec, PEN-200 and OSCP
- CompTIA Security+: A common baseline for security jobs. CompTIA revises the exam every few years, and V8 arrives in November 2026, so check which version you're booking. CompTIA, Security+
Certificate, degree or master's: what helps a penetration tester
The closest occupation is information security analyst, which typically needs a bachelor's degree in computer and information technology or a related field. Some enter with a high school diploma plus industry training and certifications, and many worked in IT first, often as systems administrators.
Hands-on certificates matter most in testing, because exams like OSCP are attacks on live lab systems. OSCP is the best known, and specialised certificates cover web, cloud and red team work.
A master's in cybersecurity or information assurance helps for research and leadership roles. Security analysts may advance to chief security officer or another computer and information systems manager job. Some organisations require or prefer a graduate degree for those jobs, and an MBA fits that route.
While you study, write "OSCP, PEN-200 in progress, exam [month year]", and add the year once you pass.
Penetration Tester resume with no experience
Testing firms hire juniors on proof of method, so show work they can check: lab machines completed, a practice report written in a client format, and accepted bug bounty findings. Earlier IT or development jobs count too.
- Give capture-the-flag results and lab platforms you've completed.
- Write up one authorised lab test as a sample report.
- List bug bounty findings that were accepted, without sensitive details.
- Add Security+ or OSCP once earned.
- List IT, development or sysadmin work.
Moving up: tester, senior, principal
Penetration tester. Open with the kinds of engagements you've worked on and your most serious finding, described by type and severity.
Senior penetration tester. You run engagements. Give the tests you scoped and led, how many reports went out under your name, and the testers you train.
Principal tester. Lead with what you've built for the practice, such as a testing method or an internal tool, then research, talks and the team you run.
Penetration tester resume format and length
One page suits most testers. Principal testers can use two if the second page adds relevant engagements or leadership.
Use a plain layout that screening software can read, and never include client names, hostnames or findings that are covered by confidentiality.
Questions
What should a penetration tester resume include?
Your areas, tools and methods, engagements completed, serious findings by type and severity, report quality and retests. Show every test was authorised and scoped. Add certificates with the year, and research or talks if you have them. Never name clients without permission.
How do I show scope and authorisation?
Describe engagements by type and scope: "authorised external and internal tests for 12 clients a year". Mention rules of engagement and reporting. Never describe testing you weren't authorised to do, even as a learning example, because it tells an employer you might do it on their clients.
Can I name clients or describe their findings?
Usually not. Most contracts forbid it. Describe clients by sector and size, and findings by type and severity: "critical authentication bypass in a payments platform for a large retailer". Ask your employer what you may share before naming anyone. Some firms allow named case studies for clients who agreed to it, and those are worth asking about.
Should I list bug bounty work?
Yes, with accepted findings by type and severity, and the platform. Don't share details of unpatched issues. Bug bounty shows initiative and skill, especially early in your career. Pair it with structured testing work, since employers also want method and reporting.
How do I show reporting skill?
Give report volume and quality: reports written, turnaround time, findings clients fixed and retests passed. Mention templates you improved or executive summaries you wrote. Offer a sample report from an authorised lab test, never a client's report. The client only sees the report, so firms read your writing closely.
Do I need a degree to be a penetration tester?
Not always. Information security analysts typically need a bachelor's degree, but some enter with a high school diploma plus industry training and certifications. Testing leans on hands-on skill, so certificates and lab work can make up for a missing degree.
Is a master's or MBA worth it for a penetration tester?
Rarely for testing itself, where hands-on skill and certificates count most. A master's in cybersecurity helps if you're aiming at research. An MBA is worth it only on the way to running a security practice or a CISO job. Most testers who move up do it through leading engagements first.
How do I show I'm ready for senior or principal?
Show that clients and colleagues rely on you: engagements you scoped and led, testers you trained, and a tool or method the team now uses. Research and talks help for principal. Shrink early roles to a line each to make room.