How to Transition from Developer to Cloud Architect - Action Plan

You’re a developer with several years of experience and you’re beginning to feel that coding is no longer satisfying you. You see a broader perspective – how systems should work together, how to optimise costs, how to design solutions that scale to millions of users. You’re wondering: am I ready for Cloud Architect?

More and more Polish developers are asking themselves this question. Cloud computing has ceased to be a technology of the future – it’s the standard of today’s business. Organisations are migrating en masse to public cloud (AWS, Azure, GCP), and demand for cloud architects is breaking records. According to an IDC report, 95% of enterprises already operate in a multi-cloud model, and global spending on cloud infrastructure in 2026 will exceed $1 trillion.

For developers, this is a particularly attractive career path. You already possess technical foundations – you understand application architecture, know design patterns, have worked with databases. Now you need to broaden your perspective: from the level of a single application to the level of an entire ecosystem of infrastructure, security, costs, and business strategy.

In this article, you’ll receive a concrete, tested plan for transitioning from developer to Cloud Architect in 12-18 months. You’ll learn the required skills, the best certifications, ways to build architectural experience, and practical tips on how to negotiate a role change in your current company or find your first job as an architect. This isn’t theory – it’s a roadmap used by hundreds of Polish specialists who have successfully made this transformation.

Quick navigation

• What differentiates a Cloud Architect from a Developer and what are the differences in thinking?
• Networking, security, IaC, cost optimisation – skills you must develop
• Which certifications are key: AWS Solutions Architect Pro, Azure Solutions Architect Expert
• 12-18 month plan: detailed transition roadmap
• How to build architectural experience whilst still being a developer
• Cloud Architect vs Developer salaries – differences and financial prospects
• How EITT supports career transformation
• FAQ: answers to the most common questions about transitioning to Cloud Architect

What differentiates a Cloud Architect from a Developer?

The fundamental difference isn’t that an architect “codes less” (although that’s true), but rather the change in perspective and scope of responsibility. A developer builds application functionality; an architect designs the foundations on which these applications run.

Mentality and way of thinking

Developer thinks: “How do I implement this feature?” Cloud Architect thinks: “Should this feature exist in this form at all?”

As an architect, you’re responsible for much broader questions:

• How will the system scale with 10x more traffic?
• Have we chosen the right trade-off between latency and cost?
• What happens when an AWS region goes down for 4 hours?
• Is this architecture compliant with the company’s security policy and regulations (GDPR, NIS2)?
• How much will this cost us with 1M users?

Practical example: Developer: “I’ll build an API for image processing, use Python + Flask, put it on EC2.” Cloud Architect: “Is this a synchronous or asynchronous workload? If async, let’s use Lambda + SQS + S3, it’ll be 80% cheaper and scales automatically. Let’s add CloudFront CDN for latency reduction and DDoS protection. Do we need multi-region for GDPR compliance? How long do we store these images and what lifecycle policies should we apply?”

Scope of responsibility

Aspect	Developer	Cloud Architect
Scope of impact	Single application/microservice	Entire ecosystem (infrastructure, networking, security, cost)
Time horizon	Sprint (2-4 weeks)	Quarters/years – long-term vision
Main stakeholders	Product Owner, Tech Lead	CTO, CFO, Security Officer, compliance
Success metrics	Functionality works, tests pass	RTO/RPO met, costs within budget, zero security incidents
Financial responsibility	None or limited	Direct – cloud bill can amount to millions of PLN annually
Technical decisions	Choice of library, framework within application	Choice of cloud provider, database engine, networking model, disaster recovery strategy

Cross-functional collaboration

A developer collaborates mainly with other programmers and testers. Cloud Architect is a strongly cross-functional role:

• With DevOps/SRE: Defining CI/CD strategy, monitoring, observability
• With Security: Designing network segmentation, IAM policies, encryption at rest/in transit
• With Finance/Procurement: Cost optimisation, negotiating Enterprise Agreements with cloud providers
• With Legal/Compliance: Ensuring architecture compliance with GDPR, NIS2, industry standards (PCI-DSS, HIPAA)
• With Business Leadership: Translating business requirements into technical architecture

An architect must speak the language of business – be able to explain to the CTO why migration to serverless will pay back in 8 months, and to the CFO why investment in multi-region will increase SLA availability to 99.99%.

”Soft” skills become critical

Whilst a developer can focus mainly on hard skills (programming language, algorithms), an architect must develop:

• Communication and presentations: Presenting architectural proposals to the board, leading Architecture Decision Records (ADR)
• Mentoring: Raising the competencies of development teams in cloud best practices
• Negotiation: Balancing between business needs, technical constraints, and budget
• Strategic thinking: Seeing 2-3 years ahead, anticipating future scalability requirements and regulatory changes

Conclusion: If you like solving complex systemic problems, you’re interested not only in “how” but also “why” and “what for”, and communication and strategic thinking aren’t foreign to you – you have potential as a Cloud Architect.

What skills need to be developed to become a Cloud Architect?

Transitioning from developer to Cloud Architect requires systematic expansion of competencies. You don’t need to be an expert in everything immediately, but you need solid foundations in five key areas:

1. Networking and connectivity in the cloud

As a developer, you could avoid deep immersion in computer networks – it was enough that the application listened on port 8080. As an architect, networking is the foundation of everything.

What you must master:

VPC (Virtual Private Cloud) and subnetting:

• Designing CIDR blocks – how to correctly divide IP space (e.g., 10.0.0.0/16 vs 10.0.0.0/24)
• Public vs private subnets – when to use each type
• Multi-tier architecture (public subnet for load balancers, private for applications, isolated for databases)
• Peering between VPCs and cross-account communication

Routing and gateways:

• Internet Gateway, NAT Gateway, Transit Gateway – differences and use cases
• Route tables and routing priorities
• VPN connections (site-to-site, client VPN)
• Direct Connect / ExpressRoute – dedicated connections to on-premise

Load balancing and traffic management:

• Application Load Balancer (ALB) vs Network Load Balancer (NLB) vs Classic Load Balancer
• Health checks, target groups, listener rules
• Cross-zone load balancing
• Global load balancing for multi-region

DNS and service discovery:

• Route 53 (AWS) / Azure DNS – routing policies (simple, weighted, latency, failover, geolocation)
• Private DNS zones for internal services
• Service discovery for microservices (AWS Cloud Map, Consul)

Practical example: You’re designing architecture for an e-commerce application operating in three availability zones. You must plan:

• CIDR: 10.0.0.0/16 (65,536 IP addresses)
• 6 subnets (3 AZ × 2 tiers: public for ALB, private for application)
• NAT Gateway in each AZ for high availability
• Transit Gateway connecting production, staging, and shared services VPC
• Latency-based routing policy for users from different regions of Poland

Learning tools: VPC Hands-on Labs (AWS Training), Azure Virtual Network Labs, visualisation tools (draw.io, Lucidchart with AWS/Azure stencils)

2. Security and compliance in cloud environment

Security is non-negotiable for a Cloud Architect. A security breach in the cloud can cost a company millions of złoty and its reputation.

What you must master:

Identity and Access Management (IAM):

• Principle of Least Privilege – granting minimal permissions
• Designing IAM roles vs IAM users
• Service Control Policies (SCP) at AWS Organisations level
• Federation (SAML, OIDC) – integration with corporate identity providers (Azure AD, Okta)
• Cross-account access patterns

Encryption at rest and in transit:

• KMS (Key Management Service) – encryption key management
• Encryption for S3, EBS, RDS, DynamoDB
• TLS/SSL certificates – AWS Certificate Manager, Let’s Encrypt
• Secrets management – AWS Secrets Manager, Azure Key Vault, HashiCorp Vault

Network security:

• Security Groups vs Network ACLs (stateful vs stateless)
• Web Application Firewall (WAF) – protection against OWASP Top 10
• DDoS protection – AWS Shield, Azure DDoS Protection
• VPC Flow Logs – network traffic analysis

Compliance frameworks:

