Cloud Architect Job Description Template 2026

Last updated: July 8, 2026

A cloud architect designs and governs an organization’s cloud environment across AWS, Azure, or GCP, owning the migration strategy, security guardrails, and cost model that engineering teams build within, and earns $130,000 to $205,000 base in the U.S. in 2026. That is a design-and-governance job, not a build-and-operate one, and the gap between those two is why so many cloud architect hires disappoint. The template below scopes the role that actually pays for itself.

A company I talked to last year hired a “cloud architect” to get their AWS spend under control. Eighteen months later the bill had roughly doubled, three teams were each running their own half-finished landing zone, and the person they hired had spent most of that time closing tickets in the console. He was good. That was never the problem. He was a cloud engineer, hired into an architect title, handed no authority to set a standard, and measured on keeping the lights on. So the lights stayed on and the strategy never showed up.

That story repeats more than any other in cloud hiring. The title says architect. The job description reads like an operations role with a nicer name. And the invoice tells you which one you actually got, usually around the time finance starts asking why a workload that ran fine on-prem now costs $40,000 a month. Nobody set the guardrails. Nobody owned the cost model. The req got filled and the problem it was supposed to solve is still sitting there. Still open. Nobody solved it.

I’m Gregg Flecke, a Senior Talent Acquisition Partner at KORE1. I’ve spent close to 30 years placing IT and infrastructure talent, and cloud architects are one of the roles hiring managers scope worst, because the line between designing the cloud and running it blurs the moment you write the posting. We earn a placement fee when you hire through us, so weigh the advice with that in mind. The template works the same whether you run the search yourself or bring us in. For the wider picture, our cloud engineer staffing practice fills these roles across 30+ U.S. metros.

Cloud Architect vs Cloud Engineer vs Solutions Architect

A cloud architect sets the design and standards for the whole cloud environment, a cloud engineer builds and operates inside those standards, and a solutions architect designs the cloud footprint for one specific product or customer problem.

Get this line wrong and the shortlist comes back wrong. Every time. It is the single most expensive mistake in the whole process, and it happens before a single resume gets read.

The cloud architect works at the environment level. How are our accounts structured, what does the network look like across regions, where do the security boundaries sit, what is our cost model, and does any of it hold up when three product teams all want to ship next quarter. They write the reference architectures and the guardrails everyone else deploys within. They sit with security, finance, and engineering leadership as often as they sit with a keyboard. The output is a design others can build on for years, not a stack that shipped this sprint. Years, not sprints.

A cloud engineer lives one layer down and makes it real. Terraform modules, CI/CD pipelines, Kubernetes clusters, the on-call rotation when something pages at 3 a.m. Critical work. Different work. If your actual need is someone to build and run the environment day to day, you want a cloud engineer, and calling it an architect role just inflates the salary and confuses the applicants. A solutions architect sits somewhere between the two, but pointed at a single problem, designing the cloud piece of one product or one client engagement rather than the whole estate. Hiring for that? The solutions architect job description template is the one you want.

Here is how the three line up on the axes that decide who applies.

Read the “hands on keyboard” row twice before you write the posting. If what you need is someone building modules and holding a pager, that is an engineer. Paying architect money to find that out four months into an open req is a bad trade, and it is the one companies make most.

What a Cloud Architect Actually Owns

The role is hard to scope because it covers four things that look separate but ride on the same decisions. A posting that names which of the four matters most for you will pull a sharper pool than one that says “cloud architecture experience required” and leaves the rest to imagination. So name them.

The foundation. Account structure, the landing zone, networking, identity, the guardrails every workload inherits. On AWS this is Organizations, Control Tower, and a well-designed multi-account setup. On Azure it is management groups and the landing zone accelerators. Get the foundation wrong and every team downstream pays for it, quietly, for years. This is the least glamorous domain and the one that separates a real architect from a senior engineer with a fancier title. That is the tell.

Migration and modernization. Most cloud architects earn their keep here first. What moves as-is, what gets rearchitected, what should never have left the data center, and in what order, so the business keeps running while it happens. A rehost that ignores the app’s data gravity turns into the $40,000-a-month surprise I mentioned earlier. Order matters. The architect who has actually run a migration, and watched one go sideways, is worth a real premium over one who has only drawn the diagram. The scars matter.

Security and compliance is the third, and it is not a bolt-on. The architect designs where the boundaries live, how identity flows, how secrets are handled, and how the environment proves it meets SOC 2, HIPAA, or FedRAMP when the auditor shows up. In a well-run org, security review is baked into the guardrails so engineers cannot easily do the wrong thing. In a badly run one, it is a slide deck nobody follows. Design it in.

Cost. This is the domain that has moved the most since 2020, and the one hiring managers still leave off the posting. Somebody owns it. Call it FinOps or call it not going broke. Either way, the architect who owns the cost model decides how spend is tagged, how teams see what they burn, and where the reserved-capacity and right-sizing calls get made. Every AI initiative leadership is excited about runs on GPU instances that cost real money, and someone has to own whether that spend is deliberate or accidental. If your architect will carry the cloud budget, say so in the posting. In plain language.

