Cloud Data Architect
Cloud Data Architect
Posted 4 days ago
SENIORITY
Lead
About the role
- Architecture & DesignDesign end to end cloud data architectures, including ingestion, processing, storage, governance, and consumption layers.
- Define modern data platform patterns such as lakehouse, data mesh, and real time streaming architectures.
- Select appropriate cloud-native services (e.g., AWS Redshift/S3/Glue, Azure Synapse/ADF/Databricks, GCP BigQuery/Dataflow).Data Engineering & Integration
- Architect pipelines for batch and real time data ingestion.
- Enable scalable data processing using Spark, Databricks, Kafka, Flink, or cloud-native tools.
- Define ETL/ELT frameworks and best practices.
- Build secure and scalable cloud data ecosystems.
- Optimize data storage, compute performance, cost, and operational efficiency.
- Implement Infrastructure as Code (Terraform, ARM, CloudFormation).Data Governance & Security
- Develop data cataloging, lineage, classification, and DQ frameworks.
- Implement cloud IAM, role-based access, encryption, and compliance (GDPR, HIPAA, SOC2, PCI-DSS if BFSI).Stakeholder Collaboration
- Work with business stakeholders to translate requirements into technical architectures.
- Partner with security, platform engineering, and product teams.
- Provide thought leadership in cloud data strategy and modernization.
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
