Role: Senior Software Engineer – Network Services / Proxy Development Employment: Contract Location: St. Louis, MO Skills: Strong hands-on development experience in Go or C is mandatory. - Candidates without demonstrated…
Engineering & IT · St. Louis, MO
Software Engineer jobs in St. Louis, MO
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.
231
Open roles today
$33–$88/hr
Typical pay range
$117k
Median, full-time
11
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 231 · sorted by freshness
$126.65k - $217.35k
Salary: $126,650 - 217,350 per year Requirements: Bachelors degree or equivalent required. At least 5 years of software engineering experience. At least 3 years of C++ experience. At least 2 years of experience with auto…
$100k - $140k
Software Engineer (Full-Stack Web) Location: Remote — must reside in CO, FL, IA, IL, KS, MO, NE, OH, or TN Travel Expectations: Once yearly - company offsite Salary : $100,000–$140,000 annually, depending on experience R…
$120k - $160k
process. ** About the Company We are an established software company with a long history of serving county and city governments... ...into a modern SaaS suite of integrated products. Our engineering organization supports…
$112.2k - $185.15k
candidates with the ability to troubleshoot and support legacy engineering tools, build scripts, and automation workflows We prefer... ...systems We prefer experience in mission systems, embedded software, simulation, or…
$56.67 per hour
job summary: Join Our Client in Creve Coeur, MO as a Software Engineer! Drive global innovation with an industry pioneer. We seek a pro with 5+ yrs exp in C#/Python/C++, robotics, machine vision, & hardware integration.…
$58 - $63 per hour
development, enhancement, and ongoing optimization of a complex enterprise ServiceNow platform. This role will focus on platform engineering, workflow automation, release management, configuration management, and AI-driv…
Associate Backend Software Engineer, Phantom WorksCompany:The Boeing CompanyThe Boeing Company is currently seeking an Associate Backend Software Engineer (Level 2) to lead our Model-Based Engineering (MBE) software team…
$126.65k - $171.35k
require at least 5 years of experience developing and debugging software in high-level programming languages such as C or C++. We... ...For Level 3 consideration, we prefer a bachelors degree in engineering, engineering…
$126.65k - $217.35k
Top Secret security clearance; a clearance active within the past 24 months is considered active. We require 5+ years of software engineering experience. We require 5+ years of experience with Java and/or C++ object-orie…
$160.65k - $217.35k
We require 9+ years of experience with embedded systems and/or software development in C or C++. We require 3+ years of experience... ...weapons, or mission systems. We prefer a bachelors degree in engineering, engineeri…
expertise to protect our country from threats. Job Description Transform technology into opportunity as a Citrix Software Virtualization Engineer with GDIT. A career in enterprise IT means connecting and enhancing the sy…
02
What software engineers earn in St. Louis
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $33–$47 | $69k–$97k |
| Mid level | $47–$66 | $97k–$138k |
| Senior | $64–$88 | $133k–$184k |
Adjusted for the St. Louis 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 St. Louis?
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.