One thing sits on top of all four. Authority. A cloud architect who can be overruled by any team that finds the guardrails inconvenient is not an architect. They are a suggestion box. The Well-Architected review only works if leadership backs the standard when a team wants to skip it. No backing, no role. Hire a senior engineer for the specific gap instead and keep the money.

Cloud Architect Job Description Template

Here is the block. Copy it, swap the bracketed prompts for your real scope, and delete the italic notes before it goes live. Those notes are for whoever fills it in, not for the candidate. It assumes a senior cloud architect inside an established engineering org. Turn the ownership language up for a principal or head-of role, down for your first cloud architect hire.

Where Cloud Architect JDs Go Wrong

I read a lot of these before a search opens. The failure patterns are consistent, and each one quietly bleeds candidates in a way the hiring manager rarely notices until the req has been open two months. Five come up the most.

The engineer role wearing an architect title. The one I opened with, and the most common by a wide margin. The responsibilities are all build-and-run: write the Terraform, manage the clusters, hold the pager. That is cloud engineering. Put an architect title on it and two bad things happen at once. The real architects skip it, because there is no design authority in the bullets. And the engineers who apply want architect pay for engineer work. Scope the posting to the altitude of the actual job. Match the altitude.

Second one. No cost ownership anywhere in the JD. The whole reason many companies hire a cloud architect in 2026 is that their bill is out of control, and then the posting never mentions cost once. Strong candidates read that omission and assume they will get blamed for the spend without the authority to shape it. If FinOps and cost governance are part of the job, and they almost always are, put them in writing. Write the cost line. It is also the fastest way to stand out from every other cloud posting that forgot.

Third, single-cloud tunnel vision on a multi-cloud reality. The JD demands ten years of deep AWS and never mentions the Azure tenant that half the company already runs after an acquisition. You just wrote a posting that filters out the exact people who could handle your actual environment. Describe the estate you have, messy edges and all, not the clean one on the slide. The real one.

Certification walls. AWS Professional and Azure Expert and a Kubernetes cert and a security cert, all required, day one. That combination describes almost nobody real, and the people who could do the work read a stacked cert list and assume the rest of the JD was written by someone who has never hired this role. List one relevant cert as preferred and weigh the track record instead.

Last, all platform and no business. A role whose whole point is aligning cloud spend and design with what the business is trying to do, and every bullet is a service name. The architect who can sit with finance and model the cost of a decision reads that posting and hears a job that will never get out of the infrastructure weeds. Write at least a third of the responsibilities in the language of outcomes, because that third is the harder half to hire for. By far.

Frameworks, Tools, and Certs to Name in the Posting

Naming the specific frameworks and tools your environment runs on does two jobs. It filters for people who have used them, and it signals to a strong architect that your practice is real rather than aspirational. Being vague costs you here in every case. So be specific.

The platform, first and clearly. AWS, Azure, or GCP, and if it is more than one, say which and roughly in what proportion. “Primarily AWS with a growing Azure footprint” tells a candidate more than three paragraphs of generic cloud language. Name it. Name the core services the role lives in too: Organizations and Control Tower, Azure Landing Zones, VPC and networking design, IAM and identity.

The Well-Architected Framework. The AWS Well-Architected Framework is the common vocabulary for this role. Its six pillars, operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability, give you the axes to judge a design against, and Azure and Google publish their own versions of the same idea. Naming it tells candidates you grade designs against a standard, not a whiteboard mood.

Infrastructure as code and the tooling around it. Terraform is the default across most multi-cloud shops. CloudFormation or Bicep if you are single-cloud and committed. Name the CI/CD and the container platform if they are central, Kubernetes, EKS, AKS, and the FinOps tooling if cost is a named part of the job.

Certs, in their place. The AWS Certified Solutions Architect Professional, the Azure Solutions Architect Expert (AZ-305), and the Google Professional Cloud Architect are the ones that come up in our searches. They are a reasonable “preferred” signal. They are a poor “required” filter, because the best architects often let a cert lapse while they were busy doing the actual work it certifies. That is the pattern.

Cloud Architect Salary Benchmarks 2026

Compensation data for this title scatters more than for almost any other, and the scatter is the useful part. The aggregators disagree by tens of thousands of dollars because they measure different things and pool different roles under the same words. Work out which number means what before you set a band.

Now the aggregators, and why they land so far apart. Salary.com puts the base average near $124,000, with a typical band of roughly $116,000 to $134,000, because it reports base pay and pools generalist and junior titles in. PayScale lands around $128,000. ZipRecruiter sits near $147,000 from posted listings. Glassdoor headlines about $202,000, but that is total pay with bonus, equity, and profit sharing folded in, not base. Read the label before you read the number. The distance between a $124,000 base figure and a $202,000 total-pay figure is not two different jobs. It is one cloud architect role measured two different ways. Same person. Two numbers.

