Position Summary Lead Cloud Infrastructure Engineer II - Workplace Engineering/M365 AI & Engineering helps organizations build, deploy, and operate integrated solutions across software, data, AI, networks, and hybrid clo…
Software Engineer jobs in Kansas City, 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
9 shown of 346 · sorted by freshness
space, advanced facilities, and an environment conducive to productivity and growth.Role OverviewThe Senior Information Security Engineer will be a part of Cboe’s Security Engineering and Operations Team to manage, deplo…
impact, and OT safety and availability constraintsCoordinate remediation efforts with IT infrastructure, application owners, plant engineers, and operations teams, ensuring clear ownership and trackingApply risk-based vu…
team connection, this role follows a four day in office work model. Role OverviewCboe Data Vantage is looking for an experienced software engineer who is excited about combining strong engineering skills with financial q…
strong partnership and team connection, this role follows a four day in office work model.Role Overview We are seeking a Senior Cloud Engineer for Cboe’s Cloud Operations team. The Cloud Operations team is responsible fo…
While the internal title for this position is Senior Automation Engineer, this role has been posted externally under a different title... ...trust principles, and secure handling of model inputs/outputsSolid software eng…
Position Summary Salesforce Life Sciences Cloud Senior ConsultantDeloitte's Sales & Service practice partners with the world's leading life sciences companies to reimagine how their commercial, medical, and field organiz…
variety of business applications, helping clients optimise operational efficiency. These individuals analyse client needs, implement software solutions, and provide training and support for seamless integration and utili…
Position Summary AI & Engineering/ EaaS - DevOps Engineer IIIBuild and scale modern DevOps capabilities that help clients accelerate... ...and operational improvement to help organizations strengthen software delivery pe…
What software engineers earn in Kansas City
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $34–$48 | $70k–$99k |
| Mid level | $48–$68 | $99k–$141k |
| Senior | $65–$90 | $136k–$188k |
Adjusted for the Kansas City 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 Kansas 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.