Before you connect anything, you know who will read your map. The engineer on your first map stays in your channel afterwards.
Each lead owns one part of the map and still works on it most weeks.

Ran platform engineering at a payments company for a decade. Still reviews the Terraform templates before they ship.

Decides what the map says first. Sits in on first-map calls every week.

Reads trust policies across AWS, Entra ID and Google Cloud, and writes the rules that turn them into hops.

Follows deploy tokens from the workflow file to the last thing they can reach, then writes the smallest change that breaks the path.

Sits in the shared channel from the first map on, and writes most of the first pull requests himself.
Your engineer has a name and a profile on this page, and answers in your channel on working hours.
credentials across six leads. We hire on the work, not the badge. This list is here because buyers ask for it.
Credential | Issued by | Leads | Used on |
CISSP | ISC2 | 1 | Security programme |
CCSP | ISC2 | 2 | Cloud security |
AWS Solutions Architect | Amazon Web Services | 1 | Templates |
AWS Security | Amazon Web Services | 1 | Identity |
AZ-500 | Microsoft | 1 | Identity |
CKS | Linux Foundation | 1 | Pipelines |
Terraform Associate | HashiCorp | 1 | Pull requests |
CKA | Linux Foundation | 1 | Customer clusters |
Cloud Security Engineer | Google Cloud | 1 | Customer accounts |

One day in five is yours for research, and every role shows its pay.