Claude Prompts for DevOps Engineer Job Search

You are an expert recruiter for DevOps and platform roles. Here is my resume:

[PASTE RESUME]

And the job description:

[PASTE JOB DESCRIPTION]

Rewrite my bullet points to match this role. Lead each with the reliability or velocity outcome (deploy frequency raised, lead time or MTTR cut, uptime improved, cloud cost reduced, toil automated away), quantify it, and mirror the exact stack from the job description (for example Kubernetes, Terraform, Docker, AWS or GCP, CI/CD, Jenkins or GitHub Actions, Prometheus, Ansible) without inventing anything. Flag any bullet that reads as a stretch.

Act as an ATS parser for DevOps engineer roles. From this job description:

[PASTE JOB DESCRIPTION]

List the tools, platforms, and exact keyword phrases (for example Kubernetes, Terraform, Docker, AWS, CI/CD, infrastructure as code, observability, Helm, GitOps, SRE) an ATS would score against, ranked by prominence. Then tell me which are missing from my resume:

[PASTE RESUME]

and where I could add each one truthfully.

Help me quantify this DevOps work for my resume: [DESCRIBE THE PIPELINE, MIGRATION, OR AUTOMATION]. Ask me up to 4 questions to surface the impact (deploy time or frequency before and after, incidents or downtime avoided, hours of manual work removed, cloud spend saved). Then write 2 resume bullets in the format 'accomplished X by doing Y, resulting in Z'.

Write a concise cover letter for this DevOps engineer role:

[PASTE JOB DESCRIPTION]

Using my background:

[PASTE RESUME OR SUMMARY]

Under 250 words, no cliches. Open with a concrete reason I fit this team or their infrastructure challenges, cite one pipeline, migration, or reliability win I delivered and its result, and close with a clear call to action. Match the company's tone.

Write a 4 to 5 sentence LinkedIn message to the hiring manager or platform lead for this DevOps engineer role: [PASTE ROLE AND COMPANY]. Introduce me briefly, give one specific reason I am interested in their platform or scale, and mention one relevant thing I have built ([DETAIL], for example a CI/CD or Kubernetes win). Warm, human, under 90 words.

Act as a senior platform engineer interviewing me for a [SENIORITY] DevOps role. Give me one realistic design question (for example: design a zero-downtime deployment pipeline, a multi-region Kubernetes setup, or an autoscaling strategy). After I answer, probe like a real interviewer: ask about rollout and rollback, secrets management, observability, failure modes, and cost. Then tell me what a strong answer covers. Ask the question now and wait for my answer.

Quiz me on the technical questions common in DevOps interviews: how a Kubernetes pod, deployment, and service relate, what happens during a rolling update, how CI/CD pipelines gate and promote a release, containers vs VMs, Linux troubleshooting (high load, disk full, a hung process), and infrastructure as code trade-offs. Ask one question at a time, wait for my answer, then correct me and give the concise version an interviewer wants to hear.

Act as an interviewer running an on-call incident exercise for a DevOps role. Give me a realistic page (for example: latency spiked 5x after a deploy, or a service is crash-looping in production). Walk me through it like a real incident: ask how I would triage, what dashboards and logs I would check, how I would decide to roll back, how I would communicate, and what I would put in the postmortem. Then tell me what a strong responder does differently. Give me the page now and wait.

Compare my resume against job descriptions for [TARGET ROLE, for example Senior SRE or Platform Engineer]. My resume: [PASTE RESUME]. Target job descriptions: [PASTE 2 to 3]. Identify the specific tooling, cloud, and reliability-practice gaps between me and these roles, ranked by how much they matter, and for each suggest the fastest credible way to close or reframe it.