and inclusive, with great opportunity for professional growth. Find your future with us. The Boeing Company is seeking a Software Engineer (Experienced or Senior) with an Active Top Secret Security Clearance to support o…
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.
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.
Open software engineer roles
12 shown of 350 · sorted by freshness
speed, flexibility, and ingenuity to strengthen and protect our nation’s vital interests. Requisition #: 1520 Job Tittle: Software Engineer III Location: St. Louis, MO Clearance: Secret Required Certification: CompTIA Se…
life. Since 2016 Total Expert has enabled more than seven trillion dollars of funded loan volume. The role We’re hiring Software Engineers who build production software through AI coding agents and design the system that…
of-the-art solutions as part of Team Rapsodo. About the Role We are looking for a curious, resourceful, and hands-on Software Engineer to join our Rapsodo Operating System (ROS) team in St. Louis, Missouri. You will help…
About Us:Temu is seeking highly motivated and experienced Software Engineers to join our team. As a rapidly growing company, we are looking for talented individuals committed to helping us achieve our goals. In this role…
layouts, diagrams, charts, code comments and clear code. Develop software solutions by studying information needs; studying systems flow,... ...recommendations to the program manager and Chief Software Engineer. Coordina…
Overview Help build and scale the deployment platforms that power mission critical software. As a Software Development Engineer II focused on CI/CD and platform automation, you will design and implement tools, pipelines,…
backend systems that power mission critical geospatial applications supporting Defense and Intelligence operations. As a Software Development Engineer II, you will design and develop scalable backend services and APIs th…
Overview Are you ready to launch your career by building software that makes a real-world impact? As a developer on our team, you... ...while contributing to projects that matter. You’ll work alongside engineers and ment…
trusted mobility company Enterprise Fleet Management an affiliate of Enterprise Mobility is excited to announce the opening of a Engineer 2 Software. The Information Technology (IT) department of Enterprise Fleet Managem…
solutions for Defense, Intelligence, and Federal clients. We enhance situational awareness for soldiers and analysts by integrating software development with geospatial intelligence. Our projects range from data collecti…
Scale AI is seeking a highly skilled and motivated Software Engineer, ARC (Architecture, Reliability, & Compute) to join our dynamic Public Sector Engineering team. As a part of this team, you will define how the company…
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.
What employers ask for
The skills these listings keep naming
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.
Resume tips that move the needle
For software engineers specifically — generic advice costs you here
Name the languages and frameworks per role or project, not just in a skills block, so screeners can match you to the stack.
Quantify outcomes in engineering terms: latency reduced, error rate cut, deploy time shortened, users served.
Link to a GitHub profile or portfolio only if the pinned work is recent and readable.
Describe your role on team projects precisely — 'built the payments service' reads very differently from 'worked on payments'.
Keep the tech list honest; anything on the resume is fair game in the interview.
For senior roles, show scope: systems owned, engineers mentored, decisions driven.
Where this role goes
Typical progression
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.