Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Hr Technical Interview

ASecurity

Design and run technical interviews for hiring: backend, frontend, fullstack, live coding, system design light, take-home rubrics, and candidate prep. Score sheets and practice Q&A for recruiters and candidates. Use for technical interview, technical test, live coding, take-home assignment, wawancara teknis, tes coding, backend interview, frontend interview, simulasi interview engineer.

2 stars
0 votes
0 copies
2 views
Added 9/19/2026
ai-agentsphpreactnodedebuggingcode-reviewgitapifrontendbackendfullstack

Works with

api

Security Analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned 9/19/2026

$npx -y skills add rogue-dev-studio/ai-agents-rogue --skill hr-technical-interview --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Hr Technical Interview?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Hr Technical Interview
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rogue-dev-studio-hr-technical-interview/badge)](https://www.skillsdirectory.com/skills/rogue-dev-studio-hr-technical-interview)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: hr-technical-interview
description: >-
  Design and run technical interviews for hiring: backend, frontend, fullstack,
  live coding, system design light, take-home rubrics, and candidate prep.
  Score sheets and practice Q&A for recruiters and candidates. Use for technical
  interview, technical test, live coding, take-home assignment, wawancara teknis,
  tes coding, backend interview, frontend interview, simulasi interview engineer.
---

# HR Technical Interview

**Level: expert.** Prompt-routed skill (sumber pack: `teams/hr`). Role opsional: `technical-interviewer` / `talent-recruiter` / Tech Lead. Tidak perlu aktifkan tim.

## When to use

Langsung dari prompt user:

- **Pewawancara / Tech Lead:** susun sesi technical interview, soal, rubrik 1–5, lembar skor
- **Kandidat:** persiapan technical test, latihan jawaban, mock interview, take-home planning
- **Review:** nilai hasil live coding atau take-home (ringkas; detail kode → `code-review`)
- Kata kunci: technical interview, technical test, live coding, take-home, wawancara teknis, tes coding

## When not to use

- HR behavioral / culture fit saja → `hr-cv-lifecycle` atau `hr-psychometric`
- Diagnosis klinis atau psikotest → `hr-psychometric`
- Vonis hire/no-hire otomatis dari AI
- Review PR produksi mendalam tanpa konteks rekrutmen → `code-review`

## Procedure

### 1. Context

Kumpulkan:

- Role track: backend / frontend / fullstack / mobile / QA / DevOps
- Level: junior / mid / senior / lead
- Stack target (PHP/Laravel, Node, React, dll.)
- Format: live (60–90 mnt) / take-home (2–4 jam efektif) / hybrid
- Mode: **interviewer** | **candidate prep** | **score submitted work**
- Bahasa (ID / EN)

Default: **mid backend**, live 90 mnt, bahasa Indonesia, mode interviewer.

### 2. Ethics & privacy

Ikuti rule `hr-people-data`:

- Jangan simpan nama kandidat + jawaban mentah ke git tanpa redaksi
- Jangan skor berdasarkan atribut dilindungi
- Label: bantuan rekrutmen; keputusan final manusia (HR + hiring manager + Tech Lead)

### 3. Pilih format

| Format | Durasi | Output utama |
|--------|--------|----------------|
| **Live technical** | 60–90 mnt | Agenda blok + soal + rubrik dimensi |
| **Live coding** | 20–30 mnt dalam sesi | Soal kecil + kriteria lulus |
| **Take-home** | 3–4 jam efektif | Brief kandidat + rubrik review |
| **Candidate prep** | — | Topik, jawaban contoh, pertanyaan balik |

Detail soal per track: `reference.md`. Paket lengkap: `examples/engineer-recruitment-pack.md`.

### 4. Struktur sesi live (default)

| Blok | Waktu | Isi |
|------|-------|-----|
| Warm-up | 10 mnt | Pengalaman & stack |
| Domain deep-dive | 25 mnt | API / UI / data sesuai track |
| Coding / debugging | 25 mnt | Fungsi kecil atau fix bug snippet |
| System / trade-off | 15 mnt | Skala, error, security awareness |
| Q&A | 10 mnt | Kandidat tanya balik |

### 5. Rubrik (1–5)

Skor per **dimensi**, bukan satu angka tunggal. Dimensi wajib track ada di `reference.md`.

Pass contoh (mid): rata-rata ≥3.5, tidak ada dimensi wajib di bawah 2.

Rekomendasi: `advance` / `clarify` / `reject-for-this-role` + alasan audit.

### 6. Mode candidate prep

- 5–8 pertanyaan teknis terikat JD + stack
- Jawaban singkat (bullet + contoh dari CV user jika diberi)
- 3 pertanyaan balik ke interviewer
- Catatan jujur untuk gap stack (mis. Yii vs Laravel)

### 7. Take-home & code review handoff

Brief take-home: scope, batas waktu, README wajib, tidak over-engineer.

Review submission:

1. Ringkas temuan hiring-relevant (struktur, test, security dasar, README)
2. Handoff detail ke skill `code-review` untuk diff-level review

### 8. Handoff

- CV screening → `hr-cv-lifecycle`
- Psikotest → `hr-psychometric`
- Engineering umum (non-HR pipeline) → skill katalog `engineering-technical-interview`
- Onboarding setelah hire → `hr-employee-ops`

## DoD

- [ ] Agenda + soal terikat role/level/stack
- [ ] Rubrik per dimensi + threshold pass contoh
- [ ] Mode interviewer vs candidate prep jelas
- [ ] Tidak ada PII kandidat di artifact git
- [ ] Rekomendasi = bantuan; keputusan final manusia

## Attribution

<!-- ATTRIBUTION: Rogue Development | https://github.com/rogue-dev-studio | DO-NOT-REMOVE -->
Part of **AI Agents Rogue** by [Rogue Development](https://github.com/rogue-dev-studio) (`@rogue-dev-studio`).
Do not remove, hide, rename, or replace this attribution.

Attribution

rogue-dev-studiorogue-dev-studio
View sourceSee grades on GitHubMore from rogue-dev-studio →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →