PlayBooker is a growing catalogue of documentation modules, organized by the area of the business they support. The launch catalogue centres on the Career Progression Framework; additional categories are released as building blocks over time.

Every module is designed to be white-labelled, customized, and published into your existing knowledge base — Confluence, a Git-based wiki, or an internal portal — without forking from upstream.

People & Management

Job descriptions, career ladders, coaching guides, team norms.

  • Job descriptions and role expectations
  • Career ladders and progression frameworks
  • Coaching guides and growth plans
  • Team norms and operating principles

Hiring & Interview Playbooks

Interview loops, rubrics, and practical formats designed for an AI-enabled hiring world.

  • Interview loops and rubric templates
  • Practical interview formats that stay relevant with AI tooling
  • Code review and architecture review exercises
  • Behavioural interview frameworks tied to competencies

Engineering Practices

Design doc expectations, code review standards, onboarding, "how we build" guides.

  • Design doc expectations and templates
  • Code review standards
  • Developer onboarding guides
  • Architecture, reliability, and security baseline guides

Platform & Architecture

Cloud-first principles, tagging policy baselines, naming conventions, operational readiness.

  • Cloud-first architecture principles
  • Tagging policy baselines with org overlays
  • Environment naming conventions
  • Operational readiness checklists

Tooling Tutorials

Selective, baseline tooling guides built for internal enablement, not SEO.

  • Concept-clarity guides for adopted tools (e.g. Bazel)
  • Internal-first tutorials with explicit prerequisites
  • Reference architectures for common tool integrations

How modules are shaped

Every module ships with the same contract:

  • Stable slugs for blocks and sub-sections, so upgrades are safe.
  • Customizable display names for roles, tools, and policies.
  • Configuration-driven inclusion — toggle whole sections on or off.
  • Org-policy overlays — extend the baseline without rewriting it.
  • Versioned releases with changelogs and an upgrade path.

The aim is stable structure, flexible presentation: your customizations survive every upgrade.

What’s not in scope

PlayBooker is deliberately not a hosted documentation platform. It does not compete with Confluence, Notion, or your wiki of choice. It is also not a consulting service. The product is the catalogue and the customization surface — your team owns where it lives and how it evolves.