How efficient is your hiring pipeline, really?

This hiring pipeline assessment asks 10 questions about how your last search actually went, and it takes about 3 minutes. Your score, your band and the stages to fix first show up right here on the page, and you don't need to give an email.

Take the assessment →

When the whole hiring process runs through you

It's Monday, and 140 applications are waiting in your inbox for a role that went live on Thursday. Some came from job boards, some the client forwarded, and a few arrived as replies to an old thread. Before you've opened one, a candidate from last week writes back asking "what time works?"

Then the client asks why the person they referred didn't make your shortlist. You had a reason, but it's somewhere in your head from last Tuesday. Nothing breaks all at once. Small things slip at every stage, and you pay for them in evenings.

Take the assessment

Take the assessment

Answer for your most recent search, the way it actually went. If two answers fit, pick the lower one.

Your result

Your score and band

We add up your points as soon as you answer Q10. Each question is worth 0 to 3 points, so the most you can score is 30. Your total puts you in one of four bands.

Your result shows your score, your band and a short note on what it means for your next search. Every band is described in full further down this page, with three next steps for each.

Your weakest areas

Below your score, your two or three lowest scoring questions show as "Fix first" cards. Each card names the area and gives you one fix, with a link if you want more detail. When two questions tie, the earlier one comes first. Here's the fix for each of the ten areas.

  • Tracking. Move every live search into one pipeline this week, so no application depends on you remembering which inbox it landed in.
  • Role definition. Before the post goes up, write three to five outcomes the hire must deliver and get the client to agree to them, which is the first step in structured hiring.
  • Screening. Read every resume against the same must-haves instead of the last good one you saw, or use candidate ranking to score each applicant against the job before you decide.
  • Interviews. Choose the questions for each stage before the first interview and ask them of everyone, starting from a set built with the interview question generator.
  • Feedback. Have every interviewer, the client included, fill in a one-page scorecard before the debrief, which is the habit that makes structured interviews work.
  • Candidate communication. Reply to every applicant within two business days, and let the Email agent turn applications that reach your connected inbox into applicants in your pipeline instead of a folder you forgot to check.
  • Speed. Work out your real time to hire with the time to hire calculator, then cut the longest wait first.
  • Visibility. Name each stage of your process and who owns it, as in how to build a hiring pipeline, then check every open role once a day for anyone waiting on you.
  • Metrics. Start with time to hire and where your hires came from, and add more recruiting metrics only when you'll act on them.
  • Decisions. Write down the reason for every yes and every no before you tell the client, and keep a person on each call even when AI does the first pass, as we explain in fair AI hiring.

What to fix first

Start with your lowest card. If two areas tie, fix the one that comes earlier in the process, because tracking and role definition set the ceiling for everything after them. If applications are scattered or resumes get read on gut, a faster shortlist only gets you to the wrong people sooner. Pick one fix, make it during your next search, and retake the assessment when that search closes. One change you actually make beats three you plan.

Your score, band and fix-first areas are already on screen above. Add your email only if you want occasional Curriculo updates.

What the four bands mean

Every band is here in full, whatever you scored.

Scattered (0 to 10)

Your hiring runs on inboxes and memory. Applications reach you from too many places, so part of every week goes on finding people before you can judge anyone. When a client asks why someone was cut, you're rebuilding the answer from scratch. Start with intake and role definition, because every later stage depends on them.

  1. Put every applicant in one place. Move every live search into one pipeline before the next post goes up. Connect your Gmail or Microsoft 365 inbox to Curriculo's Email agent, and applications that reach it become applicants in your pipeline. Per-job addresses, like you+CODE@yourdomain, work on Gmail only.
  2. Write down what good looks like. Before the post goes up, write three to five outcomes the hire must deliver in a doc you share with the client, and get a yes on them. Then put a salary range, an experience range, each location and the work mode on the Curriculo job form, so people know what they're applying for. The guide on how to build a hiring pipeline covers the stages that come after.
  3. Reply to every applicant within two business days. A short, kind no beats silence, and it's the habit candidates remember. Emails the Email agent can't match to a job go to Review needed, with no automatic email sent to them, so add that list to your reply routine.

Sign in at curriculo.me

Reactive (11 to 18)

You have the pieces, but they don't connect. Candidates are tracked somewhere, but screening and interviews change from search to search. When two finalists went through two different processes, you end up weighing a strong feeling about one against a few notes on the other. Tighten the handoffs and your decisions get easier to make and to explain.

  1. Turn your must-haves into a scorecard. List the outcomes for the role, give each a 1 to 4 rating, and have every interviewer fill it in before the debrief. The guide to structured hiring shows how to set one up and where AI fits.
  2. Ask the same questions at each stage. Choose the questions for each round before the first interview happens, and share them with the client's interviewers. The interview question generator gives you a starting set, and structured interviews explains how to run them.
  3. Ask your first-call questions up front. Most first calls cover the same ground, like notice period, salary expectations and location. Add those as screening questions on the Curriculo job form, so the answers arrive with the application and you can read them next to the resume before you book anyone.

Sign in at curriculo.me

Structured (19 to 25)

Your process is repeatable. Candidates live in one place, interviews follow a plan, and you can usually explain a decision in one message. The next gains come from speed and visibility, which means knowing where candidates stall and how long a search really takes.

  1. Score every applicant against the same job. Once your job posts say clearly what the role needs, scoring every applicant against the job is worth doing, and candidate ranking shows how that works. In Curriculo, the Resume screening agent asks each applicant one round of questions, then gives a 0 to 100 score with an AI summary. A person makes every decision.
  2. Measure your time to hire. Run your last three searches through the time to hire calculator and find the stage where the days go. Then pick the recruiting metrics you'll actually act on, and leave the rest.
  3. Know who's waiting every morning. At the start of each day, check every open role for anyone who hasn't heard from you in two business days. Curriculo's Daily briefing agent gives you a morning summary of your pipeline, so you start that check from a summary and skip the scroll through the inbox.

