You think — your finalist is already signing elsewhere

A typical call from a client: 'we lost the candidate.' When did you make the offer? We haven't yet — wanted to think a bit more. How long since the final? Two and a half weeks. Why offer speed decides more than offer amount.

There's a conversation that keeps repeating in my work. A client calls, voice upset: "Anastasia, we lost the candidate." I ask: "When did you make the offer?" — "Well... we haven't made it yet. We wanted to think a bit more." — "How long since the final interview?" — "About two and a half weeks."

Then I stay silent for about five seconds. Not for effect — I just need a second not to say anything I shouldn't.

Two and a half weeks in 2026 IT hiring isn't "a bit of thinking." In that time an active candidate has been to three or four interviews, received two offers and started a new job. Literally.

Where the delay comes from

I've thought about this a lot. The reasons vary, but none of them actually justifies losing a person you yourself wanted to hire.

First — fear of mistake. "What if we are wrong? What if someone better appears?" Understandable psychology. But it works in a world where the candidate sits and waits exactly for you. He doesn't.

Second — bureaucracy. The offer has to go through HR, the manager, the CFO, legal and the manager again. I know companies where that takes ten working days. In that time a competitor calls, makes an offer and gets a "yes."

Third — perfect-candidate syndrome. "He's good, but let's see one more." Then one more, then one more. While you look — the first one leaves.

Fourth — an outdated picture of the market. Some managers still think there are many candidates and they're patient. That was true in 2015.

The Alexei story I won't forget

Last autumn. Client — a media-tech company I'll call StreamTech. We spent three weeks searching for a senior iOS developer. Difficult role: there are few such specialists, and the good ones are taken.

We found Alexei. Five years of experience, contributions to several well-known apps, fit the team culture well. The final interview — everyone delighted. That same evening I wrote to the client: "Make the offer tomorrow. Day after at the latest. He's actively looking, parallel processes definitely exist."

The reply came a day later: "We want to weigh everything once more. Show me a couple of candidates for comparison."

Five more days passed. Alexei wrote to me himself. "Anastasia, I've accepted another offer. They made it the day after the interview. There was no reason to wait longer."

StreamTech found someone else — after six more weeks of searching. Found. But at a different level. And more expensive.

Alexei didn't leave because he found a better place. He left because the other company showed respect for his time. That's part of the offer too — invisible, but felt.

Slow hiring is literally an antipattern

Here's what I think is most important on this topic — and what I increasingly say to clients.

Every IT company in 2026 lives, one way or another, by agile principles. Fast iterations. A Friday deploy is normal. Made a mistake — rolled back, fixed, moved on. "Fail fast, learn faster" isn't a slogan — it's a real working philosophy.

And here is the paradox: companies that work brilliantly with this philosophy in product development behave in hiring like a waterfall project from 2003. They gather requirements for months, endlessly approve, launch when it's already too late.

You deploy to production every day. You aren't afraid of mistakes — because you can roll back and fix. Why is hiring scarier?

What timing is normal

I get asked this specifically. Let me answer specifically.

After the final interview: decision in 1–2 working days. Not "we'll think about it," but concrete "yes" or "no." If yes — verbal pre-offer the same day.

Written offer: 2–3 working days. While legal spends a week — a competitor is already in touch. Solution: give the CTO authority to sign offers independently, at least for roles up to senior.

Candidate's reply: 3–5 working days is normal. If they ask for two weeks — don't wait in silence. Call, ask directly: any objections? What's getting in the way? Most likely they're waiting for another offer or have a question that a conversation can resolve.

Whole process from first contact to offer: 3–4 weeks. If yours takes two months — that's not thoroughness. That's a broken process.

What can be done internally

• Agree the budget for the role before the search starts — so you don't re-approve the offer once the candidate is found.
• Give the hiring manager the right to make a verbal pre-offer immediately: "we want to hire you, details tomorrow."
• Reduce the number of sign-offs: a role up to senior should not pass through five approvals.
• Run two or three finalists in parallel — so you don't restart from zero if the first declines.

One more thing

Developers are smart people. They look at your hiring process — and draw conclusions about how the company is run inside. If the offer decision takes two weeks — that's how feature launches will be decided too. Or production-bug responses.

Speed of offer is part of your employer brand. The most honest part, because here you cannot write a nice page on a website. Only show it.

Hire fast. Mistake rarely, but don't be afraid. Correct honestly. That's how good products get built — and good teams too.