Get Google Cloud Engineers
GCP infrastructure engineers from Brazil, Argentina, and Colombia who build on BigQuery, Cloud Run, GKE, and Vertex AI. They write Terraform for GCP, design data-intensive architectures, and run production workloads on Google Cloud at scale.
GCP engineers in the US command $160k-$210k. LATAM equivalents deliver at $72k-$108k — especially relevant for data-intensive GCP workloads that require ongoing optimization.
UTC-3 to UTC-5 means 4-8 hours of overlap with US teams. GCP BigQuery and Pub/Sub pipelines often run continuously — shared on-call without extreme hours is realistic.
GCP work often involves data platform conversations with analysts, data scientists, and backend engineers. LATAM GCP engineers communicate across these audiences clearly.
Google Cloud's strengths — BigQuery, Dataflow, Pub/Sub, Vertex AI — align with LATAM's strong data engineering community. Many GCP engineers here have data backgrounds.
Professional Cloud Architect, Data Engineer, and ML Engineer certifications are common in LATAM. We verify certifications and run live technical screens regardless.
Every candidate completes all five stages before you see their profile. You can also run your own technical round after our screening.
A timed test measuring analytical thinking, pattern recognition, and problem-solving clarity, independent of specific programming language knowledge.
A structured interview assessing communication style, conflict resolution, ownership mindset, and English proficiency in a professional context.
A 90-minute live session covering GCP VPC design, IAM policy structure with least-privilege service accounts, and a Terraform module written live for a Cloud Run + Cloud SQL deployment. We probe BigQuery expertise — query optimization, partitioning strategy, and slot vs on-demand pricing. For data-focused candidates, we also cover Pub/Sub consumer design and Dataflow pipeline architecture. The session includes a cost scenario: a BigQuery bill has tripled, and we walk through how they'd diagnose and reduce spend.
Verification of work history, education, and identity with written consent, aligned with applicable privacy rules including LGPD where relevant.
We speak with at least two professional references who worked with the candidate in an engineering context, not personal contacts.
After our screening, you can optionally run your own technical round before making an offer.
Sample profiles
Anonymized profiles from our vetted talent pool. Actual candidates may vary.
São Paulo, Brazil
4+ years experience
Montevideo, Uruguay
7+ years experience
Buenos Aires, Argentina
10+ years experience
Want to see profiles matched to your specific requirements?
Request matched profilesWhat to expect
GCP engineers in our network bring a data-infrastructure mindset to cloud work. They treat BigQuery optimization and Pub/Sub reliability as seriously as compute provisioning. They use AI tools to speed up IaC work and security scanning.
GitHub Copilot for Terraform GCP module scaffolding — Cloud Run services, IAM bindings, and Pub/Sub topic configurations get written faster with less boilerplate error.
GCP Cost Recommender and Active Assist suggestions are reviewed and actioned weekly. BigQuery slot and commitment optimization is a regular task, not a quarterly event.
AI-assisted security scanning with Checkov for Terraform GCP configurations. Overly permissive IAM policies and missing VPC firewall rules get flagged before deployment.
They document BigQuery schema decisions and partition strategies in the data catalog so analysts and data scientists can work independently.
They own the reliability of their data pipelines — Pub/Sub dead-letter queues, Dataflow error metrics, and Cloud Composer DAG failure alerts are all set up before go-live.
Junior GCP Engineer
Mid GCP Engineer
Senior GCP Engineer
Lead GCP Engineer
FAQ
Related roles
Tell us your GCP setup and what you're building. We'll have a shortlist in 3 days.
Cloud Composer (managed Airflow)
Cloud SQL (PostgreSQL/MySQL)
Terraform (Google provider)
Pulumi (GCP support)