Engineering & IT · Kansas City, MO

Mobile Developer jobs in Kansas City, MO

Mobile developers build apps for iOS and Android, either natively in Swift and Kotlin or with cross-platform tools like React Native and Flutter, and ship them through the app stores.

40
Open roles today
$33–$86/hr
Typical pay range
$115k
Median, full-time

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 mobile developer roles

3 shown of 40 · sorted by freshness

Embedded Software Engineer

IERUS Technologies, Inc. · Kansas City, MO · Full-time

customers with a diverse set of competencies including software development, air and missile defense, and systems engineering. IERUS develops value for our defense and commercial customers through accelerations of the te…

Posted 1w ago
+ Save to tracker View listing

Software Engineer

Premier Tech Inc · Kansas City, MO

You’ll Do Modernize legacy Java EE applications by migrating JSF/PrimeFaces interfaces to Angular single-page applications. Develop and enhance Spring Boot microservices that replace legacy Java applications. Build and…

Posted 1w ago
+ Save to tracker View listing

Software Engineer - QA

Cboe Digital · Kansas City, MO · Full-time
$93.5k - $121k

pursue them and bring on a challenge. As champions of internal mobility and access to opportunity, we encourage our people to “go for it... ...conducive to productivity and growth. Role Overview We develop, automate and…

Posted 4w ago
+ Save to tracker View listing
02

What mobile developers earn in Kansas City

Hourly first — that's how the offer arrives

ExperienceHourlyAnnual, full-time
Entry level $33–$45 $68k–$94k
Mid level $45–$65 $94k–$136k
Senior $63–$86 $132k–$179k

Adjusted for the Kansas City market from national ranges.

03

What employers ask for

The skills these listings keep naming

Swift/SwiftUI or Kotlin/ComposeReact Native or FlutterMobile app architecture (MVVM)REST APIs and offline syncApp store release processPerformance and battery profilingPush notificationsUI testing and crash monitoring
04

Interview questions worth rehearsing

With the thing the interviewer is actually listening for

Native or cross-platform — how do you choose for a given product?

Frame it as tradeoffs: team size, performance needs, platform-specific features, and long-term maintenance. Avoid religious answers in either direction.

How do you handle offline support and data sync?

Discuss local storage, sync strategies, and conflict resolution. Acknowledging that sync is genuinely hard reads as experience, not weakness.

Walk me through your app release process.

Cover build automation, staged rollouts, crash monitoring, and how you handle a bad release you cannot instantly roll back. Store review constraints are the key difference from web.

How do you keep an app responsive and battery-friendly?

Talk about keeping work off the main thread, profiling tools, and being deliberate with background tasks and network calls.

Tell me about a platform-specific problem you had to solve.

A concrete story — an OS update breaking behavior, a permissions change, a device-specific bug — shows you have shipped for real.

How do you structure an app so it stays maintainable as it grows?

Describe your architecture pattern and, more importantly, why: testability, separation of UI and logic, and how new developers find their way around.

How do you test a mobile app beyond unit tests?

Mention UI tests, device labs or simulators, beta channels like TestFlight, and crash/analytics monitoring after release.

05

Resume tips that move the needle

For mobile developers specifically — generic advice costs you here

01

Link your published apps and include store metrics if favorable — downloads, ratings, or featured placements.

02

State your platform depth clearly: iOS, Android, or cross-platform, with the languages and years for each.

03

Mention release ownership — shipping to the App Store or Play Store, staged rollouts, crash-rate improvements.

04

Quantify quality: crash-free rate, app size reduction, startup time improvements.

05

If you worked on a well-known app, name your specific features rather than the app alone.

06

Where this role goes

Typical progression

01 Junior Mobile Developer
02 Mobile Developer
03 Senior Mobile Developer
04 Staff Mobile Engineer
Ten quiet minutes a day

Applying for mobile developer 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.
40 Mobile Developer roles in Kansas City Save them into one pipeline Save them into your pipeline
Start free My tracker