Skip to content
Cyber Recrut

Probation for security hires: setting clear objectives

Probation for a cybersecurity hire: the French legal frame, observable objectives by role, checkpoints and the final decision. A method for managers and CISOs.

Published on 7 min read

Many probation periods in cybersecurity end on a feeling rather than a finding. The manager "senses" that the new hire is up to the job, or that they are not, without being able to say what that rests on. This guide offers a simple method to set clear objectives from day one, track them and reach a decision both sides understand.

Before talking about objectives, a few reference points from the French Labour Code (Code du travail) for a permanent contract (CDI). They do not replace your collective agreement and the employment contract, which may set shorter periods.

PointWhat the Labour Code provides
Maximum initial length (article L1221-19)2 months for employees, 3 months for supervisors and technicians, 4 months for managers and engineers (cadres)
Renewal (article L1221-21)Once only, if an extended industry agreement allows it and the contract mentions it
Formalities (article L1221-23)Probation is never presumed: it must be written in the contract or offer letter
Employer notice period (article L1221-25)From 24 hours to one month depending on how long the employee has been present
Employee notice period (article L1221-26)48 hours, reduced to 24 hours under eight days of presence

Two practical consequences follow. First, renewal requires the employee's explicit agreement: it is never a formality to slip in at the end. Second, probation exists to assess skills and fit for the role. Ending it for an unrelated reason exposes the company. Current texts are available on legifrance.gouv.fr.

Why it is harder in cybersecurity

Assessing a salesperson over three months is already difficult. Assessing a security professional is harder still, for four reasons.

  • The value is often invisible. An analyst who triaged alerts well, an engineer who hardened a configuration: when the work is done right, nothing happens. Without written objectives, nothing shows.
  • Context takes time. An experienced hire knows their tools, but needs weeks to understand your critical assets, your flows and your historical exceptions.
  • Access arrives gradually. For good security reasons, the new hire does not get every permission on day one. Blaming them for delays caused by late access would be unfair.
  • The environment changes during probation. An incident, an audit or a migration can upend the plan. Objectives must be able to adapt without losing their meaning.

None of this justifies having no objectives. It simply means choosing them with care.

Setting objectives that actually help

A good probation objective is observable, tied to the real duties of the role and achievable in the time available. "Get up to speed on the SIEM" meets none of these criteria. "Handle level 1 alerts on the email perimeter alone, with occasional review" meets all three.

Start from the job description

Objectives should follow from what was announced during hiring. If the job description promised detection work and the new hire spends weeks managing user accounts, the gap comes from the company, not from them. Reread the job description before writing the objectives, and fix one or the other if needed.

Cover three dimensions

To avoid a purely technical assessment, set objectives in three areas:

  1. Technical: what the person should be able to do alone by the end of probation.
  2. Context: what they should know about your environment, procedures and key contacts.
  3. Behaviour: how they communicate, escalate and document. Our article on soft skills in cybersecurity covers the ones that really matter.

Three to five objectives are enough. Beyond that, nobody follows them.

Examples by role

RoleTechnical objectiveContext objectiveBehaviour objective
SOC analystTriage common alerts on a defined perimeter aloneKnow the critical assets and escalation proceduresWrite tickets the next shift can act on
PentesterRun a test on a simple scope, from preparation to reportMaster the team's methodology and report templatesPresent findings to a client without overstating or downplaying them
GRC analystLead a risk analysis on a limited scopeKnow the internal framework and audit deadlinesGet answers from operational teams without blocking their work
Cloud security engineerPropose and get approval for a fix to a real misconfigurationUnderstand how accounts or subscriptions are organised and the deployment rulesGet a change accepted by development teams

These are starting points. Adjust them to the target level: you do not expect the same autonomy from a junior and from an experienced hire.

Planning checkpoints

Objectives you only reread on the last day are useless. A simple schedule is enough, matched to the actual length of the probation period.

  • Day one: present the objectives in writing, check they are understood and ask the new hire what seems unclear or unrealistic.
  • After the first third: a short check on onboarding. Is access in place? Is the buddy available? This is the time to fix what is blocking.
  • Halfway: a real review, objective by objective. If a gap appears, say so clearly and agree on what needs to change. A new hire should never discover a problem at decision time.
  • Before the deadline: the decision, made early enough to respect the notice period. The longer the employee has been present, the longer that notice: plan several weeks ahead.

For a SOC analyst, our 90-day onboarding plan offers detailed milestones that fit naturally with this schedule.

Confirm, renew or end

At the end of probation, there are three possible outcomes. Each one should be owned.

Confirm

This is the most common outcome when hiring was well framed. Use the final review to set objectives for the next six months: confirmation is not an end, it is the start of the development plan. It is also a direct lever to retain your cybersecurity team.

Renew

Renewal is only legitimate if a specific question remains open and can be settled in the extra time. For example, the new hire has not yet been assessed on call because the schedule did not allow it. Renewing out of caution, without knowing what more you expect, only postpones a decision and worries the person.

End

If objectives are not met despite genuine support, ending probation is a responsible decision. It will be better understood if the gaps were shared at the halfway review. Also ask yourself about the cause: an unrealistic objective, a misleading job description or poor onboarding are the company's responsibility, and will repeat with the next hire.

The most common mistakes

  • Writing nothing down. Verbal objectives drift, and everyone remembers them differently on review day.
  • Setting objectives the new hire does not control. "No major incident" does not depend on them.
  • Assessing on tasks missing from the offer. If on-call was never announced, it cannot become a criterion. Our article on remote work and on-call helps clarify this from the interview stage.
  • Confusing probation with onboarding. One assesses, the other supports. Both are needed.
  • Forgetting the new hire's view. The review runs both ways: they are assessing your company too, and they can leave.

In short

A useful probation period rests on a few written objectives, drawn from the job description and split between technical skills, context and behaviour. It is run with regular checkpoints, an honest halfway review and a decision made early enough to respect the legal frame. The result: fewer surprises, and a decision everyone understands.

Probation starts at the hiring stage. At Cyber Recrut, a recruiter and a security practitioner work with you to define the real duties of the role, and the candidates we present have proven their skills on hands-on labs. That gives you a concrete basis for writing their first objectives. See how we work or tell us about your hiring need.

Related articles