Skip to main content

Lead Software Engineer, Databricks & Cloud

Posted yesterday

us bankIrving (TX)

SENIORITY

Lead

Apply (opens in a new tab)

About the role

Overview: In this role you lead the design and delivery of scalable, governed data products on a Databricks Lakehouse across Azure and AWS. You provide technical direction across engineering, product, architecture, and governance to enable trusted analytics, reporting, and AI use cases for Business Banking. You stay hands-on with coding and reviews while guiding cross-cloud data pipelines and data quality controls. You’ll shape best practices and empower distributed teams to deliver high-impact data solutions. Compensation / Benefits Healthcare (medical, dental, vision) Life insurance Disability insurance 401(k) retirement plan Paid vacation Paid holidays
Responsibilities: Lead Databricks data engineering across Bronze, Silver, and Gold layers with emphasis on Silver/Gold data products Translate business requirements into scalable data architecture, delivery standards and acceptance criteria Hands-on development and code reviews for batch, CDC, streaming, API and file-based pipelines Review data models and designs for quality, security, scalability, performance Drive cross-cloud data integration across Azure, AWS, Databricks, and Snowflake Embed data quality, lineage, governance, PII and PCI controls, monitoring and reliability Establish CI/CD, testing, source control, deployment, and observability practices Provide technical leadership across distributed teams through influence rather than direct management Partner with product, architecture, governance, platform, and business stakeholders to resolve dependencies and risks
Key requirements: Bachelor’s degree, or equivalent work experience Six to eight years of relevant experience Strong hands-on experience with Python, PySpark, SQL, Spark SQL, and ETL/ELT development Hands-on expertise with Databricks, Delta Lake, Unity Catalog, medallionarchitecture, and Databricks Workflows/Lakeflow Experience building batch, CDC, streaming, API, and file-based pipelines (Kafka or Azure Event Hubs) Cloud data engineering experience with Azure and/or AWS (ADLS Gen2, Data Factory, S3, IAM) Knowledge of Snowflake, Delta Sharing, Delta UniForm, Apache Iceberg, and cross-cloud data sharing Experience with data modeling, Power BI/DAX, data quality, governance, lineage, and PII/PCI controls Strong knowledge of Git, CI/CD, automated testing, architecture reviews, and engineering best practices Ability to provide technical direction and guidance across distributed teams through influence Influencing without direct authority Cross-functional collaboration Strong communication with stakeholders Databricks (Lakehouse, Delta Lake, Unity Catalog) Medallion architecture (Bronze/Silver/Gold) ETL/ELT development (Python, PySpark, SQL)

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