Building a quick market map for Staff SREs in Austin, I’ve been using this X-ray: site:linkedin.com/in (“site reliability” OR SRE) AND (Kubernetes OR “K8s”) AND (Terraform OR “infra as code”) AND (Austin OR “Greater Austin”) -jobs -hiring -recruiter, which surfaced 118 viable profiles in about 20 minutes. If you’ve tuned this for remote-first teams or to better exclude DevOps generalists (e.g., adding (“on-call” AND SLO) NOT (“help desk” OR desktop)), I’d love to compare notes and fold improvements into a cleaner talent mapping workflow.
Quick tweak that’s helped me: building on @laura37’s angle, add (“PagerDuty” OR “on-call” OR “error budget”) to your X‑ray to bias toward true SREs and cut DevOps noise; when Austin results drift, I’ll also exclude “platform engineer” — , that overlap drives me nuts. Tiny caveat: you’ll miss a few who don’t name tools, so I swap in Prometheus/Grafana if the 20‑minute sweep stalls.