Non-IT Engineer (civil, mechanical, chemical, electrical, industrial engineer) → IT

Cloud platforms and infrastructure companies explicitly seek engineers because cloud architecture is fundamentally systems engineering. AWS, Microsoft Azure, Google Cloud, and infrastructure consulting firms actively hire non-IT engineers who understand systems thinking, CAD/architecture, and technical problem-solving. A 2023 LinkedIn analysis found that "cloud architect" job postings prefer "systems thinking background" and "engineering education" strongly.

Real examples: Alex Torres, a mechanical engineer, transitioned to AWS cloud architecture; his experience designing complex industrial systems translated directly to designing scalable cloud infrastructure. In South Africa, mining companies, Sasol, and utility companies actively transition engineers into OT (Operational Technology) security and IT roles because engineers understand the systems they're protecting.

Engineers transition most successfully into: (1) Cloud Engineering (AWS, Azure, GCP), (2) DevOps Engineer roles, (3) OT/ICS Security (especially electrical/chemical engineers), (4) Systems Architecture, (5) IoT Engineering.

This plan is 15–20 hours/week for 12–13 weeks. Assumes you have engineering background and can learn quickly.

Days 1–30: Foundations + Cloud Platform Selection

Month 1 milestone: Cloud Practitioner fundamentals completed. Free cloud account set up and used. Simple architecture diagram created. Infrastructure-as-code basics started.

Days 31–60: Depth + Certification

Month 2 milestone: Cloud specialization certification earned (AWS SAA or Azure Administrator). Portfolio with IaC project demonstrating infrastructure automation. Ready for cloud engineer roles.

Days 61–90: Portfolio + Applications

Month 3 milestone: Portfolio with 4+ cloud projects on GitHub, LinkedIn rebranded for cloud engineering, 10+ applications submitted, interview-ready on cloud architecture and systems design.

Phase 1 — Entry (Months 0–3): Get baseline credential

Why start here: Cloud Practitioner certs introduce cloud fundamentals and cost very little. Solutions Architect or Administrator certs position you for cloud engineer roles. Together, you're job-ready for cloud engineering in 3 months.

Phase 2 — Specialise (Months 3–9): Land first IT job

Hire-ready milestone: AWS Solutions Architect Associate + Portfolio with Infrastructure-as-Code projects. This positions you for cloud engineer and DevOps roles.

Phase 3 — Advance (Months 9+): After first IT job

Complete Phase 3 certs on the job. Most cloud-using companies fund certifications. Negotiate in offer.

How your current engineering salary compares to cloud engineering:

The payoff point: This transition pays off at first IT job. Cloud Engineer roles (R48,000–R74,000/month) are typically 20–50% higher than mid-career engineering salaries. The trajectory grows steeply: by year 3, you're likely earning 50%+ more than your starting engineering salary. By year 5, potential earnings are 2–3x.

What to say in interviews about salary: Research Cloud Engineer rates: Johannesburg R45,000–R70,000; Cape Town R42,000–R65,000; remote R60,000–R95,000+. Say: "Based on my engineering background, cloud certifications, and market rates for cloud engineers, I'm expecting R55,000–R70,000/month. I'm flexible based on specialization opportunities and team composition."

How to position your engineering experience on IT CV

Your engineering background is a strength—frame it as "systems architecture" and "infrastructure design."

