Przejdź do treści
Biblioteka skilli
Zarządzanie i produkt · Nauka i wyjaśnianie

hr-devops

/hr-devops

Pomaga HR i rekruterom zrozumieć DevOps, platform engineering, SRE, infrastrukturę chmurową i CI/CD, porównywać role, oceniać kandydatów i tworzyć pytania rekrutacyjne.

Repozytorium
hr-skills ↗
Licencja
MIT
Ostatnia zmiana repozytorium
10.09.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
4
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 10.09.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Pomaga HR i rekruterom zrozumieć DevOps, platform engineering, SRE, infrastrukturę chmurową i CI/CD, porównywać role, oceniać kandydatów i tworzyć pytania rekrutacyjne.

Oryginalny opis (EN)

Help HR managers, recruiters, and talent acquisition teams understand DevOps, Platform Engineering, Site Reliability Engineering (SRE), cloud infrastructure, CI/CD, and modern software delivery workflows. Use when asked to explain DevOps, screen DevOps candidates, understand CI/CD, compare DevOps and SRE, evaluate infrastructure skills, create DevOps interview questions, understand cloud systems, or any DevOps hiring and recruiting task.

Jak działa

  1. Supported tasks
  2. What DevOps means in 2026
  3. DevOps ecosystem (2026)
  4. Types of DevOps-related roles
  5. Key prompts
  6. DevOps hiring insights
  7. Important hiring realities
  8. Common HR misunderstandings
  9. Tips
Sekcje z nagłówków SKILL.md, w oryginale · 346 linii, 1 352 słów
Podgląd SKILL.md
---
name: hr-devops
description: "Help HR managers, recruiters, and talent acquisition teams understand DevOps, Platform Engineering, Site Reliability Engineering (SRE), cloud infrastructure, CI/CD, and modern software delivery workflows. Use when asked to explain DevOps, screen DevOps candidates, understand CI/CD, compare DevOps and SRE, evaluate infrastructure skills, create DevOps interview questions, understand cloud systems, or any DevOps hiring and recruiting task."
metadata:
  author: Tuan Duc Tran
  version: "1.0.1"
---

# HR DevOps hiring

Comprehensive DevOps and Infrastructure Engineering knowledge for HR and recruiters — from understanding CI/CD pipelines and cloud systems to evaluating DevOps candidates, interpreting infrastructure workflows, and improving technical hiring decisions.

## Supported tasks

- Explaining DevOps and infrastructure concepts for non-technical recruiters
- Understanding modern DevOps ecosystems and cloud workflows
- Screening DevOps and SRE candidates effectively
- Evaluating infrastructure portfolios and GitHub profiles
- Creating DevOps interview questions and hiring scorecards
- Comparing DevOps, SRE, Platform Engineering, and Cloud Engineering roles
- Understanding CI/CD pipelines and deployment systems
- Identifying DevOps seniority levels and skill expectations
- Understanding scalability, reliability, observability, and cloud infrastructure
- Writing DevOps job descriptions and hiring requirements
- Explaining DevOps terminology used by engineers
- Understanding collaboration between developers, QA, security, and operations teams

## What DevOps means in 2026

Modern DevOps is no longer:

- "just server management"
- "only deployment automation"
- "a person who does everything infrastructure-related"

In 2026, DevOps increasingly includes:

- cloud-native infrastructure
- CI/CD automation
- infrastructure as code
- observability
- platform engineering
- developer experience (DX)
- reliability engineering
- Kubernetes orchestration
- security automation
- AI-assisted operations

Many companies are also shifting from traditional DevOps roles toward Platform Engineering and Internal Developer Platforms (IDPs).

## DevOps ecosystem (2026)

### Cloud platforms

- AWS
- Google Cloud Platform (GCP)
- Microsoft Azure
- Cloudflare

### Containers and orchestration

- Docker
- Kubernetes
- Helm

Kubernetes remains the dominant orchestration platform for scalable cloud-native systems.

### CI/CD tools

- GitHub Actions
- GitLab CI
- Jenkins
- CircleCI
- Argo CD

### Infrastructure as Code (IaC)

- Terraform
- Pulumi
- Ansible

### Monitoring and observability

- Prometheus
- Grafana
- Datadog
- New Relic
- OpenTelemetry

### Platform engineering and deployment

- Vercel
- Netlify
- Railway
- Render

### Linux and networking

