Role: Azure Devops Engineer
Location: Remote
Job Descrpition:
CI/CD and git based development
Has built automated deployments with PR checks, release gates, isolation, and rollback
Fabric lakehouses + warehouses
Understands delta tables, shortcuts, SQL analytics endpoints, Spark, and Fabric warehouse behavior
Enterprise pipeline engineering
Has built automated pipelines with retries, incremental loads, recovery, and transparent failure states
Python
Can develop, debug, and maintain Python code in Fabric ingestion pipelines + source control and dbt deployment pipelines
dbt core
Understand the dbt command-line-interface (CLI)
Project work with dbt including testing and CI
Monitoring and operation
Can implement alerts, centralized logs, pipeline run tracking, and has experience with incident investigation.
Analytics engineering
Understands reconciliation, deduplication, idempotency, data profiling and schema contracts
Less critical but still very valuable:
Spark performance engineering
Can diagnose Delta and Spark execution problems, partitioning, concurrency, and capacity usage
Very close to critical tier, because while our pipelines are functioning I do not believe they are optimized, which could become a bigger problem over time.
Azure devops or github actions (same product, different name)
Experience with the fabric CLI or REST API
We should be able to use all functionality in fabric without these things, but these provide way more flexibility in pipelines especially
Azure identity and security
Primarily understanding of ownership and access as it applies to fabric pipelines, service principals, and logic apps used in the data layer