Kforce is looking for a Senior Software Engineer in Kansas City, MO. Responsibilities: ~ Use appropriate tools, programming languages, coding standards, and best practices to develop new product features and maintain exi…
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.
585
Open roles today
$34–$90/hr
Typical pay range
$120k
Median, full-time
2
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
3 shown of 585 · sorted by freshness
Job Description Job Description Description: Senior Software Engineer – Aerospace & Defense Test Systems Location: Kansas City, MO Job Type: Full-Time Industry: Aerospace, Defense, Automated Test Equipment Citizenship Re…
Consultant â Software Engineer Client: NAIC (National Association of Insurance Commissioners) Contract: 12 months Location: Remote (All candidates must reside within 100 miles of Kansas City) Hours: 37.5 hrs/week Note:…
02
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.
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.