Bad version (doesn't translate):

• "Mechanical engineer for 8 years"
• "Designed industrial systems"

Good version (IT-relevant):

• "8 years systems engineering experience designing complex technical architectures; skilled in project methodology, scalability analysis, and optimization; transitioning expertise to cloud infrastructure and systems architecture"
• "CAD and simulation background; comfortable with technical specifications and large-scale system design; experienced in managing project dependencies and system reliability"

Create "Technical Architecture & Engineering" section:

• Engineering Background: Systems design, technical architecture, project methodology, CAD experience, scalability thinking
• Cloud/IT Skills: AWS / Azure / GCP cloud architecture, Infrastructure-as-Code (Terraform), DevOps fundamentals, systems engineering

What to put on LinkedIn right now

• Headline: Engineer → Cloud Engineer | AWS Certified | Systems Architecture & DevOps

• About section:

Non-IT engineer transitioning to cloud architecture and systems engineering.
8+ years designing complex technical systems; skilled in architecture, scalability, and optimization.
AWS/Azure/GCP certified. Applying engineering systems-thinking to cloud infrastructure.
Passionate about designing reliable, scalable systems in the cloud.

• Skills to add immediately:
  • Cloud Architecture (AWS / Azure / GCP)
  • Infrastructure-as-Code (Terraform / CloudFormation)
  • Systems Engineering
  • DevOps Fundamentals
  • Cloud Infrastructure
  • Scalability Design
  • Disaster Recovery Planning
  • Technical Architecture
  • Auto-scaling & Load Balancing
  • Infrastructure Automation

Portfolio items that bridge the gap

The "why IT?" question for engineer backgrounds

Employers will be curious: why leave engineering for IT? You need a compelling answer.

Framework for your answer: "I've spent [X years] designing and optimizing complex systems. I realized I'm more interested in the digital infrastructure that powers businesses—cloud platforms, distributed systems, infrastructure automation. Cloud engineering is systems engineering in the digital domain. It combines my architectural thinking with the scale and complexity I love. I want to design systems that support millions of users, optimize for cost and performance, and ensure reliability at scale. IT cloud engineering is the natural evolution of my career."

Variation for OT/ICS security: "My [civil/electrical/chemical] engineering background gives me understanding of operational systems that most IT people lack. I'm interested in protecting critical infrastructure through IT security—applying both engineering and security expertise to OT systems."

Common technical interview questions for Cloud Engineer roles

1. Q: "Design a scalable cloud architecture for a SaaS application expecting 1 million users." → A: Components: Load balancer, auto-scaling application servers, managed database (RDS), CDN for static content, caching layer (Redis), separate analytics systems. Design for: availability zones, failover, elastic scaling. Show: architectural thinking, understanding of cloud services, scalability concepts. This is where your engineering background shines.

2. Q: "Explain Infrastructure-as-Code and why it matters." → A: IaC = defining infrastructure in code (Terraform, CloudFormation). Benefits: reproducibility, version control, automation, disaster recovery. Example: "Instead of clicking AWS console, I define infrastructure in code, commit to Git, deploy via pipeline. If a server fails, infrastructure automatically recreates from code." Your engineering documentation experience applies.

3. Q: "How would you optimize cloud costs for this company's workload?" → A: Analysis: 1) Right-sizing instances (use smaller if over-provisioned), 2) Reserved instances for baseline load, 3) Auto-scaling to match demand, 4) Storage optimization, 5) CDN to reduce data transfer. Calculation: savings vs. performance trade-offs. Show: optimization mindset, financial awareness.

4. Q: "Design a disaster recovery strategy for a critical database." → A: Multi-region redundancy, automated backups, RTO (Recovery Time Objective), RPO (Recovery Point Objective) targets, failover procedures, regular testing. Your engineering risk management background is here.

5. Q: "Tell me about a complex system you designed and the trade-offs you made." → A: Use real engineering example, translate to cloud: "I designed [complex system] with constraints on cost, performance, and reliability. I: 1) analyzed requirements, 2) identified trade-offs, 3) made decisions based on business priorities, 4) documented reasoning. Similar approach in cloud architecture: business requirements drive technical choices."

Red flags to avoid in interviews

• "I don't understand IT." Wrong. You're cloud-certified. Say: "I'm new to IT professionally, but my engineering background gives me systems-thinking advantage."

• "Engineering is too constrained; I want freedom." Don't lead with escaping engineering. Lead with: "Cloud engineering excites me because it's systems design at unprecedented scale."

• "I just want to earn more." Fair, but don't lead with salary. Lead with: "I'm passionate about cloud architecture and large-scale systems design."

Is this career change viable in SA?

Absolutely yes. Sasol, Anglo American, BHP, Eskom, and critical infrastructure operators actively transition engineers into IT/OT security roles. Mining companies especially need engineers who understand operational systems. Additionally, Microsoft, AWS, and Google have SA operations teams and consulting partners who hire engineers into cloud roles.

