Cloud Solutions Architect

Algossian Labs Pvt. Ltd.; Dubai; Hybrid; AED 279,000 - 433,000; Full time

Job summary

Algossian Labs Pvt. Ltd. in Dubai seeks a Lead Cloud Architect to drive enterprise cloud engagements across the Gulf.

You will design multi-account landing zones, run migrations, and craft modernisation roadmaps with a cost envelope approved by the board. The role is hybrid with office days in Dubai; you will lead architecture boards, codify reference architectures with Terraform, and coach delivery squads on cloud patterns.

Qualifications

• 8+ years in cloud engineering with 3+ years leading enterprise architecture.
• Deep AWS expertise; working knowledge of Azure or Google Cloud.
• Proven landing-zone and large-migration delivery, including regulated workloads.
• Excellent written and spoken communication with executives and regulators.
• Cost modelling ability with defendable 3-year TCO projections.

Responsibilities

• Design multi-account landing zones with policy as code, hub networking and a documented CIDR plan.
• Run discovery and produce migration roadmaps with sequencing, risk, cost model and a business case.
• Act as the senior technical voice in customer architecture boards and regulator conversations.
• Codify reference architectures and Terraform modules so the next engagement starts further along.
• Coach delivery squads on cloud patterns and review their designs before they become commitments.

Skills

Cloud architecture

AWS expertise

Azure/Google Cloud

Landing zone & migration

Cost modelling

Executive communication

Terraform

Tools

Terraform

Policy as Code

Job description

Lead cloud architecture for enterprise engagements across the Gulf — landing zones, migration programmes and modernisation roadmaps with a cost envelope a board will approve.

Cloud & Platform Dubai, UAE hybrid full time lead · 8–12 years

$76K – $118K USD per year · posted 3 months ago

The role in one paragraph

Lead cloud architecture for enterprise engagements across the Gulf — landing zones, migration programmes and modernisation roadmaps with a cost envelope a board will approve.

Hybrid — two anchor days in the office Reporting line, on-call expectation and the first ninety days are covered in the opening conversation — ask hard questions there.

What you will own

• Design multi-account landing zones with policy as code, hub networking and a documented CIDR plan.
• Run discovery and produce migration roadmaps with sequencing, risk, cost model and a business case.
• Act as the senior technical voice in customer architecture boards and regulator conversations.
• Codify reference architectures and Terraform modules so the next engagement starts further along.
• Coach delivery squads on cloud patterns and review their designs before they become commitments.

What we need from you

Treat this as a description of the work, not a checklist to score yourself out of. If you meet most of it and can argue the rest, apply.

Eight or more years in cloud engineering with at least three leading enterprise architecture.

Deep AWS expertise, plus working competence in Azure or Google Cloud.

Proven landing-zone and large-migration delivery, including regulated workloads.

Excellent written and spoken communication with executive and regulatory audiences.

Cost modelling ability — you can defend a three-year total cost of ownership projection line by line.

Useful, not required

• Professional-level certification on AWS, Azure or Google Cloud.
• Experience with data residency requirements in the GCC region.
• Background in banking, insurance or public sector cloud adoption.

The loop, from application to written decision

Same four steps for every candidate at this level. You will know the format of each stage before you sit it.

01

Conversation with the hiring manager

Thirty minutes with the person who runs the team, not a recruiter screen. We describe the actual system, the actual roadmap and the actual on-call expectation, and you interrogate all three.

30 minutes · Day 1

02

Technical deep dive

Ninety minutes on a real problem from our backlog with client details removed — a schema that needs a new access pattern, an incident timeline, a service boundary to argue about. No algorithm puzzles.

90 minutes · Day 2

03

Paid practical exercise

A scoped change in a repository skeleton with a failing test, in your own environment and your own time within a two-hour budget. We pay a fixed stipend because your time has a price.

2 hours, paid · Day 3

04

Craft, values and decision

Forty-five minutes with someone outside the hiring team, then a written decision the same day with specific feedback either way. No silence, no expanding take-homes.

45 minutes · Day 4