How Do You Actually Start a Recruitment Process?
Many people believe that opening a recruitment process simply means writing a job description. However, the process should be far more comprehensive than just listing the technical characteristics of the person expected to fill the role.
This blog is intended for hiring managers who are approaching hiring for the first time or want to optimise their existing process.
Why Most Hiring Processes Start the Wrong Way
When the need for a new employee appears, the first step is to clearly define the technical scope of the position.
A role should never be “something in between, but we’re not exactly sure what.”
It is essential to carefully analyse every responsibility this person will actually have.
Do not be afraid to create a unique position based on the real needs of your team rather than trying to fit into templates used by other companies.
At the same time, do not evaluate candidates solely based on what they are currently doing.
Hiring managers often assume that candidates must actively perform every required task in their current role because they see it as the candidate’s most advanced or most relevant position.
However, candidates have often covered different parts of the process in previous roles, which means they may already have the complete cycle of experience your company actually needs.
How to Define the Right Qualifications
Once you define what the person will actually do, the next step is determining which skills are mandatory from day one and which skills your company is willing to invest resources into developing.
One of the biggest mistakes in writing a job description is placing critical qualifications into the “nice to have” section simply because they represent a smaller percentage of the workload.
For example, technical teams often describe front-end as “nice to have” because it only represents 20% of the role.
The problem is that candidates will interpret the position incorrectly.
Strong Full-stack candidates may reject the opportunity because they assume the role is not content-rich enough - full-stack engineers usually want to actively work across the entire stack, not only on back-end tasks.
On the other hand, incomplete candidates may apply because they believe you are looking for a pure back-end engineer, while in reality, you need a full-stack profile.
Even if those candidates pass the CV screening stage, they are often rejected during interviews because their knowledge does not align with the actual needs of the team.
Everything that is truly necessary for the role belongs in the main requirements section.
The “nice to have” section should only include skills your company is genuinely prepared to develop internally by investing both time and resources.
How Long Does a Recruitment Process Actually Take?
After defining the position itself, the next step is planning the hiring timeline.
This is the part companies often underestimate, even though it later creates the biggest pressure on both the team and the hiring process itself.
The market standard notice period is 30 days, which means that once a candidate accepts the offer, you still need to account for at least another month before they can officially join your company.
For senior and C-level positions, this period is often significantly longer.
This is exactly why companies should not start hiring only once the role becomes “urgent.” That situation usually leads to chaotic decision-making and lowered hiring standards.
If your process consists of three interview stages, it is realistic to dedicate one week to each stage to interview all relevant candidates properly.
Afterwards, you should reserve an additional week for final decisions and offer preparation.
However, hiring processes rarely end with the first offer sent.
Candidates may ask for time to think, receive counteroffers from their current employer, or simply reject the opportunity.
Because of this, it is important to leave additional working days in your timeline so you still have enough room to extend the offer to your second-choice candidate without creating operational chaos or unnecessary pressure.
When everything is combined: one month of active recruitment, one month of notice period, delays between stages, You can very easily reach a full quarter for a single hire.
That is a long period of time, which is why it is crucial to realistically assess from the beginning how much time you actually have.
Job Ads vs Headhunting - What Actually Delivers Results?
Many companies initially rely entirely on job ads, but it is important to understand how job ads work in reality.
The more specific and demanding the qualifications are, the lower the probability that the right candidates will apply organically through an ad.
This is especially true for senior and hard-to-fill positions, where the best candidates are often not actively looking for jobs at all.
That does not mean job ads have no value.
On the contrary:
- they increase company visibility,
- contribute to employer branding,
- and help introduce your company to parts of the market that may not know you yet.
However, if the role needs to be filled within a shorter timeframe, it is usually best to combine job ads with headhunting from the very beginning.
Time is a non-renewable resource, which is why companies should not wait for an ad to “do its job” before starting active sourcing.
Whether sourcing is handled internally or through an external recruitment agency, a proactive approach is almost always necessary for urgent and complex positions.
How to Organise Interviews Without Creating Chaos
One of the biggest mistakes in recruitment is organising interviews ad hoc between meetings and daily product work.
If you do not establish a system in advance:
- Who interviews,
- When interviews happen,
- and how quickly feedback is expected,
The process quickly becomes slow and chaotic.
The best approach is to predefine specific days and time slots reserved for interviews and allow candidates to adapt to that structure.
Otherwise, both hiring managers and candidates constantly try to squeeze interviews between other obligations, which significantly prolongs the entire process.
If the role is urgent:
- reduce the number of hiring stages,
- involve fewer people in the process,
- and organise interviews closer together.
If hiring is a priority, there should not be a one-week gap between interview rounds.
It is also important to discuss notice period flexibility during the very first conversation with the candidate.
That information can significantly affect onboarding timelines and overall project planning later on.
If your company is in a hurry, it is not enough to simply expect candidates and teams to move faster - the process itself must become more structured, operationally simpler, and easier to execute.
Conclusion
A hiring process does not begin when a job ad is published. It begins much earlier - the moment you clearly define what you actually need, how much time you have, and how many resources you are willing to invest in turning someone into a functional part of your team.
The biggest hiring problem is usually not the lack of candidates on the market.
It is unclear role definition, poorly structured qualifications, and a process that is operationally unprepared to support successful hiring.
When hiring is not properly structured:
The wrong candidates are attracted,
The process takes longer than expected,
Teams lose time on interviews that lead nowhere,
and pressure on the business and product only increases
On the other hand, a well-structured process allows companies to:
- identify the right people faster,
- reduce operational chaos,
- and make higher-quality hiring decisions without lowering standards under time pressure.
Hiring should not be treated as an administrative task to be completed.
This is a serious process that directly affects team stability, development speed, and the company's long-term growth.