A DevOps resume is read for what you ran in production: what you owned on call, what you automated, and what changed after an incident.
Open with a title that matches the posting, then the most recent role. The first bullets should name a system, an on-call or release duty, and an outcome you can explain. A tool list with no system behind it reads as a keyword block.
Include the platform, the path to production, and one incident or reliability change. Leave out tools you only installed once.
Weak: “Worked with Kubernetes and CI/CD.” Stronger: “Primary on-call for the payments API. Cut repeat pages by changing the retry path after the March outage.” Use your system and your date. If you do not have the number, do not invent one.
No. List tools you operated in a role above. A skills block that the jobs do not support is the first thing a hiring manager asks about.
It is the evidence pattern. You write it in the builder from your own roles. cvharbor does not fill in employers you did not have.