What should an IT freelancer in France charge, and is demand rising?
Daily rates (TJM) and demand for 31 tech profiles, calculated from over 100,000 offers since 2022 and rebuilt every day as open data.
freelance.shellbear.me · data.json · Data history
-
What can I charge? The median rate and usual range for your stack or role, and how they have moved over time.
-
Is demand rising? Offers per month, and the change over a year.
-
What moves my rate? Experience, remote work and location, plus the skills most often requested alongside yours.
-
How do profiles compare? Every profile side by side, sortable by rate or demand.
-
Which profiles are growing?
/tendancesranks profiles by their change in offers over a year, with their median rate, in views by family (engineering roles, languages, mobile, infra and security, data and AI, management) and by technology (Databricks, Vue, LLM…). Each view can be copied as an image or downloaded as CSV. -
What is open right now?
/missionslists the missions currently online on Free-Work, Freelance-Informatique and Silkhom, filterable by profile, rate, region, remote work and experience. Each advertised rate is drawn against the profile's usual range from the statistics, so missions above or below the market stand out. Each one links to the original listing; a mission found on several platforms appears once with a link to each.
Every statistic comes from one file, public/data.json, updated daily under CC BY 4.0. Each update is a commit, so git log -p public/data.json gives you the full history.
curl -s https://freelance.shellbear.me/data.json \
| jq '.categories[] | select(.id == "go") | {n, rate}'Each entry in categories contains:
| Field | Meaning |
|---|---|
id, label, group |
The profile |
n, nPrior |
Offers in the last 12 months and the 12 before that |
rate, ratePrior |
25th, 50th and 75th percentile for those periods |
volume |
Offers per month, aligned with the top-level months |
p25, p50, p75 |
Rate per month, over a trailing 3-month window |
experience, remote, location |
Rate and offers per group, over the last 12 months |
skills |
Most requested skills, as a share of tagged offers |
subgroups |
Offers and median rate per technology or specialty within the profile, in both periods; each offer counts once |
The top-level remoteByMonth is aligned with months and gives, for each month, the offers stating a remote mode (n) and how many are on-site (none), hybrid (partial) or fully remote (full). It is null before 2026, when Free-Work did not report the mode, and for months with fewer than 100 such offers.
Please credit this project and Free-Work, the source of the offers. This project is independent and not affiliated with Free-Work.
- Advertised rates: these are the rates shown in offers, not what is actually invoiced. When an offer gives a range, its middle is used.
- Reposts: an offer republished by the same company within 30 days counts once. Without this, a single reposted offer can dominate a small profile.
- Profiles: offers are sorted from their title, with Free-Work's job label as a fallback. An offer can count in several profiles. The rules and their tests are public, and they can be wrong.
- Small groups: groups of fewer than 5 offers are not published.
- Known gaps: some collection days are missing, so a drop in volume isn't always a drop in the market. Experience, remote and location data only exist from early 2026.
There is no server and no public database. A daily job produces static files.
flowchart LR
A[Free-Work API] --> B[GitHub Actions<br/>every day]
C[(Private Parquet<br/>on Cloudflare R2)] <--> B
B --> D[data.json<br/>committed to git]
D --> E[Static site on<br/>Cloudflare]
pipeline/fetch.tsmerges the last 7 days of offers into a private Parquet file, so a failed run heals itself the next day. Descriptions are not stored.pipeline/build.tsturns that file into aggregated statistics. The offer history never leaves the private file.- The workflow deploys the site and commits
data.json. If the job ever stops, the page shows a warning once the data is more than 3 days old.
Each profile also has a plain page at its own address, such as /tjm/developpeur-python, with a table of all of them. The interactive page draws its figures with JavaScript on a single address, which search engines read poorly, so pipeline/build-pages.ts writes the same statistics as text from data.json, along with the sitemap. These pages are built at deploy time and not committed. Their addresses are listed in pipeline/pages.ts and must not change once published.
The missions page has its own list. pipeline/build-offers.ts reads the offers open today on each platform (one adapter per platform in pipeline/sources/) and writes offers.json with what is needed to filter and link out: title, company, advertised rate, place, remote mode, experience and date. Descriptions and contacts are never read. The file is rebuilt from scratch every day, so an offer that left its platform leaves the list, and it is neither committed nor part of the open data. If a platform can't be read, its offers are carried over for up to 3 days.
Built with Bun, DuckDB and uPlot, with no framework. The page weighs about 40 KB, plus 130 KB for its font, Bricolage Grotesque, which is served by the site itself and kept by browsers for a year.
bun install
bun run dev # the site with the committed data.json, on http://localhost:8787
bun run verify # formatting, type checking and testsThe private offers file isn't in this repository, so bun run fetch and bun run build only work for maintainers. Improving how offers are sorted doesn't need it: add a real title to the tests, update the rules and open a pull request.
Code under GPL-3.0. Statistics in public/data.json under CC BY 4.0.


