Software Engineer vs Penetration Tester: Which Pays More?
Side-by-side salary comparison by city, experience level, and career growth outlook. Data reflects current market rates.
Software Engineer
Design, develop and maintain software systems and applications.
Penetration Tester
Conduct authorised attacks on systems to find and report vulnerabilities.
Software Engineer earns more on average — the national median is $6,800/year (5%) higher than a Penetration Tester. However, salaries vary significantly by city, employer, and experience level — see the city-by-city breakdown below.
Software Engineer vs Penetration Tester — Salary by City
National median figures in USD across top cities.
| City | Software Engineer | Penetration Tester | Difference |
|---|---|---|---|
| San Francisco, CA | $194,950 | $193,496 | Software +$1,454 |
| New York, NY | $166,830 | $140,470 | Software +$26,360 |
| Seattle, WA | $189,468 | $188,841 | Software +$627 |
| Austin, TX | $148,834 | $145,769 | Software +$3,065 |
| Chicago, IL | $149,966 | $135,251 | Software +$14,715 |
| Boston, MA | $176,542 | $171,501 | Software +$5,041 |
| London, UK | £73,942 | £102,480 | Software $28,538 |
| Toronto, Canada | CA$126,152 | CA$166,911 | Software $40,759 |
Frequently Asked Questions
Does a Software Engineer or Penetration Tester earn more?+
A Software Engineer earns more on average. The national median salary for a Software Engineer is $135,980/year, compared to $129,180/year for a Penetration Tester — a difference of $6,800 (5%).
Which has better career growth — Software Engineer or Penetration Tester?+
Software Engineer roles are growing at 25% YoY while Penetration Tester demand is growing at 30% YoY. Penetration Tester has stronger near-term demand growth.
Can you switch from Software Engineer to Penetration Tester?+
Yes. Many professionals transition between these roles, especially since both are in the same category. Shared skills include: Python.
Which is harder to automate — Software Engineer or Penetration Tester?+
Penetration Tester has a lower AI automation risk (22% vs 48%). Based on Oxford Martin School and McKinsey 2023 analysis.