Remote work: Very viable. Many international cloud consulting firms hire SA-based cloud engineers at premium rates (R60,000–R120,000+/month for experienced). SA's time zone (UTC+2) aligns with Europe, making remote work feasible.

BEE/EE: Engineering + IT certification is excellent for large corporate targets. Many companies seek "technically educated professionals transitioning to IT" for diversity initiatives.

SA salary reality check

Cloud Engineer / Systems Engineer (entry-level) in SA:

• Johannesburg (highest demand): R45,000–R70,000/month
• Cape Town (growing): R42,000–R65,000/month
• Remote (international vendors): R60,000–R100,000+/month
• OT/ICS Security specialists (critical infrastructure): R50,000–R80,000/month

Factors pushing higher: AWS/Azure/GCP certifications, IaC expertise (Terraform), container knowledge (Kubernetes), location (Gauteng highest), remote international roles.

SA-specific resources

SA success story

Dr. Kabelo's journey (representative story): Kabelo was a mechanical engineer at Sasol for 8 years, earning R55,000/month. He understood Sasol's production systems deeply but realized he was more interested in the IT that enabled those systems than in the mechanical engineering itself. In 2022, at age 35, he decided to transition to cloud engineering.

Sasol supported his transition (they need engineers who understand operations moving into IT). They funded his AWS Cloud Practitioner (free course) and AWS Solutions Architect Associate (R2,300 exam). Kabelo self-funded study materials (R2,000 Udemy course, R1,500 practice exams). Total personal cost: R3,500.

Within 9 months of starting study, he transitioned to Sasol's IT Cloud Infrastructure team at R72,000/month—a 30% salary increase. His engineering background + cloud certification made him invaluable because he understood both industrial operations and cloud architecture. By year 2, he's Senior Cloud Engineer earning R98,000/month. By year 3, he's architecting Sasol's cloud transformation at R125,000/month.

His journey shows that engineers have a clear IT transition path, especially in companies that understand the value of engineering backgrounds in cloud architecture.

Where to find others making this transition

Mentors to follow

• Adrian Cantrill (AWS Expert): AWS solutions architect. Excellent teaching. YouTube videos. YouTube

• Andrew Ng (AI/Systems): Engineer-turned-technologist. Bridging engineering and AI/ML. Coursera

• Njabulo Nkomo (LinkedIn): South African IT career transition mentor. Help for engineers. Search "Njabulo Nkomo IT South Africa."

• Cloud architects at Sasol, Anglo American, etc.: Reach out on LinkedIn to engineers who made the transition at major SA companies. Many offer informal mentorship.

Q: Do I need to learn programming if I'm transitioning to cloud?

Helpful but not required for architecture roles. Cloud Engineer roles often include some coding (Python, infrastructure-as-code), but your engineering background gives you a head start. DevOps roles require more coding. Cloud Architect roles less so.

Q: Which cloud platform should I specialize in: AWS, Azure, or GCP?

AWS has largest market share and most job openings (in SA and globally). Azure is strong in enterprises and South Africa (especially Microsoft ecosystem). GCP is strong in startups and data/ML. Recommend: Start with AWS or Azure (more SA jobs), then expand to others.

Q: Can I transition without leaving my engineering job?

Yes. Cloud Practitioner (free) + AWS Solutions Architect Associate (self-study, 6–8 weeks) = can be done part-time while employed. Complete while working, then transition.

Q: What's the career path from cloud engineer?

Cloud Engineer → Senior Cloud Engineer → Cloud Architect → Principal/Distinguished Engineer → Cloud Director/VP. Clear technical and management paths.

Q: Are OT/ICS security roles available in SA?

Yes. Mining, critical infrastructure (Eskom, Transnet), and utilities need OT security. Your electrical/mechanical engineering background is valuable. Slightly more specialized market than general cloud, but growing.

Q: How long before I'm earning significantly more than engineering?

Immediately in some cases (cloud engineering R48,000–R74,000 vs. engineering R28,000–R45,000). By year 2–3, clearly higher. By year 5, potentially 2–3x engineering salary for senior cloud architects.

Template version: 2026-05-02 | Career Changer Guide CCH10 | Maintained by IT Career Roadmap | ZAR baseline: R18/$1 USD