We source, vet, and manage hiring so you can meet qualified candidates in days, not months. Strong English, U.S. time zone overlap, and compliant hiring built in.
.svg){kind=logo}
Pulumi is an Infrastructure as Code (IaC) platform that lets developers provision and manage cloud infrastructure using general-purpose programming languages instead of declarative YAML or domain-specific languages. Instead of learning CloudFormation syntax or HCL, teams write Python, Go, TypeScript, or C# code to define AWS, Azure, Google Cloud, Kubernetes, or other cloud resources. This approach brings software engineering discipline to infrastructure: version control, testing, reusable components, and CI/CD integration.
Pulumi gained significant traction in the last 3-4 years, particularly among teams that value developer experience and rapid iteration. Unlike Terraform (which requires learning HCL), Pulumi lets backend developers use their existing language skills. The platform ships with strong support for AWS (including bleeding-edge services), Azure, GCP, Kubernetes, and dozens of other cloud providers. Pulumi has over 15,000 GitHub stars and is used by companies like Tableau, Zoom, and MongoDB for production infrastructure.
Pulumi's core value proposition: if your team already knows Python or TypeScript, you can code infrastructure the same way you code applications, sharing logic across frontend, backend, and infrastructure layers.
Pulumi shines in situations where you need rapid infrastructure iteration or where your infrastructure is complex and benefits from real programming constructs. Hire a Pulumi engineer if you're migrating from manual cloud setup or basic CloudFormation to a more mature IaC practice, building multi-cloud strategies (Pulumi's abstraction layer makes this easier), or you want infrastructure decisions made by the same team that owns the application code.
Pulumi is particularly strong for teams running Kubernetes at scale, teams that need reusable infrastructure components across multiple projects, or organizations managing infrastructure across multiple AWS accounts or regions. It's also ideal if your infrastructure needs conditional logic, loops, or dynamic resource generation. For example, if you're provisioning a VPC, multiple subnets, security groups, and RDS databases per environment, Pulumi's programming model is much cleaner than CloudFormation templates with dozens of parameters.
Pulumi is not a good fit if your organization needs a completely YAML/declarative-only tooling (some teams prefer that constraint for auditability), if you're heavily committed to Terraform already and need zero migration effort, or if your infrastructure is extremely simple and stable (a single Lambda, a static S3 bucket). In those cases, simpler approaches work fine.
Team composition: A Pulumi hire typically pairs with DevOps/Platform Engineering skills, cloud (AWS, Azure, or GCP) expertise, and Python or Go knowledge. If you're managing Kubernetes infrastructure, Pulumi developers need to understand networking, RBAC, and stateful applications. Complement with security/compliance expertise for regulated industries.
Core competencies: strong programming fundamentals (Python, Go, TypeScript, or C#), deep knowledge of at least one cloud provider (AWS preferred given dominance), Kubernetes familiarity, and CI/CD integration experience. Evaluate code quality and design patterns, not just infrastructure knowledge. A great Pulumi engineer thinks about abstraction, reusability, and testing infrastructure the same way they'd think about application code.
Must-haves: hands-on experience with Pulumi (not just Terraform), cloud provider SDKs and APIs, YAML-free mindset, Git workflows, and ability to reason about infrastructure cost and performance. Must understand the distinction between Pulumi stacks (environments), configurations, and state management.
Red flags: developers who view infrastructure as a separate discipline disconnected from application development, those unfamiliar with IaC version control workflows, or those with deep Terraform-only experience but skepticism about language-based IaC.
Junior (1-2 years): Can provision basic cloud resources (VPCs, compute, databases) using Pulumi and one cloud provider. Understands the Pulumi programming model, stacks, and basic configuration. Knows how to import existing resources and read documentation. Likely has bootcamp training or academic background.
Mid-level (3-5 years): Builds reusable Pulumi components, manages multi-environment infrastructure, understands state management and drift detection. Can architect infrastructure for high availability and disaster recovery. Troubleshoots cross-cloud networking and security. Integrates Pulumi into CI/CD pipelines.
Senior (5+ years): Designs infrastructure strategy across multiple cloud providers, mentors teams on IaC best practices, optimizes for cost and performance, and handles complex migration scenarios. Understands Pulumi internals (CrossGuard, automation API, policy-as-code) and can extend the platform with custom providers or SDKs.
Soft skills for remote work: async communication in written form, ability to explain complex infrastructure decisions clearly, ownership mindset (infrastructure as a product, not a chore), and collaborative problem-solving with application teams.
Tell me about a time you had to migrate infrastructure to a new cloud provider or redesign a major infrastructure component. What went wrong, and how did you handle it? Listen for thoughtful decision-making, willingness to learn new tools, and how they communicated with stakeholders. Strong candidates mention automation, testing, and rollback plans.
Describe your experience using Pulumi. What was the biggest challenge you faced with it? Strong answers mention specific Pulumi features (stacks, configuration, automation API) and real problems. Good candidates are honest about limitations and workarounds they used.
Walk me through how you'd set up a CI/CD pipeline that deploys infrastructure via Pulumi. Strong candidates mention pull request previews, approval workflows, automated testing, and secrets management. They should understand the distinction between development and production stacks.
How do you approach infrastructure code reviews? What do you look for? Strong answers mention security, cost optimization, code reusability, documentation, and alignment with organizational standards. They understand that infrastructure reviews are like application code reviews, not just checklist exercises.
Tell me about a time you had to debug an infrastructure issue in production. How did you approach it? Listen for methodical troubleshooting, understanding of logs and monitoring, and how they collaborated with application teams.
In Pulumi, what's the difference between a Stack, a Config, and a Secret? How would you structure these for an application with dev, staging, and production environments? Strong candidates explain that Stacks represent isolated infrastructure environments, Config is for non-sensitive values, and Secrets are encrypted. They describe concrete organization (separate stack files, environment-specific configuration, secure secret storage).
You have a Pulumi program that creates 50 AWS resources. How would you prevent drift between your desired infrastructure and actual cloud state? What's Pulumi's role in that? Strong answers mention automated refreshes, state file management, policy-as-code (CrossGuard), and monitoring. They understand that Pulumi doesn't automatically detect drift but can be integrated with audit tools.
How would you write a reusable Pulumi component that teams across your organization can consume? What design decisions would you make? Strong candidates describe creating a custom component class/function, handling configuration polymorphically, supporting multiple cloud providers, and publishing (via GitHub, registries, or internal package managers).
Explain how you'd use Pulumi's Automation API to programmatically manage infrastructure. When would you use this vs. the CLI? Strong answers mention orchestrating multiple stacks, triggering deployments from webhooks or scheduled tasks, building self-service infrastructure platforms, and testing infrastructure code.
You're tasked with implementing infrastructure policy enforcement (e.g., all S3 buckets must have encryption enabled). How would you do this with Pulumi? Strong candidates mention Pulumi CrossGuard (policy-as-code), custom enforcement in CI/CD, and different enforcement levels (advisory vs. blocking).
Write a Pulumi program (Python or TypeScript) that creates the following infrastructure: VPC with public and private subnets, an RDS database in the private subnet, and an ALB in the public subnet. The program should accept environment-specific parameters (DB size, instance type) via Pulumi Config. Include output exports for the ALB DNS name and RDS endpoint. (Estimated time: 45 minutes. Rubric: correct resource definitions, proper subnet configuration, parameterization via Config, correct outputs, clean code structure.)
Latin America Market Rates (2026):
US Market Rates (for comparison):
LatAm Pulumi talent is concentrated in Brazil and Argentina, with growing communities in Mexico and Colombia. Rates vary: Brazil offers the deepest pool with competitive mid-level talent; Argentina commands a slight premium for seniority; Colombia and Mexico offer emerging talent at lower rates. Senior Pulumi architects are scarce across LatAm, so expect to pay premium rates or work with contractors from multiple countries. Direct hire (if handled independently) typically costs 20-30% more than staffing rates due to compliance and tax burden.
Time zone alignment: Most LatAm Pulumi talent operates in UTC-3 (Buenos Aires, São Paulo) to UTC-6 (Mexico City), giving 6-8 hours of real-time overlap with US East Coast teams. This enables synchronous standups, pair programming, and rapid incident response without awkward timing.
Engineering culture: LatAm's tech hubs, especially in São Paulo, Buenos Aires, and Medellin, have strong DevOps and cloud-native communities. Brazil's universities emphasize cloud computing and infrastructure automation. The culture values practical problem-solving and shipping code fast, which aligns well with Pulumi's philosophy of developers managing infrastructure.
English proficiency: Senior and mid-level LatAm developers generally have strong English skills, especially in tech-forward Argentina and Brazil. This eliminates friction in code reviews, documentation, and architecture discussions.
Cost efficiency: Pulumi developers from LatAm typically cost 40-60% less than US equivalents without sacrificing code quality. This is especially valuable for infrastructure roles, which are often under-resourced in US-based teams.
Pulse on modern tooling: LatAm developers are early adopters of IaC and cloud-native practices. They're pragmatic about tool selection and often contribute to open-source infrastructure projects, which correlates with Pulumi expertise.
Share your requirements: Tell us about your infrastructure architecture, which cloud providers you use, team size, and desired seniority level. If you're migrating from Terraform or CloudFormation, we'll factor that in.
We match from our pre-vetted network: South maintains a network of vetted Pulumi engineers across LatAm who've been assessed on cloud provider knowledge, programming fundamentals, and infrastructure design. We prioritize candidates with proven Pulumi experience, not just transferable skills.
You interview: You conduct technical interviews (we provide assessment templates and interview guides). We'll share candidate portfolios and past infrastructure projects to speed evaluation.
Ongoing support: Once matched, we handle onboarding, provide a 30-day replacement guarantee if the hire isn't a fit, and remain available for questions throughout the engagement. If you need to swap candidates or scale the team, we facilitate that seamlessly.
South's difference: Unlike generic staffing platforms, we understand infrastructure tooling deeply. Our matching process evaluates for architectural thinking, not just syntax knowledge. Ready to hire? Start the conversation at https://www.hireinsouth.com/start.
Pulumi is used to provision and manage cloud infrastructure (AWS, Azure, GCP, Kubernetes) using code in Python, Go, TypeScript, or C#. Teams use it to automate infrastructure deployment, manage multi-environment setups, and enforce infrastructure policies. It's the language-based alternative to Terraform or CloudFormation.
Yes, Pulumi is excellent for Kubernetes. It can manage cluster provisioning, networking, RBAC, and application deployments. Use Pulumi to define infrastructure (EKS, GKE, AKS) and Kubernetes resources (namespaces, services, deployments) in a single, cohesive program.
Pulumi uses general-purpose languages; Terraform uses HCL. If your team prefers code over YAML, or if you want to reuse existing programming logic, choose Pulumi. If your organization is already deep in Terraform, migration overhead might not be worth it. Both are excellent IaC tools; it's mostly a culture and skill fit question.
Mid-level Pulumi developers in LatAm cost $65,000-$90,000/year. Senior engineers (5+ years) run $105,000-$150,000/year. Rates vary by country and experience. Compare that to $130,000-$220,000/year for equivalent US talent.
Typically 2-4 weeks from initial conversation to offer. We prioritize candidates from our pre-vetted network, which dramatically speeds the timeline vs. general recruiting.
For building new infrastructure from scratch, a mid-level developer works well. For complex migrations, multi-cloud strategies, or scaling existing systems, hire senior talent. For small projects or maintenance, junior developers with good mentorship can succeed.
Yes. South supports both full-time and project-based engagements. Short-term projects (3-6 months) work well for infrastructure migrations or building reusable components. We can help you scope and schedule those engagements.
Most are in UTC-3 to UTC-6 (Argentina, Brazil, Colombia, Mexico). This provides 6-8 hours of overlap with US East Coast business hours, ideal for standups and collaborative work.
We assess hands-on cloud provider knowledge, Pulumi programming (stacks, components, configuration), code quality and design patterns, and infrastructure architecture thinking. Candidates complete technical assessments and infrastructure design discussions with our team.
We offer a 30-day replacement guarantee. If the hire isn't working out, we'll match you with a different candidate at no additional cost. We're invested in your success.
Yes. South manages payroll, taxes, benefits, and local employment compliance. You pay South a transparent all-in rate; we handle the administrative and legal side.
Absolutely. We regularly staff multi-person teams. Whether you need a team of infrastructure engineers or a mixed team of backend and infrastructure talent, we can scale to your needs.
