senior-data-engineer

Design scalable data pipelines and governance for modern data stacks.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/devCharuzu/philfida-taskmanage --skill senior-data-engineer-devcharuzu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: senior-data-engineer
Source: https://github.com/devCharuzu/philfida-taskmanage/tree/main/.windsurf/skills/senior-data-engineer
Command: npx skills add https://github.com/devCharuzu/philfida-taskmanage --skill senior-data-engineer-devcharuzu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires yaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Data engineering teams and organizations struggle to design scalable data architectures, orchestrate complex pipelines, enforce data quality, and govern evolving schemas across modern data stacks.

Core Features & Use Cases

  • Architectural guidance for batch vs streaming, data modeling patterns (star/snowflake, SCDs, Data Vault), and DataOps governance.
  • End-to-end pipeline orchestration, data quality contracts, and lineage tracking across warehouses, lakes, and marts.
  • Real-world scenarios include building a batch ETL for a data warehouse, implementing streaming pipelines for event streams, and establishing governance with schema evolution and monitoring.

Quick Start

Configure and run a production-grade data pipeline skeleton using the senior-data-engineer skill.

Frequently Asked Questions about senior-data-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design scalable data pipelines for modern data stacks?

Establish data quality in ETL pipelines by implementing data quality contracts and lineage tracking across warehouses, lakes, and marts. This approach enforces quality standards while providing governance and monitoring throughout the data pipeline lifecycle.

What is the best way to orchestrate batch and streaming ETL workflows?

Orchestrate batch and streaming ETL workflows by applying end-to-end pipeline orchestration patterns tailored for modern data stacks. This provides actionable guidance for architecture decisions, data modeling, and DataOps best practices across your data infrastructure.

How does schema evolution and lineage tracking work across data lakes and warehouses?

Schema evolution and lineage tracking work by operationalizing governance patterns that monitor and manage changing schemas across warehouses and lakes. This ensures data quality enforcement and maintains consistent lineage throughout the evolving data pipeline infrastructure.

Can I use this approach for both data warehouse and data lake architectures?

Yes, you can use this approach for both data warehouse and data lake architectures. It designs and operationalizes scalable data pipelines and governance across modern data stacks, supporting batch and streaming ETL, data modeling, and schema evolution for both environments.

When do I need DataOps governance and data quality contracts in my data pipeline?

You need DataOps governance and data quality contracts when establishing scalable data pipelines that require enforced quality standards and lineage tracking. This becomes necessary when managing schema evolution, data modeling patterns, and orchestration across complex modern data stacks.