Apache Airflow Support Engineer at AnanSys Software Inc. | Torre

Apache Airflow Support Engineer

Emma highlights
This highlight was written by Emma’s AI. Ask Emma to edit it.
Full-time

Legal agreement: To be defined

USD75.4K - 100K/year

~COP150M - 200M/year

+ Equity

+ Bonuses

location_on
Remote (anywhere)
Match
skeleton-gauges
You have opted out of job matches in .
To undo this, go to the 'Skills and Interests' section of your preferences.
Review preferences
Shared by
Paulina Romero Moreno
about 10 hours ago

Requirements and responsibilities


🚨 Now Hiring: Apache Airflow Support Engineer | 6+ Month | REMOTE 🚨Role Focus: This is a support/operational role, not pure engineering. The client is SLA-bound and requires excellent "bedside manner" and documentation discipline.Must-have qualifications4+ years hands-on with Apache Airflow in production (not just “used it in a pipeline”) — scheduler, executors, DAG lifecycle, backfillsStrong troubleshooting of Airflow failures: restart loops, scheduler lag, task queue issues, executor problems, dependency conflictsAWS production experience, specifically ECS on EC2 (containerized Airflow) — sizing, deployment, networkingSecurity hardening: RBAC, secrets backends, TLS, and reducing Airflow’s provider surface / CVE footprint — this is FedPoint’s core pain, so weight it heavilyComfortable with CVE triage and vulnerability justification — assessing exploitability, documenting findings for compliance reviewPython proficiency (Airflow is Python-native; needed to read/debug DAGs and providers)Docker/containerization fundamentalsStrong written communication — client-facing support with SLA-bound response/resolutionStrongly preferredExperience 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 meansMonitoring: CloudWatch, Prometheus, GrafanaSoft requirements that matter for support (not engineering)Calm under production-incident pressure; good bedside manner with a stressed clientDocumentation discipline — runbooks, justification write-ups, ticket hygieneAble to work a defined coverage window reliably (federal clients notice SLA misses)AnanSys Software Inc.