• GDPR – data residency, right to erasure, data portability
• NIS2 – requirements for operators of essential services
• ISO 27001, SOC 2 – security controls
• Industry-specific: PCI-DSS (finance), HIPAA (healthcare)

Zero Trust Architecture:

• Network microsegmentation
• Continuous verification
• Assume breach mindset

Practical example: You’re designing architecture for a fintech processing payment data (PCI-DSS requirement):

• Isolation of cardholder data environment (CDE) in a separate VPC
• Encryption at rest for all data (KMS with customer-managed keys)
• WAF with rules blocking SQL injection and XSS
• VPC Flow Logs sent to SIEM (Security Information and Event Management)
• Multi-factor authentication (MFA) mandatory for administrative access
• Regular penetration testing and vulnerability scanning
• Audit logs in CloudTrail with immutable storage (S3 Object Lock)

Learning tools: AWS Security Specialty certification path, Azure Security Engineer Associate, hands-on labs with IAM policies, CTF (Capture The Flag) challenges for cloud security

3. Infrastructure as Code (IaC) and automation

An architect does not configure infrastructure manually through the console. Everything must be replicable, versioned, and auditable – this requires IaC.

What you must master:

IaC frameworks:

• Terraform (most popular, multi-cloud)
• AWS CloudFormation / Azure Resource Manager (ARM) / Google Cloud Deployment Manager
• Pulumi (IaC in programming languages: Python, TypeScript)
• CDK (Cloud Development Kit) – AWS/Azure CDK

Key IaC concepts:

• State management (Terraform state file, remote backend in S3)
• Modules and reusability – how to structure IaC code
• Drift detection – detecting manual changes in infrastructure
• Plan → Apply → Destroy workflow
• Dependency management between resources

CI/CD for infrastructure:

• GitOps – infrastructure changes through pull requests
• Automated IaC testing (linting, security scanning, cost estimation)
• Staged deployments (dev → staging → production)
• Rollback strategies

Configuration management:

• Ansible, Chef, Puppet – for configuration at OS/application level
• Differences between IaC (provisioning) and configuration management

Immutable infrastructure:

• “Cattle vs pets” concept – disposable infrastructure, not patched
• Golden images (AMI, custom VM images)
• Container-based infrastructure (ECS, EKS, AKS)

Practical example: You write a Terraform module for a standard web application:

• VPC with subnets (public + private in 3 AZ)
• Application Load Balancer
• Auto Scaling Group with Launch Template
• RDS Multi-AZ for database
• S3 bucket for static assets + CloudFront distribution
• IAM roles for EC2 instances
• CloudWatch alarms for key metrics
• Everything parameterisable (variables.tf) and testable

Learning tools: HashiCorp Learn (Terraform tutorials), AWS CloudFormation workshops, Terraform Associate certification, hands-on projects on GitHub

4. Cost optimisation and FinOps

A developer rarely sees the cloud bill. An architect is responsible for every złoty spent in the cloud. FinOps (Financial Operations) is a growing discipline in cloud computing.

What you must master:

Cloud pricing models:

• On-Demand – pay-as-you-go, most expensive, full flexibility
• Reserved Instances / Reserved Capacity – 1-3 year commitment, savings up to 72%
• Savings Plans – more flexible than RI, savings up to 66%
• Spot Instances – unused AWS capacity, savings up to 90%, but can be reclaimed
• Differences between providers (AWS vs Azure vs GCP)

Cost allocation and tagging:

• Resource tagging strategy (project, team, environment, cost centre)
• Cost allocation reports
• Chargeback and showback – allocating costs to departments

Right-sizing and waste elimination:

• Identifying overprovisioned resources (instances with 5% CPU)
• Downscaling or changing instance types
• Removing zombie resources (unused EBS volumes, unattached Elastic IPs, old snapshots)
• Lifecycle policies for S3 (transition to cheaper storage classes, expiration)

Architectural patterns for cost optimisation:

• Serverless – you pay for execution time, not idle capacity (Lambda, DynamoDB on-demand)
• Auto Scaling – matching capacity to actual load
• Multi-tier storage – hot data in SSD, cold data in Glacier
• Content delivery – CDN instead of direct origin requests
• Database optimisation – read replicas, caching (Redis, Memcached), query optimisation

Monitoring and alerting:

• AWS Cost Explorer, Azure Cost Management, GCP Billing Reports
• Budgets and alerts when thresholds are exceeded
• Anomaly detection – unusual cost increases
• Third-party tools: CloudHealth, Cloudability, Apptio

Practical example: You audit costs of an e-commerce application:

• Current bill: 50,000 PLN/month
• Optimisations found:
  • EC2: changing t3.large (always on-demand) to t3.medium with Savings Plan → -15,000 PLN/month
  • RDS: downsize from db.m5.xlarge to db.m5.large (overprovisioned) → -5,000 PLN/month
  • S3: lifecycle policy for logs (transition to Glacier after 90 days) → -2,000 PLN/month
  • Unused EBS volumes and snapshots → -3,000 PLN/month
  • CloudFront with cache for static assets (reduction of origin requests) → -5,000 PLN/month
• Total: 30,000 PLN savings monthly (60% cost reduction)

Learning tools: FinOps Foundation training, AWS Cost Optimisation workshops, hands-on cost audits in demo accounts

5. Cloud-native design patterns and best practices

An architect must know proven patterns for typical architectural problems. You don’t reinvent the wheel – you apply proven solutions.

What you must master:

Well-Architected Frameworks:

• AWS Well-Architected Framework (5 pillars: operational excellence, security, reliability, performance efficiency, cost optimisation)
• Azure Well-Architected Framework
• Google Cloud Architecture Framework

Reliability patterns:

• Multi-AZ deployments – redundancy in availability zones
• Multi-region architectures – disaster recovery and latency optimisation
• Circuit breaker – protection against cascading failures
• Retry with exponential backoff – graceful degradation
• Health checks and auto-recovery

Scalability patterns:

• Horizontal scaling (scale out) vs vertical scaling (scale up)
• Stateless applications – easy to scale
• Database sharding – data partitioning
• Read replicas – offloading read traffic
• Caching layers (Redis, Memcached, CloudFront)

Decoupling patterns:

• Message queues (SQS, Azure Service Bus) – asynchronous processing
• Event-driven architecture (EventBridge, SNS, Event Grid)
• API Gateway – backend services abstraction
• Service mesh (Istio, Linkerd) – for microservices

Data patterns:

• Database per service vs shared database (microservices)
• CQRS (Command Query Responsibility Segregation)
• Event sourcing
• Data lake architectures (S3 + Athena + Glue)

Disaster recovery patterns:

• Backup and Restore (RTO/RPO in hours, cheapest)
• Pilot Light (RTO/RPO in tens of minutes)
• Warm Standby (RTO/RPO in minutes)
• Multi-Site Active/Active (RTO/RPO near zero, most expensive)

Practical example: You’re designing architecture for a B2B SaaS with requirements:

• Availability: 99.95% SLA
• Scalability: from 100 to 100,000 concurrent users
• Disaster recovery: RTO 15 minutes, RPO 5 minutes

Your proposal:

• Region: eu-central-1 (Frankfurt) – primary, eu-west-1 (Ireland) – DR
• Compute: ECS Fargate (serverless containers) with Auto Scaling
• Database: Aurora PostgreSQL Multi-AZ + cross-region read replica
• Frontend: S3 + CloudFront (global CDN)
• API: ALB + API Gateway with WAF
• Messaging: SQS for async tasks, SNS for notifications
• Monitoring: CloudWatch + X-Ray for distributed tracing
• Backup: Automatic snapshots every 5 minutes, cross-region replication
• DR procedure: Route53 health check with automatic failover to Ireland

Learning tools: AWS Solutions Architect certification, Azure Solutions Architect Expert, case studies from AWS/Azure blogs, books: “Designing Data-Intensive Applications” (Martin Kleppmann), “Cloud Native Patterns” (Cornelia Davis)

