Interview Preparation¶
Every question on the pages below links back to the concept page that actually teaches it. That's deliberate: memorizing "role defaults are lowest precedence" is worth far less than understanding why — which is the difference between passing a screening question and holding up under a senior follow-up.
How This Is Organized¶
By subject, since that's how you'll actually study:
- Core Concepts — idempotency, precedence, modules, command vs. shell
- Architecture & Performance — execution model, SSH, forks/strategy
- Scenario-Based Questions — reasoning through an open-ended production problem, not a fact lookup
- Roles, Collections & Modules
- Senior & Architect Questions
By Level, Roughly¶
| Level | Where to focus |
|---|---|
| Beginner | Core Concepts — first half |
| Intermediate | Core Concepts full, Roles, Collections & Modules |
| Advanced | Architecture & Performance |
| Senior / Architect | Scenario-Based Questions, Senior & Architect Questions |
How senior interviews actually differ
A senior interview rarely asks "what is forks" in isolation — it asks you to reason through a situation ("2-hour playbook run, 500 hosts, go") using several concepts at once. Scenario-Based Questions is built around exactly that shape.
Next¶
Start with Core Concepts.