$150k - $230k
Veeva Systems is a mission-driven organization and pioneer in industry cloud, helping life sciences companies bring therapies to patients faster. As one of the fastest-growing SaaS companies in history, we surpassed $3B…
Engineering & IT · Kansas City, MO
Cloud Architect jobs in Kansas City, MO
Cloud architects design how an organization's systems run on platforms like AWS, Azure, and GCP — balancing reliability, security, and cost, and guiding teams through migrations and growth.
168
Open roles today
$43–$100/hr
Typical pay range
$136k
Median, full-time
1
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 cloud architect roles
3 shown of 168 · sorted by freshness
$134.5k - $265.1k
Recruiting for this role ends on 12/31/2026. Work you'll do As a Cloud Security Manager on the Cloud Cyber Risk team, you will be... ...(JSON)-based infrastructure configuration ~3+ years architecting security on Microso…
Job Title: UI Architect – .NET, React & Enterprise Banking Solutions Location: Kansas City, Missouri Responsibilities Lead the architecture, design, development, and modernization of a large-scale SaaS platform built on…
02
What cloud architects earn in Kansas City
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $43–$57 | $89k–$118k |
| Mid level | $57–$75 | $118k–$155k |
| Senior | $72–$100 | $150k–$207k |
Adjusted for the Kansas City market from national ranges.
03
What employers ask for
The skills these listings keep naming
Deep AWS, Azure, or GCP expertiseArchitecture patterns and tradeoffsNetworking and security designInfrastructure as codeCost modeling and FinOpsMigration planningKubernetes and containersStakeholder communicationWriting architecture documents
04
Interview questions worth rehearsing
With the thing the interviewer is actually listening for
Design a highly available architecture for a customer-facing web application.
Ask about requirements and budget first. Cover multi-AZ, load balancing, data replication, and failure modes — and say what you would deliberately not build at this scale.
How would you plan a migration from on-premises to the cloud?
Talk about assessment, choosing rehost versus refactor per workload, sequencing by risk, and running hybrid during the transition. Phased beats big-bang.
A team's cloud costs doubled in a quarter. How do you investigate?
Visibility first — cost explorer, tagging — then the usual suspects: data transfer, oversized instances, forgotten environments. Show you treat cost as an architectural property.
When would you advise against microservices?
Small teams, unclear domain boundaries, or operational immaturity. Arguing against a fashionable pattern with specifics is a strong signal for an architect.
How do you get engineering teams to actually follow your architecture?
Influence over mandate: reference architectures, paved-road templates, and review checkpoints. Acknowledge that unused architecture documents are a failure mode.
How do you design for disaster recovery, and how do you set RTO/RPO?
Explain that RTO/RPO are business decisions with price tags, then map them to backup, pilot-light, or active-active patterns. Mention actually testing the recovery.
Tell me about an architecture decision you got wrong.
Pick a real one, explain the reasoning at the time, and what your process learned from it. Architects who claim a clean record are not believed.
05
Resume tips that move the needle
For cloud architects specifically — generic advice costs you here
01
Anchor each role in scale and outcomes: workloads migrated, availability achieved, annual spend managed or reduced.
02
List current professional-level certifications (AWS Solutions Architect Professional, Azure Solutions Architect); they are near-mandatory screens for this title.
03
Show breadth across compute, networking, data, and security — architecture hiring looks for T-shaped depth.
04
Include the organizational side: teams guided, architecture reviews run, standards adopted.
05
Name a migration or greenfield build you owned end to end; a single deep case study outweighs a list of services.
06
Where this role goes
Typical progression
01
Cloud Engineer
02
Senior Cloud Engineer
03
Cloud Architect
04
Principal Architect
Ten quiet minutes a day
Applying for cloud architect 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.