ForHosting KIT · Text & AI

Interview questions

Give the endpoint a role and the skills or seniority you're hiring for, and it returns a set of interview questions paired with a short note on what a good answer should reveal. It's built for hiring managers and recruiting tools that need more than a generic list of "tell me about a time when."

● StablePer request + per batch$0.003

Run — $0.003 + $0.0135/batch How it works & API

Use it from WebAPIEmailApp soonTelegram soon

Run it online

Run this on our servers with your account. Free tools run in your browser; this one bills your KIT balance per the price above.

The problem with stock question banks

Search for interview questions online and you get the same fifty prompts recycled across every job site, useful mainly for warming up but not for actually distinguishing candidates for a specific role. A senior backend engineer and a junior one need different questions entirely, and a support-lead interview should probe different judgment than a data-analyst one. This endpoint generates a set scoped to the role and level you specify, and — more importantly — attaches a short note per question describing what to listen for in the answer, since a good question without an evaluation cue just shifts the guesswork onto the interviewer.

Calling the endpoint

POST /text/interview-questions with the role, the level or seniority, and any specific skills or focus areas you want covered. The task runs asynchronously: you get a task_id back immediately and the finished question set is delivered by signed webhook or a signed link good for 24 hours, so there's no blocking call to manage while a hiring pipeline is under load.

Why 'what to listen for' matters more than the question

Structured interviewing became standard practice in hiring precisely because unstructured, free-form questions produce inconsistent evaluations between interviewers. The fix has always been pairing each question with a rubric of what a strong, weak, or evasive answer looks like — that's the part hiring guides recommend and the part most generators skip because it's the harder half to write. We generate both halves together so the question is actually usable in a real interview loop, not just a talking point.

Fitting it into a hiring workflow

This is built for ATS platforms, recruiting agencies running multiple simultaneous searches, and hiring-manager tools that assemble a question bank per open role automatically. Because it's async with webhook delivery, a platform can trigger generation the moment a job requisition is created and have the question set waiting before the first candidate is scheduled. Billing is a flat per-request fee plus a per-batch charge, and it's only applied to a completed batch — retries on failure are automatic and free.

What you can do with it

New requisition, instant question bank

An ATS triggers generation the moment a hiring manager opens a requisition, so interviewers have a tailored set before the first screen is scheduled.

Recruiting agency running parallel searches

An agency staffing five different roles at once generates a distinct, level-appropriate question set for each without writing any of them by hand.

Panel interview calibration

A hiring team uses the 'what to listen for' notes to align multiple interviewers on what a strong answer looks like before the loop starts.

Internal mobility screening

An HR platform generates lateral-move interview questions focused on transferable skills rather than reusing the external hiring question set.

FAQ

Is the interview question generator API free to use?

There's no free tier — free tiers get abused and slow everyone down. Access runs on a prepaid ForHosting KIT balance: top up from $10.00 (it never expires) and each request is charged at its published price, so a call with no balance returns HTTP 402. No subscription, no tokens, no invented credits, and a failed task is never charged.

Do the questions come with expected answers?

Each question includes a short note on what to listen for in a strong answer, not a scripted correct answer — interviews aren't multiple choice.

Can I set the seniority level?

Yes, send the level or seniority alongside the role so the questions match a junior, mid, or senior bar rather than a generic one.

How many questions come back per batch?

The batch is sized to the role and focus areas you request rather than a fixed count, since a narrow technical role needs a different set than a broad generalist one.

How do I retrieve the generated set?

Via signed webhook, recommended for integration into a hiring pipeline, or a signed link valid for 24 hours if you prefer to fetch it manually.

Can I generate question sets in bulk for many roles?

Yes — each POST to /text/interview-questions is an independent async task, so a recruiting agency can fire one per open requisition in parallel.

Are the questions behavioral, technical, or both?

They're scoped to what you specify in the request; describe the focus areas and level you need and the set is generated around them.

What happens to the role details I send?

They're deleted after the retention window and never used for training — the endpoint's only job is producing the question set.

For developers — API access

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

API endpoint

POSThttps://api.kit.forhosting.com/text/interview-questions

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, and soon from our app, email and Telegram.

Call it from your stack

curl -X POST https://api.kit.forhosting.com/text/interview-questions \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d &#39;{"input":"…"}'

const res = await fetch("https://api.kit.forhosting.com/text/interview-questions", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.KIT_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "input": "…"
  })
});
const { task_id } = await res.json();

import os, requests

res = requests.post(
    "https://api.kit.forhosting.com/text/interview-questions",
    headers={"Authorization": f"Bearer {os.environ[&#39;KIT_KEY']}"},
    json={
    "input": "…"
},
)
task_id = res.json()["task_id"]

<?php
$res = file_get_contents("https://api.kit.forhosting.com/text/interview-questions", false, stream_context_create([
  "http" => [
    "method"  => "POST",
    "header"  => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
    "content" => &#39;{"input":"…"}',
  ],
]));
$task = json_decode($res, true);

body := bytes.NewBufferString(`{"input":"…"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/text/interview-questions", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)

Example request

{
  "input": "…"
}

Example response

{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "text.interview_questions",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Pricing

Per request$0.003

Per batch$0.0135

Published price — no tokens, no invented credits. A failed task is never charged.

Limits

max_tokens 20000

Errors

HTTP	Code	Meaning
`401`	`unauthorized`	Missing or invalid API key.
`402`	`insufficient_balance`	Your balance doesn't cover the task price.
`404`	`unknown_type`	That task type doesn't exist.
`429`	`rate_limited`	Too many requests. Use the webhook instead of polling.
`422`	`task_failed`	The task failed after 3 retries. You are never charged for it.

Read the full KIT documentation →