HR Basics

Hiring & interviews

Hiring works best when the company knows what job it is filling, asks consistent questions, documents the process, and treats candidates like people instead of résumé-shaped mysteries.

Empty candidate chair facing an interview table in a polished HR office at dusk

The interview room

The candidate chair should not be a trap door.

Hiring is the process of defining a role, attracting candidates, evaluating qualifications, choosing a finalist, and making an offer. Interviews are only one part of that process. They are important, but they work best when the company has already done the boring work: clarify the job, define the must-haves, prepare questions, and decide how the hiring team will compare candidates.

Without structure, interviews become vibes, interruptions, favorite-candidate bias, and the manager saying, “I’ll know it when I see it.” That is when the Policy Goblin starts sharpening a pencil.

A good hiring process is not colder. It is clearer. Candidates deserve a process that knows what it is measuring.

Before posting the job

The hiring process should start before the job is advertised. HR and the hiring manager should agree on the actual role, not the fantasy version of the role.

  • Role purpose: what problem this hire is supposed to solve.
  • Core duties: the work the person will actually do most weeks.
  • Required qualifications: the true minimum requirements, not a wish list.
  • Preferred qualifications: useful extras that should not quietly become hidden requirements.
  • Schedule and location: onsite, hybrid, remote, travel, hours, and any physical or operational requirements.
  • Pay range and level: the budget, title, reporting line, and decision authority.
  • Selection criteria: how candidates will be compared before anyone falls in love with one résumé.

What HR should help control

HR usually helps keep the process consistent. That can include job posting language, application flow, interview scheduling, candidate communication, documentation, offer preparation, and handoff into onboarding.

HR also helps remind the hiring team that interviews are not casual conversations with legal consequences hidden inside them. Questions should relate to the job, the candidate’s experience, and the ability to perform the work.

Practical rule: ask every candidate for the same role a consistent core set of questions, then document the job-related reasons for moving forward or not moving forward.

Interview structure

A useful interview does not need to be robotic. It needs a plan. A basic structure can look like this:

  1. Welcome and context: explain the role, the team, and the structure of the conversation.
  2. Experience questions: ask about relevant past work, responsibilities, tools, and results.
  3. Scenario questions: ask how the candidate would handle realistic situations tied to the role.
  4. Role logistics: confirm availability, schedule, location, travel, and other job-related requirements.
  5. Candidate questions: give the candidate time to evaluate the company too.
  6. Next steps: explain the timeline and how follow-up will work.

Questions that usually belong in the room

Good interview questions are connected to the job. They help the company understand skills, judgment, communication, reliability, and fit for the work environment without wandering into personal territory.

  • “Tell us about a project similar to this role.”
  • “What tools or systems have you used for this type of work?”
  • “Describe a time you had to manage competing deadlines.”
  • “How do you communicate when a project is blocked?”
  • “What kind of supervision or team structure helps you do your best work?”
  • “This role requires [job-related requirement]. Are you able to meet that requirement?”

Questions to avoid

Interviewers should avoid questions that pry into protected or personal areas instead of the job. The exact rules vary by location, and employers should get qualified advice for their jurisdiction, but the general idea is simple: keep the conversation tied to the work.

Do not use the interview to ask about personal family plans, medical details, age, religion, political views, national origin, disability status, or other non-job-related personal topics. If a job has a real requirement, ask about the requirement directly, not the personal category behind it.

Important: This page is general workplace education and entertainment. It is not legal advice. Hiring and interview rules vary by jurisdiction and situation.

How to compare candidates

The hiring team should decide how it will evaluate candidates before the interviews begin. Otherwise the loudest opinion in the room often wins.

  • Use the same core criteria for all candidates applying to the same role.
  • Write job-related notes during or immediately after the interview.
  • Separate required qualifications from nice-to-haves so the process does not drift.
  • Watch for vague feedback like “not a culture fit” without specifics.
  • Document the reason for moving a candidate forward or closing them out.

The offer and handoff

Once a finalist is selected, the process should move from interview mode to offer mode. Confirm title, pay, start date, reporting line, work location, schedule, contingencies, and any required forms or checks before sending the offer.

Then onboarding begins. The best hiring process does not end with “Congratulations.” It ends with the new hire knowing where to show up, what to bring, who to meet, and whether the laptop exists.

Simple definition

Hiring is the structured process of finding and selecting a qualified person for a role. Interviews are the job-related conversations used to evaluate whether the candidate and role match.

Next step

After the offer, the owl takes over.

A clean hiring process should hand off into a clean onboarding process: equipment, forms, introductions, expectations, and first-week support.

Onboarding Owl investigating a missing laptop at a new hire desk