The infrastructure as code argument has two sides that rarely engage properly. Terraform's position is that infrastructure should be declarative, that HCL's limited expressiveness is a feature because it constrains what a tired engineer can do at four in the afternoon, and that the state of your infrastructure should be readable without executing anything. Pulumi's position is that infrastructure is software, that pretending otherwise produces templating languages that slowly reinvent programming badly, and that developers should get loops, functions, types, unit tests and their IDE. Both positions are defensible.
Pulumi's documentation argues its own side competently and never seriously presents the other one, which is what documentation does and which a learner should compensate for. The materials themselves are well organised. There are get started guides per cloud provider covering AWS, Azure, Google Cloud and Kubernetes, a Dev Center with tutorials, templates and examples, and concept documentation that explains stacks, projects, resources and the programming model. Language coverage is genuine: TypeScript, Python, Go, .NET, Java and YAML, with examples that actually exist in each rather than one first-class language and five translations.
The YAML option is quietly interesting, because it means a team that wanted the declarative model can have it inside Pulumi's engine, which undercuts the framing of the whole debate in a useful way. Migration documentation from Terraform is present and takes the job seriously, including importing existing state, which is the part that determines whether a migration is feasible at all. Pulumi Neo is the newer addition, described as a purpose-built infrastructure agent, sitting alongside the option to use your own coding agent. This is the direction every infrastructure vendor is moving and the material on it is necessarily early.
My general view on infrastructure agents is that they are good at the part that was already easy, generating a plausible resource definition, and that the hard part was never writing the code. The hard part is knowing that this security group change will break a peered network at two in the morning, and an agent that confidently generates infrastructure is a faster path to an outage than an engineer who is slow because they are thinking. I would treat agent-generated infrastructure as a draft that a human reviews properly, and I would be wary of any material that presents it as more than that. Certification is a mess that is not Pulumi's fault but is Pulumi's problem.
There is no official Pulumi certification. Search for one and you will find training companies advertising Pulumi Training and Certification, marketplace courses offering completion certificates, and learning platforms with Pulumi paths, none of which are issued or recognised by Pulumi. This is the same vacuum-filling pattern as Fivetran, and it is worth stating plainly because someone is going to pay for one of those courses believing it is a vendor credential. The genuine weakness in the learning material is one that most tool documentation shares.
It teaches the tool thoroughly and infrastructure design hardly at all. You will learn how to define a VPC in Pulumi. You will not learn how to think about network segmentation, blast radius, environment separation, or the organisational question of who is allowed to apply changes to production. That knowledge is what separates infrastructure engineers from people who can run a deploy command, and it comes from elsewhere.
The risk specific to Pulumi is that general-purpose languages give a clever engineer enough room to build an abstraction layer over their infrastructure that only they understand, which is a real failure mode I have seen more than once. Terraform's constraints prevent a class of bad decisions by making them tedious. Pulumi removes the constraint and relies on discipline. Three point eight.
Well-maintained multi-language documentation with honest migration guidance, for a tool that rewards teams with software engineering discipline and punishes those without it, plus a third-party certification market that should be ignored entirely.