Which certifications are key for Cloud Architect?

Certifications won’t replace practical experience, but they’re a strong signal to employers that you’ve mastered the fundamentals. More importantly – the process of preparing for certification systematises knowledge.

Certification path – recommended steps

Stage 1: Foundation (3-6 months)

Start with a foundational certificate from your chosen provider:

AWS Certified Solutions Architect – Associate

• Level: Intermediate
• Preparation time: 2-4 months (assuming 10-15h/week)
• Cost: ~$150 (approx. 600 PLN)
• Covers: Designing solutions in AWS (compute, storage, databases, networking, security), cost optimisation, reliability
• Recommended for: Developers transitioning to Cloud Architect, first AWS certification
• Materials: AWS Training (free), A Cloud Guru, Tutorials Dojo Practice Exams, AWS documentation

OR

Microsoft Certified: Azure Solutions Architect Expert

• Requirements: First pass Azure Fundamentals (AZ-900), then Azure Administrator Associate (AZ-104), finally Azure Solutions Architect Expert (AZ-305)
• Level: Expert (requires 2 lower-level certificates)
• Preparation time: 4-6 months total
• Cost: ~$165 per exam (~660 PLN), 3 exams in total
• Covers: Designing architecture for infrastructure, security, data platform, business applications
• Recommended for: Companies with Microsoft ecosystem, enterprise projects with Azure AD integration
• Materials: Microsoft Learn (free), Pluralsight, WhizLabs, Azure documentation

Which to choose: AWS or Azure?

• AWS: Dominates market (32% share), most job offers for AWS architects, broader service ecosystem
• Azure: Strong position in enterprise (especially companies with Microsoft 365/Active Directory), growing market share (23%)
• Practical advice: Choose the provider used in your current company or dominant in your region (check job offers on NoFluffJobs/JustJoinIT)

Stage 2: Professional (6-12 months from start)

After Associate/Expert, go for Professional level:

AWS Certified Solutions Architect – Professional

• Level: Advanced
• Preparation time: 3-6 months (requires solid practice)
• Cost: ~$300 (approx. 1,200 PLN)
• Covers: Advanced architecture (multi-region, hybrid cloud, migration strategies), enterprise-level cost optimisation, compliance, disaster recovery
• Informal requirements: 1-2 years experience with AWS
• Difficulty: High – case studies require deep understanding of trade-offs
• Recommended for: Those targeting Senior Cloud Architect roles, AWS-focused companies

Materials:

• AWS Training: Advanced Architecting on AWS (3 days, paid)
• Adrian Cantrill’s SAP-C02 Course (Udemy, ~$15)
• Tutorials Dojo Practice Exams (hardest, most realistic)
• AWS Whitepapers (mandatory): Well-Architected Framework, Disaster Recovery, Security Pillar

Microsoft Certified: Azure Solutions Architect Expert (AZ-305)

• Already covered above as part of Azure path
• After AZ-305 consider specialisation:
  • Azure Security Engineer Associate (AZ-500) – for security-focused roles
  • DevOps Engineer Expert (AZ-400) – for architects working closely with DevOps

Stage 3: Specialisations (12-18 months+)

After a solid foundation, consider specialist certificates:

AWS Certified Security – Specialty

• For architects focused on security, compliance (finance, healthcare)
• Covers: advanced IAM, encryption, incident response, logging & monitoring

AWS Certified Advanced Networking – Specialty

• For architects designing complex network topologies (hybrid cloud, multi-VPC, Direct Connect)

Google Cloud Professional Cloud Architect

• If you work in a multi-cloud environment or the company uses GCP
• GCP has approx. 11% market share, but strong position in ML/AI workloads

Kubernetes certificates (CNCF):

• Certified Kubernetes Administrator (CKA) – for architects working with EKS/AKS/GKE
• Certified Kubernetes Application Developer (CKAD)

Do certifications actually help in getting a job?

Data from Polish market (NoFluffJobs, Bulldogjob, 2025-2026):

• 68% of Cloud Architect offers require or prefer AWS/Azure certifications
• Median salary for Cloud Architect with AWS SAP certification: 24,000-28,000 PLN gross (employment contract)
• Median salary for Cloud Architect without certification: 18,000-22,000 PLN gross
• Difference: ~25-30% higher offer with certification

Testimonials from EITT specialists:

“I passed AWS Solutions Architect Professional after 6 months of intensive study. Within a month I received 3 offers – two 30% higher than my previous salary as senior developer.” – Piotr K., Cloud Architect at international fintech

“Certificates opened doors. In interviews they asked less about basic stuff, we immediately moved on to case studies. Recruiters knew I had the foundation.” – Agnieszka M., Azure Solutions Architect

Important note: Certificate without practice is a red flag. Employers check:

• Can you explain architectural decisions from the certification?
• Have you used these technologies in real projects?
• Do you have a portfolio (GitHub with IaC, architecture diagrams)?

Conclusion: Certifications are a key element, but only in combination with practical experience. Treat them as a learning structure, not an end in itself.

How to build a transition plan – 12-18 month roadmap?

Here’s a proven, concrete roadmap for transitioning from developer to Cloud Architect. It assumes you work full-time (you’ll invest 10-15h weekly in learning) and have at least 2-3 years experience as a developer.

Months 1-3: Cloud fundamentals + first certification

Goals:

• Understand basics of one cloud provider (AWS or Azure)
• Pass Associate/Fundamentals certification
• Build first environment in the cloud

Concrete actions:

Week 1-2: Theory + setup

• Set up AWS Free Tier account or Azure Free Account
• Learning: AWS Cloud Practitioner Essentials (free AWS Training course) OR Azure Fundamentals (AZ-900) on Microsoft Learn
• Install AWS CLI / Azure CLI, configure credentials
• Do first lab: launch EC2 instance / Azure VM, connect via SSH, install webserver

Week 3-8: Certification preparation

• AWS: A Cloud Guru/Udemy course “AWS Certified Solutions Architect Associate”
• Azure: Microsoft Learn learning path for AZ-104 (Administrator) + AZ-305 (Architect)
• Hands-on labs (weekly):
  • Week 3: VPC setup with public/private subnets, NAT gateway, bastion host
  • Week 4: Load balancer + Auto Scaling Group
  • Week 5: RDS Multi-AZ database + backups
  • Week 6: S3 bucket + lifecycle policies + CloudFront
  • Week 7: IAM roles, policies, federated access
  • Week 8: CloudWatch monitoring, SNS alerts
• Document everything: Create architectural diagrams in draw.io, take notes

Week 9-12: Intensive revision + exam

• Practice exams: Tutorials Dojo (AWS) / WhizLabs (Azure) – do tests, analyse mistakes
• Read AWS Well-Architected Framework (whitepaper) / Azure Well-Architected Framework
• Week 12: Pass certification exam

Result after 3 months:

• ✅ AWS SAA or Azure Administrator/Fundamentals certificate
• ✅ Practical ability to set up basic infrastructure
• ✅ Portfolio: 6-8 hands-on projects (publish on GitHub)

Months 4-6: Deepening knowledge + IaC

Goals:

• Master Infrastructure as Code
• Implement automation in current job (first architectural projects)
• Develop networking and security

Concrete actions:

Terraform (Months 4-5):

• Week 13-14: HashiCorp Learn – Terraform Associate tutorials
• Week 15-16: Rewrite your hands-on labs from months 1-3 in Terraform
• Week 17-18: Create reusable Terraform module for standard 3-tier application (web/app/db)
• Week 19-20: CI/CD for Terraform (GitHub Actions – plan/apply on pull request)

Networking deep dive (Month 5):

• Course: “AWS Advanced Networking” or “Azure Virtual Networks Deep Dive”
• Hands-on labs:
  • VPC peering and Transit Gateway (AWS) / VNet peering and Virtual WAN (Azure)
  • VPN site-to-site setup
  • Private Link / Private Endpoints
  • Advanced network segmentation and Security Groups

Security (Month 6):

