Skip to main content

Azure Databricks Developer Louisville, KY & Pittsburgh, PA (Onsite) Contract

Posted yesterday

acestackPittsburgh (PA)

SENIORITY

Senior

Apply (opens in a new tab)

About the role

Azure Databricks Developer
Location: Louisville, KY & Pittsburgh, PA – 100% Onsite Long Term Contract – W2/ C2CInterview Mode: Face-to-Face (F2F) – Final Round Note: Locals Only – No relocation or remote options
Job Description: We are seeking a highly skilled Azure Databricks Developer to join our team for an onsite role requiring in-person interviews. The ideal candidate will have strong hands-on experience working with Azure Data Services, especially Databricks, and should be comfortable working directly from the client location.
Key Responsibilities:
  • Design, develop, and optimize data pipelines using Azure Databricks and Apache SparkBuild scalable ETL/ELT processes to ingest data from various sources (structured, semi-structured)
  • Work closely with data architects and analysts to understand data requirements and implement solutions
  • Write advanced PySpark/Scala scripts and performance-tune Spark jobs
  • Implement data quality checks and validation rules
  • Integrate with Azure components like Data Lake Storage (ADLS), Data Factory, Synapse, Event Hubs
  • Support deployment, monitoring, and debugging in Azure environments
  • Collaborate in Agile/Scrum teams, attend stand-ups, demos, and code reviews
Required Skills:
  • 8+ years of experience in Data Engineering roles 5-7+ years of strong hands-on experience with Azure Databricks
  • Strong knowledge of PySpark, SQL, Spark SQLExperience with Azure Data Factory, ADLS Gen2, Synapse Analytics, and Azure DevOpsProficiency in working with Delta Lake, DataFrames, and optimization techniques
  • Excellent understanding of data modeling and large-scale data processing
  • Strong debugging, performance tuning, and troubleshooting skills
  • Ability to work onsite and attend face-to-face interviews
Nice to Have: Experience with Power BI, Azure ML, or Real-time streaming (Event Hubs/Kafka) Knowledge of CI/CD pipelines and automation using Azure DevOps

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