Skip to main content

Azure Data Engineer

Posted yesterday

esolutionsChicago (IL)

SENIORITY

Lead

Apply (opens in a new tab)

About the role

Cloud Data Engineer
Location: Remote long term contract
Key Responsibilities: Design, develop, and implement data platform solutions using Azure Data Factory (ADF), Self-hosted Integration Runtime (SHIR), Logic Apps, Azure Data Lake Storage Gen2 (ADLS Gen2), Blob Storage, and Snowflake. Review and analyse existing on-premises ETL processes developed in SSIS and T-SQL.Perform data validation testing/QA to ensure data consistency between on-premises SQLServer and cloud-based Azure and Snowflake environments. Implement DevOps practices and CI/CD pipelines using GitActions. Collaborate with cross-functional teams to ensure seamless integration and data flow. Optimize and troubleshoot data pipelines and workflows. Ensure data security and compliance with industry standards.
Preferred Qualifications: Experience with data modelling and database design. Knowledge of data governance and data quality best practices. Experience with development in Databricks for data engineering and analytics workloads. Familiarity with other cloud platforms (e.g., AWS, Google Cloud).Certification in Azure or Snowflake.

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