• Course: AWS Security Fundamentals / Azure Security Engineer (AZ-500 materials)
• Hands-on labs:
  • IAM policy design (least privilege)
  • KMS encryption (at rest for S3, RDS, EBS)
  • WAF rules (OWASP Top 10 mitigation)
  • GuardDuty / Security Centre setup
• Final project: Design secure architecture for fintech application (PCI-DSS compliance)

At work:

• Propose initiative: “I can prepare proof-of-concept migration of our dev environment to cloud?”
• Take responsibility for cloud-related tasks in the team
• Participate in architecture decision meetings – observe, ask questions

Result after 6 months:

• ✅ Ability to write production-grade Terraform
• ✅ Deep knowledge of networking and security
• ✅ First architectural projects in current company (POC, dev environment)

Months 7-9: Advanced architecture + second certification

Goals:

• Pass Professional/Expert certification
• Master cloud-native patterns (microservices, serverless, containers)
• Prepare for role change

Concrete actions:

AWS Solutions Architect Professional / Azure Solutions Architect Expert (Months 7-9):

• Week 25-32: Adrian Cantrill SAP-C02 course (AWS) or official Microsoft learning path AZ-305
• Hands-on labs (advanced):
  • Multi-region active-active architecture with Route53 failover
  • Hybrid cloud: Direct Connect / ExpressRoute setup (simulation)
  • Migration strategy: lift-and-shift vs re-architecture
  • Disaster recovery: Warm Standby implementation
  • Cost optimisation: Reserved Instances strategy, Savings Plans calculator
• Practice exams: Tutorials Dojo Professional level – target >85% score
• Week 36: Pass Professional/Expert exam

Containers and orchestration (Month 8):

• Docker fundamentals (if you don’t know yet)
• Kubernetes basics – Certified Kubernetes Administrator (CKA) materials
• AWS ECS/EKS or Azure AKS – deploy containerised application
• Service mesh basics (Istio introduction)

Serverless (Month 9):

• AWS Lambda deep dive / Azure Functions
• API Gateway + Lambda integration
• DynamoDB / Cosmos DB (NoSQL in cloud)
• Project: Create serverless API (Lambda + API Gateway + DynamoDB) with IaC

At work:

• Initiate discussion: “Should we consider serverless for our new project?”
• Present cost-benefit analysis of cloud migration for one project
• Propose yourself as “Cloud Champion” in team – mentor for other developers

Result after 9 months:

• ✅ Professional/Expert certificate (AWS SAP or Azure AZ-305)
• ✅ Ability to design complex architectures (multi-region, hybrid, serverless)
• ✅ Visibility as cloud expert in current company

Months 10-12: Building portfolio + networking + job search

Goals:

• Create portfolio showing architectural skills
• Build personal brand
• Start recruitment conversations for Cloud Architect position

Concrete actions:

Portfolio projects (Month 10): Create 2-3 showcase projects on GitHub:

Project 1: E-commerce platform architecture

• Multi-tier (web/app/db), Auto Scaling, RDS Multi-AZ, S3 + CloudFront, WAF
• Terraform code + detailed documentation (README.md)
• Architecture diagram (draw.io/Lucidchart)
• Cost estimation (AWS Pricing Calculator)

Project 2: Serverless data pipeline

• S3 → Lambda → DynamoDB/RDS → API Gateway
• Event-driven (S3 event notifications)
• IaC (Terraform or SAM/CloudFormation)
• Monitoring (CloudWatch Dashboards)

Project 3: Disaster recovery solution

• Active-passive setup (primary region + DR region)
• RTO/RPO calculations
• Runbook (failover procedure)

Personal brand (Month 11):

• LinkedIn: Add certificates, describe your cloud projects, use keywords (AWS, Azure, Terraform, Cloud Architect)
• Blog/Medium: Write 2-3 articles:
  • “5 mistakes I made learning AWS”
  • “How I optimised cloud costs by 40% in my company”
  • “Terraform best practices – lessons from real projects”
• Conferences/meetups: Participate in AWS User Group Poland, Azure User Group, give lightning talk

Job search (Month 12):

• Update CV (format: developer → cloud engineer → cloud architect progression)
• Apply for positions: Cloud Architect, Solutions Architect, Cloud Infrastructure Architect
• Target: Companies with mature cloud adoption (fintech, SaaS, e-commerce scale-ups)
• Prepare for interviews:
  • Whiteboard architecture: Practise designing architecture on whiteboard (20-30 minute case study)
  • Behavioural questions: STAR format (Situation, Task, Action, Result)
  • Technical deep dive: Prepare for questions about trade-offs (CAP theorem, eventual consistency, cost vs performance)

In current company:

• Officially propose transition: “I’d like to develop towards Cloud Architect, can we plan a transition?”
• If company doesn’t have such role – start external job search

Result after 12 months:

• ✅ Portfolio on GitHub with 3 showcase projects
• ✅ Active personal brand (LinkedIn, blog)
• ✅ First job offers as Cloud Architect OR transition in current company

Months 13-18: First 6 months as Cloud Architect

Goals:

• Build credibility in new role
• Deepen knowledge in areas specific to your industry
• Mentor others, develop team capabilities

Concrete actions:

First projects (Months 13-15):

• Take ownership of 1-2 key architectures
• Document Architecture Decision Records (ADR) – why we chose X instead of Y
• Conduct Well-Architected Review for existing systems
• Propose quick wins (cost optimisation, security hardening)

Specialisation (Months 16-18): Choose niche according to industry:

• Fintech/Banking: Security (AZ-500, AWS Security Specialty), compliance (PCI-DSS)
• Healthcare: HIPAA compliance, data privacy
• Media/Gaming: Serverless, high-traffic architectures, CDN optimisation
• IoT: Edge computing (AWS Greengrass, Azure IoT Edge)

Mentoring:

• Conduct lunch & learn for developers: “Cloud fundamentals for developers”
• Code review for IaC pull requests
• Help junior developers prepare for certification

Continuous learning:

• Follow AWS/Azure release notes (new services, features)
• Read case studies (AWS Architecture Blog, Azure Blog)
• Additional certifications (Kubernetes, security specialty)

Result after 18 months:

• ✅ Stable position as Cloud Architect
• ✅ Track record of successful projects
• ✅ Industry recognition (conferences, blog, LinkedIn)
• ✅ Salary 22,000-28,000 PLN gross (mid-level Cloud Architect in Poland)

How to build architectural experience whilst being a developer?

The biggest challenge: how to gain architectural experience when I’m not yet an architect? This is a classic catch-22. Here are proven strategies:

1. Start with small steps in current company

Don’t wait for an official title – start acting like an architect today.

Concrete steps:

Take responsibility for development infrastructure:

• “Can I move our dev/staging environment to cloud?”
• “I’ll automate test environment provisioning with Terraform”
• This is a great experimental ground without production risk

Propose proof-of-concept for new technologies:

• “I’ll check if serverless (Lambda) will work for our background jobs – shall we do a POC?”
• POC gives you space to experiment and build portfolio case studies

Participate in architecture discussions:

• Even if you don’t have a formal role, ask questions in technical meetings:
  • “Why did we choose ALB instead of NLB?”
  • “Have we considered multi-AZ for this database?”
• You show you’re thinking architecturally

Volunteer for cloud migration projects:

• If company is migrating to cloud – that’s gold. You’ll work close to architects, learn through observation

Write Architecture Decision Records (ADR):

• Document technical decisions in team (even if there’s no such process yet)
• ADR format: Context → Decision → Consequences
• This shows you understand not just “how” but “why”

Success example:

“I started by moving our dev environment to AWS with Terraform. After 3 months I proposed staging migration – got green light. After a year I was de facto cloud lead in the team, despite still officially being a senior developer. A year later I got promoted to Cloud Architect.” – Tomasz P., Cloud Architect at Polish scale-up

2. Side projects – Your architectural laboratory

Personal projects give you 100% control and space to experiment.

What to build:

Real-world applications, not tutorials:

