Interviews
Zimac supports both sides of interview preparation: use your own resume for grounded candidate coaching in chat, or use the Interviews studio to run a hiring conversation end to end with a structured plan, live per-question notes, and a formalized verdict.
Coach the candidate; structure the interviewer. Resume-led prep builds a detailed practice pack without inventing experience. The Studio’s hiring workflow starts from a ready-to-run plan, captures evidence question by question, and helps turn those notes into a clear verdict.
☷ Structured plans
A ready-to-run set of questions tailored to the role and candidate.
☷ Resume-led prep
Technical deep dives, project defense, likely questions, and practice priorities.
☷ Live note-taking
Rate and jot notes per question as the interview happens.
☷ A clear verdict
Turn your notes into a formalized recommendation you can compare.
☷ All on file
Every plan, its notes, and its verdict kept together for later.
What it is#
Interviews is the studio for planning, conducting and closing out a candidate interview. It exists to make interviews consistent — the same structure, captured the same way — so that when it's time to decide, you're comparing real, per-question evidence rather than half-remembered impressions.
Prepare from your resume#
Attach your own resume or CV as a document or image and send /interview-prep, optionally followed by a role, company, level, or job-description context. A file clearly named as a resume or CV can be sent without any typed prompt. If no target is supplied, Zimac labels a best-effort assumption from the resume and still prepares the pack.
The result covers your candidate story, every material technical claim, deep dives on the relevant systems and technologies, project-defense narratives, likely opening and follow-up questions, speakable answer outlines, weak-answer traps, a risk and gap audit, and a prioritized mock-interview plan. Zimac labels what the resume establishes, what is technical inference, and what is suggested phrasing; missing personal details stay unknown or use placeholders such as [your actual metric].
Building a plan#
Ask Joy to prep an interview — for a role, a team, a candidate — and she compiles a structured, ready-to-run plan and hands it over as an interactive card with a "Conduct interview" button. You walk in with the questions already laid out, so you can focus on the conversation instead of improvising the structure.
Conducting the interview#
Hit Conduct and the plan becomes a live note-taking surface. As you work through it you capture, per question, a rating and your notes — and you can skip a question you didn't get to — plus overall notes at the end. Everything is recorded against the plan, so the raw material of your judgment is preserved exactly as you took it down.
The verdict#
When the interview's done, the studio reads back everything you captured and helps you formalize the feedback into a hiring verdict — a clear recommendation, rendered as a verdict card. Because it's built from your per-question ratings and notes, the decision is grounded in what you observed, and it sits on file next to the plan for the debrief.
Your interviews#
The studio keeps your interviews together — the candidate and role, whether each has been conducted, and any recorded verdict — so you can see the pipeline at a glance and reopen any one to review the notes behind a decision.