Start from the role, not a generic list
The fastest way to write a weak interview is to open a "top 50 questions" list and pick. Those questions were written for someone else's role. Start instead from the role brief: what does this person do day to day, and what does good vs. weak look like for that work?
InterviewQ takes the role, seniority, focus, and count as inputs so the set is built around the actual job rather than a generic template.
Split behavioral and technical on purpose
Decide the mix before you write. Behavioral questions ("Tell me about a conflict you resolved") show how someone works; technical questions ("How would you approach X") show how they reason about the craft.
A Mixed set balances both. A focused set leans into the dimension that matters most for the hire. The split should reflect the role, not habit.
Write the rubric before you need it
For each question, note what a strong answer includes — one line is enough. "Names the conflict, the action, and the outcome" is a rubric. It keeps scoring consistent across candidates and interviewers, and it stops the panel from grading on vibes.
Tune the level to seniority
The same question reads differently at Junior vs. Lead. A system-design question for a Lead should test trade-offs; for a Junior, it should test fundamentals. InterviewQ tunes phrasing to the level you select so the question meets the candidate where they are.
Review for bias and relevance
Before you send the invite, scan the set for phrasing that could surface protected-class bias or simply miss the role. Bias-aware framing and a relevance review are preparation steps, not a compliance guarantee — the human still owns the final call.