• Good project: E-commerce shop with full infrastructure (VPC, ALB, RDS, S3, CloudFront, monitoring)
• Poor project: “Hello World Lambda” from AWS tutorial

Focus on technological diversity:

• Project 1: Monolith on EC2 + RDS (traditional architecture)
• Project 2: Microservices on ECS/EKS (containers)
• Project 3: Serverless (Lambda + API Gateway + DynamoDB)
• This shows you can choose the right tool for the problem

Documentation > Code:

• README.md: Problem → Solution → Architecture → Cost estimation → Lessons learned
• Architecture diagram (draw.io, cloudcraft.co)
• ADR (Architecture Decision Records) – explain key decisions
• Recruiters look at documentation, not code (most won’t read all Terraform anyway)

Open source contributions:

• Contribute to projects related to cloud infrastructure (Terraform providers, Kubernetes operators)
• This shows collaboration skills and community activity

Publish case studies:

• Blog post: “How I built disaster recovery solution for 1000 PLN monthly”
• Share on LinkedIn, Reddit (r/aws, r/azure), Dev.to

Success example:

“I built a side project – Airbnb clone with full AWS infrastructure (ECS, Aurora, S3, CloudFront, Route53). Wrote case study ‘How I built scalable Airbnb clone for $50/month’. Post got 20k views on Dev.to. I received 5 messages from recruiters within a month.” – Karolina S., currently Cloud Architect in Warsaw

3. Freelancing and consulting

Freelancing allows you to gain exposure to different projects and technologies faster than full-time employment.

Where to look:

• Upwork, Toptal: Projects “AWS migration”, “Terraform infrastructure”, “Cloud architecture consulting”
• Polish platforms: Useme, Gruper – “Cloud infrastructure”, “DevOps”
• LinkedIn: Actively comment on posts with hashtag #AWS #Azure #CloudArchitecture – clients will find you

Which projects to take:

• First project: “Terraform automation for small business” – low risk, builds confidence
• Second project: “AWS migration for legacy application” – more complex, better paid
• Avoid: Projects only “maintenance” (patching, monitoring) – you’re not building architecture skills

Pricing:

• Junior level (first projects): 150-250 PLN/h
• Mid-level (after 6-12 months): 300-450 PLN/h
• Senior level (18+ months): 500-800 PLN/h

Benefits:

• Experience diversification – you see different architectures, problems, stacks
• Portfolio case studies (with client consent)
• Additional income – you can invest in training, certificates, conferences
• Network – satisfied clients recommend further

Success example:

“I took 3 freelance projects over a year (after hours, parallel with employment). Each was different: e-commerce migration, IoT platform on AWS, multi-cloud setup. It was intensive, but I built a portfolio that opened doors to my first job as architect.” – Marcin L., Cloud Solutions Architect

4. Community activity

Personal branding accelerates your career – you become a “known expert”.

Concrete actions:

LinkedIn:

• Publish regularly (1-2 posts weekly): TIL (Today I Learned), quick tips, lessons learned
• Comment on posts from industry cloud influencers (Adrian Cockcroft, Corey Quinn, AWS Heroes)
• Use hashtags: #AWS #Azure #CloudArchitecture #Terraform #DevOps

Blogging:

• Medium, Dev.to, own blog (Hugo/Jekyll + GitHub Pages)
• Write practical content: “How to…”, “5 mistakes…”, “Complete guide to…”
• SEO: target keywords “AWS architecture”, “Terraform tutorial”, “cloud cost optimisation”

Conferences and meetups:

• Listen and network: AWS Summit Poland, Microsoft Ignite, DevOpsDays
• Lightning talks (5-10 min): Low entry threshold, great training
• Full presentations (30-45 min): After a year’s experience, propose talk “My journey from developer to Cloud Architect”

YouTube/Twitch:

• Live coding: “Building AWS architecture from scratch”
• Niche, but highly engaging – you show practical skills in real-time

Networking effect:

• Recruiters find you through content
• Referrals from community (most cloud architect offers aren’t publicly advertised)
• Invitations to consulting gigs

Success example:

“I started writing on Medium – articles about Terraform and AWS. After 6 months I had 5000 followers. I received invitation to speak at AWS User Group Poland, then conference. A recruiter from international company found me through LinkedIn – she saw my posts. Got offer 35% higher than previous position.” – Ania W., Senior Cloud Architect

5. Mentoring and teaching

“If you can explain it, you truly understand it.”

Concrete actions:

Internal training in company:

• Conduct lunch & learn: “AWS basics for developers”, “Terraform introduction”
• This builds your position as expert in-house

Mentoring juniors:

• Become mentor for junior developers learning cloud
• Platforms: MentorCruise, GrowthMentor, ADPList (free mentoring)

Teaching online:

• Create mini-course on Udemy (even free) – it’s a portfolio piece
• Tutorials on YouTube

Benefits:

• Consolidates knowledge – teaching forces deep understanding
• Builds confidence – if you can teach, you can present architectures to stakeholders
• Network and reputation

Cloud Architect vs Developer salaries – how much can you earn?

Transitioning to Cloud Architect is a significant financial leap. Here’s real data from the Polish market (2025-2026).

Median salaries – comparison

Data from NoFluffJobs, Bulldogjob, JustJoinIT (sample: 2000+ offers, 2025-2026):

Position	Junior	Mid	Senior	Lead/Principal
Backend Developer	8,000-12,000	14,000-18,000	18,000-24,000	24,000-30,000
Cloud Engineer	12,000-16,000	16,000-22,000	22,000-28,000	28,000-35,000
Cloud Architect	–	20,000-26,000	26,000-34,000	34,000-45,000+

All amounts in PLN gross (employment contract), Warsaw/remote

Key conclusions:

• Mid-level Cloud Architect earns like Senior Developer (20-26k vs 18-24k)
• Senior Cloud Architect earns ~40% more than Senior Developer (26-34k vs 18-24k)
• Lead Cloud Architect earns like VP Engineering (34-45k+)

What influences salaries?

1. Certifications

• Without certification: lower end of range (18-22k for mid-level)
• AWS SAA: +10-15%
• AWS SAP: +25-30%
• Multi-cloud (AWS + Azure): +15-20%

2. Industry

• Highest paying: Fintech, banking, gaming, e-commerce scale-ups (30-40% premium)
• Average: Software houses, enterprise, outsourcing (baseline)
• Lowest: Agencies, small local companies (15-25% below baseline)

3. Company size

• Startup (<50 people): Lower base salary (15-25k), but equity
• Scale-up (50-500): Medium/high (22-32k), equity or bonus
• Enterprise (500+): Medium base (20-28k), stability, benefits
• Big Tech (Google, Amazon): Highest (35-50k+), equity, benefits

4. Experience

• 0-2 years as architect: Mid-level (20-26k)
• 2-5 years: Senior (26-34k)
• 5+ years: Lead/Principal (34-45k+)

5. Contract type

• Employment contract: Baseline (as in table above)
• B2B: +20-30% gross, but no social security, holidays (real take-home ~equal or +10%)
• Foreign contract (UK, DE, Nordics): +50-100% (45-70k PLN equivalent)

Examples of real offers (anonymised)

Offer 1: Mid-level Cloud Architect, fintech (Warsaw, remote)

• Salary: 24,000-28,000 PLN gross (employment contract)
• Requirements: AWS SAA, 3+ years experience (including 1 year cloud), Terraform
• Stack: AWS, Kubernetes (EKS), Terraform, Python
• Benefits: Private healthcare, Multisport, conference budget 5000 PLN/year

Offer 2: Senior Cloud Architect, e-commerce scale-up (remote EU)

• Salary: 30,000-36,000 PLN gross (B2B) or 24,000-28,000 PLN (employment contract)
• Requirements: AWS SAP or Azure Expert, 5+ years total experience, 2+ as architect
• Stack: Multi-cloud (AWS + GCP), Terraform, Kubernetes, Istio
• Benefits: Equity (0.1-0.5%), unlimited PTO, equipment budget

