What to put on a DevOps engineer’s digital card
- Platform focus A line like “Kubernetes on AWS, GitOps and observability” instantly tells peers which problems you handle.
- Primary cloud Recruiters often hire for one cloud first; stating yours saves a screening round.
- Infrastructure write-ups Short stories about migrations and incidents show how you think about reliability.
- Code repository link Public modules, scripts or Helm charts let engineers see the quality of your configuration.
- LinkedIn Many platform hiring conversations start with a LinkedIn message after a meetup.
- Email A personal email that you check outside on-call hours is better than a work address.
- Observability stack Naming Prometheus, Grafana, ELK or a commercial monitoring tool shows how you watch systems in production, which is a common topic in platform interviews.
- On-call experience A short line such as “weekly rotation, incident commander for payment services” signals that you have carried real production responsibility and handled pressure calmly.
When to share it
- At cloud community days and Kubernetes meetups where you meet platform teams and hiring managers.
- After speaking at a meetup, shown on the final slide with links to your demo code.
- In open-source project profiles and issue discussions, so maintainers can reach you about contributions.
- At vendor workshops and partner events where solution architects and customers exchange details.
What to say when you send it
A card link on its own is easy to ignore. Add a line that reminds the person where you met and what to do next — for example:
Hi Deepa, enjoyed your talk on cost controls at the cloud community day. Here is my card with the write-up on moving our pipelines to GitOps. Happy to swap notes on autoscaling if your team is working on it.
Where to put the QR code
- The last slide of a meetup talk, alongside a link to your demo repository.
- A sticker on your laptop lid at cloud community days and conferences.
- The README of a Terraform module or Helm chart you maintain publicly.
Mistakes to avoid
- Linking repositories with secrets in history Even deleted keys remain in commit history. Scan and clean repositories before you add them to a card, and rotate any credentials that were ever exposed.
- Listing every cloud equally If you have run production on one cloud and only read about others, say so. Interviewers test depth, and a balanced list of three clouds can backfire when the first deep question lands on the one you have never used.
- Using an internal dashboard as a demo A link to an employer’s monitoring dashboard, even read-only, can expose sensitive data. Use screenshots of a demo environment instead.
Tips for a card that gets saved
- Keep the cloud and platform line to a few items; a precise focus invites better conversations than a full tool list.
- Make sure linked repositories contain no secrets, keys or internal addresses, even in old commits.
- If you prefer not to be contacted at night, leave your phone off and use email and LinkedIn only.