The project configuration is key to mastering the process of finding top candidates faster and helping Talendary identify the type of candidate we should help you find.
Follow this short guide on how to master the key feature: Project Configuration.
Step 1 - upload information about the candidate
The first step is to upload accurate information about the candidate. You have three options to choose from:
Upload CV
Project Description
Enter text (e.g. tell Talendary about the role or upload a job ad)
Step 2 - Talendary will Present a First Draft of the Project Configuraiton
Let’s take a real-life example: pretend we are looking for a Senior Backend Developer for Talendary and have just finished the requirements meeting with our Hiring Manager.
We created a job ad, uploaded it to Talendary, and received the following result. Below is a breakdown of each section.
Requirements
The first section of the project outlines the requirements, detailing the "should-have" and "must-have" criteria that a candidate must meet to be considered relevant for the role.
Skills
The second section outlines the skills a candidate should have based on their previous work experience to be a strong fit for the role.
This may include tasks they have performed, responsibilities they have taken on, and the competencies they have developed in their previous positions.
Bonus
The final section outlines bonus qualifications—experiences or skills considered a plus but not strictly required for the role.
These experiences can help a candidate stand out or increase their chances of being selected.
However, not having them doesn’t automatically disqualify someone. Examples include industry-specific experience, certifications, or advanced degrees.
Step 3 - Source talents from Linkedin Recruiter
Let’s head over to LinkedIn Recruiter and perform an initial search for candidates.
Keep in mind that we haven’t made any changes to the project configuration yet - let’s review the results below.
As we can see, the results are quite generic, with many candidates scoring very high, making it difficult to identify who is truly the best fit. Let’s return to our project configuration to refine the list of requirements and improve the search results.
Step 4 - Improve Project Configuration
Let’s review the different sections and make improvements.
Requirements
As a reminder, here is the old one:
And let's remind ourselves from the requirement meeting what we actually are looking for:
A Senior Backend Developer for Talendary
From that description, we can change the requirements as per below:
Old Requirement | New Requirement | Explanation |
Several years of experience in backend development | +5 years of experience in object-oriented programming languages | We need to define what "Several Years" and "backend development" mean to Talendary. |
Fluency in Swedish and English | Fluency in Swedish and English (if not stated in the CV, make an educated guess) | We will add a parenthesis to let Talendary guess if the language is not clearly stated in the CV. |
Proficiency in multiple programming languages | +5 years of experience in Python and Typescript | We need to define what "Proficiency" means to Talendary and the tech stack we use. |
| Proven track-record as a top performer (e.g., indicated by frequent promotions, more responsibility, awards, performance metrics) | Describe the traits you are looking for to help Talendary understand what to search for. |
| Previous experience from high growth startups i.e. Spotify, Klarna or similar company | Describe the company culture and type of candidate you are seeking.
|
The updated requirements section now looks like this:
Skills
As a reminder, here is the old one:
From that description, we can change the requirements as per below:
Old Requirement | New Requirement | Explanation |
Backend development experience | Experience in configuring and managing infrastructure for web applications. | A more detailed description of what type of backend development experience. |
Problem-solving skills | Competency in writing, maintaining, and deploying efficient code. | We want problem-solving to be focused on coding. |
Proficiency in multiple programming languages | Proficiency with Docker, PostgreSQL, Redis, and related tools. | A more detailed description of what the candidate needs experience from. |
Knowledge of software development lifecycle | General startup business knowledge within Sales, Marketing, and Product management. | Since everything else already focuses on software development we want to broaden the scope of this one. |
Team collaboration skills |
| Good as is! |
| Leadership and management experience of tech or non-tech teams | A skill that we thought was missing. |
The updated requirements section now looks like this:
Bonus
As a reminder, here is the old one:
From that description, we can change the requirements as per below:
Old Requirement | New Requirement | Explanation |
Experience with cloud services | Experience with modern cloud providers (e.g. GCP, AWS, Azure) | A more detailed description when it comes to cloud providers. |
Knowledge of database management | Experience with HR tech and recruitment tech SaaS. | A more detailed description about the industry. |
The updated requirements section now looks like this:
Step 5 - Analyze the candidates with the new project description
After updating the project scorecard, save your changes and let Talendary re-evaluate the candidates.
We can see that the results are more diverse, making it easier to identify and reach out to the potential best-fit candidates.
Thats a wrap! If you need a more thorough explanation, don't hesitate to reach out to: [email protected]