Offer 3: Lead Cloud Architect, international bank (Warsaw, hybrid)

• Salary: 38,000-44,000 PLN gross (employment contract)
• Requirements: AWS + Azure certifications (SAP + AZ-305), 7+ years experience, security specialty
• Stack: Hybrid cloud (AWS + Azure + on-premise), regulatory compliance (PCI-DSS, GDPR)
• Benefits: Annual bonus 20%, private healthcare family, company car

Offer 4: Principal Cloud Architect, Big Tech (remote global)

• Salary: 50,000-65,000 PLN equivalent (USD contract, ~$160k-$200k base)
• Requirements: 10+ years experience, multiple certifications, proven track record at scale
• Stack: Multi-cloud, kubernetes at scale, FinOps, architecture governance
• Benefits: Equity (RSU), relocation package, global healthcare

Growth prospects – next career steps

After reaching Senior/Lead Cloud Architect position, you have several paths:

1. Technical specialisation:

• Principal/Staff Architect (45-60k+): Architect for entire organisation, strategic technical decisions
• Distinguished Engineer (60-80k+): Highest IC (individual contributor) level – equal to VP

2. Management:

• Head of Cloud / Cloud Lead (40-50k): Managing team of architects (5-10 people)
• VP Engineering / CTO (50-80k+): C-level, strategic technology leadership

3. Consulting:

• Independent consultant (500-1200 PLN/h): High-value, project-based
• Partner in consulting firm (equity + profit sharing)

4. Entrepreneurship:

• Cloud-native startup (with technical co-founder as CTO)
• DevOps tooling / IaC automation (building product for other architects)

Conclusion: Cloud Architect is one of the best paid and fastest growing career paths in IT. Investment of 12-18 months in learning and transition pays back many times over in 2-3 years.

How EITT supports transformation from developer to Cloud Architect?

At EITT we understand that career transformation isn’t just about learning technology – it’s changing mindset, building confidence, and practical experience. Our “Developer to Cloud Architect” programme was designed specifically for people in your situation.

Our approach: from foundations to first job

1. Assessment and personalised roadmap

We start with individual consultation:

• Current state assessment: What skills do you already possess? (languages, frameworks, infrastructure experience)
• Target role analysis: Cloud Architect in which industry? AWS/Azure/GCP? Enterprise vs startup?
• Gap analysis: What do you need to learn to achieve the goal?
• Personalised roadmap: 12-18 month plan with milestones, recommended training, projects

Result: PDF document “Your Cloud Architect Roadmap” with concrete action plan.

2. Comprehensive cloud training – from basics to Professional

We offer a complete educational path tailored to your level:

Foundation level (3-4 months):

AWS for Developers – path to Solutions Architect (5 days, on-site/online)

• VPC, EC2, S3, RDS, Lambda – AWS fundamentals
• Hands-on labs: Setting up 3-tier web application
• Best practices: Security, cost optimisation
• Preparation for AWS Solutions Architect Associate
• Format: 40h (5 days × 8h), instructor + labs
• Price: 4,500 PLN

OR

Microsoft Azure for Architects – AZ-305 (4 days)

• Azure compute, storage, networking
• Identity management (Azure AD)
• Security and compliance
• Preparation for AZ-305 (Solutions Architect Expert)

Advanced level (6-9 months):

AWS Solutions Architect Professional – intensive bootcamp (10 days)

• Advanced architecture (multi-region, hybrid cloud)
• Migration strategies (6R framework)
• Disaster recovery planning
• Enterprise cost optimisation
• Security and compliance (GDPR, NIS2)
• Format: 80h (2 weeks intensive) + 40h self-paced labs
• Price: 9,500 PLN (includes exam voucher + 3 months lab access)

Infrastructure as Code with Terraform (3 days)

• Terraform fundamentals
• Best practices: modules, state management, CI/CD
• Multi-environment strategies
• Security scanning (tfsec, Checkov)
• Hands-on: Full application deployment
• Format: 24h (3 days), heavily hands-on (70% labs)
• Price: 3,200 PLN

Cloud Security Engineering (3 days)

• Advanced IAM, Zero Trust Architecture
• Encryption, secrets management
• Network security (Security Groups, NACLs, WAF)
• Incident response in cloud
• Format: 24h (3 days)
• Price: 3,500 PLN

Kubernetes for Cloud Architects (4 days)

• Kubernetes architecture
• EKS/AKS deployment and management
• Service mesh (Istio basics)
• Security (RBAC, Network Policies)
• Format: 32h (4 days)
• Price: 4,000 PLN

Specialisation level:

FinOps – Cloud Cost Optimisation (2 days)

• Cloud pricing models deep dive
• Cost allocation strategies
• Automation tools (AWS Cost Explorer, Cloudability)
• Real case study: Optimising costs by 40%
• Format: 16h (2 days)
• Price: 2,800 PLN

Multi-Cloud Architecture (3 days)

• AWS vs Azure vs GCP – when to choose what
• Multi-cloud networking (interconnects)
• Unified observability
• Terraform multi-cloud
• Format: 24h (3 days)
• Price: 3,500 PLN

3. Practical projects and mentoring

Cloud Architecture Capstone Project (3 months, part-time):

• You work on real-world case study (e.g., “Design architecture for fintech processing 1M transactions/day”)
• Mentor (Senior Cloud Architect with min. 5 years experience) reviews your solutions weekly
• You deliver: Architecture diagram, IaC code (Terraform), documentation, cost estimation, DR plan
• Result: Portfolio piece ready to show recruiters
• Price: 5,000 PLN (3 months 1:1 mentoring)

Code review and feedback:

• You send your IaC projects (Terraform, CloudFormation) for review
• Senior architect from EITT provides detailed feedback (security, cost, best practices)
• Format: Asynchronous (Slack/email), 48h turnaround
• Price: 500 PLN/review

4. Job search support

Career coaching (3 sessions × 1.5h):

• Session 1: Preparing CV and LinkedIn profile (optimisation for Cloud Architect roles)
• Session 2: Mock interview – technical (whiteboard architecture design)
• Session 3: Mock interview – behavioural + negotiation strategies
• Price: 2,400 PLN

Networking events:

• Access to EITT Cloud Architects Community (Slack, quarterly meetups)
• Connection with EITT alumni working as Cloud Architects (referrals)

5. Financing and flexibility

Flexible payment:

• Instalment payments (up to 12 instalments 0%)
• Employer-sponsored training (we collaborate with HR/L&D departments)

Success guarantee:

• If you don’t pass certification after our course – free re-take of course (condition: attendance >90%, passing quizzes)

Why EITT?

• 500+ experts: Our trainers are practitioners – Senior Cloud Architects with AWS/Azure/GCP certifications, working in enterprise and scale-ups
• 2500+ training sessions delivered: Trusted by Orange, PZU, PKO BP, Allegro, Polish fintechs and scale-ups
• 4.8/5 average rating: From training participants (data from last 12 months)
• Practical approach: 60-70% of time is hands-on labs, not boring theory
• Real-world case studies: We use examples from Polish market, regulations (GDPR, NIS2), problems you encounter at work

Success stories:

“I completed full EITT path: AWS for Developers → Terraform → AWS Professional bootcamp. In 14 months I jumped from senior developer to Cloud Architect. Salary increased by 35%. Best investment in my career.” – Piotr K., Cloud Architect at international fintech (Kraków)

“Mentoring from EITT opened my eyes to how architects really think. My mentor (architect with 8 years experience) showed me not just ‘how’ but ‘why’. That’s priceless.” – Agnieszka M., currently Azure Solutions Architect (Warsaw)

Ready to start transformation?

👉 Check our Cloud training and certifications 👉 Book free consultation – we’ll plan your roadmap 👉 Download guide “From Developer to Cloud Architect – Complete Roadmap 2026”

FAQ – most common questions about transitioning to Cloud Architect

Do I need computer science degree to become Cloud Architect?

