Penetration tester with nearly 7 years of offensive security experience across web applications, internal networks and Active Directory for clients in healthcare, retail and finance. Delivered 120+ engagements, including domain compromise paths that drove client segmentation projects. Brings methodical testing, clean exploit documentation and remediation guidance developers can act on.
Experience
Penetration Tester, Redline Assurance Group (Tulsa, OK)
Jun 2022 – Present
Lead 30 engagements a year across external, internal, web and wireless scopes for clients with up to 15,000 employees
Chained Kerberoasting and ADCS misconfigurations to reach domain admin in 70% of internal tests, prompting tiered admin redesigns
Wrote reports with step-by-step reproduction and prioritized fixes, earning a 4.8/5 client satisfaction average
Built a BloodHound and Python reporting pipeline that trimmed report drafting time by 30%
Associate Security Consultant, Summit Ridge Cyber (Oklahoma City, OK)
Jan 2020 – May 2022
Performed OWASP-based web application tests for 45 clients using Burp Suite Pro
Ran PCI DSS segmentation tests for 12 merchants, validating cardholder data isolation
Network Technician, Mapleton Public Schools (Tulsa, OK)
Jul 2018 – Dec 2019
Maintained switches and wireless for 14 school buildings serving 9,000 students
Education
B.S. Cyber Security, The University of Tulsa (Aug 2014 – May 2018)
Skills
Offensive Tools: Burp Suite Pro, Metasploit, Cobalt Strike, BloodHound, Impacket
Testing Scope: Web apps, APIs, Active Directory, internal and external networks, wireless
Scripting: Python, PowerShell, Bash
How to write a Penetration Tester resume
A strong Penetration Tester resume shows the systems you built, the scale they run at, and the measurable effect on speed, reliability or cost. Put your most relevant recent role first and make every bullet show a result, not a duty.
Sections, in order
Summary
Experience
Projects
Skills
Education
Length: One page for most candidates; move to two only if every line is relevant.
Summary: Write two or three lines: your role, your strongest skills, and one result that proves them.
Skills to feature
Programming languages
System design
Cloud platforms (AWS, GCP, Azure)
CI/CD
Testing and code review
Databases and SQL
Observability
Security fundamentals
APIs and integrations
Technical documentation
Example bullet points
Rebuilt the checkout service in Go, cutting p95 latency from 900 ms to 180 ms for 2M monthly users
Introduced contract tests and staged rollouts, reducing production incidents by 45% in two quarters
Migrated 30 services to Kubernetes with Terraform, lowering cloud spend by $250k a year
Tips from recruiters
Group skills by category (for example "Languages: Go, TypeScript") so recruiters and ATS parsers find them quickly.
Link to a repository, demo or write-up for at least one project you can talk about in depth.
Name the stack inside each bullet; keyword matching happens at the bullet level, not only in the skills list.
Recommended templates
Classic (ATS-friendly): Jake's-style LaTeX classic: small caps and hairline rules
Tech (ATS-friendly): Developer style: mono headings and tags, sans body
Modern (ATS-friendly): Clean single column with accent headings and rules
Penetration Tester resume FAQ
What should a Penetration Tester resume include?
A Penetration Tester resume should show the systems you built, the scale they run at, and the measurable effect on speed, reliability or cost. Use these sections in this order: Summary, Experience, Projects, Skills and Education. Put your most relevant recent role first and make every bullet show a result, not a duty.
What is the best resume template for a Penetration Tester?
Classic, Tech and Modern work well for Penetration Tester roles. They are single-column with standard headings, so applicant tracking systems (ATS) parse them reliably.
How long should a Penetration Tester resume be?
One page for most candidates; move to two only if every line is relevant.
Which skills should a Penetration Tester put on a resume?
Prioritize the skills named in the job posting. Common ones for Penetration Tester roles are Programming languages, System design, Cloud platforms (AWS, GCP, Azure), CI/CD, Testing and code review and Databases and SQL.
How do I write strong Penetration Tester resume bullet points?
Start with an action verb, say what you did, and end with a measurable result such as latency, uptime and deploy frequency. For example: "Rebuilt the checkout service in Go, cutting p95 latency from 900 ms to 180 ms for 2M monthly users."