{"schemaVersion":"jobsearcher.job.v1","id":"588567d2d0058fe5bcba12b4","url":"https://jobsearcher.com/jobs/588567d2d0058fe5bcba12b4","canonicalUrl":"https://jobsearcher.com/jobs/588567d2d0058fe5bcba12b4","title":"Apache Airflow Engineer","description":"Must-have qualifications\n4+ years hands-on with Apache Airflow in production (not just “used it in a pipeline”) —\nscheduler, executors, DAG lifecycle, backfills\nStrong troubleshooting of Airflow failures: restart loops, scheduler lag, task queue issues,\nexecutor problems, dependency conflicts\nAWS production experience, specifically ECS on EC2 (containerized Airflow) — sizing,\ndeployment, networking\nSecurity hardening: RBAC, secrets backends, TLS, and reducing Airflow’s provider\nsurface / CVE footprint — this is FedPoint’s core pain, so weight it heavily\nComfortable with CVE triage and vulnerability justification — assessing exploitability,\ndocumenting findings for compliance review\nPython proficiency (Airflow is Python-native; needed to read/debug DAGs and providers)\nDocker/containerization fundamentals\nStrong written communication — client-facing support with SLA-bound response/resolution\nStrongly preferred\nExperience supporting federal / government contractor environments; familiarity with\nFISMA/NIST 800-53/800-171 concepts (support context, not as a certifier)\nKubernetes (some clients run Airflow there even if FedPoint is ECS)\nCI/CD, infrastructure-as-code (Terraform/CloudFormation)\nPrior SLA-based support or managed-services experience (vs. pure engineering) —\nknows what “2-hour response” discipline actually means\nMonitoring: CloudWatch, Prometheus, Grafana\nSoft requirements that matter for support (not engineering)\nCalm under production-incident pressure; good bedside manner with a stressed client\nDocumentation discipline — runbooks, justification write-ups, ticket hygiene\nAble to work a defined coverage window reliably (federal clients notice SLA misses)\nExperience:\nApache Airflow in production : 4 years (Required)\nscheduler, executors, DAG lifecycle, backfills : 1 year (Preferred)\nAWS production experience, specifically ECS on EC2: 3 years (Preferred)\nWork Location: Remote","company":"Igate","rawCompany":"igate","city":"Remote","state":"OR","isRemote":false,"isActive":false,"createdAt":"2026-08-04T21:31:36.991Z","occupations":[{"code":"15-1299.08","title":"Computer Systems Engineers/Architects","slug":"computer-systems-engineers-architects"},{"code":"15-1252.00","title":"Software Developers","slug":"software-developers"},{"code":"15-1244.00","title":"Network and Computer Systems Administrators","slug":"network-and-computer-systems-administrators"}],"industries":[{"code":"541512","title":"Computer Systems Design Services","slug":"computer-systems-design-services"},{"code":"541511","title":"Custom Computer Programming Services","slug":"custom-computer-programming-services"},{"code":"541519","title":"Other Computer Related Services","slug":"other-computer-related-services"}],"jobPosting":{"@context":"https://schema.org","@type":"JobPosting","title":"Apache Airflow Engineer","description":"Must-have qualifications\n4+ years hands-on with Apache Airflow in production (not just “used it in a pipeline”) —\nscheduler, executors, DAG lifecycle, backfills\nStrong troubleshooting of Airflow failures: restart loops, scheduler lag, task queue issues,\nexecutor problems, dependency conflicts\nAWS production experience, specifically ECS on EC2 (containerized Airflow) — sizing,\ndeployment, networking\nSecurity hardening: RBAC, secrets backends, TLS, and reducing Airflow’s provider\nsurface / CVE footprint — this is FedPoint’s core pain, so weight it heavily\nComfortable with CVE triage and vulnerability justification — assessing exploitability,\ndocumenting findings for compliance review\nPython proficiency (Airflow is Python-native; needed to read/debug DAGs and providers)\nDocker/containerization fundamentals\nStrong written communication — client-facing support with SLA-bound response/resolution\nStrongly preferred\nExperience supporting federal / government contractor environments; familiarity with\nFISMA/NIST 800-53/800-171 concepts (support context, not as a certifier)\nKubernetes (some clients run Airflow there even if FedPoint is ECS)\nCI/CD, infrastructure-as-code (Terraform/CloudFormation)\nPrior SLA-based support or managed-services experience (vs. pure engineering) —\nknows what “2-hour response” discipline actually means\nMonitoring: CloudWatch, Prometheus, Grafana\nSoft requirements that matter for support (not engineering)\nCalm under production-incident pressure; good bedside manner with a stressed client\nDocumentation discipline — runbooks, justification write-ups, ticket hygiene\nAble to work a defined coverage window reliably (federal clients notice SLA misses)\nExperience:\nApache Airflow in production : 4 years (Required)\nscheduler, executors, DAG lifecycle, backfills : 1 year (Preferred)\nAWS production experience, specifically ECS on EC2: 3 years (Preferred)\nWork Location: Remote","datePosted":"2026-08-04T21:31:36.991Z","dateModified":"2026-08-04T21:31:36.991Z","hiringOrganization":{"@type":"Organization","name":"Igate","sameAs":"https://jobsearcher.com"},"jobLocation":{"@type":"Place","address":{"@type":"PostalAddress","addressLocality":"Remote","addressRegion":"OR","addressCountry":"US"}},"identifier":{"@type":"PropertyValue","name":"JobSearcher","value":"588567d2d0058fe5bcba12b4"},"url":"https://jobsearcher.com/jobs/588567d2d0058fe5bcba12b4"}}