We are a large growing MEP Design Engineering company in Oklahoma that works on many of Oklahoma’s biggest and best commercial electrical engineering and design projects. This is a full-time position with great salary an…
Engineering & IT · Oklahoma City, OK
Security Engineer jobs in Oklahoma City, OK
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.
63
Open roles today
$34–$90/hr
Typical pay range
$118k
Median, full-time
6
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 63 · sorted by freshness
and create automation scripts to streamline assessments and reporting in a remote, deadline-driven environment. The role requires scripting experience (Python/PowerShell), knowledge of cloud and security standards, and t…
Cohesity, a leader in AI-powered data security, seeks a Sr Sales Engineer to enable enterprise sales engagements across security, data protection, and cloud tech. You’ll support opportunities end-to-end, engage diverse t…
Job Description Job Description Position Summary The Director of Network Engineering is responsible for the planning, design, implementation, optimization, and lifecycle management of the company's fiber broadband networ…
$80k - $100k
Job Title: Network Engineer Location: Oklahoma City, OK Assignment Type: Direct Hire | Full-Time Pay: $80,000 - $100,000... ...designing and improving network environments while maintaining secure, reliable connectivity…
$50 - $60 per hour
Description The M&A End User Migration Engineer is responsible for hands-on migration of acquired company employees into the end-user... ...• Troubleshoot user migration issues and escalate to endpoint, security, messagi…
At MKEC, it's all about our team. We're passionate about our mission of providing superior engineering solutions that are responsive to our clients' needs. Since our start in 1982, our growth has been fueled by respect f…
Cloud Services Engineer (Morpheus) - Active Secret Clearance Required Location: Hybrid (Remote with up to 50% travel to DISA locations... ...Travel: Approximately 50% Employment Type: Full-Time Security Clearance: US cit…
$100 per hour
The Quality Engineer is responsible for developing, applying and maintaining procedures to ensure quality assurance (QA) and quality control (QC) of products, assets, and materials and supplies. The Quality Engineer has…
$65k - $75k
Job Title: Project Engineer Pay Rate: $65,000-$75,000 yearly Location: Oklahoma City, Oklahoma 73110 Area Code: 405 Shift: 1st Employment... ...data analysis and visualization. * Possession of a Secret Security Clearance…
Developer/Architect position supports the Department of Homeland Security (DHS), Customs and Border Protection (CBP) in the area of... ...~ Education: Bachelor’s degree in Computer Science, Software Engineering, or relat…
$100k - $150k
Job Title: Mechanical Engineer PE Location: Oklahoma City, OK Type: Direct Hire Compensation: $100,000 - $150,000 Contractor Work Model: Hybrid – onsite and remote Overview The Mechanical Engineer PE applies standard eng…
02
What security engineers earn in Oklahoma City
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $34–$47 | $71k–$98k |
| Mid level | $47–$66 | $98k–$138k |
| Senior | $64–$90 | $134k–$187k |
Adjusted for the Oklahoma City 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 Oklahoma City?
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.