IT recruitment: role profile, screening and costs
IT recruitment finds people with suitable skills; it does not automatically deliver a finished IT project. A useful mandate describes the work, technology environment and required availability. Agencies can then target the search and quote on a comparable basis.
Clarify the work before the job title
A systems engineer, cloud specialist and project lead do different work. Identify development, operations, support, security, data or leadership. Describe responsibility: maintaining an existing system differs from building a new platform.
For several vacancies, distinguish roles and workloads in one brief. Seniority should reflect duties and decision responsibility, not just years of experience. A service with a defined deliverable may be better requested as the relevant IT project.
| Area | Specify in the profile |
|---|---|
| Development | Application, technology, maintenance or new development |
| Operations and support | Systems, user support, working hours |
| Project or leadership | Goal, responsibilities and collaboration |
Define relevant technology requirements
Name the main platforms, programming languages or applications and how they are used. Listing every product in the business rarely makes a good profile. Separate essential practical experience from knowledge a suitable specialist can deepen on joining.
For cloud, data and AI, operations, architecture, data preparation or integration are more precise than a broad label. A certificate can be an indicator but does not replace relevant experience. Describe interfaces and teamwork without publishing credentials, source code or confidential system plans.
Separate employment, temporary assignments and projects
With direct hiring, you become the employer. In labour leasing, the agency employs the specialist and supplies them for the assignment. Project support may use another contract model. Clarify parties, direction and billing instead of treating every time-limited project as a freelance engagement.
Switzerland has different requirements for placement and labour leasing. Check the appropriate permit and any additional cross-border scope. For project work, review duties, deliverables and the contract together; the contract title alone does not establish the actual working arrangement.
Make technical screening understandable
Ask how the agency checks practical ability, availability and fit with the role. A profile should explain relevant experience rather than list keywords. Define what the agency assesses and which technical decisions your team makes.
Use a structured interview or a short relevant work sample when useful for the role. Agree its scope and evaluation in advance. Selection does not need production-system access; obtain prior consent for reference enquiries.
Establish a comparable cost basis
For direct hiring, compare the recruitment fee, salary basis, minimum and payment trigger. Planned annual salary is not the recruitment fee. Check workload, variable compensation and charges for advertising, extra assessments or a replacement search.
For a time-limited assignment, use the same assumptions about workload, duration, on-site days and billing unit. Ask what the rate includes and what travel, standby or extra charges apply. An hourly rate without volume cannot be compared with a one-off recruitment fee.
| Quote item | Check |
|---|---|
| Direct hiring | Fee basis, minimum, trigger |
| Time-limited assignment | Workload, duration and included costs |
| Screening | Technical assessment and extras |
| Replacement or cancellation | Conditions and financial consequences |
Plan work arrangements and onboarding
On-site, hybrid and remote work create different search requirements. Specify the actual location, required attendance, working languages and desired start. A realistic project period and main duties help; an urgent request does not guarantee an immediately available specialist.
Plan a contact person, onboarding and later handover. Set up access according to the actual duties. For limited assignments, documentation, knowledge transfer and removal of permissions form part of the agreed close.
A short, informative brief
An initial request needs the main area, role, essential skills, count, workload, work arrangement, location and timing. Add planned salary if known for direct hiring, or duration for limited support. One common field can explain differences between roles.
CVs, confidential project documents and credentials are unnecessary for quote comparison. Agree later applicant-data handling purposefully and securely. Compare the actual mandate and terms rather than promised speed or the size of a profile database.
Frequently asked questions
How much does IT recruitment cost?
It depends on the role, search and contract. Recruitment fee, annual salary and an hourly assignment are different cost items.
Must every technology already be mastered?
Separate essential experience from learnable skills. Duties and onboarding opportunities define the profile.
Are freelancers and temporary staff the same?
No. Clarify employer, contract and actual work organisation. The project name alone does not determine the model.
Can I recruit several IT roles together?
Yes. State the total and explain differences in roles, technology and workload in the common brief.
Must I provide access or source code?
Not for the initial request. Describe duties and technology; confidential material and later access are handled separately.
Is rapid placement assured?
No. Availability, requirements and selection affect timing. Agree progress updates and assess specific profiles.
