Must-have qualifications
4+ years hands-on with Apache Airflow in production (not just “used it in a pipeline”) — scheduler, executors, DAG lifecycle, backfills
Strong troubleshooting of Airflow failures: restart loops, scheduler lag, task queue issues, executor problems, dependency conflicts
AWS production experience, specifically ECS on EC2 (containerized Airflow) — sizing, deployment, networking
Security hardening: RBAC, secrets backends, TLS, and reducing Airflow’s provider surface / CVE footprint — this is FedPoint’s core pain, so weight it heavily
Comfortable with CVE triage and vulnerability justification — assessing exploitability, documenting findings for compliance review
Python proficiency (Airflow is Python-native; needed to read/debug DAGs and providers)
Docker/containerization fundamentals
Strong written communication — client-facing support with SLA-bound response/resolution
Strongly preferred
Experience supporting federal / government contractor environments; familiarity with FISMA/NIST 800-53/800-171 concepts (support context, not as a certifier)
Kubernetes (some clients run Airflow there even if FedPoint is ECS)
CI/CD, infrastructure-as-code (Terraform/CloudFormation)
Prior SLA-based support or managed-services experience (vs. pure engineering) — knows what “2-hour response” discipline actually means
Monitoring: CloudWatch, Prometheus, Grafana
Soft requirements that matter for support (not engineering)
Calm under production-incident pressure; good bedside manner with a stressed client
Documentation discipline — runbooks, justification write-ups, ticket hygiene
Able to work a defined coverage window reliably (federal clients notice SLA misses)
Work Location: Remote
