Skip to main content

Data Engineer Azure/ Python/ SQL

Posted yesterday

software technologyAndrews Air Force Base (MD)

SENIORITY

Senior

Apply (opens in a new tab)

About the role

Data Engineer (Python)6 month C2HREMOTE or hybrid onsite (Manager sits in Dallas, TX but open to other CVS locations) Azure (Databricks preferred)SQLSnowflake (preferred) Building out Snowpark nowPySpark (preferred but not a must have) PythonTypical Engineering mindsetBe ready to scale as required; may go into GCP, but nothing is set in stoneCore Python ProgrammingSeparate teams for DevOps, Production Support and Data Scientist workData Science team communicates with the core customers and business, then the Data Engineering team architects and puts into productionMethodology: Moving from Waterfall to Agile (slowly) Working with Rally now, moving to Jira as that transition continuesMust-Haves (Concepts & Tools):PythonAzureSQL
Nice to Have: 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