Job description

We are looking for a Cloud Architect who is responsible for overseeing a company's cloud computing strategy. This includes cloud adoption plans, cloud application design, and cloud management and monitoring. They ensure that the cloud environment is scalable, resilient, secure, and cost-effective. 1. Strategy and Design This is the "blueprint" phase of the job. You aren't just picking services; you are designing a system that can survive a server failure or a sudden spike in traffic. • Architecture Design: Designing multi-tier cloud architectures that utilize IaaS, PaaS, and SaaS providers (like AWS, Azure, or Google Cloud). • Cloud Selection: Evaluating which cloud providers or hybrid-cloud configurations best suit the organization's specific needs. • Scalability Planning: Ensuring the infrastructure can grow (or shrink) automatically based on demand to optimize performance. 2. Governance and Security In the cloud, a small configuration mistake can lead to a massive data breach. The Architect is the primary defender. • Identity & Access Management (IAM): Designing "Least Privilege" models to ensure only the right people have access to sensitive data. • Compliance: Ensuring the cloud setup meets industry standards like GDPR, HIPAA, or SOC2. • Security Frameworks: Implementing encryption at rest and in transit, firewalls, and DDoS protection. 3. Cost Optimization (FinOps) One of the biggest challenges in the cloud is the "surprise bill." An Architect must be a good steward of the company's budget. • Cost Modeling: Estimating monthly spend before a project launches. • Resource Rightsizing: Identifying underutilized resources and shutting them down or downsizing them. • Reserved Instances: Planning long-term capacity purchases to save money compared to "on-demand" pricing. 4. Leadership and Collaboration Architects rarely work in a vacuum. They act as the "connective tissue" between various departments. • Bridging Business and Tech: Translating a CEO's goal (e.g., "We need to launch in Europe") into a technical requirement (e.g., "We need a multi-region deployment with data residency compliance"). • Mentorship: Guiding Cloud Engineers and Developers on best practices for "Cloud Native" development. Technical Skills vs. Soft Skills Technical Proficiency Professional Soft Skills Networking: VPCs, DNS, Load Balancing, CDN Communication: Explaining "The Cloud" to non-techies Programming: Python, Go, or Java for automation Decision Making: Choosing between cost and performance IaC: Terraform, CloudFormation, or Ansible Adaptability: Keeping up with weekly cloud updates Data: SQL, NoSQL, and Data Lake architecture Problem Solving: Troubleshooting systemic outages

Requirements

Must-haves

Strategy and Design
This is the "blueprint" phase of the job. You aren't just picking services; you are designing a system that can survive a server failure or a sudden spike in traffic.
Architecture Design: Designing multi-tier cloud architectures that utilize IaaS, PaaS, and SaaS providers (like AWS, Azure, or Google Cloud).
Cloud Selection: Evaluating which cloud providers or hybrid-cloud configurations best suit the organization's specific needs.
Scalability Planning: Ensuring the infrastructure can grow (or shrink) automatically based on demand to optimize performance.
Governance and Security
In the cloud, a small configuration mistake can lead to a massive data breach. The Architect is the primary defender.
Identity & Access Management (IAM): Designing "Least Privilege" models to ensure only the right people have access to sensitive data.
Compliance: Ensuring the cloud setup meets industry standards like GDPR, HIPAA, or SOC2.
Security Frameworks: Implementing encryption at rest and in transit, firewalls, and DDoS protection.
Cost Optimization (FinOps)
One of the biggest challenges in the cloud is the "surprise bill." An Architect must be a good steward of the company's budget.
Cost Modeling: Estimating monthly spend before a project launches.
Resource Rightsizing: Identifying underutilized resources and shutting them down or downsizing them.
Reserved Instances: Planning long-term capacity purchases to save money compared to "on-demand" pricing.
Leadership and Collaboration
Architects rarely work in a vacuum. They act as the "connective tissue" between various departments.
Bridging Business and Tech: Translating a CEO's goal (e.g., "We need to launch in Europe") into a technical requirement (e.g., "We need a multi-region deployment with data residency compliance").
Mentorship: Guiding Cloud Engineers and Developers on best practices for "Cloud Native" development.
Technical Skills vs. Soft Skills
Technical Proficiency
Professional Soft Skills
Networking: VPCs, DNS, Load Balancing, CDN
Communication: Explaining "The Cloud" to non-techies

Nice-to-haves

None flagged.

Application prep

Use the role’s language and application details while tailoring your materials.

Keywords to mirror

awsazurerestpythongojavasql

Platform: breezy
Effort: medium