senior-data-engineer

Design and review data pipelines, analytical models, and data platform operations.

1|Updated Aug 7, 2025
One-click install
npx skills add https://github.com/zzafergok/arktos --skill senior-data-engineer-zzafergok
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: senior-data-engineer
Source: https://github.com/zzafergok/arktos/tree/main/.agent/skills/senior-data-engineer
Command: npx skills add https://github.com/zzafergok/arktos --skill senior-data-engineer-zzafergok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Data pipelines often fail silently, lose records, or produce metrics nobody can trust because contracts, quality checks, and operational behavior were never defined. This Skill guides the design, implementation, and review of data systems whose correctness, lineage, and reliability remain inspectable over time. ## Core Features & Use Cases - Data Contract Definition: Establish producers, consumers, grain, keys, event time, update semantics, retention, privacy classification, and freshness needs before choosing technologies. - Pipeline & Modeling Guidance: Apply idempotent ingestion, watermarking, backfill safety, partitioning, and explicit grain definitions for dimensions, facts, and derived metrics. - Data Quality & Operations: Define actionable checks for schema conformance, uniqueness, completeness, referential integrity, and freshness, plus instrumentation for throughput, latency, cost, and lineage. - Use Case: When building a new streaming ingestion pipeline into a warehouse, use this Skill to define the data contract, design duplicate handling and late-arrival behavior, assign quality check owners, and plan schema evolution and rollback. ## Quick Start Ask the AI to review your pipeline design or plan a new data pipeline using the senior data engineer skill, describing your sources, consumers, and latency requirements.

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 a reliable data pipeline?▼

Start by establishing a data contract covering producers, consumers, grain, keys, event time, and freshness needs. Then make ingestion idempotent, define late-arrival and backfill behavior, partition by verified access patterns, and instrument throughput, latency, and error rates.

What data quality checks should a pipeline have?▼

Validate schema and type conformance, uniqueness and key stability, completeness and null behavior, referential integrity, value ranges, freshness, and reconciliation with authoritative sources. Each failing check needs an owner and an actionable severity, not just noise.

When should I choose streaming vs batch processing?▼

Do not choose before understanding latency, scale, team, and operational constraints. The data contract's freshness needs and update semantics determine whether streaming or batch fits, not technology preference.

How do I handle backfills without corrupting current data?▼

Design replay and backfill paths explicitly so they do not corrupt current results or overload downstream systems. Preserve raw source fidelity when audit or replay is required, and validate backfills with staged deployment and rollback plans.

How should schema changes be managed in data pipelines?▼

Confirm which system owns each field and how schema changes are communicated to consumers. Plan compatible schema evolution, staged deployment, backfill validation, rollback, and deprecation with lineage metadata to identify affected downstream consumers.