Security engineer with 9 years of experience securing cloud-native SaaS platforms across detection, hardening and secure development. Cut critical vulnerabilities open past SLA by 85% through automated remediation workflows. Brings hands-on AWS security, threat modeling and the ability to make secure defaults easy for developers.
Experience
Senior Security Engineer, Ledgerline Software (San Francisco, CA)
Apr 2022 – Present
Built automated vulnerability triage linking Wiz findings to service owners, cutting criticals past SLA by 85%
Rolled out SSO and hardware-key MFA for 1,100 employees, eliminating phishable credentials for production access
Led threat models for 12 new features, adding controls before launch rather than after pentest findings
Owned SOC 2 Type II technical controls, closing the audit with no exceptions two years running
Security Engineer, Quarry Peak Labs (Oakland, CA)
Jun 2019 – Mar 2022
Deployed GuardDuty and Security Hub across 45 AWS accounts with Slack-routed alerts
Wrote Semgrep rules for injection and secrets, blocking 200+ risky commits in the first year
Systems Engineer, Bayline Networks (San Jose, CA)
Jul 2017 – May 2019
Hardened 400 Linux servers to CIS benchmarks using Ansible
Automated patching cycles, raising monthly patch compliance from 70% to 97%
Education
B.S. Computer Science, University of California, Davis (Sep 2013 – Jun 2017)
A strong Security Engineer 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
Security Engineer resume FAQ
What should a Security Engineer resume include?
A Security Engineer 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 Security Engineer?
Classic, Tech and Modern work well for Security Engineer roles. They are single-column with standard headings, so applicant tracking systems (ATS) parse them reliably.
How long should a Security Engineer resume be?
One page for most candidates; move to two only if every line is relevant.
Which skills should a Security Engineer put on a resume?
Prioritize the skills named in the job posting. Common ones for Security Engineer 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 Security Engineer 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."