# Hiring content studio for job descriptions and interview kits

> Turn a bare Greenhouse role into a polished job description and a full interview kit your panel can actually use, reviewed by a recruiter before anything ships.

- Workflow type: app
- Services: Greenhouse, AI Generation, Google Docs, Google Sheets
- Categories: HR & People
- Published: 2026-08-14

## What it does

- Lists your open roles in one place and shows at a glance which ones already have an approved interview kit and which are still bare
- Drafts a rewritten job description plus a complete interview kit: the competencies to test, the questions to ask at each stage, and a scoring rubric
- Holds every role to the same house competency framework and tone of voice, so hiring content reads consistently across departments instead of depending on whichever hiring manager wrote it
- Lets recruiters edit any section by hand and redo just the parts they do not like, then publishes the approved kit as a shareable doc and logs it to a tracking sheet

## What you'll need

- A Greenhouse account, with read access to your jobs and job posts. This app never edits your live postings
- A Google account for the published interview kits and the tracking spreadsheet
- Your house competency framework and tone of voice guide, pasted into the app once so every draft follows it
- A tracking spreadsheet where each approved kit gets logged

## Prompt

Build me a hiring content studio: an internal app my recruiters open to turn a bare Greenhouse job into a polished job description and a consistent interview kit, so the quality of a role's hiring content does not depend on whichever hiring manager happened to write it. Greenhouse stays strictly read only in this app. The value is producing reviewed hiring content, not silently editing live postings, so no handler should ever write back to Greenhouse.

Design the whole app around a review queue rather than one shot generation. The recruiter's job is to review and approve, not to write from scratch, and the home view should make it obvious what still needs attention.

Home view, the role queue. Use Greenhouse List Jobs and List Job Posts to show every open role with its department and hiring manager, and List Job Openings to show how many seats are open on each. Each row carries a status badge: Bare when there is no kit yet, Draft when generation has run, In review when a recruiter has started editing, and Approved when it has been published. Sort so Bare and Draft roles come first, and give me filters by department and by status. The point of this screen is that I can see in one glance which roles already have an approved kit and which are still bare.

Role detail view. Opening a role calls Greenhouse Get Job Post to pull the full posting text and the application questions, and shows that source material alongside the draft so the recruiter can compare what exists against what the app proposes. Nothing on this screen edits Greenhouse.

Generation. A Generate a draft action calls AI Generation Generate Completion to produce two things: a rewritten job description, and an interview kit made up of the competencies to assess, stage by stage interview questions mapped to those competencies, and a scoring rubric for each competency. Every generation call must include the house competency framework and the tone guide stored in the app, along with the role's actual posting text and application questions, so output stays consistent across departments while the content stays specific to the role.

Section level editing and regeneration, which is the most important interaction in the app. Store the draft as distinct sections, for example job description, competencies, each interview stage, and the scoring rubric. Every section is editable inline and saves on its own. Every section also has its own regenerate button that reruns Generate Completion for just that section, with an optional instruction box so the recruiter can say something like make this less corporate or add a systems design question. Regenerating one section must never overwrite the recruiter's edits to the other sections, and there should be no need to reroll the entire document to fix one part of it.

Approval and publishing. When a recruiter approves a kit, call Google Docs Create Document to make a document titled after the role, then Google Docs Batch Update Document to write the formatted content for the hiring panel: the job description, the competencies, the questions grouped under each interview stage, and the scoring rubric, using real headings so the panel can navigate it. Save the resulting document link on the role, show it on the role detail view, and use Google Docs Get Document if you need to read a published kit back. Then call Google Sheets Append Values to add a row to a tracking sheet with the date, role title, department, the recruiter who approved it, and the document link.

Settings view. A place to store and edit the house competency framework and the tone of voice guide, since these are what keep output consistent across departments. Changes here apply to every future draft and regeneration without touching kits that are already approved.

Persistence. Store kits against the Greenhouse job id so they survive reloads and are shared across the recruiting team rather than living in one person's session. Keep the per section content, the current status, who approved a kit and when, and the published document link.

## How to customize

- Edit the competency framework and tone guide at any time. Every new draft picks up the change, so you can steer house style without touching individual roles
- Change the interview stages a kit is built around, for example swapping a take home exercise for a live working session, or adding a founder round for senior roles
- Decide what gets logged to the tracking sheet and who on the team is allowed to mark a kit approved

## FAQ

### Will this change our live job postings in Greenhouse?

No. The app only reads from Greenhouse. It pulls your open roles, the posting text, and the application questions, and nothing is ever written back. The polished job description lands in a Google Doc for your team to review and use as they see fit.

### Can we edit what the AI writes?

Yes, and that is the point. Every section is editable inline, and each one has its own regenerate button, so if you like the competencies but hate the phone screen questions you redo just that section instead of rerolling the whole document and losing your edits.

### Will every department end up with the same generic kit?

No. Each draft is built from that specific role's posting text and application questions, then shaped by your house competency framework and tone guide. The framework keeps the structure and standards consistent while the content stays specific to the role.

### Where does the finished interview kit end up?

When a recruiter approves a kit, the app creates a shareable Google Doc formatted for the hiring panel, with the job description, competencies, stage by stage questions, and the scoring rubric. It also adds a row to your tracking spreadsheet so you can see which roles have been through the process.

### What happens with roles that have no job post written yet?

They show up on the home view flagged as bare, which is usually exactly the list you want to work down. You can still generate a kit from the role's basic details, and the app is designed so bare roles surface first rather than getting lost.

Use this prompt in General Input: https://www.generalinput.com/prompts/hiring-content-studio-for-job-descriptions-and-interview-kits