Practitioner Edition

Working with agents, role by role

A practical guide, by role

One platform chapter, one chapter of shared habits, then eight roles. Each role explains what to delegate, when in the day to do it, and where a person still decides; the section after it reads the same work on screen.

It is written for the person doing the work rather than the person buying the tool. No architecture diagrams to approve, no maturity model to score yourself against — just the part of your queue an agent can hold, and the part that stays yours.

Every role chapter ends with a real product screen and three notes on how to read it, so the habit survives contact with the console.

  • August 2026
  • 19 pages
  • Creator: CloudThinker Team
Language

Prefer not to download? Read the whole guide online

Working with agents, role by role — a practical CloudThinker guide, eBook cover
Written for
  • Platform / DevOps
  • SRE
  • Software Engineering
  • Security
  • Cloud Architecture
  • Engineering Management
  • On-call
  • Automation
Contents

Read it online, chapter by chapter

  1. 01Start hereOne control plane for agentic cloud operationsBefore the role pages, understand the shape of the platform. Every role in this guide works through the same entry point, and the instruction is written in plain language rather than a console or a script. The next chapter covers the three habits that make it work; after that, find your role.
  2. 02Before the role pagesThree habits to learn before the role pagesThese three habits turn the platform on the previous page into daily practice. Every role page assumes them, and each role page is followed by an example showing the same work on screen.
  3. 03Role 01 / 08Platform / DevOps EngineerYou own platform reliability while the request queue keeps growing. This chapter covers which parts of that queue an agent can hold for you.
  4. 04Role 02 / 08Site Reliability EngineerYou own availability. This chapter covers how to keep that without personally answering every alert at 2am.
  5. 05Role 03 / 08Software EngineerYou want changes that pass review the first time. This chapter covers what to check before a human reads your diff.
  6. 06Role 04 / 08Security EngineerYour goal is less real exposure, not a smaller backlog. This chapter covers how to tell the two apart.
  7. 07Role 05 / 08Cloud Architect / Cost OwnerYou are asked to keep architecture and cost pointing the same way. This chapter covers how to see both at once.
  8. 08Role 06 / 08Engineering ManagerYou need the state of the system without asking people to write status. This chapter covers where to read it.
  9. 09Role 07 / 08On-call EngineerYou carry the pager for a week. This chapter covers how to spend that week on real failures.
  10. 10Role 08 / 08Automation OwnerYou turn repeated work into automations. This chapter covers what qualifies and who has to own it.