Remote ETL Data Engineer Needed
Budget: $15 – $25 USD
I have a steady stream of U-S based projects that call for an experienced data engineer who is comfortable designing, building, and maintaining production-grade ETL pipelines. All work is fully remote, paid in USD, and comes with clear requirements, predictable milestones, and long-term potential.
You will be diving into real client datasets—ranging from SaaS-product telemetry to traditional ERP exports—then creating robust extraction, transformation, and loading workflows that land clean, query-ready data in cloud warehouses. Expect to optimize SQL, script transformations in Python, automate orchestration with tools such as Airflow or AWS Glue, and document everything so future engineers can pick up right where you leave off.
A detailed PDF is attached that lays out the engagement model, compensation structure, tech stack guidelines, and the short onboarding process. Give it a quick read, then send back:
• A brief note on the largest ETL system you’ve owned (volume, tech, outcome)
• Links to any GitHub repos or architecture diagrams you can publicly share
• Your weekly availability and preferred time-zone overlap with U-S teams
I reply within one business day and schedule a short technical chat for qualified engineers. Once we’re aligned, you’ll start with a paid test ticket before rolling onto a multi-month roadmap of work. Questions are welcome—just drop them in your proposal and I’ll clarify right away.
You will be diving into real client datasets—ranging from SaaS-product telemetry to traditional ERP exports—then creating robust extraction, transformation, and loading workflows that land clean, query-ready data in cloud warehouses. Expect to optimize SQL, script transformations in Python, automate orchestration with tools such as Airflow or AWS Glue, and document everything so future engineers can pick up right where you leave off.
A detailed PDF is attached that lays out the engagement model, compensation structure, tech stack guidelines, and the short onboarding process. Give it a quick read, then send back:
• A brief note on the largest ETL system you’ve owned (volume, tech, outcome)
• Links to any GitHub repos or architecture diagrams you can publicly share
• Your weekly availability and preferred time-zone overlap with U-S teams
I reply within one business day and schedule a short technical chat for qualified engineers. Once we’re aligned, you’ll start with a paid test ticket before rolling onto a multi-month roadmap of work. Questions are welcome—just drop them in your proposal and I’ll clarify right away.