A vacancy often begins with pressure: a growing ticket queue, a project that needs momentum or an experienced colleague moving on. Before searching, it is worth making space for a more precise conversation. What needs to change when the right person joins, and what will they need from the business to do it well?
01 / The brief
Start with the work, then the job title.
Two businesses can advertise the same title and need very different people. An IT support role might centre on patient first-line conversations, independent site visits or complex escalation work. Write down the responsibilities that will occupy most of the person’s week, including the less glamorous tasks.
Then identify a few outcomes you would expect during the first three months. These should reflect the role’s level and the support available: learning the environment, taking ownership of a defined queue or improving a particular process. This gives the search a useful direction and the interview a practical reference point.
Separate what must be present on day one from what can be learned. A long technology list can hide the distinction between essential depth and occasional exposure. Discuss the actual environment, the team’s strengths and where the new hire will need help.
02 / The conversation
Give every stage a reason to exist.

An initial conversation can establish relevant experience, motivation and expectations. A later meeting might explore technical judgement or introduce the colleagues the person would work with. Two stages can be useful, but the number is less important than the purpose. Avoid repeating the same questions with a different audience.
Agree the evidence you are looking for before the interviews. Ask candidates for examples related to the responsibilities and use consistent core questions. Make notes against the agreed requirements, leaving room to explore individual experience. Fluency and confidence are useful observations, but neither proves someone can do the work.
Tell candidates who they will meet, how long the meeting will take and when they can expect an update. Leave time for their questions. What they ask can reveal the information they need to decide whether they can contribute and develop in your environment.
A clear brief gives everyone a better chance of recognising the right match.
03 / Relevant evidence
When the role is hands-on, make the evidence practical.
For some technical positions, a focused exercise adds information that conversation alone cannot provide. An IT support candidate could prioritise a small set of fictional tickets, investigate a simulated access problem or explain a technical issue to a non-technical colleague.
Use a safe test environment and a task that reflects the role’s level. Decide what you are assessing: diagnosis, communication, prioritisation, safety or a combination. A short, well-designed exercise is often more useful than a sprawling task with an unclear finish line.
Explain the format, duration, criteria and permitted resources beforehand. Discuss any adjustments needed and keep the time commitment proportionate. Do not use the assessment to obtain unpaid productive work or give access to live customer data. If the role does not need a test, do not add one merely to make the process look rigorous.
Keep in mind
- Does this exercise reflect the actual work?
- Can it run safely without live data or production access?
- Have we explained what good evidence looks like?
- Is the time commitment reasonable?
- What useful information will it add to our decision?
04 / Expectations
Be as clear about the opportunity as the requirements.

Salary matters, but it does not describe the whole opportunity. Explain working hours, location, on-call duties where relevant, management support and how decisions are made. If progression depends on a future business need, say that rather than implying a promotion is already waiting.
Candidates may be weighing development, stability, flexibility or the chance to take on greater responsibility. Understanding those priorities helps you discuss the opportunity accurately. A capable person can still be the wrong match for an environment that cannot offer what they are looking for.
Before deciding, compare the evidence with the original brief. Resolve unanswered questions, identify any training needs and agree an achievable start. Clear expectations cannot guarantee retention, but they provide a stronger foundation than assumptions on either side.
05 / Beyond one vacancy
A recruitment partnership that grows with your business.
Understanding a business takes more than reading its latest advertisement. At Connex, our aim is to understand your team, technical environment and plans, so a search reflects the work ahead rather than a job title in isolation.
As that understanding develops, the next brief can begin with more context: what mattered last time, what has changed and which capabilities the team now needs. Useful feedback helps refine the search and keeps expectations aligned.
We aim to earn a place as a trusted recruitment partner through consistent service and informed conversations. For your business, the benefit is continuity: someone you can return to as your needs develop, who already understands the questions worth asking.
Photography & editorial notes
Licensed stock photography illustrates the situations described. People and workplaces pictured are not presented as Connex employees, clients or candidates. Scenes may feature different people.
Photos from Pexels, used under the Pexels Licence. Photo sources: Business professionals meeting in an office · Group of People Gathered Around Wooden Table · Woman in a Job Interview.
Written by Connex Recruitment. Published 16 November 2026. Guidance should be adapted to the role, workplace and individual circumstances.