- Linux
- Bash
- NGINX
- DNS
- Load balancing

### Security and secrets management

- Vault
- SOPS
- IAM
- Security scanning

## Types of DevOps-related roles

### DevOps Engineer

Focuses on:

- CI/CD pipelines
- deployment automation
- infrastructure management
- cloud systems
- release workflows

### Site Reliability Engineer (SRE)

Focuses on:

- reliability
- uptime
- incident response
- scalability
- production stability

Google originally popularized SRE as a software engineering approach to operations and reliability.

### Platform Engineer

Focuses on:

- internal developer platforms
- developer productivity
- self-service infrastructure
- engineering workflows
- platform standardization

### Cloud Engineer

Focuses on:

- cloud architecture
- networking
- infrastructure provisioning
- cloud security
- cloud operations

### DevSecOps Engineer

Focuses on:

- infrastructure security
- compliance automation
- secrets management
- security scanning
- secure CI/CD pipelines

## Key prompts

### DevOps fundamentals

1. "Explain DevOps, SRE, and platform engineering in simple terms for [non-technical sourcers]."
2. "What does a DevOps Engineer actually do day to day in a team building [scale-up SaaS applications]?"
3. "What is the difference between [DevOps, SRE, Platform Engineer, and Cloud Engineer] roles?"
4. "Why is DevOps and automation important in modern software organizations aiming for [continuous delivery]?"
5. "What infrastructure and automation skills are most important for [Applied AI vs Cloud Infrastructure] roles in 2026?"

### CI/CD and automation

1. "What is a CI/CD pipeline, and why do companies use it to accelerate [software release cycles]?"
2. "What is the difference between [GitHub Actions, Jenkins, and GitLab CI] from a candidate screening perspective?"
3. "How do DevOps engineers automate secure deployments for [microservices-based applications]?"
4. "What software delivery workflows are common in [modern DevOps-centric engineering teams]?"
5. "What automation and scripting skills (for example, Bash, Python) should recruiters recognize on resumes for [Site Reliability Engineers]?"

### Cloud and infrastructure

1. "Why are cloud platforms (for example, AWS, GCP) important in [modern DevOps environments]?"
2. "What is Kubernetes, and why is it widely used in [enterprise scaling]?"
3. "What cloud infrastructure and networking skills are expected from a [Senior/Staff DevOps Engineer]?"
4. "How do DevOps engineers manage application [scalability, high availability, and database replication]?"
5. "What cloud and container ecosystem trends should recruiters understand when hiring in [2026]?"

### DevOps candidate screening

1. "How can I evaluate a DevOps candidate's [infrastructure and automation depth] without being highly technical?"
2. "What are common red flags when screening [DevOps vs Platform Engineer] candidates?"
3. "What should I look for in a DevOps candidate's [GitHub repository, infrastructure portfolio, or Terraform configurations]?"
4. "How do I distinguish between [Junior, Middle, Senior, and Staff] DevOps engineers?"
5. "Create a technical screening scorecard and interview questions for a [Senior Site Reliability Engineer] role."

### DevOps terminology for HR

1. "Explain [CI/CD, Kubernetes, Docker, Infrastructure as Code, and observability] in simple terms for [new recruiters joining the team]."
2. "What do DevOps engineers mean by [reliability, uptime, SLOs, and MTTR]?"
3. "What is the difference between [containers and virtual machines], and why does it affect [our hiring requirements]?"
4. "What is Infrastructure as Code, and why do teams use [Terraform vs Pulumi]?"
5. "Which DevOps terms are [core competencies] versus [transient technologies] that I should filter for on resumes?"

## DevOps hiring insights

### Junior DevOps Engineer

Common expectations:

- Linux fundamentals
- Basic cloud platform knowledge
- CI/CD awareness
- Docker familiarity
- Scripting basics

### Mid-level DevOps Engineer

Common expectations:

- CI/CD pipeline management
- Infrastructure as Code experience
- Cloud deployment knowledge
- Monitoring and logging familiarity
- Kubernetes awareness
- Automation workflows

### Senior DevOps Engineer

Common expectations:

- Scalable infrastructure architecture
- Reliability engineering expertise
- Security and compliance awareness
- Incident management leadership
- Multi-cloud and networking knowledge
- Observability and monitoring strategy
- Mentoring and technical leadership

### Staff / Lead DevOps Engineer

Common expectations:

