Freelance IT missions
Freelance IT missions in France cover development, data, infrastructure and cybersecurity, on contracts of three to twelve months. Technical skill is rarely the sticking point: what ends a mission early is the gap between how the expert works and how the team receiving them works.
Written by Robertino CalcaterraLast updated:
What kinds of IT missions exist?
The French market splits into four broad families, and expectations differ sharply between them.
Development. Front-end, back-end, full-stack. These are the most numerous and the shortest missions: reinforcing a roadmap that has slipped, picking up an abandoned project, scaling up before a launch. The stack asked for changes fast, but the underlying demand is steady.
Data and AI. Data engineering, data science, building pipelines, putting models into production. Longer missions, often six to twelve months, because the time needed to absorb the business context is real. It is also the segment where expectations are most often vague at the start.
Infrastructure and DevOps. Cloud, containers, CI/CD, observability. Technical work, but heavily cross-team: the expert works with teams that each have their own habits, and a good share of the job is getting changes of method accepted.
Cybersecurity. Audit, compliance, incident response. A tight segment, with short and high-pressure missions, where being able to frame a risk for non-specialists counts as much as the technical expertise.
What day rate in IT?
The day rate depends on the speciality, the seniority, the location and the legal status. The ranges circulating online vary so much from one source to another that they are no help in deciding.
Rather than an indefensible figure, we built a day-rate calculator that starts from your income target, your billable days and your actual charges. The contribution rates it uses are the official French ones, checked against the open-source libraries that run URSSAF's own simulator.
What companies are really looking for
Job ads talk about technologies. Interviews talk about technologies. Missions that end early, almost never.
What comes up most often fits into four points, none of which a technical test measures.
Autonomy on poorly documented code. Most missions involve working on something that already exists and that nobody has time to explain. The question is not whether you can code, it is whether you can make progress without a complete specification.
Written communication someone can use. A large share of these missions is partly remote. An expert who does not document their decisions creates a dependency the company pays for after they leave.
Being able to work with the in-house team. Teams have their conventions, sometimes questionable, often old. Arriving and wanting to redo everything is the fastest way to stall a mission.
Flagging a problem early. A blocker raised in week two costs a fraction of what it will cost in month three.
Why do IT missions fail?
Rarely for technical reasons. The Leadership IQ study, which tracked 20,000 hires across 312 organisations, attributes 89% of failures to behaviour rather than technical skill. Technical ability accounts for only 11% of the causes. Worth noting that Leadership IQ is a private consultancy, not a peer-reviewed journal: the figure is a strong directional signal, not a precise measurement.
In IT specifically, three mismatches recur.
The pace of decisions. An expert used to deciding quickly in a small structure lands in a large account where every technical choice passes through three approvals. The skill is there; the frustration arrives in month two.
The level of autonomy expected. Some companies hand over a problem, others a specification. An expert waiting for precise specs in a company that expects proposals comes across as passive, when they are doing exactly what they believe was asked of them.
The relationship to quality. An expert who refuses to ship code they consider substandard is an asset in one context and a blocker in another. Nobody discusses this before signing.
None of these three shows up in a technical interview. All three show up in a behavioural assessment.
How to find a mission that actually fits you
By stopping the search at the stack. Two React missions at the same day rate can be completely different experiences depending on the level of autonomy, the pace of decisions and the team's culture.
Four questions to ask before accepting: am I being given a problem or a specification? How many people have to approve a technical choice? What happens when someone disagrees in this team? How reliable is the documentation that already exists?
That is precisely what Migbirds assesses before proposing a mission: not only what you can do, but how you work, and whether that matches the mission's actual context.
Frequently asked questions
What day rate for a freelance IT mission?
It depends on the speciality, the seniority and your legal status. Rather than a generic range, our day-rate calculator starts from your income target and your actual charges to work out the rate you need, using the official French contribution rates.
Do you need to be a micro-entrepreneur to take a freelance IT mission?
No. Micro-entreprise, EURL, SASU or portage salarial all work. Your status changes your tax and your cover, not your eligibility for a mission. Worth knowing: portage gives you unemployment insurance, micro-entreprise essentially does not.
How long does a freelance IT mission last?
Three to twelve months depending on the family of work. Development tends to sit around three to six months; data and infrastructure more often run to twelve, because absorbing the business context takes longer.
How can I tell whether a mission will suit me before accepting it?
By asking about how the team works, not only about the technology: the level of autonomy expected, how many approvals a technical choice needs, what happens when there is a disagreement. Two missions with the same stack and the same day rate can be very different experiences.
Other sectors
Missions that match the way you work
Migbirds assesses soft skills, motivation and behavioural fit to anticipate whether a mission and you will genuinely work together. Before the commitment, not after.
Create my free profile