# hr-round

Adopt this skill: https://proskills.md/skills/other/nishant-tiwari24-cracked-skills-interview-hr-round

Page: https://proskills.md/skills/other/nishant-tiwari24-cracked-skills-interview-hr-round
This document is the public skill bundle for that page. It contains SKILL.md and every helper file the catalog carries. No login is required.

## File: skills/interview/hr-round/SKILL.md
size: 4663
sha: d833eee1d31b71ddf0e7c9c4ef8813f0f425d60a
upstream: https://github.com/nishant-tiwari24/cracked/blob/main/skills/interview/hr-round/SKILL.md

````text
---
name: hr-round
description: Practise HR and behavioral interview rounds ("tell me about yourself", "why this company", strengths/weaknesses, conflict, failure, leadership, gaps, salary expectations). The agent asks one question at a time, scores each answer on STAR structure, specificity and length, rewrites it in the candidate's own voice using their real facts, and builds a reusable story bank. Use when the user wants HR round prep, behavioral interview practice, managerial round prep, or help answering a specific HR question.
---

# HR round

Most technical candidates lose HR rounds through **vagueness**, not through wrong answers. Your job: turn their real experiences into crisp, specific, honest stories they can reuse across dozens of questions.

## 0. Setup

1. Call the Skill tool with "cracked-profile". Also read `$CRACKED_DIR/stories.md` if it exists, since those stories are reusable.
2. Pick the mode (default **full round**):
   - **Full round**: 6–8 questions mixing the categories in [QUESTIONS.md](QUESTIONS.md), always starting with "Tell me about yourself".
   - **Single question**: the user brings one question and you work on it.
   - **Company mode** (whenever a company is named): call the Skill tool with "company-intel". Build the round from its brief: map questions to the company's **published values or leadership principles** (e.g. one story per principle for companies that interview against them), include "why <Company>" and "why this team" grounded in what the company publicly does, and add reported HR-round themes (relocation, bonds, shifts for service companies; ownership and ambiguity for startups). Score each answer for **fit with the value it targets**, too. Never invent company facts. With no company named, run a general round and don't ask.

## 1. The loop (one question at a time)

Ask the question as an interviewer would, then wait. If they want, they can answer as if speaking. Tell them to aim for 60–120 seconds, which is about 150–250 words.

After each answer, give feedback in this shape:

```
Score: 6/10
✔ <what worked: one line>
✘ <the biggest problem: one line>
STAR check: Situation ✔ · Task ✘ · Action ✔ · Result ✘ (no outcome or number)
Length: ~320 words, about 2.5 min. Cut by a third.
Red flag: <only if present, e.g. blaming a teammate, "my weakness is perfectionism", badmouthing a past employer>
```

Then a **rewritten answer**:
- Use **only facts the candidate gave you**. If a result or number is missing, ask for it, or leave `[result: e.g. reduced build time from X to Y]` as a placeholder. Never invent outcomes.
- Keep their voice: simple, natural spoken English, not corporate filler. It should sound like a confident version of them.
- Keep it to 150–250 words.

Offer a retry ("Want to try it again out loud?") before moving on. In a full round, keep momentum: one retry max per question.

## 2. Special-case questions

- **Tell me about yourself**: present (who you are, what you do) → past (2 highlights tied to the role) → future (why this role). No life story, no reciting the resume, under 90 seconds.
- **Weakness**: a real but non-fatal weakness, plus concrete steps they're taking, plus evidence of progress. Reject clichés.
- **Salary expectations**: in placements, usually defer to the company's standard package. Off-campus, give a researched range and anchor on the role. Never give a number below their real floor.
- **Why should we hire you?**: three proofs tied to the job description, not three adjectives.
- **Gaps, backlogs, low CGPA**: own it in one sentence, pivot to what changed, then to evidence. No over-explaining.
- **Questions for the interviewer**: they must have 2–3 good ones ready. Supply strong options tailored to the role.

## 3. Story bank

The real deliverable. After the session, update `$CRACKED_DIR/stories.md`: each polished story is saved once and mapped to every question type it can answer:

```markdown
## Story: <short name>
Answers: conflict, teamwork, pressure, leadership
Situation: …
Task: …
Action: …
Result: …
Numbers: …
```

Five to seven strong stories cover about 90% of behavioral questions. Tell them which categories are still uncovered.

## 4. Scorecard

Call the Skill tool with "cracked-profile" and log a scorecard. Dimensions: **Structure (STAR), Specificity, Concision, Authenticity, Confidence**. Weak-spot tags include `star-structure`, `vague-results`, `too-long`, `cliches`.

---

*Skill calls:* if your agent has no Skill tool, open the named skill's `SKILL.md` in the cracked skills folder (`core/`, `interview/`, `profile/`, `strategy/`) and follow it instead.
````

## File: skills/interview/hr-round/agents/openai.yaml
size: 112
sha: bfdbaa44564c8e0ef9b427c244d5754dc9ebb14d
upstream: https://github.com/nishant-tiwari24/cracked/blob/main/skills/interview/hr-round/agents/openai.yaml

