Cloud Infrastructure Engineer @Platform Science
All Others
Salary unspecified
Remote Location
Employment Type full-time
Posted 1mth ago

[Hiring] Cloud Infrastructure Engineer @Platform Science

1mth ago - Platform Science is hiring a remote Cloud Infrastructure Engineer. πŸ’Έ Salary: unspecified πŸ“Location: Brazil

Role Description

Platform Science is looking for a Cloud Infrastructure Engineer to join our CloudOps team. CloudOps owns the foundational cloud infrastructure that enables our engineering teams to build, deploy, and operate products at scale. The team manages identity, networking, governance, security guardrails, backup, disaster recovery, and shared cloud services across a multi-account AWS environment spanning hundreds of accounts and multiple business units. We are also extending this operating model across Azure and GCP.

This is a hands-on senior individual contributor role for an engineer who enjoys building foundational infrastructure and solving complex cloud problems. You will own infrastructure and platform capabilities end to end, work primarily through Infrastructure as Code, and create guardrails and self-service capabilities that allow engineering teams to move quickly without sacrificing security or reliability.

The scope is intentionally broad. You may work on:

  • Cloud identity and permissions
  • Private networking
  • Multi-cloud governance
  • Backup and disaster recovery
  • Security remediation
  • Developer self-service capabilities

AI-assisted engineering is also part of how the team operates. We use AI coding agents to accelerate implementation and automation while maintaining rigorous engineering review, security, and production standards.

Qualifications

  • 5+ years of professional experience in Cloud Infrastructure, DevOps, Site Reliability Engineering, Platform Engineering, Systems Engineering, or a related infrastructure discipline.
  • 3+ years of hands-on experience with AWS or another major public cloud, with significant AWS experience strongly preferred.
  • 1+ years of Infrastructure as Code experience, preferably using Terraform and/or Terragrunt.
  • Experience operating AWS at organizational scale, including AWS Organizations, multi-account architecture, and Control Tower or a comparable landing-zone architecture.
  • Production experience with at least one additional major cloud platform β€” Azure or GCP β€” beyond managing a single workload.
  • Strong experience designing reusable Infrastructure as Code modules and patterns consumed by other engineering teams.
  • Hands-on experience with cloud identity and access management, including SSO, SAML federation, SCIM provisioning, IAM policies, roles, permission boundaries, and least-privilege access models.
  • Strong cloud networking fundamentals, including IP address planning, VPC/VNet design, routing, transit architectures, DNS, private connectivity, and network security.
  • Experience designing or maintaining CI/CD pipelines using tools such as GitHub Actions, Jenkins, or similar technologies.
  • Experience scripting or programming with Python, Go, Bash, or similar languages.
  • Strong Linux fundamentals.
  • Working knowledge of Kubernetes and cloud-native infrastructure.
  • Experience using AI coding agents or AI-assisted development tools such as Claude Code, Cursor, Codex, or similar tools.
  • Ability to independently own complex infrastructure projects from design through production implementation.
  • Strong written and verbal communication skills with the ability to collaborate across Engineering, Security, FinOps, and other technical teams.
  • Advanced English proficiency.
  • Bachelor’s degree in Computer Science, Software Engineering, Information Technology, or a related technical field.
  • Must reside in Brazil.

Requirements

  • Own and evolve our multi-account AWS Landing Zone, including AWS Organizations, Control Tower, Account Factory for Terraform (AFT), organizational structures, Service Control Policies, tagging standards, and permission boundaries.
  • Extend cloud governance, operational standards, security controls, observability, and backup capabilities across AWS, Azure, and GCP.
  • Improve cloud identity and access management using least-privilege principles.
  • Design and operate cloud networking capabilities.
  • Help transition workloads from public-internet exposure to private and zero-trust networking models.
  • Build self-service infrastructure capabilities for engineering teams.
  • Design and maintain backup, restore, and disaster recovery capabilities across cloud regions, accounts, and business units.
  • Implement immutable and ransomware-resistant backup strategies.
  • Build reusable Terraform/Terragrunt modules and infrastructure patterns.
  • Develop and maintain CI/CD automation for cloud infrastructure.
  • Partner with Security teams to investigate and remediate cloud security findings.
  • Partner with FinOps teams to identify cloud cost optimization opportunities.
  • Build and maintain documentation, cloud standards, operating procedures, and shared responsibility models.
  • Use AI coding agents as part of the engineering workflow.
  • Develop reusable prompts, context, workflows, and agent capabilities.

Preferred Qualifications

  • Experience with AWS Control Tower and Account Factory for Terraform (AFT).
  • AWS IPAM, Transit Gateway, or Cloud WAN.
  • Multi-cloud governance across AWS, Azure, and/or GCP.
  • Cross-account immutable backup and ransomware protection.
  • MongoDB Atlas, Elastic Cloud, or similar managed data platforms.
  • Wiz, GuardDuty, CrowdStrike, or other cloud security posture/security platforms.
  • Zero-trust networking technologies such as Zscaler ZPA.
  • Cloudflare WAF and DNS.
  • Certificate and PKI lifecycle management.
  • Agentic automation pipelines or automated remediation workflows.
  • MCP servers or reusable AI agent skills.
  • Secure access patterns and permission boundaries for AI-driven automation.
  • Cloud cost optimization and FinOps.
  • SOC 2 or comparable security/compliance frameworks.
  • GitHub organization administration.
  • AWS, Azure, GCP, Terraform, Kubernetes, or related technical certifications.

What Success Looks Like at the IC4 / P4 Level

  • Independently own complex infrastructure projects.
  • Make sound technical decisions within established architectural direction.
  • Identify infrastructure risks and propose practical solutions.
  • Build reusable systems rather than one-off fixes.
  • Reduce operational work through automation and self-service.
  • Apply security and least-privilege principles by default.
  • Work effectively across multiple cloud environments.
  • Review infrastructure changes with strong technical judgment.
  • Partner effectively with senior engineers and cross-functional stakeholders.
  • Mentor and influence other engineers through technical expertise.
Before You Apply
️
remote Be aware of the location restriction for this remote position: Brazil
β€Ό Beware of scams! When applying for jobs, you should NEVER have to pay anything. Learn more.
Cloud Infrastructure Engineer @Platform Science
All Others
Salary unspecified
Remote Location
Employment Type full-time
Posted 1mth ago
Apply for this position
Did not apply βœ“
Applied βœ“
Sent Follow-Up βœ“
Interview Scheduled βœ“
Interview Completed βœ“
Offer Accepted βœ“
Offer Declined βœ“
Application Denied βœ“
Unlock 125,000+ Remote Jobs
️
remote Be aware of the location restriction for this remote position: Brazil
β€Ό Beware of scams! When applying for jobs, you should NEVER have to pay anything. Learn more.
Apply for this position
Did not apply βœ“
Applied βœ“
Sent Follow-Up βœ“
Interview Scheduled βœ“
Interview Completed βœ“
Offer Accepted βœ“
Offer Declined βœ“
Application Denied βœ“
Unlock 125,000+ Remote Jobs
Γ—
Apply to the best remote jobs
before everyone else

Access 125,000+ vetted remote jobs and get daily alerts.

4.9 β˜…β˜…β˜…β˜…β˜… from 500+ reviews

⚑ 127,069+ remote jobs, refreshed hourly

πŸ”” Real-time alerts: Apply first, direct to employer

πŸ›‘οΈ Vetted companies, no scams, true remote only

Unlock All Jobs Now

Maybe later