--- title: "ETL Developer | Managed Data Engineering | Azendo" description: "Assign an ETL Developer to your roadmap under one monthly agreement, working from Thailand with an Azendo service delivery manager accountable for delivery." url: "https://azendo.co/services/data-engineering/etl-developer/" --- [← Data engineering](https://azendo.co/services/data-engineering/) # ETL Developer assigned to your roadmap. An ETL Developer handles extraction and transformation across the systems you already run, including the legacy ones with no clean API. Assigned under one service agreement with a minimum monthly capacity in hours, run by a service delivery manager in Chiang Mai, Thailand — five hours ahead of Northern Europe. [Contact us](https://azendo.co/get-in-touch/) [See pricing](https://azendo.co/pricing/) Part of our service line [Data engineering](https://azendo.co/services/data-engineering/) This role is delivered as part of our data engineering services. Take the role on its own, or the whole discipline as one delivery team. ## What an ETL Developer does on a managed data engineering team. Skills and scope are agreed before delivery starts, so the first sprint is productive rather than a ramp-up month. The work runs to the same backlog, the same repositories and the same definition of done as your own team's. ### ETL Developer skills and technology we assign for * [SQL](https://azendo.co/skills/sql/) * [Python](https://azendo.co/skills/python/) * [SSIS](https://azendo.co/skills/ssis/) * [Talend](https://azendo.co/skills/talend/) * [Informatica](https://azendo.co/skills/informatica/) * [Fivetran](https://azendo.co/skills/fivetran/) * [Airbyte](https://azendo.co/skills/airbyte/) * [Airflow](https://azendo.co/skills/airflow/) * [Change data capture](https://azendo.co/skills/change-data-capture/) * [incremental loads](https://azendo.co/skills/incremental-loads/) * [slowly changing dimensions](https://azendo.co/skills/slowly-changing-dimensions/) * Building extraction jobs against databases, APIs, flat files and legacy systems. * Transformation logic, deduplication and reconciliation between sources that disagree. * Scheduling, monitoring and error handling so failures are visible and recoverable. * Building reconciliation reports so finance can verify a load matched the source system. * Handling late-arriving and out-of-order data without corrupting existing records. ## Seniority levels we assign. Mid-level suits most work. Senior matters where legacy systems have no clean extraction path. Seniority is one of the inputs behind the [committed monthly capacity](https://azendo.co/pricing/) written into your agreement. ## When an ETL Developer is the right assignment. Common in organisations with a long tail of older systems still holding important data. On an ongoing roadmap this role is most often assigned alongside a Data Engineer or an Analytics Engineer. All 4 roles in this service line can sit on the same agreement, and capacity moves between them at the monthly cycle rather than requiring a new contract. This capacity is assigned under [managed data services](https://azendo.co/services/data-engineering/) rather than sold as a separate engagement. 160 h Typical monthly capacity for this role Fixed Monthly price, unaffected by leave or holidays 4–6 weeks From signed scope to delivery starting Monthly Cycle to raise or lower committed hours ## Other roles in data engineering. [Data Engineer Data engineering role](https://azendo.co/services/data-engineering/data-engineer/)[Analytics Engineer Data engineering role](https://azendo.co/services/data-engineering/analytics-engineer/)[Database Administrator Data engineering role](https://azendo.co/services/data-engineering/database-administrator/) The same delivery team, on your product, month after month. Chiang Mai and Bangkok, Thailand — five hours ahead of Northern Europe ## Questions about assigning an ETL Developer. Can you extract from systems with no API? Usually, through database replication, file exports or change data capture. We will assess feasibility before committing. How do you handle sources that disagree? Reconciliation logic agreed with your team, because the correct answer is a business decision rather than a technical one. ## Add ETL developer capacity to your roadmap. Tell us the scope and the stack. We come back with the profile, the capacity and what the first month looks like, or you can [talk to a service delivery manager](https://azendo.co/get-in-touch/) first. [Contact us](https://azendo.co/get-in-touch/) [How it works](https://azendo.co/how-it-works/) ## Assign a ETL Developer to your roadmap.