What You’ll DoAs a Senior Principal Network Reliability Engineer, you will:Provide technical leadership for the deployment, operation, and lifecycle management of OCI’s global network infrastructure.Define and drive the…
Engineering & IT · Seattle, WA
Security Engineer jobs in Seattle, WA
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.
207
Open roles today
$48–$126/hr
Typical pay range
$166k
Median, full-time
10
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 207 · sorted by freshness
$118.3k - $188.6k
Position Summary: The Senior Information Security Engineer will be responsible for the ongoing development, implementation, and support of security strategies that strengthen PI’s enterprise, cloud, and artificial intell…
$159.3k - $202.4k
to no-checkout retail, we push the boundaries of technology in every direction using the globe’s largest AWS deployment.As a Security Engineer, you will collaborate with software development teams to ensure we keep our c…
$175k - $227.5k
live inside our own environment and the risks that come in through every vendor and partner we rely on. We're looking for a Sr. Security Engineer I to own our Security Risk Management program end-to-end—running risk iden…
$161k - $221k
Secure Every Identity, from AI to Human Identity is the key to unlocking the potential of AI. Okta secures AI by building the trusted... ...business or erode our customers’ trust. The Defensive Cyber Engineering organiza…
hardware with innovative and deployable solutions.Minimum Qualification(s)- Bachelor or higher degree in computer science, electronic engineering, network engineering or related fields.- Proficiency in computer network a…
$173.4k - $234.6k
Senior Product Security Event Detection EngineerCompany:The Boeing CompanyBoeing is seeking a Product Security Event Detection Engineer (Level 4) to join the Risk Management Capability team onsite in Seattle, WA or Evere…
$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…
specialized Information Technology support for our strategic business partners within the client Corporate Center. Job Title: IAM Security Engineer Location: Seattle, WA, 98101 Duration: 3 Months Work Type: Onsite Job Ty…
ll have the autonomy and support to make an impact as we build for the long term. About the role Samsara Security is looking for a Senior Threat Detection Engineer. This is a hands-on engineering role: you will build and…
$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…
$110k - $165k
Company Founded by CPAs, tax attorneys, and engineers, Taxbit is the leading innovator automating global tax reporting for the digital... ...Singapore. #### Opportunity for Impact The Corporate Security Engineer is a cri…
02
What security engineers earn in Seattle
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $48–$66 | $100k–$138k |
| Mid level | $66–$93 | $138k–$194k |
| Senior | $90–$126 | $188k–$262k |
Adjusted for the Seattle 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 Seattle?
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.