Prepare interview questions from a resume
prepare_interview_questionsBuilds the grounding of a job interview prep for a project, program or product manager, TPM, PMO lead or business analyst from their resume text and, if they have it, the job posting. Use it when someone shares a resume (pasted or attached) before an interview, or asks what a hiring manager will ask them. Returns data read by fixed rules written by practitioners: every resume line word for word with its number; each requirement of the posting with a call (covered, partial, not_found, not_checked) and every resume line found for it; the main requirement; inconsistencies of dates and figures; up to 10 likely questions, each with what the answer must prove and an id (the ids of requirement, resume line, behavioral and industry questions go to check_interview_answer); and a plan by the days left to interview_date (by window when there is no date). checks says what each field means; not_found means the rules found no line, not that the person lacks the experience. Optional: interview_stage and interviewer_title shift the mix of questions; interviewer_profile is read only for subject words; company adds questions from what some large US employers publish, with source links; draft checks the quotes and gap calls of a prep draft against the resume. For practice before an interview, not during it; it does not write answers. English text; contact details are removed first; nothing sent with a call is stored. handoff_code reads the resume and the job posting the person saved on the PM Career Desk site or in its Chrome extension; that code holds them, with personal details removed and encrypted, for up to 2 hours.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "prepare_interview_questions"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | The language the person writes in, as a code such as es, fr or ru; empty or en for English. The result names this language; findings are written in English. | |
| role | No | Optional. One of project-manager, program-manager, technical-program-manager, product-manager, scrum-master, pmo, it-manager, business-analyst, delivery-manager; a title as written (for example Senior Program Manager) is also read. Empty when not sure. | |
| draft | No | Optional. A prep draft written from a result of this tool for the same resume and posting, up to 20000 characters. The result is then the check of the draft: its quotes that are not in the resume word for word, its gap calls on requirements where the rules found resume lines, its covered calls where they found none, and its figures not in the resume or the posting. The draft is read in memory only and not stored. | |
| entry | No | Optional. Where the person started: directory, site, udemy or other. Counted only; with handoff_code the code's own entry is used. | |
| company | No | Optional. The employer's name as written in the posting. | |
| industry | No | Optional. The employer's industry, one of healthcare-life-sciences, financial-services, software-saas, government-public-sector, consulting-services, retail-supply-chain, manufacturing-industrial, energy-utilities; a plain name such as healthcare or banking is also read. Adds questions written for that industry. Empty when not sure. | |
| job_posting | No | The full text of the job posting, as the person gave it. Optional; with it the result adds the requirements, the gaps and questions about them. | |
| resume_text | No | The resume as plain text, copied in full from what the person pasted or from the text of the file they attached. At least the summary and the experience section. May be empty when handoff_code is given. | |
| handoff_code | No | Optional. A handoff code PCD-XXXX-XXXX-XXXX-XXXX that the person made on the PM Career Desk site or in its Chrome extension. The resume and the job posting saved under it are read instead of resume_text and job_posting. A code works for 2 hours, and for 30 minutes after its first read. | |
| interview_date | No | Optional. The interview date as YYYY-MM-DD. | |
| resume_outline | No | Optional structure of the resume: roles with title, company, dates and bullets; summary; skills; certifications; education. Every line must appear word for word in resume_text; lines that do not are left out and counted in the result. Without it the plain text is read. | |
| interview_stage | No | Optional. The interview stage: recruiter_screen, hiring_manager, panel, company_round or unknown. Shifts the mix of intro, requirement, resume line and behavioral questions. | |
| job_requirements | No | Optional. The requirement lines of the job posting, each word for word from job_posting; lines that are not are left out and counted in the result. Without them the requirements are read from job_posting. | |
| interviewer_title | No | Optional. The interviewer's job title as the person gave it, up to 120 characters, for example Director of Engineering. Read for the function and level only; no name is needed. | |
| interviewer_profile | No | Optional. The text of the interviewer's profile that the person pasted, up to 3000 characters. Contact details are removed and only subject words of a fixed list are kept to choose questions; the text is not returned and not stored. |