$75k - $85k
liaison between clients, engineers, field technicians, subcontractors, and internal stakeholders throughout the project lifecycle. Develop and maintain project schedules, budgets, resource plans, and project milestones.…
Engineering & IT · Kansas City, MO
Frontend Developer jobs in Kansas City, MO
Frontend developers build the interfaces people actually see and use, turning designs into fast, accessible web experiences with HTML, CSS, JavaScript, and frameworks like React.
325
Open roles today
$29–$81/hr
Typical pay range
$108k
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 frontend developer roles
5 shown of 325 · sorted by freshness
$65k - $80k
detailed design documentation including SOWs, system schematics, rack elevations, and BOMs. Collaborate with project managers to develop project timelines, manage resources, and ensure on-time delivery. Interface directl…
$150k - $180k
Free From Market is a VC-backed, social enterprise startup with the mission to empower everyone to manage their health through food. The company works with insurance companies, health care providers, community-based orga…
$110 - $120 per hour
1099 Independent Contractor Engagement – Sr. D365 CE Developer Contract Type: 1099 Independent Contractor (Individual Consultant Only) | C2C: Not Accepted | Duration: 6 Months, potential extension | Location: Remote, U.S…
Sr. D365 F&O Developer – 1099 Contractor Contract: 1099 Independent Contractor only; C2C not accepted | Duration: 6 months, potential extension | Location: Remote, U.S.-based | Client: State government | Rate : $90–$120/…
02
What frontend developers earn in Kansas City
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $29–$43 | $61k–$89k |
| Mid level | $43–$61 | $89k–$127k |
| Senior | $59–$81 | $122k–$169k |
Adjusted for the Kansas City market from national ranges.
03
What employers ask for
The skills these listings keep naming
JavaScript and TypeScriptReact, Vue, or AngularHTML and semantic markupCSS and responsive layoutAccessibility (WCAG)Performance optimizationREST and GraphQL APIsTesting (Jest, Playwright)Working with designers
04
Interview questions worth rehearsing
With the thing the interviewer is actually listening for
What happens between typing a URL and the page rendering?
Cover DNS, the request, HTML parsing, and the render pipeline at a comfortable level of detail. Depth on the rendering side is where frontend candidates stand out.
How do you make a page fast?
Talk about measuring first — Core Web Vitals, profiling — then levers like code splitting, image optimization, and caching. Tie it to a real page you improved.
How do you approach accessibility in your work?
Go beyond alt text: keyboard navigation, focus management, semantic HTML, and testing with a screen reader. Concrete habits are convincing.
Explain how you would manage state in a growing React application.
Show that you match the tool to the problem — local state, context, or a store — rather than defaulting to one library for everything.
Tell me about a time a design was not feasible as specced. What did you do?
Show collaboration: you explained the constraint, offered alternatives, and protected the user experience rather than silently shipping something different.
How do you handle browser or device inconsistencies?
Mention progressive enhancement, feature detection, and testing on real devices. A specific war story helps.
Walk me through a component you are proud of.
Pick one with interesting constraints — accessibility, reuse, performance — and explain the API you designed for it, not just what it looked like.
05
Resume tips that move the needle
For frontend developers specifically — generic advice costs you here
01
Link to live work: a portfolio, deployed projects, or specific pages you shipped — frontend is one of the few fields where reviewers can click your output.
02
Cite performance numbers where you have them, such as Lighthouse scores or load-time improvements.
03
Mention accessibility work explicitly; it is increasingly a screening criterion.
04
Be specific about your framework depth — 'React with TypeScript, 4 years' beats a list of ten libraries.
05
Show collaboration with design: mention Figma handoff, design systems, or component libraries you maintained.
06
Where this role goes
Typical progression
01
Junior Frontend Developer
02
Frontend Developer
03
Senior Frontend Developer
04
Staff Frontend Engineer
Ten quiet minutes a day
Applying for frontend 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.