Engineering & IT · Kansas City, MO

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.

346
Open roles today
$34–$90/hr
Typical pay range
$120k
Median, full-time
9
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

9 shown of 346 · sorted by freshness

Lead Workplace Engineer II/M365

Deloitte · Kansas City, MO
$141.2k - $278.3k

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…

Posted 2d ago
+ Save to tracker View listing

Information Security Engineer II

Dairy Farmers of America · Kansas City, KS

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…

Posted 2d ago
+ Save to tracker View listing

Senior Cloud Engineer

Cboe Exchange · Kansas City, MO
$148.75k - $192.5k

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…

Posted 3d ago
+ Save to tracker View listing

Senior AI Platform Engineer

Cboe Exchange · Kansas City, MO
$119k - $169.4k

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…

Posted 3d ago
+ Save to tracker View listing

DevOps Engineer III

Deloitte · Kansas City, MO
$116.2k - $229.1k

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…

Posted 4d ago
+ Save to tracker View listing
02

What software engineers earn in Kansas City

Hourly first — that's how the offer arrives

ExperienceHourlyAnnual, 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.

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 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.

Start with this search No email, no resume, no sign-up. Open your tracker Everything you saved is already there.
346 Software Engineer roles in Kansas City Save them into one pipeline Save them into your pipeline
Start free My tracker