Several hiring tracks run at the same time: in SaaS and product companies

A founder opens the hiring tracker on Monday. Engineering has four open roles, sales has two SDRs and an account executive open, customer success has one. Each lead keeps a separate sheet, a separate interview panel and a separate idea of a good candidate. Two people have waited a week for feedback, and one is already in a final round elsewhere.

Nobody here is lazy. Four leads are each doing a sensible thing, and the sum of it is chaos. A small amount of shared structure repairs it, with no need for an in-house recruiting team.

• A backend candidate sends back a take-home and waits ten days, because the reviewer is buried in a hotfix.
• A sales candidate meets three people who ask the same discovery questions, because nobody wrote down what each round covers.
• Offers go out with different notice, joining and variable pay terms for similar levels.
• One lead rejects a profile another lead would have loved, and the candidate never learns why.
• The founder sits in every final round, which delays every pipeline equally.

Empty seats cost sprint capacity first. The short-handed squad carries the backlog, the review queue and the pager meanwhile. The quieter cost is reputation. Product talent talks, and a slow, muddled process becomes a story in a peer WhatsApp group. Sourcing gets harder next quarter. There is a pay drift cost too, since hurried offers get negotiated one by one.

Every function owns its own hiring, which is right when judging craft. The pipeline as a whole belongs to nobody. Interview slots are booked by whoever has a free calendar. Feedback lands when the reviewer surfaces from the sprint. And without a scorecard, every interviewer measures something different.

1. 1

   Create one pipeline view

   A single tracker with role, hiring lead, stage, days in stage, next action and owner, kept in a shared sheet or your HR system.

2. 2

   Write a short scorecard per role family

   Three to five criteria: system design, code review habits and communication for a backend role; discovery, objection handling and CRM hygiene for a seller.

3. 3

   Fix the stages and what each tests

   Screening call, skills round, deep-dive with future peers, then a leader conversation. Name who runs each.

4. 4

   Set response times

   Feedback inside two working days after each interview, and a yes or no on the offer soon after the last round.

5. 5

   Hold a thirty-minute weekly review

   Walk through candidates stuck for more than a few days and agree one unblocking step each.

6. 6

   Standardise the offer structure

   Fixed pay, variable pay, ESOP grant and joining terms drawn from a band, so two offers at one level do not diverge.

Role and level (for example, Senior Android Engineer, L4).
Hiring lead and panel members.
Source (referral, job board, recruiter, outbound).
Stage (screen, skills round, deep-dive, leader, offer, joined).
Days in current stage.
Next action and who owns it.
Scorecard result (average per criterion).
Offer band and any exception noted.

Open it every Monday. Rows with a high number in the days column are discussed first, and the owner leaves the call with a named next step. Sort by role family once a month to see where you are losing people: most firms find the slowest stage is feedback after the skills round, not sourcing.

A sales hire might do a mock discovery call on a made-up customer. An engineer might review a small pull request and explain what they would change. A customer success candidate might handle a heated renewal email in front of the panel. Each test should resemble the first month of the real job, which also tells the candidate what the work is like.

Referrals bring the best product hires and also the most awkward rejections, so tell the referrer what happened. Campus drives for graduate engineers and associate support roles need their own batch calendar, since offers wait months for joining. Keep those candidates warm with a monthly note from the future lead, a link to the engineering blog and an early look at their onboarding plan. At the offer stage, share the full break-up of fixed pay, variable pay and grant terms in one document, so the candidate does not compare partial numbers against another employer.

Some companies bring in a partner for the harder roles and run the rest themselves. A recruitment process consulting engagement can design the stages, scorecards and tracker, and our IT specialised recruitment service helps when engineering roles need sourcing. A written compensation and rewards strategy keeps offers aligned to the same bands.

• Close the loop with every candidate, including a short, honest rejection.
• Review days-to-offer and acceptance by role each quarter.
• Retire any stage that never changes a decision.
• Coach interviewers to sell the role without overpromising on the roadmap.

Pay drift, forgotten OKRs and equity records are covered on the SaaS and product companies hub.