We're Hiring: Entry-Level / Junior / Mid-Level Business Analyst & Data Analyst Are you ready to kick-start or grow your career as a Business Analyst or Data Analyst? Join Midwestern IT and work on exciting projects while…
Product & Management · Kansas City, MO
Business Analyst jobs in Kansas City, MO
Business analysts translate business problems into clear requirements. They study processes and data, document what a system or team needs, and bridge the gap between stakeholders and technical teams.
242
Open roles today
$27–$61/hr
Typical pay range
$87k
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 business analyst roles
4 shown of 242 · sorted by freshness
life, group term life, and AD&D. JOB SUMMARY The Senior Analyst position is a key role within the IPFS corporate finance department... ...will lead the FP&A support for IPFS' payment facilitation business. In addition, t…
• Drive business development strategy aligned with the firm’s growth goals • Identify, pursue, and secure new clients and project opportunities • Build and maintain strong relationships with owners, developers, public ag…
Business Development Manager - Kansas City Posted on 10/16/2025 Location Kansas City, MO Description Job Purpose: Drive Sales of Magswitch automation products through Major Account relationships and solutions-based sales…
02
What business analysts earn in Kansas City
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $27–$36 | $56k–$75k |
| Mid level | $36–$48 | $75k–$99k |
| Senior | $45–$61 | $94k–$127k |
Adjusted for the Kansas City market from national ranges.
03
What employers ask for
The skills these listings keep naming
Requirements gatheringProcess mappingSQLExcel and data analysisStakeholder interviewsUser stories and acceptance criteriaVisio or LucidchartGap analysis
04
Interview questions worth rehearsing
With the thing the interviewer is actually listening for
Walk me through how you gather requirements for a new project.
Describe a repeatable approach: identify stakeholders, interview and observe, document, then validate back with the people affected before anything is built.
Tell me about a time stakeholders asked for a solution rather than describing a problem.
Show that you asked why until the underlying need surfaced, and that the eventual solution differed from the original request.
How do you handle changing requirements mid-project?
Reference a change process: assess impact on scope and timeline, get the tradeoff decision made explicitly, and update documentation so everyone works from one source.
Describe a process you improved. How did you measure it?
Map the before state with numbers such as cycle time or error rate, describe the change, and give the after numbers. Concreteness matters more than scale.
How comfortable are you with SQL and data analysis?
Be honest about your level and give an example query or analysis you performed to answer a real business question.
How do you write requirements a developer will not misinterpret?
Mention acceptance criteria, concrete examples, and edge cases, plus reviewing drafts with engineers before they are final.
Tell me about a project where business and technical teams were talking past each other.
Position yourself as the translator: describe how you restated each side's constraints in the other's language until a workable option appeared.
05
Resume tips that move the needle
For business analysts specifically — generic advice costs you here
01
Frame each engagement as problem, analysis, recommendation, and measured result rather than a list of documents produced.
02
Quantify process improvements in hours saved, error rates cut, or revenue affected.
03
Name the systems you analyzed, such as Salesforce, SAP, or in-house tools, since many BA roles are system-specific.
04
Show your data range: SQL queries written, dashboards built, or datasets reconciled.
05
Include one example of requirements work that prevented rework or caught a costly gap before build.
06
Where this role goes
Typical progression
01
Junior Business Analyst
02
Business Analyst
03
Senior Business Analyst
04
Lead Business Analyst
05
Product Manager
Ten quiet minutes a day
Applying for business analyst 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.