```text
interface:
  display_name: "HR Round"
  short_description: "Behavioral answers, STAR feedback and a story bank"
```

## File: skills/interview/hr-round/QUESTIONS.md
size: 1794
sha: 2f9ff8aceba94533b5e53379d35d54262cdf2ce9
upstream: https://github.com/nishant-tiwari24/cracked/blob/main/skills/interview/hr-round/QUESTIONS.md

```text
# HR and behavioral question bank

Pick across categories. Variants matter: interviewers rephrase, and the story bank must survive rephrasing.

## Opening
- Tell me about yourself. / Walk me through your resume.
- Why did you choose computer science / engineering?

## Motivation and fit
- Why do you want to work here?
- Why this role?
- Where do you see yourself in 3–5 years?
- What do you know about our company and products?
- Why should we hire you?
- Are you open to relocation / shifts / a service agreement?

## Self-awareness
- What are your strengths? Your biggest weakness?
- What feedback have you received that you disagreed with?
- What's something you taught yourself recently?

## Behavioral (STAR)
- Tell me about a time you had a conflict with a teammate.
- Tell me about a time you failed. What did you learn?
- Describe a time you showed leadership without authority.
- Tell me about a time you worked under a tight deadline.
- Tell me about the most challenging bug or technical problem you solved.
- Describe a time you had to learn something quickly.
- Tell me about a time you disagreed with a decision and what you did.
- Tell me about a time you went beyond what was asked.
- Describe a project you are most proud of.

## Situational
- You're stuck on a task and your lead is unavailable. What do you do?
- A teammate isn't pulling their weight before a deadline. What do you do?
- You realise you shipped a bug to production. Walk me through your next hour.

## Tricky
- Do you have other offers?
- What are your salary expectations?
- Explain the gap in your education/career. / Why the backlog? / Why the low CGPA?
- If you get a better offer after joining, will you leave?
- Do you plan to pursue higher studies?

## Closing
- Do you have any questions for us?
```

## File: README.md
upstream: https://github.com/nishant-tiwari24/cracked/blob/main/README.md

````text
<p>
  <a href="https://github.com/nishant-Tiwari24/cracked">
    <picture>
      <source media="(prefers-color-scheme: dark)" srcset="./assets/logo-dark.svg">
      <source media="(prefers-color-scheme: light)" srcset="./assets/logo-light.svg">
      <img alt="cracked" src="./assets/logo-light.svg" width="369">
    </picture>
  </a>
</p>

# Skills For Getting Hired

