Google Cloud Lead Data Engineer

Location: Remote — Latin America (Open to applicants located anywhere in the LATAM region).

Fueled is a leading digital strategy, design, and engineering agency. We are a 300+ person team that has designed and built hundreds of digital products and experiences for brands like Google, Apple, The New York Times, ESPN, Victoria's Secret, MGM Resorts, Albertsons, and CLEAR.

As a Lead Data Engineer at Fueled, you own the warehouses behind our clients' marketing analytics. GA4 exports, marketing platform APIs, and CMS content land in BigQuery, Dataform models them, and Looker Studio dashboards sit on top. When you hand over a warehouse, the client's team should be able to trust it and run it.

Most of the work happens inside a client's Google Cloud project, using the access they grant. You work on a fixed budget with a project manager and strategists. You write the Python that pulls the data and the SQL that shapes it, and you also write the runbook and answer the client when they ask why a number changed.

Intentionally remote, our team thrives in a culture that values flexibility, creativity, and cutting-edge technology. For engineers in Latin America, that means real-time collaboration with US-based teams during your normal working day, compensation in USD, and a seat at the table on projects for globally recognized brands – all from wherever you work best. Together, we're shaping the future of digital experiences.

What you will do:

• Lead the data engineering on client engagements that bring marketing and product data into BigQuery: GA4 exports, marketing platform APIs, CMS content, and other client systems. You own the design from the raw landing tables to the views a dashboard reads, and you mentor Fueled engineers moving into data work.

• Build and operate Dataform projects, from clean layers and analytical views through assertions, scheduled runs, and promotion from development to production across GCP projects. This is also where reporting requirements become data. You map GA4 events and parameters to the KPIs a report needs, and when a dashboard disagrees with its source, you find the cause and fix it in the model, not in the chart.

• Write and maintain Python ingestion services on Cloud Run that pull from rate-limited APIs, with watermarks, backfills, and recovery for missed days built in from the start.

• Set up what keeps a warehouse running after we hand it over, inside the client's own Google Cloud tenancy: IAM for service accounts, Cloud Monitoring alerts, cost controls, and runbooks their engineers can follow. You work with the access they grant and write access requests an admin can act on the same day.

• Work as part of a project team. The project manager gets estimates you can defend and early warning when they change. Client stakeholders who are not engineers get technical decisions explained in their terms, including what the data can and cannot support.

What you will achieve:

• From day one, you take over a live client warehouse and document where every piece lives: code, container images, buckets, secrets, and service accounts.

• Your first production change ships through Dataform with assertions and a scheduled run. When a client asks why a dashboard disagrees with GA4, you reconcile it and answer them the same week.

• By month three, a client holds runbooks their engineers use without calling us, and a Fueled engineer you mentored runs nightly jobs on their own.

• Within six months, you have led the data engineering on a new engagement from discovery through handover, on budget, with the client's data team signing off on the design.

• By the end of your contract, you'll have a portfolio of enterprise-grade work, sharpened skills, and a standing invitation for future collaboration.

About you:

• You have shipped Dataform or dbt on BigQuery in production, with assertions and scheduled runs, and you know the GA4 BigQuery export schema before and after you flatten it.

• You have written and owned Python data pipelines in production: API clients with pagination and rate limits, watermark tables, idempotent backfills, containerized and deployed on Cloud Run or something like it.

• You are comfortable at the IAM level: custom runner service accounts, impersonation, and promotion across GCP projects. You know GA4 exports never backfill, and you plan cutovers around that.

• You have put Looker Studio or Looker on BigQuery through a service account, and you can trace one metric from a GA4 event parameter to a dashboard tile. When a client asked why the numbers disagreed with the source, you reconciled them and wrote the answer in plain language.

• You like working in a team with project managers, strategists, and client stakeholders. You estimate honestly, flag changes early, and deliver within a fixed budget. You have inherited someone else's cloud project and left it better documented than you found it.

Contractor Fee

Compensation is determined based on a variety of factors including relevant experience, projects, geographic location, and business needs.

Join our Contractor Pool

This role is designed as a contract position, offering you the opportunity to experience our team and culture while showcasing your contributions. When the fit and business needs align, some contractors are invited to explore a transition into full-time roles.

If you are passionate about Fueled’s mission and think you have what it takes to be successful in this role, even if you don’t check all the boxes – please apply. We’d appreciate the opportunity to review your application. Everyone gets a response.

Upon meeting the necessary criteria, you’ll join the Fueled contractor network, granting you access to project invitations tailored to your expertise and availability when they arise.

Any data provided will be processed in accordance with applicable law and our privacy policy. Curious about what to expect during our talent process? Check it out here.

We don't want you to miss any communication from us! To ensure you receive updates on your application, please add to your contacts list!

Originally posted on Himalayas