No, computer science degree isn’t required. The cloud computing market is extremely meritocratic – what counts is practical knowledge and skills, not diploma.

Data from survey amongst Cloud Architects (Poland, 2025):

• 62% have computer science degree (bachelor’s or master’s)
• 24% have degree from different field (mathematics, physics, economics, even humanities)
• 14% don’t have higher education – self-taught, bootcamps, certifications

What’s more important than diploma:

• Cloud certifications (AWS/Azure/GCP) – concrete, verifiable proof of knowledge
• Project portfolio – you show you can design architectures
• Practical experience – years working as developer/DevOps are equally valuable as degree

Example: One of the most valued Cloud Architects in Polish fintech is a person who:

• Studied English philology (!)
• Changed career to IT through programming bootcamp
• Worked 3 years as backend developer
• Independently passed AWS SAA and SAP
• Today earns 38,000 PLN gross as Lead Cloud Architect

Conclusion: If you have experience as developer (2-3+ years), certifications and portfolio – diploma won’t be a barrier.

How long does transitioning from developer to Cloud Architect realistically take?

Realistic timeframe: 12-24 months, depending on starting point and learning intensity.

Breakdown:

Fast track (12-15 months) – requires:

• Strong developer background (3+ years)
• Intensive learning (15-20h weekly)
• Full-time employment with access to cloud projects
• 2-3 certifications in this time (Associate → Professional)

Standard track (18-24 months) – more typical:

• 2-3 years experience as developer
• Moderate learning pace (10-15h weekly)
• Gradually taking on architecture responsibilities in current company
• 2 certifications (Associate + Professional)

Slow track (24-36 months) – if:

• Limited time available (5-10h weekly)
• Working in company without cloud projects (harder to build experience)
• Starting from junior developer level

Key milestones on timeline:

Time	Milestone	Possible title
3-6 months	First certification (SAA/AZ-104)	Still Developer (with cloud skills)
6-12 months	Hands-on projects in company, second certification (SAP/AZ-305)	Cloud Engineer or Junior Cloud Architect
12-18 months	Ownership for key architectures, portfolio	Mid-level Cloud Architect
18-24 months	Leading architecture decisions, mentoring	Senior Cloud Architect

Real examples:

Kasia (12 months):

• Start: Senior Backend Developer (Python, 4 years experience)
• Months 1-4: AWS SAA, Terraform, labs at weekends
• Months 5-8: Took ownership for migrating dev/staging to AWS in company
• Months 9-12: AWS SAP, production architecture proposal, promotion to Cloud Architect
• Result: Internal promotion, +30% salary

Michał (24 months):

• Start: Mid-level Frontend Developer (React, 2 years experience)
• Months 1-12: AWS SAA, backend learning (Node.js + databases), hands-on labs
• Months 13-18: Rewrote personal projects to IaC (Terraform), AWS SAP
• Months 19-24: Freelancing (3 small cloud migration projects), LinkedIn personal branding
• Result: New job as Cloud Architect in startup, +40% salary

Conclusion: 12-24 months is realistic timeframe with consistent work and strategic approach.

Do I need to know programming to be Cloud Architect?

Yes, but not at production developer level.

Required programming skills for Cloud Architect:

Basics of 1-2 languages (Python, Bash, Go):

• Python: For automation scripts, Lambda functions, SDK usage (boto3 for AWS)
• Bash: For scripting, automation, infrastructure troubleshooting
• Go (optional): For performance-critical Lambdas, Kubernetes operators

Level: You don’t need to write complex algorithms or frameworks. Enough to:

• Understand code written by developers (code review)
• Write simple automation scripts (100-200 lines)
• Debug infrastructure issues

IaC you must know:

• Terraform/CloudFormation: This is cloud architects’ “language” – declarative, not procedural
• Level: Intermediate – ability to write modules, state management

What’s NOT required:

• Advanced algorithms, data structures
• Deep understanding of specific frameworks (React, Django, Spring)
• Ability to write production-grade applications from scratch

Practical example: As Cloud Architect you might need to write:

• Lambda function that reacts to S3 event and processes file (50 lines Python)
• Bash script for backup automation (30 lines)
• Terraform module for standard 3-tier application (200-300 lines HCL)

But you WON’T:

• Implement application business logic
• Write frontend UI
• Debug complex bugs in application code

Conclusion: If you have 2-3 years as developer, your programming skills are sufficient. If your experience is mainly frontend (HTML/CSS/JS) – you should educate yourself in backend basics (REST API, databases, Linux).

Is Cloud Architect remote work, or do you need to be in office?

Cloud Architect is one of the most remote-friendly roles in IT.

Data from Polish market (job offers 2025-2026):

• 78% of Cloud Architect offers: Fully remote or hybrid (2 days/week in office)
• 15% of offers: Hybrid (3-4 days in office)
• 7% of offers: Fully on-site

Why Cloud Architect is great remote role:

• Working with cloud: Infrastructure is in AWS/Azure, not in local office – doesn’t matter if you work from Warsaw or Kraków
• Collaboration tools: Architecture discussions via Zoom/Teams, diagrams in Miro/Lucidchart, code reviews in GitHub
• Flexibility: Senior-level role – greater autonomy, trust-based work culture

When on-site is required:

• Highly regulated industries: Banking, government – may require on-site for security/compliance reasons
• Startup culture: Some startups prefer in-person collaboration (but this is rare)
• Occasional on-site: Architecture workshops, kickoffs, quarterly planning – usually 1-2 days/quarter

International perspective: Remote + cloud skills open doors to working for foreign companies:

• B2B contracts for UK/Germany/Nordic companies
• Salaries 50-100% higher (but in USD/EUR)
• Timezone compatibility (Western Europe: 1-2h difference, USA West Coast: 9h – more difficult)

Example:

“I work as Cloud Architect for London company, live in Gdańsk. Full remote, synchronous meetings only 2-3 times weekly (rest async Slack). I fly to London 4 times yearly for week-long planning. I earn in GBP, living costs in Poland – lifestyle upgrade.” – Adam R., Senior Cloud Architect

Conclusion: If work-life balance and remote flexibility are important to you – Cloud Architect is an excellent choice.

Do I need to specialise in one cloud provider, or is multi-cloud better?

Strategy: Start with one (deep), then expand (breadth).

Phase 1 (first 12-18 months): Deep dive in one provider

Advantages of specialisation:

• Faster path: Mastering one provider takes 1/3 of time vs. trying to learn all at once
• Certification: Professional certifications require deep knowledge of one ecosystem
• Job market: Most companies use 1 main provider (80% workloads) + second as backup

Which to choose:

• AWS: Largest market share (32%), most job offers, broadest ecosystem
• Azure: Strong position in enterprise (Microsoft ecosystem), growing share (23%)
• GCP: Smallest (11%), but strong in ML/AI, data analytics, tech startups

Polish realities (Cloud Architect job offers, 2025-2026):

• AWS: 58% of offers require/prefer AWS
• Azure: 32% of offers require/prefer Azure
• GCP: 10% of offers require/prefer GCP

Conclusion Phase 1: Choose AWS (largest job market) or Azure (if your company/industry is Microsoft ecosystem).

Phase 2 (after 18-24 months): Multi-cloud breadth

When to add second provider:

• You’ve mastered the first (Professional/Expert certificate + 1-2 years practice)
• You see multi-cloud job offers (usually better paid)
• Your company actually uses multi-cloud

Multi-cloud in practice:

• Most multi-cloud companies are 80/20: Main provider (AWS) + backup/specialisation (GCP for BigQuery, Azure for Active Directory integration)
• Rare: True multi-cloud (equal load between providers) – usually only in very large enterprises

Second provider – what you must know:

• Fundamentals are similar (VPC = Virtual Network, EC2 = VM, S3 = Blob Storage) – concepts transfer
• 60-70% of knowledge from first provider is transferable
• Focus on differences: Unique services, pricing models, management paradigms

Example multi-cloud career path:

