Pulumi is the modern alternative to Terraform — write infrastructure in real programming languages (TypeScript, Python, Go, C#) instead of HCL. The interview is unique among IaC companies for its emphasis on language-internals work, since the platform compiles user code into a state machine that talks to cloud APIs.
Process
Recruiter screen → 60-minute coding pair (often Go) → onsite virtual: 2 coding, 1 system design, 1 craft deep-dive, 1 behavioral. Cycle: 3–4 weeks.
What they actually ask
- Design a state engine for declarative infrastructure changes (plan / preview / apply). Focus on how the engine diffs desired state against the last-known state and the live cloud, then turns that diff into a create/update/delete/replace plan. Interviewers probe what happens on partial failure mid-apply and how you keep state consistent when an operation is interrupted.
- Design a multi-language SDK that surfaces a consistent API across TypeScript, Python, Go, and Java. Be ready to describe a language-neutral core behind an RPC boundary with thin per-language bindings, so behavior stays identical everywhere. Expect questions on how you version the schema and generate SDKs from a provider definition instead of hand-writing each language.
- Design dependency-aware resource ordering (DAG construction and execution). Explain how you build a dependency graph from resource references, run a topological sort to find a safe order, and parallelize independent branches. A common follow-up is detecting cycles and handling a resource whose input depends on another resource’s output that only exists after apply.
- Coding: practical Go problems, often involving graph traversal or state machines. These are real engineering tasks, not puzzles — parse a structure, walk a graph, or model transitions with clean error handling. Write idiomatic Go with sensible use of goroutines, channels, and context, and talk through edge cases as you go.
- Behavioral: open-source mindset, written communication, pragmatic decision-making. Since much of Pulumi is public, expect questions about working in the open — responding to GitHub issues, writing design docs, and making decisions others can follow asynchronously. Have an example ready where you shipped a pragmatic fix under real constraints instead of the ideal one.
Levels and comp (2026)
- SE II: $170K–$210K total
- Senior SE: $240K–$310K
- Staff: $340K–$450K
- Principal: $470K–$610K
Prep priorities
- Be fluent in Go and at least one Pulumi language (TypeScript or Python). The engine and providers are written in Go, so that is where most interview coding happens; the SDK language is where you show you understand the user’s experience.
- Understand cloud provider APIs and IaC fundamentals (drift, state, idempotency). Know why applying the same program twice should be a no-op, how drift is detected between recorded state and reality, and what a resource replacement means for the resources that depend on it.
- Read the Pulumi engineering blog and OSS codebase. Skim the pulumi/pulumi repo so you can speak to how the engine, language hosts, and resource providers fit together; referencing real code signals you did the work.
Frequently Asked Questions
Is Pulumi fully remote?
Yes. Distributed across US and EU. Hubs in Seattle and Brno are optional.
How does Pulumi compare to Terraform?
Pulumi uses real programming languages with type checking, IDEs, and reuse. Terraform is HCL-only but has broader adoption. Pulumi is winning new accounts; Terraform dominates legacy.
Do I need IaC experience to interview?
Strongly preferred. At minimum, work through Pulumi tutorials and deploy something to AWS/GCP/Azure with it.
Similar company guides
Prepping for Pulumi? Put it to work:
