( . Job Description : Summary Lead Solutions Design Engineers are responsible to support the growth of our Supply Chain Solutions... ..., Transportation Management Systems ie; JDA, OTM, , Mapping Software ie; Tableau exp…
Engineering & IT · Oklahoma City, OK
Software Engineer jobs in Oklahoma City, OK
Software engineers design, build, and maintain the applications and systems behind modern products. The work spans writing code, reviewing designs, and keeping software reliable as it grows.
211
Open roles today
$32–$86/hr
Typical pay range
$113k
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 software engineer roles
12 shown of 211 · sorted by freshness
ABOUT THE JOB As a Principal Software Engineer V (UAV Embedded), you will architect and implement mission-critical software for our next-generation UAV flight computers. You will be the primary link between complex fligh…
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…
GovCIO is seeking a Senior Azure Cloud Architect to lead the HDR infrastructure on Azure Government. The role focuses on architecture, reliability, security, and modernization across production, DR, and non-production en…
Job Description Job Description Allied High Tech Products is seeking a Software Controls Engineer for our Oklahoma City R&D facility. This role will work with software, mechanical, electrical, and materials engineering t…
$60 - $65 per hour
NET Full-Stack Developer Industry: Technology Consulting / Software Development Location: Remote (Oklahoma residents only; occasional... ...Required: Bachelor's degree in Computer Science, Engineering, or equivalent prof…
Cloud Services Engineer (Morpheus) - Active Secret Clearance Required Location: Hybrid (Remote with up to 50% travel to DISA locations... ...and public cloud platforms Implement and maintain Software- Defined Networking…
$110k - $120k
Job Description Job Description Cloud Engineer (AWS / Terraform) Location: Oklahoma City, OK (Hybrid -onside 3 days a week) Compensation: $110,000–$120,000 DOE (no annual bonus) plus medical, dental, vision, PTO Direct H…
$70k - $90k
Overview Our client is seeking a Data Solutions Developer to join their technology team in Oklahoma City. This role combines software development, data integration, reporting, and analytics to support business operations…
Immediately Welcome to Love's: Our Cloud Platform Operations Engineer is responsible for the day-to-day operation, stability, and... ...or a related discipline such as Information Technology, Software Engineering, or Com…
This Senior Software Application Developer/Architect position supports the Department of Homeland Security (DHS), Customs and Border... ...~ Education: Bachelor’s degree in Computer Science, Software Engineering, or rela…
Church, our Digital Product team builds technology that helps people take their next step in their faith journey. As a Senior Software Engineer, you’ll design and build solutions that support the systems and platforms us…
02
What software engineers earn in Oklahoma City
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $32–$45 | $67k–$93k |
| Mid level | $45–$64 | $93k–$134k |
| Senior | $62–$86 | $129k–$178k |
Adjusted for the Oklahoma City market from national ranges.
03
What employers ask for
The skills these listings keep naming
Data structures and algorithmsSystem designGit and code reviewTesting and debuggingSQL and databasesAPIs and integrationCloud fundamentals (AWS/GCP/Azure)Clear written communicationCross-team collaboration
04
Interview questions worth rehearsing
With the thing the interviewer is actually listening for
Walk me through a project you built and the technical decisions behind it.
Pick one project and go deep. Explain the tradeoffs you weighed, not just the stack you used, and name one thing you would do differently now.
How would you design a URL shortener (or similar small system)?
Start with requirements and rough scale before drawing boxes. Interviewers care more about how you reason through storage, uniqueness, and reads versus writes than a perfect answer.
Tell me about the hardest bug you have debugged.
Describe your process: how you reproduced it, narrowed the cause, and confirmed the fix. A methodical story beats a dramatic one.
How do you decide when code is good enough to ship?
Talk about tests, review, and risk relative to the change. Showing judgment about tradeoffs matters more than claiming perfection.
Describe a time you disagreed with a teammate about a technical approach.
Show that you argued from evidence, listened, and committed to the outcome. Avoid stories where the point is simply that you were right.
How do you approach learning an unfamiliar codebase?
Mention concrete tactics: reading tests, tracing a request end to end, making a small safe change first. This signals you can become productive quickly.
What would you do if a production incident happened right before a deadline?
Prioritize stabilizing production and communicating early. Interviewers want calm triage, not heroics.
05
Resume tips that move the needle
For software engineers specifically — generic advice costs you here
01
Name the languages and frameworks per role or project, not just in a skills block, so screeners can match you to the stack.
02
Quantify outcomes in engineering terms: latency reduced, error rate cut, deploy time shortened, users served.
03
Link to a GitHub profile or portfolio only if the pinned work is recent and readable.
04
Describe your role on team projects precisely — 'built the payments service' reads very differently from 'worked on payments'.
05
Keep the tech list honest; anything on the resume is fair game in the interview.
06
For senior roles, show scope: systems owned, engineers mentored, decisions driven.
06
Where this role goes
Typical progression
01
Junior Software Engineer
02
Software Engineer
03
Senior Software Engineer
04
Staff Engineer
05
Principal Engineer
Ten quiet minutes a day
Applying for software 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.