The Bureau of Labor Statistics has no line for cloud architect specifically. Its closest category, computer network architects, reports a $130,390 median wage for 2024 and projects 12% growth through 2034, faster than the average across all occupations, with about 11,200 openings a year. Treat that as a floor and a direction, not a match, since it skews toward network design and pulls the median down. Location moves the band more than most hiring managers expect. A senior cloud architect in San Francisco, Seattle, or New York runs 15% to 25% above the same role in Austin, Denver, or most of the Midwest, and the candidates who could take either offer tend to run that math themselves before a recruiter finishes the first call. One more premium worth budgeting for: an architect who genuinely knows two clouds, not one plus a demo, commands more than either single-cloud specialist, because that person is rare and you already know why you need them.

Adapting the Template by Company Stage

The block above is a skeleton. Where your company sits changes which parts carry the weight.

Your first cloud architect. If nobody has held this seat, the job is as much about standing up the practice as running it. Say that plainly. This person writes the first standards, builds the landing zone from a blank account, and spends the early months earning the authority the role needs before the new-hire goodwill runs out. That is a specific temperament. Someone who likes a blank page and can build trust fast. Lead with the mandate and name the executive backing it, because without that backing the job cannot work and the right candidate already knows it.

A mature cloud practice. If there is already a landing zone, a framework in use, and a platform team, the role narrows and sharpens. Now you are hiring for a specific gap, a multi-cloud expansion, a cost turnaround, a compliance-heavy migration. Pick one. Name the existing setup, the tools, and the exact gap this hire fills. A strong architect reads that specificity as proof the practice is real, and reads a vague cloud post as proof it is not.

What Hiring Managers Ask Us Before Posting a Cloud Architect Role

Cloud architect or cloud engineer, which one do I actually need?

Design authority is the dividing line. A cloud architect sets the environment’s structure, standards, and cost model and holds the authority to enforce them; a cloud engineer builds and operates inside those standards day to day. If the work you have in mind is writing infrastructure code and carrying a pager, that is an engineer, and pricing it as an architect just inflates the offer and confuses applicants. If the work is deciding how the whole estate is structured and governed, that is an architect. Write the responsibilities first and the right title falls out of them.

Can I promote my best cloud engineer into the architect seat?

Sometimes, and it is often the best hire you can make, but not automatically. The skills that make a great engineer, deep hands-on command of the platform, are necessary but not sufficient. The architect job adds three things: designing for scale before it exists, saying no to a team with authority behind it, and speaking the language of cost and business outcomes. Some engineers have been quietly doing all three and just lack the title. Others are brilliant builders who do not want to stop building. Screen for the design-and-govern instinct, not just the years.

One cloud or all three, how much multi-cloud does the posting really need?

Match the requirement to the estate you actually run, not the one that sounds impressive. Most companies are deep on one cloud with a smaller second footprint, usually from an acquisition or a single SaaS dependency, and they need an architect who is expert in the primary and competent in the secondary. Demanding true depth in all three filters your pool down to almost nobody and pays a premium you probably do not need. If you are genuinely multi-cloud by strategy, say so and budget for it. If you are AWS with a little Azure, write that.

Do the AWS and Azure architect certifications actually matter?

They are a useful signal and a bad gate. The AWS Solutions Architect Professional, Azure Solutions Architect Expert, and Google Professional Cloud Architect all show a candidate invested in the platform and passed a hard exam. That is worth something as a “preferred.” Requiring them screens out strong architects who let a cert lapse while running real migrations, and screens in people who test well without having owned much. Weight the track record first: a migration they steered, a cost problem they solved, a standard they made stick.

What salary range should I post for a cloud architect?

$130,000 to $205,000 base covers most mid-to-senior cloud architect roles in 2026, with principal and head-of positions climbing past that on total comp. Post the range. California, Colorado, New York, and Washington now require it on the listing, and even where it is optional, senior candidates filter out postings that hide it. Use a spread of about $40,000. It reads as room to level the right person, not indecision, and it screens out the mismatches before anyone burns four rounds finding the gap.

Should this be a contract or a direct hire?

Direct hire for the standing seat, contract for a bounded program. The value of a cloud architect compounds through knowing your environment and holding the trust to enforce standards, and a six-month contractor rarely builds either. Where a contract fits is a defined effort with an end date, a data-center exit, a cloud migration, a cost turnaround, where you want senior depth without a permanent line on the org chart. Contract-to-hire is the middle path when you want to see the work before you commit. KORE1 staffs these as direct hire, contract, and contract-to-hire, and the right model follows the shape of the work.

Next Steps

Take the template and make it yours. Pick the real level, name the platform and the domains that matter, list the tools you actually run, put cost ownership in writing, post the range, and cut anything that does not describe your hire. A short, specific cloud architect JD beats a long generic one in every search we run.

If you want a second read on a posting that has sat open too long, help leveling a role that lives between engineer and architect, or a shortlist of people who have genuinely owned a cloud environment, that is our desk. Reach out to a recruiter on our team. KORE1 places cloud architects and senior IT talent across 30+ U.S. metros through direct hire, contract, and contract-to-hire, with an average time-to-fill of 17 days and 92% of those hires still in seat a year later. When the shortlist is in front of you, our cloud architect interview questions help separate the designers from the console operators, and the full guide to hiring a cloud architect walks the search end to end.