Sign in at curriculo.me

In control (26 to 30)

Your pipeline is clear, consistent and measured. Candidates hear back, clients get reasons in one message, and you know how long a search takes. The work now is keeping it that way as you take on more clients, and cutting the admin that still lands on your desk.

  1. Review your scorecards after each hire. A few months in, check whether the people who scored well early are doing well in the job, and rewrite the questions that didn't predict anything. If you use AI in screening, keep a person on every advance or reject decision, the way we describe in fair AI hiring.
  2. Cut the inbox admin. Every application you copy by hand is time you're not spending with candidates or clients. With the Email agent, applications that reach your connected Gmail or Microsoft 365 inbox become applicants in your pipeline, and on Gmail you can give each job its own address, like you+CODE@yourdomain.
  3. Let the job page do the first filter. Put the salary range, the experience range and every location in the post before it goes live, so the people who apply have already decided the role fits. Curriculo's public job pages show the salary up front and keep the apply button in reach.

Sign in at curriculo.me

What a hiring pipeline assessment measures

Think of it as a quick hiring process audit you run on yourself. The ten questions cover five parts of your process. If you want the plain definition first, start with what a hiring pipeline is.

Tracking and one source of truth

This part checks whether every candidate lives in one place you trust. If applications are spread across your inbox, LinkedIn messages and whatever the client forwards, you spend the week finding people before you can judge them. One source of truth also means you can answer "where is this candidate?" without opening three tabs.

Role definition and screening

Role definition asks whether you know what good looks like before applications arrive, written down and agreed with the client. Screening asks whether every applicant gets read against that same bar, or whether the bar drifts with the hour and how many resumes came before. A clear role makes screening faster and much easier to explain.

Interviews and scorecards

Consistent interviews mean the same questions at each stage for everyone on a role, so two finalists get compared on the same evidence. A scorecard is a one-page sheet you write for each role. It lists the outcomes with a simple rating for each, and every interviewer fills it in before the debrief. A shared doc is enough to run it, and it stops the first person to speak from shaping everyone else's opinion.

Speed and candidate communication

Speed covers how long a search takes from the post going live to a shortlist the client can act on. Candidate communication covers whether applicants hear back, how fast, and whether the people you pass on hear anything at all. Slow replies cost you the candidates with other options, and those are often the ones you wanted.

Metrics and decisions

Metrics asks whether you track anything at all, starting with time to hire, and whether the numbers change how you run the next search. Decisions asks how the final call gets made. It might be the most senior voice, a gut call, or a debrief tied to written evidence with the reasons kept. When a client asks why, a written reason lets you answer in one message.

How to improve your hiring pipeline score

  1. Put every applicant for every search in one system.
  2. Write three to five outcomes for each role, agree them with the client, and screen against them.
  3. Ask the same interview questions at each stage, and collect scorecards before the debrief.
  4. Reply to every applicant within two business days, including the people you pass on.
  5. Track your time to hire, and write down the reason behind each decision.
  6. Retake the assessment after your next search and see what moved.

How Curriculo helps

Curriculo is an ATS. Connect your Gmail or Microsoft 365 inbox, and the Email agent turns applications that reach it into applicants in your pipeline. Emails that can't be matched to a job go to Review needed, with no automatic email sent to them. The Resume screening agent asks each applicant one round of questions, then gives a 0 to 100 score with an AI summary. A person makes every decision. The Daily briefing agent gives you a morning summary of your pipeline, and the Calendar agent works with your calendar.

Starter is free forever, with unlimited jobs and 1,000 ranked candidates. Pro is $50/mo early-bird, 50% off $100, with 10,000 ranked candidates. There are no per-seat fees, and pricing has the details. Sign in with Google or Microsoft.

Sign in at curriculo.me

Frequently asked questions

A hiring pipeline assessment is a short self-audit that scores how well you track, screen, interview and decide on candidates. You answer ten questions about how your last search actually went, get a score out of 30 and a band, and see which stages to fix first. It takes about three minutes.

About three minutes. There are ten scored questions with one answer each, plus an optional question about how many roles you hire for in a year, which doesn't count toward your score.

Each of the ten questions is worth 0 to 3 points, for a maximum of 30. Your total places you in one of four bands: Scattered, Reactive, Structured or In control. Your two or three lowest scoring questions show up as the areas to fix first, each with a practical next step.

A score of 19 or higher means your process is structured and repeatable, with candidates in one system, interviews that follow a plan and written feedback before every debrief. A score of 26 or higher means your pipeline is also fast and measured. Below 11, start with tracking and role definition.

Fix the basics in order. Put every applicant in one system so nothing gets lost, then write three to five outcomes the hire must deliver and screen against them. Ask the same questions at each interview stage and collect scorecards before the debrief. Then reply to every applicant within two business days.

Not for one or two hires a year, when a careful spreadsheet can work. Once several searches run at the same time, an ATS keeps every candidate for every role in one place. Curriculo's Starter plan is free forever, Pro is $50/mo early-bird, and there are no per-seat fees.

No. Your score, band and fix-first areas show on the page as soon as you answer the last question, with no email or sign-in. There's an optional field under your result if you want Curriculo updates.

Retake it after each search you close, or once a quarter if you're hiring all the time. Answer for the search you just ran, the way it actually went. Comparing scores shows whether the change you made actually moved anything.

Written by Dev Rishi Khare, former machine learning engineer at Amazon and Synopsys.

Ready to hire with precision?

Start free, invite your whole team, and see your first scored candidate in 15 minutes.

en