groups within MSI as well as researchers. ASO also manages and runs the High Performance Computing (HPC) systems, storage, internal cloud, and other infrastructure of the Supercomputing Institute, including: High Perform…
Engineering & IT · Minneapolis, MN
Cloud Architect jobs in Minneapolis, MN
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.
272
Open roles today
$47–$108/hr
Typical pay range
$148k
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 cloud architect roles
12 shown of 272 · sorted by freshness
$115k - $130k
automation, and continuous improvement of enterprise cybersecurity platforms, with a primary focus on Microsoft Defender, Microsoft Purview, cloud security capabilities, and identity and access management (IAM). The Cybe…
~ Architect, implement, configure, and support Saviynt Identity Governance & Administration (IGA) solutions. ~ Implement Saviynt modules across on-premises and cloud environments. ~ Lead and guide teams on new implementa…
IAM Engineer Minneapolis, MN | 6 - 12 years of experience Duration: Full Time Job Description IAM Engineer Must Have Technical/Functional Skills Hands-on experience with Broadcom API Gateway (Layer 7) implementations. St…
stakeholder management - Defining roles across customer, partner, and AWS teams Certifications (Recommended) AWS Solutions Architect Associate (minimum) or Professional AWS Certified SysOps Administrator Associate AWS Ce…
challenges, rapidly prototype solutions directly with stakeholders, and architect scalable, secure systems. You operate with high autonomy,... ...expertise with technologies such as Python, Vue.js, AWS/GCP cloud platform…
$75.19 - $120.3 per hour
Title : Identity and Access Management (IAM) Architect Location : Remote (May require onsite work in Minneapolis, MN) Job Type... ...Architect to lead enterprise identity strategy across their Google Cloud and Microsoft…
$139k - $198k
leading edge of IoT innovation! As a Staff Engineer on the Cloud- to-Cloud (C2C) team, you will be the architectural backbone of... ...API Gateway. You should be intimately familiar with the AWS Well- Architected Framewo…
for its comprehensive approach to marketing technology. Gage is seeking developers to design, develop and support large scale Azure cloud- based web applications for our Fortune 500 clients. We are looking for experience…
$115k - $130k
an exciting opportunity to join an industry leading healthcare company. As a Senior Azure Developer you will architect, build, and maintain cutting-edge cloud solutions on Microsoft's Azure platform. This position demand…
$85k - $125k
I am partnered with a full-service consulting firm with multiple locations throughout the United States. My client offers paid holidays, 401k with a generous match, work/life balance, tuition reimbursement, and more! Qua…
$80 - $90 per hour
Join a dynamic team eager to innovate with ServiceNow expertise. We are seeking a SOM SN Architect for a remote contract position with a focus on enhancing the ServiceNow capabilities within our client's organization bas…
02
What cloud architects earn in Minneapolis
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $47–$62 | $97k–$128k |
| Mid level | $62–$81 | $128k–$168k |
| Senior | $78–$108 | $163k–$224k |
Adjusted for the Minneapolis 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 Minneapolis?
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.