Skip to content
TryHired.
Job titles · Security

Application Security Engineer: security built into the code, not bolted on

What AppSec engineers do with development teams, how the work differs from security operations, and how developers and penetration testers move into it.

Updated Nov 14, 2026 · Sources: OWASP, ISC2, O*NET 31.0
Quick answer

An application security engineer helps development teams build software that resists attack. The work includes reviewing designs and code, running and tuning security testing in the build pipeline, triaging findings from scanners, bug bounties and penetration tests, and teaching developers to fix whole classes of bugs. The fastest route in is usually from software development or penetration testing, because the job needs both coding and attacker thinking.

The job

What an Application Security Engineer does

Our view

AppSec sits inside the software lifecycle. Instead of watching networks for intrusions, the engineer works with product teams on threat models, secure coding standards and the tools that check code before it ships. A good AppSec engineer makes the secure way the easy way, so developers adopt it without a fight.

Credibility with developers is the core asset. AppSec engineers who can read a pull request, explain exactly why it is vulnerable and propose a fix that fits the codebase get listened to; those who only forward scanner output do not.

  • Threat-modelling a new feature with the team building it and agreeing on mitigations.
  • Reviewing high-risk pull requests and the findings from static and dynamic analysis tools.
  • Tuning scanners so they report real problems and stay quiet about noise.
  • Triaging a bug-bounty or penetration-test report and helping the owning team fix the root cause, not just the instance.
  • Running short secure-coding sessions built around bugs the company has actually had.

O*NET lists Application Security Engineer as a job title under Information Security Engineers (15-1299.05). That occupation covers wider work, so the O*NET section below describes the whole occupation; the rest of this page is specific to the title.

What's different

AppSec engineer vs security analyst and penetration tester

Our view
  • Security analysts typically monitor and respond to incidents; AppSec engineers work upstream, before code ships.
  • Penetration testers find vulnerabilities in a time-boxed test; AppSec engineers stay with teams and prevent the next ones.
  • The job needs real programming fluency in the languages the company uses, not only security knowledge.
  • Success is measured in vulnerabilities prevented and fixed, and in how quickly teams fix what is found.
How to get in

How to become an Application Security Engineer

Advice
  1. Start from development or testing. Developers who learn security and penetration testers who learn development both fit well.
  2. Study the common web vulnerability classes and practise finding them in deliberately vulnerable training applications.
  3. Add security checks to a real pipeline, then learn to separate real findings from noise.
  4. Volunteer for security work in your current team: dependency updates, threat models, code reviews of authentication or input handling.
  5. Write up what you find clearly, with risk and fix; written communication is half of the job.
Tools and skills

What Application Security Engineers work with

Advice
  • Static analysis and dependency scanners integrated into CI, and the judgment to tune them.
  • Dynamic testing and proxies for web applications and APIs.
  • Threat modelling methods and simple diagrams teams can maintain.
  • Code reading in the company's main languages and frameworks.
  • Identity and session knowledge: authentication, authorization and secrets handling, where many serious bugs live.
  • Teaching and influence: short, practical guidance developers can apply the same day.
O*NET data

What O*NET says about Information Security Engineers

Data

The data below describes the whole O*NET occupation Information Security Engineers (15-1299.05), not application security engineers specifically. Use it to see what the wider occupation is rated on; the sections above describe what is different about this title.

Core tasks O*NET rates highest in importance for Information Security Engineers
#Task (O*NET wording)
1Identify security system weaknesses, using penetration tests.
2Coordinate monitoring of networks or systems for security breaches or intrusions.
3Assess the quality of security controls, using performance indicators.
4Train staff on, and oversee the use of, information security standards, policies, and best practices.
5Scan networks, using vulnerability assessment tools to identify vulnerabilities.
Skills O*NET rates highest in importance for Information Security Engineers
SkillImportance (1–5)
Reading Comprehension4.12
Critical Thinking4.00
Active Listening3.88
Writing3.62
Monitoring3.62
Speaking3.50

