Who We Are WPP Enterprise Solutions designs, builds, and operates the growth systems that competitive businesses rely on. In a world where Al is reshaping how companies drive growth, we lead clients in business transform…
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.
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 business analyst roles
5 shown of 283 · sorted by freshness
job summary: We are seeking a Technology Business Analyst to serve as a high-impact, techno-functional bridge supporting our client's enterprise IT Data Program. Going well beyond traditional reporting or BI, this proact…
do work that matters Summary The Lead App Development Analyst typically leads and coordinates highly complex or enterprise critical... ...Facilitates cross functional communications with business customers stakeholders t…
to do work that matters Summary The Sr App Development Analyst will lead highly complex or enterprise critical projects that require... ...Duties and Responsibilities Drives communications with business customers and tec…
The Business Data Analyst I role follows a hybrid schedule, with three days per week in the office and two days working from home. The position also requires 10-15% local travel to other sites. The Business Data Analyst…
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.
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 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.
Resume tips that move the needle
For business analysts specifically — generic advice costs you here
Frame each engagement as problem, analysis, recommendation, and measured result rather than a list of documents produced.
Quantify process improvements in hours saved, error rates cut, or revenue affected.
Name the systems you analyzed, such as Salesforce, SAP, or in-house tools, since many BA roles are system-specific.
Show your data range: SQL queries written, dashboards built, or datasets reconciled.
Include one example of requirements work that prevented rework or caught a costly gap before build.
Where this role goes
Typical progression
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.