- Organization-wide infrastructure leadership
- Platform engineering strategy
- Reliability and scalability ownership
- Internal developer platform design
- Cross-team engineering enablement
- Long-term infrastructure decision making

## Important hiring realities

### DevOps is NOT "someone who does everything"

Many companies incorrectly expect DevOps engineers to simultaneously handle:

- cloud infrastructure
- cybersecurity
- backend engineering
- networking
- SRE
- platform engineering
- database administration
- QA automation

This is often unrealistic.

### Modern DevOps is increasingly platform-oriented

Many engineering organizations are shifting toward:

- platform engineering
- developer experience optimization
- self-service infrastructure
- internal tooling
- automation-heavy workflows

rather than traditional manual operations work.

### Kubernetes knowledge alone does NOT equal strong DevOps skills

A candidate may:

- deploy Kubernetes clusters
- but still lack:
  - reliability engineering
  - automation maturity
  - incident management
  - scalability thinking
  - operational ownership

### Strong DevOps engineers often think in systems

Strong candidates usually demonstrate:

- automation mindset
- reliability thinking
- scalability awareness
- debugging ability
- infrastructure ownership
- developer enablement
- operational discipline

rather than only tool lists.

## Common HR misunderstandings

### DevOps ≠ only operations

Modern DevOps often includes:

- software engineering
- automation
- cloud architecture
- platform engineering
- observability
- infrastructure as code
- reliability engineering

### SRE ≠ traditional DevOps

SRE roles are often more focused on:

- reliability
- uptime
- production engineering
- incident response
- service-level objectives (SLOs)

### More cloud certifications ≠ stronger DevOps engineer

Strong DevOps engineers usually demonstrate:

- production experience
- automation ownership
- incident handling
- infrastructure design
- scalability thinking
- operational maturity

rather than only certifications.

## Tips

- Senior DevOps and SRE professionals should be evaluated on their reliability ownership, scalability architecture, and developer enablement rather than just tool lists or certifications.
- Portfolios and resumes are most credible when they show real-world infrastructure-as-code automation (e.g. Terraform), deployment system pipelines, and production incident response.
- Recruiters should clarify the exact DevOps focus needed: SRE (production uptime and reliability), Platform Engineering (internal tooling/automation), or Cloud Infrastructure.
- Foundation technologies such as Docker, Kubernetes, and CI/CD pipelines remain central skills in DevOps, but the core value lies in reducing developer friction and build times.
- Avoid "unicorn" job descriptions that expect a single individual to simultaneously master cloud architecture, deep backend development, cybersecurity, database administration, and SRE.
Pliki w paczce (4)
  • SKILL.md 10 KB
  • content/understanding-infrastructure-ci-cd-and-modern-software-delivery.md 7 KB
  • examples/hiring-a-senior-devops-engineer.md 17 KB
  • prompts/devops-hiring-prompts.md 1 KB

Wersje

W bazie nie ma innych skilli o nazwie hr-devops.

Migawka bazy z 13.11.2026 · wersja paczki e9bc185e4e5a (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100hr-backend
    Pomaga HR i rekruterom zrozumieć inżynierię backendową: API, bazy danych, skalowalność i infrastrukturę serwerową, porównywać frameworki, oceniać kandydatów i tworzyć pytania rekrutacyjne.
  • 100hr-qa
    Pomaga HR i rekruterom zrozumieć testowanie oprogramowania, automatyzację testów i inżynierię jakości, porównywać ręczne QA z SDET, oceniać kandydatów i tworzyć pytania rekrutacyjne.
  • 95devops-cloud
    Opisuje DevOps, infrastrukturę chmurową i platform engineering z AWS, GCP, Azure, Kubernetes, Terraform, pipeline'ami CI/CD i infrastrukturą jako kodem.
  • 100devops-sre
    Wnosi osąd inżyniera DevOps lub SRE: projektowanie potoków wdrożeń, SLO i budżety błędów, reagowanie na incydenty i kompromisy niezawodności infrastruktury.
  • 100devops-mock-interview
    Przeprowadza symulowaną rozmowę kwalifikacyjną na stanowisko DevOps lub SRE, ze scenariuszami incydentów i oceną raportu.
  • 90devops-cloud
    Projektuje, zabezpiecza i prowadzi infrastrukturę chmurową oraz potoki dostarczania: kontenery, Kubernetes, IaC, sekrety i reagowanie na incydenty.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.