The Role: Airflow Developer (UC4 to Airflow Migration)

The role has three parts:

1. Feature development to fill the UC4-to-Airflow gaps, such as custom operators, sensors, and plugins.

2. Active migration of the remaining UC4 workflows.

3. Tooling work to update and extend the migration tool.

Skills required

- Python (solid): This is the core skill. It covers clean, testable, reusable code.

- Apache Airflow: DAG design, custom operators, hooks, sensors, and plugins. Also scheduling, dependencies, retries, SLAs, backfills, pools, XComs, and deployment and versioning.

- UC4/Automic: Familiarity with jobs, job plans, schedules, calendars, agents, and variables, so legacy behavior can be read and reproduced faithfully.

- ETL and data pipeline experience:



SQL and data platform basics, since 60% of the workload is ETL.

- Migration and parity validation: Comparing legacy and recent runs for timing, dependencies, and output.

- Tooling and parsing: Building or extending a converter that reads legacy definitions and generates Airflow code.

- DevOps: Git, CI/CD, Docker/Kubernetes, and Linux/shell.

- Observability: Prometheus metrics and Grafana dashboards.

- Soft skills: Working in a deadline-driven setting, with a distributed team across time zones.

📌 /Automic Migration Consultant (Bengaluru)
🏢 Flexton
📍 Bengaluru