Skip to content

Interviews & feedback

Structured interviews, from the invite to the final scorecard.

Plan panels around the competencies a role needs, let candidates book from real availability, and give interviewers a focused workspace for preparation and structured feedback.

hireiq / interviewer / today

Sample data

Today

  • 10:00

    Technical interview

    Ananya Rao · Senior Backend Engineer

    Starts in 25 min
  • 14:30

    System design

    Daniel Kim · Senior Backend Engineer

    Scheduled
  • Yesterday

    Coding review

    Meera Iyer · Data Analyst

    Feedback due

Scorecard · Coding review

  • API design · 30%

  • Data modelling · 30%

  • Communication · 20%

Illustration of the interviewer workspace with today’s schedule and a rubric scorecard in progress.

The problem

Unstructured interviews produce opinions, not evidence.

When every interviewer asks different questions and writes free-form notes, hiring discussions turn into recollection. HireIQ ties each interview to the competencies it is meant to cover and captures feedback against a rubric.

How it works

The workflow, step by step.

  1. 1

    Plan the panel

    Interview blueprints map the role’s competencies to interview stages, and coverage flags required items that no interview, assessment, or resume evidence addresses.

  2. 2

    Let candidates book

    Candidates choose a slot from a secure scheduling link. With Google Calendar connected, proposed slots reflect interviewers’ free and busy time.

  3. 3

    Prepare with context

    Interviewers see only the requirements assigned to them, with the candidate’s evidence, assessment results, and the rubric they will score.

  4. 4

    Submit structured feedback

    Scorecards capture ratings per criterion and a recommendation, so panels can compare like with like.

Capabilities

What’s included in interviews & feedback.

  • Calendar-aware scheduling

    Google Calendar connections propose open slots and create the interview event with a Meet link. Microsoft calendar connections receive the interview event.

  • Interview reminders

    Candidates and interviewers receive reminders before the interview, so nobody needs to chase a calendar invite.

  • Rubric scorecards

    Each score records the criterion, its weight, and a 1–5 rating as a snapshot, so later rubric edits never rewrite feedback already given.

  • Interviewer calibration

    Administrators compare each interviewer’s average scores with the platform average on shared competencies to spot drift. Calibration never feeds candidate ranking.

  • Published interviewer profiles

    Interviewers maintain a profile that clients and candidates can read before they meet, including public GitHub activity where provided.

  • Interviewer training

    Keep training material and expectations for structured interviewing in the workspace interviewers already use.

Controls and safeguards

  • Interviewers only see requirements and candidates assigned to them.
  • Interviewers never see billing, team management, or administrative settings.
  • Calendar access uses the scopes the interviewer grants, and HireIQ asks for a reconnect when they change.
  • Scorecards are attributed to their author in the audit trail.

Who it helps

Interviewers
Open the day’s schedule, review context, and submit a scorecard without hunting for links.
Recruiters
Know which interviews are booked and which feedback is still outstanding.
Hiring managers
Compare structured feedback across the panel before deciding.

FAQ

Interviews & feedback: common questions

Do candidates need an account to book an interview?

No. Candidates use a secure, single-purpose link to choose a time, take an assessment, or check their application status.

Which calendars are supported?

Google Calendar can be connected for availability and creates the interview event with a Meet link. Microsoft calendars can be connected to receive interview events.

Can interviewers see other candidates?

No. The interviewer workspace is limited to the requirements an administrator assigns, and access is enforced on the server, not only in the interface.

Bring structure to your next requirement.

Create a workspace, post your first role, and see every applicant’s evidence in one pipeline.