freehire
freehire, the open-source search engine for job seekers
Runssource: GitHubhomepageGoMITcommit 900408d7e317
Go, MIT licensed. The project labels itself: ats, career, careers, golang, hiring, job aggregator, job board and job portal.
freehire runs. An Argusic agent installed it in 44 minutes and hit 5 errors on a clean machine with no GPU, and the whole session was recorded.
Postgres 17 (pgvector), Redis 7.4, Meilisearch 1.55, the Go API server on :8080, and the built SvelteKit frontend on :4173 are running; the API answered 200 on /health and /api/v1/jobs/search with 717 live Greenhouse jobs, and the web app served /jobs with real job links.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 94 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- go, pnpm, postgres, redis, meilisearch, poppler not on base image30 minutes
- go test ./internal/api/handler fails on PDF resume tests (status 400) when pdftotext not on PATH6 minutes
- web vitest fails with 'Tsconfig not found' / could not resolve node:module5 minutes
- cmd/billing-sync TestTheStoreProviderAloneKeepsTheWorkerRunning fails (run stops at gate with RevenueCat configured)3 minutes
- background children died with exec session; later server instances killed by harness
- Install time
- 44 minutes
- Cold machine to finish
- 46 minutes
- Errors hit and fixed
- 5 hit, 4 fixed with no human help
- How the result was proved
- go test ./... -> 238 ok, 1 pre-existing fail (billing-sync); curl localhost:8080/health -> 200; curl 'localhost:8080/api/v1/jobs/search?q=engineer&limit=3' -> 200 with 3 Stripe jobs; curl localhost:4173/jobs?q=engineer -> 200, HTML contains hrefs to /jobs/<slug>; npx vitest run in web -> 221 passed/2380 tests; pnpm build -> success; pnpm test in design-system -> 162 passed
- Model tokens used
- 4,427,854
- Exact commit tested
- 900408d7e317
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
**Notable observations:** - The only failing Go test is the pre-existing `billing-sync` stop-at-gate regression, unrelated to… - All 238 other Go packages pass, `go build ./...` and `go vet -tags=integration ./...` (the repo's… - Web: 221 test files / 2380 tests pass; production build succeeds. - Real end-to-end: crawled Stripe's live Greenhouse board (717 jobs), drained to Meilisearch, searc… ARNUSIC_RESULT: exec /bin/sh -lc "echo 'DONE'" in /work/repo succeeded in 0ms: DONE tokens used 4,427,854
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 44 minutes.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Hit 5 errors during setup, 1 of which were not solved.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.45 | |
| Argusic Runner | 1/3 | Runs | 96.00 | 0.93 |
Topics (from GitHub)
atscareercareersgolanghiringjob-aggregatorjob-boardjob-portaljob-scraperjob-searchjobslangchainllmmeilisearchpostgresqlrecruitmentremote-jobsself-hostedsveltesveltekit
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/freehire)Questions
- Does freehire run?
- Yes. freehire runs. Argusic installed and launched it on a clean machine in 44 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test freehire?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 900408d7e317. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test freehire?
- The run that produced this verdict cost $0.93: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does freehire take to install?
- 44 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does freehire need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing freehire?
- 5 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for freehire?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.