• Months 1-18: AWS (SAA → SAP) – deep specialisation
• Months 19-24: Azure basics (AZ-900 → AZ-104) – breadth
• Months 25+: Multi-cloud projects, specialist certifications (Kubernetes, FinOps)

Conclusion: Start with one (AWS or Azure), add second after 18-24 months. Multi-cloud is advanced skill that increases your market value, but don’t try to learn everything at once initially.

What does a typical day of Cloud Architect work look like?

Cloud Architect is a highly interactive and varied role. Here’s a real day in the life of a Cloud Architect (based on interviews with 20 architects):

9:00-9:30 – Stand-up with DevOps/Platform Engineering team

• Synchronisation: what’s working, what’s not, blockers
• Architecture questions from team: “Should we use ALB or NLB for this workload?”
• Quick decisions, unblocking team

9:30-11:00 – Deep work: Architecture design

• You design new architecture for feature/project
• Diagrams in Lucidchart/draw.io (VPC, subnets, load balancers, databases, etc.)
• Architecture Decision Record (ADR): why we’re choosing Solution A instead of B
• Cost estimation in AWS Pricing Calculator

11:00-12:00 – Architecture review meeting

• Meeting with Product, Engineering Lead, Security Officer
• You present architecture proposal: diagrams, trade-offs, costs
• Discussion: security concerns, scalability, DR strategy
• Decisions & action items

12:00-13:00 – Lunch + learning

• Read AWS/Azure blog: new features, updates
• Follow community (Reddit r/aws, HackerNews, LinkedIn)

13:00-14:30 – Hands-on: Code review and IaC

• Review pull requests with Terraform code from team
• Feedback: security issues (overly permissive IAM), cost optimisation (use spot instances), best practices
• Write/update Terraform module for new project yourself

14:30-15:30 – Incident response / troubleshooting

• Alert: RDS high CPU
• Analyse CloudWatch metrics, RDS Performance Insights
• Identify: slow query + missing index
• Collaborate with developers: query optimisation, adding index
• Documentation: post-mortem, lessons learned

15:30-16:30 – Vendor meeting / Advisory

• Meeting with AWS Solutions Architect (external) – review RI/Savings Plans usage
• Discussion: new services (e.g., AWS App Runner) – do they fit our use cases?
• OR: Advisory for another team: “We’re planning legacy app migration, how to do it?”

16:30-17:30 – Documentation & knowledge sharing

• Update Architecture Wiki (Confluence/Notion)
• Write internal blog post: “How we reduced costs by 30% with Savings Plans”
• Preparation for lunch & learn next week: “Kubernetes best practices”

17:30-18:00 – Async work & wrap-up

• Respond to Slack: questions from developers, code review comments
• Planning tomorrow
• Learning: 30 min Udemy course (e.g., advanced Kubernetes)

Weekly recurring:

• 1x week: Architecture guild meeting – all architects in company, knowledge sharing
• 1x week: Cost review meeting – cloud bill analysis, waste identification
• 1x week: Security review – IAM policies audit, security incidents
• 1-2x month: All-hands engineering meeting – strategic updates

Differences by seniority:

Junior/Mid Cloud Architect:

• More hands-on (IaC coding, troubleshooting)
• Fewer strategic meetings
• Work under Senior Architect supervision

Senior/Lead Cloud Architect:

• More strategic decisions (multi-year roadmap, provider selection)
• Mentoring junior architects and developers
• Cross-functional collaboration (finance, legal, compliance)
• Tech representation to C-level

Conclusion: Cloud Architect is a varied role – balance between hands-on technical work (40%), meetings & collaboration (40%), learning & documentation (20%). If you like variety and don’t want to only code 8h daily – this role is for you.

What if my current company doesn’t use cloud – how to gain experience?

This is a common challenge in Poland – many companies still operate on-premise. Here are strategies:

Strategy 1: Initiate cloud adoption in current company (best option)

Concrete steps:

• Start small: Propose migrating dev/staging environment to cloud (low risk, proof of concept)
• Cost-benefit analysis: Prepare presentation for management: “Cloud can save us 30% infrastructure costs + accelerate deployment 3x”
• Volunteer: “I can do POC migration of one application to AWS/Azure – 2 weeks, zero production risk”
• Quick wins: Show tangible benefits (faster provisioning, auto-scaling, backup automation)

Success example:

“My company (manufacturing, 200 people) operated 100% on-premise. I proposed migrating test environment to AWS. Management agreed to POC. After 3 months: test environment in cloud, costs -40%, deployment from 2 days to 2 hours. A year later we migrated production. Got promotion to Cloud Lead.” – Tomasz P., currently Cloud Architect

Strategy 2: Side projects + portfolio (if company isn’t open to cloud)

Actions:

• Build cloud projects in free time (15-20h/week)
• Publish on GitHub with full documentation
• Write blog posts about your projects
• This substitutes “commercial experience” in recruiters’ eyes (especially in startups/scale-ups)

Strategy 3: Part-time freelancing (building commercial experience)

Actions:

• Take 1-2 small cloud-related freelance projects (Upwork, Useme)
• Even small projects (500-2000 PLN) give you “commercial cloud experience” for CV
• 3-4 projects over 6 months = solid track record

Strategy 4: Change job to “cloud-first company” earlier

If company absolutely isn’t interested in cloud, consider:

• Moving to company using cloud as Mid/Senior Developer (don’t wait for Architect title)
• After 6-12 months in cloud environment – transition to Cloud Architect in same company or externally
• Target companies: Fintechs, SaaS, e-commerce scale-ups, software houses with cloud-native clients

How to find cloud-first companies:

• Filter offers on NoFluffJobs: tech stack “AWS” or “Azure” + “Terraform” + “Kubernetes”
• Check: Allegro, OLX, Booksy, Brainly, Polish fintechs (Ramp, Uncapped), outsourcing for EU/US clients

Strategy 5: Internship / Junior Cloud Engineer (if you have <2 years experience)

Actions:

• Some companies offer “Junior Cloud Engineer” – role between DevOps and Architect
• Accept transitional step back (may be lower salary), but gain commercial cloud experience
• After a year: transition to Cloud Architect

Conclusion: Lack of cloud in current company is a challenge, but not blocker. Best strategy: initiate cloud adoption (shows leadership, builds experience). If impossible: side projects + freelancing + change company.

---

Summary: Transitioning from developer to Cloud Architect is an achievable goal in 12-24 months for programmers with 2-3+ years experience. It requires:

• Systematic learning (cloud fundamentals, networking, security, IaC)
• Obtaining key certifications (AWS SAA/SAP or Azure AZ-305)
• Building practical experience (company projects, side projects, freelancing)
• Personal branding (portfolio, LinkedIn, blog)

Benefits are enormous:

• Salary 25-40% higher than senior developer
• Remote-friendly work
• Strategic role with business impact
• Continuous development (cloud technology evolves non-stop)
• Career prospects (Principal Architect, CTO, consulting)

EITT supports you at every stage – from first AWS/Azure certification, through practical projects and mentoring, to career coaching and job placement. With our experience (500+ experts, 2500+ training sessions, 4.8/5 rating) we know proven paths to success.

Ready to start your transformation?

👉 Check our Cloud Architecture training and AWS/Azure certifications 👉 Book free consultation – we’ll discuss your personalised roadmap 👉 Join EITT Cloud Architects Community – networking, mentoring, job opportunities

Don’t wait – invest in yourself today. In a year you’ll regret you didn’t start earlier.

Read Also

• Cloud Architect: A Strategic Role Shaping the Future of IT in Organizations
• How Much Do DevOps Engineers, Cloud Architects and Security Analysts Earn in 2026

Read also

• Cloud Architect: A Strategic Role Shaping the Future of IT in Organizations
• AWS vs Azure - Which Cloud Certification in 2026?
• How Much Do DevOps Engineers, Cloud Architects and Security Analysts Earn in 2026

Develop your skills

Want to deepen your knowledge in this area? Check out our training led by experienced EITT instructors.

➡️ Cloud Architect — EITT training