# HireAssist QA test # Write the Scorecard Before the Interview, or You'll Hire a Clone Source: https://hireassist.org/blog/the-scorecard-you-agreed-before-the-interview The loudest interviewer in the room hired his clone, and the scorecard was blank when the candidate walked in. I have watched this enough times that I do not treat it as a personality flaw. I treat it as what happens when the only shared document is the résumé. He liked the candidate because the candidate talked the way he talks. Fast, certain, a little amused by the current team. The other two interviewers had doubts. They mentioned them. He had more words. The offer went out on Friday. Six months later the team had two people who dismissed the same kinds of problems, and nobody who would sit in the boring parts of the job. A scorecard you agree before the interview is the brake. Not a culture speech. Not a reminder to "stay objective." A page that exists before anyone is charming. ## Agree it while nobody is in the waiting room Do this in a half hour, before the first screen, with the people who will interview. Four lines. What this person must be able to do in the first six months. What a weak answer sounds like, in a sentence you would actually say out loud. What you will not hire for, even if you enjoy the conversation. Write the "will not" line. It is the one that saves you. "We will not hire someone who cannot explain a decision they got wrong." Or, for a support lead, "We will not hire someone who has not done a messy handoff." The loud interviewer can still like a candidate. He cannot pretend the line was not there. If you write the scorecard after a favourite emerges, you will describe the favourite. I have seen a "must have" appear that matched one person's last job and nobody else's. That is not a standard. That is a costume. ## Same page, filled before you talk to each other Each interviewer scores before the debrief, not during it. During it, you will bargain. The loud voice sets the anchor. Everyone else edits toward him because disagreement feels like a scene. A score is not a vibe from 1 to 5 on "overall." It is a mark on each of the four lines, plus one sentence of what you heard. "Said the migration slipped because the other team was political. Could not name what he would do differently." That sentence is harder to steamroll than "I wasn't sure." Then the debrief has a shape. Where do we disagree on the lines? If the loud interviewer loved the candidate and the lines say no, the lines win. If you are going to override a line, say so in writing and say why. "We are ignoring the handoff line because we will pair them with Asha for a quarter." Sometimes that is a real reason. Often, saying it out loud kills it. Good. ## Clones are a hiring outcome, not a mystery People hire people who feel easy. Easy often means familiar. Familiar, in a small team, means you already have this person. The job was supposed to add the skill you lack, and instead you added a second opinion you already hold. The scorecard is how you hire the person who is worse at performing the interview and better at the work. They will lose a charisma contest. They should not lose a page you wrote when nobody was performing. AI can draft the first four lines from the job post so you are not inventing criteria at midnight. It can also lay the interview notes against those lines so you see the gap. It cannot attend the pre-meeting and force the argument. That half hour is the actual control. Skip it and the tool just helps you document the clone faster. ## If you only do one thing on the next role Book thirty minutes with every interviewer before any candidate is scheduled. Leave with four lines and one "will not." Put it where the notes must go. Refuse to debrief without the marks filled in. You will still have a loud voice in the room. You want that voice. You do not want it to be the process. --- # Beyond the Resume: How AI Helps You Make Better Hiring Decisions, Not Just Faster Ones Source: https://hireassist.org/blog/beyond-the-resume-how-ai-helps-you-make-better-hiring-decisions Speed is the easy sell. A founder I spoke with in Bengaluru had cut resume review from two days to twenty minutes and was proud of it. Then the team hired a senior engineer who interviewed like the loudest person on the panel. Three months later people were redoing his work. The shortlist was fast. The decision was a vibe. The resume was not the part that failed. The room was. ## What drifts when nobody shares a page Put five candidates through a week of interviews with no shared standard and watch the bar move. Monday's candidate gets a hard question about a launch that failed. Friday's candidate gets a tour and a chat about colleges, because everyone is tired. Both get a "seemed strong" in Slack. Nobody is being corrupt. Memory is just a bad instrument. The last person you liked occupies more space than the person you met on Tuesday and forgot to write down. I have sat in debriefs that were really one person campaigning. They talked more, so their favourite survived. The quieter interviewer had a concern about how the candidate blamed a whole team, and never got to the second sentence. The hire was a volume contest. ## Same job, same territories You do not need a twelve-row matrix to stop this. You need the four things this role will be judged on in six months, named before anyone walks in. And a note, written in plain language, for what a weak answer sounds like. Same territories for every candidate. Not identical theatre, but not a different interview depending on who is free. A score you enter before you hear the other interviewer. After is too late. You will edit yourself to match the person who spoke first. A tool can draft question prompts from the job post so you are not staring at a blank doc at 9pm. It can also line the notes up so the debrief is "she was shaky on the outage, he was specific" instead of "I just liked him." It cannot save you if your four things were fog. "Culture fit" as a criterion is how clones get a badge. Leave that fight for the scorecard you agree before the first call. This piece is about what happens when you skip the comparison and argue impressions instead. ## Small teams feel it faster You do not have a recruiting ops person maintaining rubrics. You have a founder, a lead, and a doc named Interview_v3_FINAL. That is fine. Someone still has to refuse a hire that is only a feeling. The useful tool is the one that makes skipping the write-up annoying. The useless one ranks a human into a single number and calls it objectivity. A single number hides which interviewer ignored the hard part. If you only speed up the top of the funnel, you arrive at a sloppy decision sooner. That is not a better process. It is a faster mistake. Fix the room where you actually choose. ## The debrief that is not a campaign Run the meeting off the page, not off whoever speaks first. Two questions are enough. Where did the scores disagree, and what did we actually hear? If the disagreement is "I liked their energy," that is not a disagreement you can hire on. Send people back to the notes. I have watched a 15-minute debrief replace an hour of re-litigation, but only when the notes existed. Without notes, fifteen minutes is just a shorter argument. With notes, you can see that three of you heard the same gap and one of you talked past it. Write the decision down in a sentence a new teammate could read in six months. "We hired her because she had shipped a migration under a deadline and could name what she would do differently." Not "great culture, strong communication." Those phrases are how you forget why you chose, and how you repeat the choice by accident. ## Speed still matters, just not first I am not against a faster shortlist. Good people do not wait while you perform thoroughness. The order is the point. Get to the conversation quickly, then refuse to decide on memory. If your process cannot tell Monday's candidate from Friday's on the same four things, you do not have a hiring process. You have a social hour with a job title at the end. --- # AI Resume Screening: How Small Teams Can Hire Faster and Smarter Source: https://hireassist.org/blog/ai-resume-screening-hire-faster-small-teams A friend running a 12-person studio in Jaipur posted an operations role on a Thursday. By Monday she had 186 emails with attachments named Resume_final_v2. She opened about forty, mostly the ones near the top of the inbox, and hired from that slice. Weeks later a colleague searched the unread pile for "warehouse" and found someone stronger. The hire was already in notice period. That is small-team resume screening. Not a philosophy. An inbox. ## Why the manual pass fails It does not fail because you are careless. It fails because resume number 90 gets less of you than resume number 4. Layouts differ. One person buried a relevant year inside a paragraph about a college fest. You were on a client call. You skimmed. By evening you were choosing from the people who happened to format well and arrive early. Meanwhile a good candidate has already taken another conversation. Nine days is a long time when you are unemployed and someone else replied on Friday. Keyword search is the old version of "help," and it is clumsy. It promotes whoever pasted your job post into a skills section. A better first pass asks whether the experience matches the work, not whether the noun appears. Years in a similar mess. A tool they used for real, not a logo wall. ## What you are trying to get A pile you can actually read. Not 186. Fifteen or twenty, where the obvious mismatches are already out. They have not done the work. The city is impossible. The thing you named in the post is nowhere in the file. Then you read. You. The shortlist is a reading list, not a decision. Applications need one front door. Not your personal Gmail mixed with newsletters. Something should read each file against the post you actually wrote. If that post is three adjectives and "self-starter," the something will be as vague as you were. Write it like a person who has done the job. The tasks. The tools. The constraint. On-site twice a week. Hindi and English. Night closes during month-end. You want a reason next to the name. "No inventory work" is useful. "72% match" is how you stop thinking. ## The audit you should not skip Open the top of the list, and open a random slice lower down. Models miss career-switchers who describe the work in different words. Ten minutes on the rejects will show you a confident blind spot before it becomes a hire. Set the must-haves before the post goes live, and keep them few. Everything else is a conversation. Speed without that list is how you only meet people who look like the last person you liked. HireAssist is built for this shape of team. One career page, resumes read against the role, then a person picks who to meet. Use that, or use a spreadsheet you actually maintain. Do not use hope and inbox order. Screening will not know if someone is kind, or if they inflated a title, or if they will fight your accountant. It will stop you spending Thursday night on people who have never done the job. That is the win. Take it. Then interview like the decision matters, because the resume never made it. ## A workflow you can run on a Tuesday Applications land in one place by the end of the day they arrive. The first pass happens the next morning, not "when I get to it." You read the reasons, not just the order. You move a small set to "talk to" and you send the rest a short no. Silence is not a brand. Before you book anyone, look at one reject that scored close and one that scored badly. If the close one is obviously relevant and the tool missed the wording, fix the job post or the must-have list. If the bad one is obviously wrong, trust the pass and stop rereading the whole pile to feel diligent. Then talk to people while they are still interested. Same week if you can. The screening did its job when the conversation starts with their actual work, not with you discovering in minute ten that they have never done it. ## What I would not automate Do not let a score send the offer. Do not hide the reason from the person on your team who has to interview. Do not add twelve "nice to haves" because a template had space. Every extra rule is another way to drop the career-switcher who would have been fine. The studio in Jaipur did not have a recruiting team. She had an evening and an inbox. That is most small companies. The fix is a door, a short list of must-haves, and a human who still reads. Faster is a side effect. The point is that the strongest file is no longer stuck under a newsletter.