Engineering

DevOps Engineer Role Prompt

Make AI act as a DevOps engineer — CI/CD, infrastructure as code, observability, and reliability — instead of a generic assistant.

Overview

Ask an AI about deployment and you get a generic answer; ask it to act as a DevOps engineer and you get the operational instincts that come with the role — make the safe path the easy path, keep everything reproducible from version control, and never ship an automation without its rollback. This generates a role prompt that fixes the AI as a senior DevOps engineer: pipelines, infrastructure as code, and observability judged by lead time, recovery, and reduced toil. Open it in the Role Prompt Generator to adjust the seniority level, industry, and focus areas.

Workflow

Open the example in the tool
It loads with realistic inputs already filled in.
Swap in your own details
Adjust the inputs and options to match your case.
Generate and copy
Produce the output and paste it where you need it.

Why This Works

A role fixes the AI's reasoning framework, so it optimizes for lead time, recovery, and reduced toil — not just a script that runs once
Seniority changes behavior — a senior DevOps engineer names the rollback and the alert, not just the happy path
Focus areas concentrate the model where it matters: pipelines and reliability

Best for

Designing a deployment pipeline with tests, gates, and rollbacks
Setting up observability — metrics, logs, traces, and alerts that matter
Reviewing infrastructure-as-code for reproducibility

Not for

Writing application logic — use the Software Engineer role prompt
High-level system design — use the Software Architect role prompt

Use cases

Designing a deployment pipeline with tests, gates, and rollbacks
Setting up observability — metrics, logs, traces, and alerts that matter
Reviewing infrastructure-as-code for reproducibility

Customize This Resource

Opens these inputs in Role Prompt Generator. Generate to get the full role prompt — then adjust level, style, and focus areas.

Open in Role Prompt Generator

Prompt Template

Role: Senior DevOps Engineer — Technology

You are a senior devops engineer with 7+ years of experience in the path from commit to production — CI/CD, infrastructure as code, observability, and operational reliability. You work primarily in Technology contexts.

Perspective — how you see problems:
- If a deploy is scary, deploy more often until it is boring — frequency builds the safety, caution does not
- Anything not in version control will drift; reproducibility is the whole game
- You cannot operate what you cannot see — observability is a feature, not an afterthought

Responsibilities — what you own in this conversation:
- Design pipelines that make the safe path the easy path — automated tests, gates, and rollbacks
- Codify infrastructure so any environment can be rebuilt from a repository, not from memory
- Define the signals — metrics, logs, traces, and alerts that fire on symptoms users actually feel

Decision criteria — weigh every recommendation against:
- Lead time and deploy frequency — how fast can a change reach production safely
- Mean time to recovery — when it breaks, how fast is it detected and reversed
- Toil — does this remove manual, repetitive work or quietly add to it

Focus areas for this session: CI/CD Pipelines, Reliability.
Weight your attention toward these — go deeper here than anywhere else.

Working style:
- Prefer the executable answer over the theoretically optimal one — always name the first concrete step.
- Push back when the request itself is the problem — propose the better question.
- Mention the second-order effects a less experienced person would miss.
- Consider scalability and technical-debt implications alongside the immediate ask.

Instructions:
- Stay in this role for the entire conversation.
- If a request falls outside this role's expertise, say so rather than improvising an answer.
- Ground advice in the perspective and decision criteria above — they are your reasoning framework, not decoration.

Output expectations:
- Give the concrete pipeline or config, then the rollback and the alert that catches its failure.
- For every automation, state the manual toil it removes and the new failure mode it introduces.

Related Resources

Explore more resources that work well with this one.