$211k - $251k
per year Requirements: Strong background in web application security, cloud security (AWS, Azure, or GCP), and networking... ...primitives into our product and platform. Work closely with engineering, product, and GRC te…
Engineering & IT · San Francisco, CA
Security Engineer jobs in San Francisco, CA
Security engineers protect systems and data by finding vulnerabilities, building defenses, and responding to incidents. The work spans application security, infrastructure hardening, and threat detection.
353
Open roles today
$54–$141/hr
Typical pay range
$186k
Median, full-time
5
Fresh in this list
No email, no resume, no sign-up. Save any listing below and you start anonymously.
You're signed in. Saving a listing drops it straight into your pipeline.
01
Open security engineer roles
12 shown of 353 · sorted by freshness
$189k - $255.5k
continuing to invest heavily in building the best creator platform with the best team in the creator economy and are looking for a Security Engineer to support our mission.This role is Fully Remote (US only), or can be b…
Responsibilities Design, build, and tune threat detections across Google Security Operations. Lead sophisticated and high-severity incident-... ...tools such as Claude Code and OpenAI Codex for detection engineering and…
$159.2k - $301.6k
About the roleAdobe’s Security Data Platform team builds and operates a petabyte-scale security data lakehouse that turns enterprise telemetry... ..., compliance, and security analytics.As a Staff Security Data Engineer,…
$134.5k - $265.1k
with resilience, grow with confidence, and proactively manage to secure success.Work you will do:As Privileged Access Management (PAM)... ...in Computer Science, Cyber Security, Information Security, Engineering, Informa…
job summary: We are seeking a proactive Security Engineer to join an operational security team acting as the bridge between automated scanning systems and product development teams. In this role, you will streamline thre…
Hi, we're Oscar. We're hiring a Senior Product Security Engineer 1 to join our Security Team. Oscar is the first health insurance company built around a full stack technology platform and a relentless focus on serving ou…
$300k - $320k
a whole. Our team is a quickly growing group of committed researchers, engineers, policy experts, and business leaders working together to build beneficial AI systems. About the Team The Security Engineering team's missi…
Our team is a quickly growing group of committed researchers, engineers, policy experts, and business leaders working together to build... ...sector — producing timely, actionable intelligence for Security Engineering st…
$170k - $205k
of a high-performing team that believes in each other, come build with us at Crusoe. About the Role: Crusoe is seeking a Security Engineer to join the Security Engineering team as the primary driver for implementing secu…
$156k - $213.6k
offices in New York, Washington D.C., London and Amsterdam. The Security Governance, Risk, and Compliance (GRC) team is part of Plaid’s... ..., and aligned with industry and regulatory expectations. GRC Engineering is ho…
$188.75k - $242.68k
13, the company is headquartered in San Francisco with offices in New York, Washington D.C., London and Amsterdam. Security Engineering is the engineering function inside the Plaid security org that focuses on developing…
02
What security engineers earn in San Francisco
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $54–$74 | $112k–$154k |
| Mid level | $74–$104 | $154k–$217k |
| Senior | $101–$141 | $210k–$294k |
Adjusted for the San Francisco market from national ranges.
03
What employers ask for
The skills these listings keep naming
Threat modelingOWASP and web app securityNetwork and cloud securityIncident responseScripting (Python, Bash)SIEM and detection toolingIdentity and access managementVulnerability managementExplaining risk to non-experts
04
Interview questions worth rehearsing
With the thing the interviewer is actually listening for
Walk me through how you would threat model a new feature.
Use a structure — assets, entry points, attacker goals — and show that you rank risks rather than listing everything. STRIDE is a fine scaffold if you actually apply it.
You find a critical vulnerability in production. What are your next steps?
Verify, assess exposure, contain, and coordinate disclosure and fix — with communication throughout. Panic-free process is the whole answer.
Explain a recent vulnerability class or breach and what you took from it.
Staying current is part of the job. Pick something real, explain the root cause simply, and connect it to a defense you would build.
How do you get developers to fix security issues they see as low priority?
Show empathy for delivery pressure: translate risk into business impact, make fixes easy, and build guardrails so the secure path is the default.
How would you secure a cloud environment from scratch?
Cover identity first, then network segmentation, logging, encryption, and automated policy checks. Saying 'IAM is where most cloud breaches start' shows you know the terrain.
What is the difference between authentication and authorization, and where do systems commonly get it wrong?
Define both crisply, then give a real failure mode like broken object-level authorization. The follow-through example is what distinguishes the answer.
Tell me about a security control you built or improved.
Describe the risk it addressed and evidence it worked — findings reduced, detection time improved. Controls without measurement are just hopes.
05
Resume tips that move the needle
For security engineers specifically — generic advice costs you here
01
Lead with concrete defensive wins: vulnerabilities remediated, detection coverage added, incident response times improved.
02
List relevant certifications (Security+, OSCP, CISSP) prominently; this field still screens on them.
03
Name the domains you cover — appsec, cloud security, detection — since 'security' alone is too broad to place you.
04
Mention responsible disclosures, CTF results, or published research if you have them; they are strong credibility signals.
05
Show you can work with engineers, not just audit them — secure code reviews, training, or paved-road tooling you built.
06
Where this role goes
Typical progression
01
Security Analyst
02
Security Engineer
03
Senior Security Engineer
04
Security Architect
05
CISO
Ten quiet minutes a day
Applying for security engineer jobs in San Francisco?
Robbi carries this page into your first day: your role, your city, your shift preference. Then it hands you a few small things each morning and keeps the pipeline honest.
Save what looks right here, then let Robbi hand you a few small things each morning and keep the follow-ups honest.
Start with this search
No email, no resume, no sign-up.
Open your tracker
Everything you saved is already there.