[![GitHub stars](https://img.shields.io/github/stars/nishant-Tiwari24/cracked?style=flat&color=c6ff3d&labelColor=0c0c0e&logo=github)](https://github.com/nishant-Tiwari24/cracked/stargazers)
[![Release](https://img.shields.io/github/v/release/nishant-Tiwari24/cracked?color=c6ff3d&labelColor=0c0c0e)](https://github.com/nishant-Tiwari24/cracked/releases)
[![Validate](https://github.com/nishant-Tiwari24/cracked/actions/workflows/validate.yml/badge.svg)](https://github.com/nishant-Tiwari24/cracked/actions/workflows/validate.yml)
[![Skills](https://img.shields.io/badge/skills-19-c6ff3d?labelColor=0c0c0e)](#reference)
[![Companies](https://img.shields.io/badge/companies-470%2B-c6ff3d?labelColor=0c0c0e)](./skills/core/company-intel/SKILL.md)
[![License: MIT](https://img.shields.io/badge/license-MIT-c6ff3d?labelColor=0c0c0e)](LICENSE)

Agent skills for tech placements and coding interviews. Straight from your terminal.

**[cracked-skills.vercel.app](https://cracked-skills.vercel.app)**: browse every skill, and search 470+ companies' most-asked questions.

**cracked** turns Claude Code, Codex, Cursor, GitHub Copilot or Gemini CLI into your **interviewer, coach and career team**: company-wise mock DSA interviews for Google, Amazon, Microsoft, Flipkart and 470+ more; timed online assessments graded against hidden test cases; system design and HR rounds; a brutal resume roast with an ATS score; and a prep plan built from your real weak spots.

**Built for** final-year and pre-final-year CS students preparing for campus placements, new grads applying off-campus, and engineers switching jobs.

<p align="center">
  <img src="./assets/demos/mock-interview.svg" alt="Example cracked mock interview: a dynamic programming problem where the interviewer answers a greedy idea with a counterexample, the code is tested against 20,000 random inputs, a follow-up is asked, and the round ends with a Hire 8/10 scorecard." width="900">
</p>

Preparing for tech interviews is hard. Sheets, courses and grind lists try to help by handing you a list of 450 problems. But a list doesn't interview you, doesn't tell you *why* you'd be rejected, and has no idea which company you're walking into on Monday.

These skills are small, composable and honest. They work with any model. They run your code instead of guessing about it. They never invent a single fact about you. Hack around with them. Make them your own.

## Installation (30-second setup)

A plugin updates itself. [skills.sh](https://skills.sh) copies editable files into your setup, and you update them by hand. Pick one per agent, because installing both gives you every skill twice.

### 1. Get the skills

<details>
<summary><strong>Claude Code</strong></summary>

```bash
claude plugin marketplace add nishant-Tiwari24/cracked
claude plugin install cracked@cracked
```

Updates itself by default.

</details>

<details>
<summary><strong>Codex</strong></summary>

```bash
codex plugin marketplace add nishant-Tiwari24/cracked
codex plugin add cracked@cracked
```

</details>

<details>
<summary><strong>Any other agent, or editable files</strong> (manual updates)</summary>

```bash
npx skills@latest add nishant-Tiwari24/cracked -a <agent>  # cursor, copilot, gemini, opencode, windsurf, amp…; omit -a to choose
```

When the installer asks which skills to take, include `setup-cracked` and `cracked-profile`. To update, run `npx skills@latest update`.

</details>

<details>
<summary><strong>Using cracked in agents without a Skill tool</strong></summary>

Skills hand off to each other ("Call the Skill tool with `company-intel`"). Claude Code and Codex do this natively. In other agents, the skills tell the model to open the named skill's `SKILL.md` and follow it, so install the whole pack, not single skills, and always include `cracked-profile`.

</details>

### 2. Run `/setup-cracked`

Run it once. It will:

- Ask up to six short questions (status, target roles, target companies, language, DSA level, deadline) and save your profile
- Build a prep brief for each target company
- Check your machine for the tools some skills use (Python, SQLite, `gh`, text-to-speech)
- Suggest your first three sessions

### 3. Bam, you're ready to go.

```text
> roast my resume ~/Downloads/resume.pdf
> mock interview for Google, medium, voice mode
> /oa-sim Amazon
```

## Why These Skills Exist

I built these skills to fix the ways interview prep fails the people doing it.

### #1: Practice Doesn't Feel Like The Real Thing

> "Everybody has a plan until they get punched in the mouth."
>
> Mike Tyson

**The Problem**: You solve a problem alone, with the editorial one click away and no clock. Then, in the real round, someone withholds the constraints, asks "can you do better?", and watches you go quiet for six minutes.

**The Fix** is an interviewer that behaves like one:

- [`/mock-interview`](./skills/interview/mock-interview/SKILL.md): a timed DSA round. It withholds constraints so you learn to ask, gives a 4-rung hint ladder instead of answers, **runs your code against hidden edge cases**, monitors how you react at every phase, and checks that the work is yours. Turn on **voice mode** to explain out loud, the skill most people never practise.
- [`/oa-sim`](./skills/interview/oa-sim/SKILL.md): a full online assessment as real files in your own editor, graded AC / WA / TLE against hidden tests whose expected outputs come from an **executed** reference solution.
- [`/system-design-mock`](./skills/interview/system-design-mock/SKILL.md) and [`/hr-round`](./skills/interview/hr-round/SKILL.md): the other rounds, with real pushback.

<img src="./assets/demos/oa-sim.svg" alt="Example /oa-sim run: a Google-style test graded against hidden tests, with failure patterns explained and a cutoff verdict." width="900">

### #2: You're Preparing For "An Interview", Not *The* Interview

> "If you know the enemy and know yourself, you need not fear the result of a hundred battles."
>
> Sun Tzu, The Art of War

**The Problem**: Google, Amazon, a mass recruiter and a seed-stage startup run completely different interviews. Generic prep treats them all the same.

**The Fix** is **company mode**. Name a company anywhere ("Flipkart OA", "HR round for Amazon") and every skill adapts.

- [`/company-intel`](./skills/core/company-intel/SKILL.md) builds a cached brief: reported rounds and OA format, **the company's most frequently reported LeetCode questions** (30-day, 3-month, 6-month and all-time windows, 470+ companies), published values, and the resume bar, each with its source.
- [`/resume-blueprint`](./skills/profile/resume-blueprint/SKILL.md) tells you what *your* resume should contain for that company.

No company named? Everything still works, in a generic product-company style.

<img src="./assets/demos/company-intel.svg" alt="Real /company-intel output: Amazon's topic mix and most reported medium and hard questions from the last 30 days." width="900">

### #3: Your Resume Says Nothing

> "Be so good they can't ignore you."
>
> Steve Martin

**The Problem**: "Worked on a website." "Responsible for backend." "Hardworking team player." Recruiters give it six seconds, and those bullets spend them saying nothing.

**The Fix**:

- [`/roast-my-resume`](./skills/profile/roast-my-resume/SKILL.md): brutal, but **calibrated to your level and market**, with an ATS score out of 100 and its breakdown. Every jab comes with a fix, and rewrites **never invent a metric**: missing numbers become `[N]`, and you get asked for the real ones.
- [`/jd-match`](./skills/profile/jd-match/SKILL.md): a transparent match score against a real job descr
````
