Data Architect
omni inclusiveEl Segundo (CA)
About the role
Has worked in the past as an Architect. Professional experience in Data Engineering using Google Big Query (GBQ) and Google Cloud Platform (GCP) data sets and building data pipelines. Hands on and deep experience working with Google Data Products (e.g. BigQuery, Dataflow, Dataproc, Dataprep, Cloud Composer, Airflow, DAG etc.).Python Programming Expert PySpark, Pandas Experience in Airflow (Create DAG, Configure the variables in Airflow, Scheduling) Big Data technologies and solutions (Spark, Hadoop, Hive, MapReduce) and multiple scripting and languages (YAML, Python).Experience in DBT to create the lineage in GCP. - Optional Worked in Dev-Sec-Ops (CICD) environment. Design and develop the ETL ELT framework using BigQuery, Expertise in Big Query concepts like Nested Queries, Clustering, Partitioning, etc. Experience in Data Integration, Data Transformation, Data Quality and Data Lineage tools. Should be able to automate the data load from Big Query using APIs or scripting language. E2E Data Engineering and Lifecycle (including non-functional requirements and operations) management. E2E Solution Design skills - Prototyping, Usability testing and data visualization literacy. Experience with SQL and NoSQL modern data stores.
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.
More like this