# Block F Interview Plan: 6 Essential Components in Career-Ops Reports

> Discover the 6 essential components of the Block F Interview Plan for career-ops reports. Get STAR stories, timelines, Q&A, and more for your interview playbook.

- Repository: [Santiago Fernández de Valderrama/career-ops](https://github.com/santifer/career-ops)
- Tags: how-to-guide
- Published: 2026-08-22

---

**Block F generates a comprehensive Interview Plan containing STAR stories, interview timelines, key talking points, preparation checklists, suggested Q&A pairs, and logistics to create a ready-to-use interview playbook.**

The **santifer/career-ops** repository structures career optimization reports into modular blocks, with Block F dedicated entirely to interview preparation. This block transforms raw job posting data from Block B and the candidate's story bank into a structured **Block F Interview Plan** that candidates can print, save, or reference during interviews.

## What Is Included in the Block F Interview Plan?

When a report is generated, Block F supplies every piece of information needed to walk into an interview prepared and confident. The plan contains six core components:

- **STAR Stories** — A curated list of the candidate’s strongest STAR (Situation-Task-Action-Result) anecdotes mapped directly to the role’s most important requirements.

- **Interview Timeline** — A step-by-step schedule covering pre-interview research, day-of preparation, and post-interview follow-up to keep the candidate on track.

- **Key Talking Points** — Bullet-point summaries of the most compelling proof-points from Block B that should be woven into interview answers.

- **Preparation Checklist** — Practical action items such as reviewing the company’s latest product release, practicing the top three competency questions, and preparing questions for the recruiter.

- **Suggested Question and Answer Pairs** — Sample answers for common interview prompts, each anchored to a STAR story so candidates can rehearse narrative flow.

- **Logistics and Contacts** — Reminders of interview format (virtual vs. onsite), interviewers’ names and titles when known, and any required technical setup.

Together, these sections turn raw data into a ready-to-use interview playbook.

## Where Block F Is Defined in the Source Code

The structure and validation of the Interview Plan are implemented across several key files in the repository:

- In [`modes/oferta.md`](https://github.com/santifer/career-ops/blob/main/modes/oferta.md) at line 209, the heading `## Block F — Interview Plan` defines the section structure and surrounding prose that appears in generated reports.

- The unit test suite in `web/tests/lib/report-sections.test.mjs` (lines 72-125) verifies that Block F is correctly parsed and identified as "Interview Plan" during the report building process.

- [`batch/batch-prompt.md`](https://github.com/santifer/career-ops/blob/main/batch/batch-prompt.md) at line 205 includes the Block F outline for batch processing templates, ensuring consistency across automated report generation.

- `gemini-eval.mjs` at line 180 contains regex patterns used to locate and evaluate Block F sections when assessing report quality.

## Generating the Interview Plan Programmatically

Developers can generate the Block F Interview Plan programmatically using the report builder library or command-line interface.

To render Block F within a report:

```javascript
// Example: Rendering Block F in a report
import { renderBlock } from './lib/report-builder.mjs';

const interviewPlan = renderBlock('F', {
  starStories: getStarStories(),
  timeline: buildTimeline(),
  talkingPoints: extractProofPoints(),
});
console.log(interviewPlan);

```

To generate a full report including Block F via CLI:

```bash

# Command-line: Generate a full report that includes Block F

node generate-report.mjs --mode oferta --output report.md

# The resulting markdown will contain a section titled "## Block F — Interview Plan"

```

The resulting data structure follows this JSON schema:

```json
{
  "block": "F",
  "content": {
    "starStories": ["..."],
    "timeline": ["Day-1: Research", "Day-2: Mock interview"],
    "talkingPoints": ["..."]
  }
}

```

## Summary

- Block F produces a comprehensive **Interview Plan** with six core components designed to prepare candidates for interviews.
- The plan integrates **STAR stories** from the candidate's history with job-specific requirements from Block B.
- Source code defines Block F in [`modes/oferta.md`](https://github.com/santifer/career-ops/blob/main/modes/oferta.md) and validates it in `web/tests/lib/report-sections.test.mjs`.
- Developers can generate the plan programmatically using `renderBlock('F', ...)` or CLI commands.

## Frequently Asked Questions

### What does Block F stand for in career-ops reports?

Block F refers to the Interview Plan section, which is the sixth modular block (F) in the report generation system. According to the source code in [`modes/oferta.md`](https://github.com/santifer/career-ops/blob/main/modes/oferta.md), this block is explicitly titled `## Block F — Interview Plan` and serves as the definitive interview preparation module.

### How does the Block F Interview Plan use STAR stories?

The plan maps curated STAR (Situation-Task-Action-Result) anecdotes from the candidate's story bank directly to the role's most important requirements. These stories provide concrete, structured examples that candidates can use when answering behavioral interview questions.

### Can the Block F Interview Plan be generated via command line?

Yes. You can generate a full report including Block F using the command `node generate-report.mjs --mode oferta --output report.md`. This produces a markdown file containing the Interview Plan section titled `## Block F — Interview Plan` as defined in the oferta mode template.

### Where is the Block F Interview Plan validated in the codebase?

Unit tests in `web/tests/lib/report-sections.test.mjs` (lines 72-125) verify that Block F is correctly identified as "Interview Plan" during parsing. Additionally, `gemini-eval.mjs` at line 180 uses regex patterns to validate the presence and structure of Block F sections when evaluating report quality.