How to hire a freelance cloud architect (and avoid a surprise cloud bill)

Cloud platforms make it easy to start. They also make it easy to end up with an expensive, fragile and insecure setup that nobody fully understands. A freelance cloud architect can design the right foundation from the start, or untangle the setup you already have.

What a cloud architect does

• Designs infrastructure: compute, databases, storage, networking and how they fit together
• Plans for reliability: backups, failover and what happens when a component breaks
• Sets up security: identity and access, network rules, encryption and secrets management
• Controls cost: right-sizing resources, choosing pricing models and setting budgets and alerts
• Automates everything: infrastructure as code, so environments can be rebuilt and reviewed
• Plans migrations from on-premises servers or between providers

This overlaps with DevOps, but the focus is different. A cloud architect designs the system; a DevOps engineer often builds and runs the pipelines and tooling around it. Many freelancers do both. See signs you need a DevOps engineer.

Signs you need one

• Your cloud bill keeps growing and nobody can explain why
• Production was set up by hand and nobody dares to change it
• You have no tested backups or recovery plan
• Everyone uses the same admin account
• You are moving to the cloud, or between cloud providers
• A customer or auditor is asking about your infrastructure security

Skills to look for

• Deep experience with your cloud provider. See AWS specialists.
• Infrastructure as code, so every change is versioned and reviewable
• Networking and security fundamentals
• Containers and orchestration, if your applications use them
• Cost optimization with concrete examples of savings
• Clear documentation: architecture diagrams and runbooks your team can follow

Questions to ask

1. "Tell me about a cloud bill you reduced. What did you change?"
2. "How would you design this application to survive the loss of one data center?"
3. "How do you manage secrets and access for a team of ten developers?"
4. "How do you test that backups actually work?"
5. "How would you migrate our current setup with minimal downtime?"

Strong candidates ask about your traffic, data, budget and team before proposing anything. Be wary of anyone who recommends a complex architecture before understanding your needs.

Scope a first engagement

A good way to start is a cloud review of one to three weeks. Ask for:

• A diagram of your current infrastructure
• The top risks for security, reliability and cost
• Quick wins, with estimated savings
• A plan for the next phase, such as moving to infrastructure as code

After the review, you can decide whether the architect implements the plan or guides your team.

Keep control of your infrastructure

• You own the cloud accounts. Freelancers get their own users with only the access they need.
• All infrastructure lives in your code repository, not on the freelancer's laptop.
• Insist on documentation and a handover session. See knowledge handover when freelancers leave.

Frequently asked questions

How much can a cloud review save?

It depends on your setup, but common savings come from removing unused resources, right-sizing servers and databases, and choosing better pricing options. A good architect will estimate savings before you commit to changes.

Should we use more than one cloud provider?

For most small and mid-sized companies, one provider is simpler, cheaper and easier to secure. Multi-cloud setups make sense for specific needs, such as strict regulatory requirements or very high availability targets.

What is infrastructure as code?

It means describing your infrastructure in configuration files stored in your code repository. Changes can then be reviewed, versioned and repeated, instead of being made by hand in a web console.

Find a vetted cloud expert

HireCurated vets solutions architects, AWS and DevOps specialists. Request a shortlist.