In-demand technology named by O*NET for this occupation: Amazon Web Services AWS software, Bash, IBM Terraform, Kubernetes, Linux, Microsoft Active Directory, Microsoft Azure software, Microsoft PowerShell.

Education reported by workers in this occupation (O*NET survey): Bachelor's Degree 47.4%; Post-Secondary Certificate 15.8%. These shares describe the whole occupation; they are not a requirement for this title.

O*NET 31.0 Database, U.S. Department of Labor, Employment and Training Administration (USDOL/ETA), used under the CC BY 4.0 license. TryHired selected, ranked and combined the data; O*NET is not responsible for these pages.

Credentials

Credentials and licenses, from the issuers

Data
  • The OWASP Top 10, published by the OWASP Foundation, is a standard awareness document for developers and web application security that many AppSec programs build training around.
  • OWASP lists the 2025 edition as its latest released version, so check which edition a course or employer refers to.
  • ISC2's CSSLP credential covers security practices, including authentication, authorization and auditing, throughout the software development lifecycle, and ISC2 lists four years of required work experience.
  • Broader security credentials are covered in the Security+, CEH and CISSP guides.

Certifications are optional unless an employer or regulator says otherwise; read the posting, and check eligibility on the issuer's own site before you apply.

Career moves

Where this role leads

Advice
Pay

What Application Security Engineers earn

Data

TryHired does not print a salary for application security engineers. The U.S. Bureau of Labor Statistics publishes pay for occupations, not job titles, so the closest official figures are for the wider occupation. For the official numbers, see information security engineer salary: those figures cover all Computer Occupations, All Other (BLS 15-1299), not application security engineers specifically.

Pay for this title depends on employer, industry, region and level, so ask how the role is graded and compare offers against the posting's own range where one is published.

Get hired

Applying for Application Security Engineer jobs

Advice
  • Show code-level evidence: vulnerabilities you found or fixed, tools you integrated and tuned, guidance you wrote.
  • Expect to review a vulnerable snippet live and explain the fix and its trade-offs.
  • Name the languages and frameworks you can read, since AppSec teams support specific stacks.
  • Mention responsible-disclosure or bug-bounty work only if you can discuss it accurately.

Two free tools start from this job title, so you only add your own experience: draft a resume summary for an Application Security Engineer role or write a LinkedIn headline for an Application Security Engineer role. Neither fills in skills or results for you: list only the work you have actually done.

Disclosure: TryHired makes HIRED, a paid job-search program, so we have a conflict of interest when we mention it. Everything on this page is free to use without buying anything.

Related titles

Other job titles in this group

FAQ

Questions people ask

What does an application security engineer do?
Works with development teams to prevent, find and fix security flaws in software, from design reviews to pipeline scanning.
Is AppSec a good path for developers?
Often, because the job needs the ability to read code and propose fixes developers will accept.
What is the OWASP Top 10?
A standard awareness document from the OWASP Foundation about critical web application security risks; the current edition is 2025.
Method

How this page is built

Facts about exams, credentials, licensing and agencies are paraphrased from the issuers' and agencies' own pages, saved on the read date shown; each one maps to a short verbatim quote in this page's claims ledger. The job, difference, path, tools and hiring sections are TryHired's explanation and advice, labelled as such. The O*NET section shows O*NET 31.0 data for the broader occupation and says so. TryHired does not print pay for job titles that BLS does not publish separately.

What this page can't tell you
  • Pay for this title: BLS publishes occupations, not titles.
  • Whether a particular employer requires a degree, a certification or a license for this title.
  • How a specific company levels or names this role.
Sources
  1. OWASP Foundation, “OWASP Top Ten”, read Nov 14, 2026.
  2. ISC2, “CSSLP – Certified Secure Software Lifecycle Professional”, read Nov 14, 2026.
  3. O*NET 31.0 Database, U.S. Department of Labor, Employment and Training Administration (USDOL/ETA), used under the CC BY 4.0 license. TryHired selected, ranked and combined the data; O*NET is not responsible for these pages.
  4. U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics (via the linked TryHired salary page)