"Free" is doing a lot of work in that headline, so let's be honest about it upfront: free usually means you pay with effort instead of money, and that is actually the point. A certificate that costs nothing but also asks nothing of you is worth exactly what you paid for it. The ones below ask something real, which is why they are worth your time.
The IBM Bobathon route
The IBM Bobathon is an exciting IBM Bobathon challenge, built with IBM Bob, an agentic AI software development tool that can read, fix and modernise code across a whole repository. The scenario, called The Legacy Fix, puts you in the role of a junior engineer fixing a broken program in your first week at a German car-parts company, a constructed training scenario, not a real company's real fault data.
It takes two to three hours, runs in English, and needs nothing but a laptop. It is free to attempt. It is not free to pass: about three in ten participants do not, based on ProoV's own grading data. Pass it and you get an IBM SkillsBuild certificate of completion, plus a ProoV scorecard tied to a link a recruiter can check directly. For the full walkthrough, see our guide to the challenge.
ProoV projects generally
Beyond the Bobathon, ProoV runs a full catalogue of graded projects across data, engineering, product and more, each one taking roughly two to three hours. Every project ends in a scorecard against a published rubric and, on a pass, a certificate anyone can verify by link. Free to sign up, and browsing the catalogue is worth doing even if you only complete one.
IBM SkillsBuild courses
Separately from the Bobathon, IBM SkillsBuild offers free structured courses across AI, data, cybersecurity and cloud, with digital credentials at the end. These are attendance and exam-style credentials rather than work-verified ones, which is not a criticism, they are genuinely useful for building a foundation. Just be clear-eyed about what finishing a course proves versus what finishing a graded project proves, and treat the course as preparation rather than the finished proof itself.
Your university's career service
If you are enrolled at a German university, your career service is very likely offering things you have not checked: CV reviews, mock interviews, workshops on specific tools, sometimes free access to paid learning platforms through a university licence. Very few students actually walk in and ask. It costs nothing but the time to book an appointment, and the advice is usually specific to the German market in a way generic online guides are not.
Open source contributions as proof you made yourself
You do not need someone else to hand you a certificate to build proof. A well-documented pull request to a real open-source project, one that was reviewed and merged by maintainers who did not know you, is its own form of verification: the "grading" is the fact that someone with a reputation to protect accepted your change. Pick a project you actually use, start with a small, real bug rather than a cosmetic fix, and keep the link. It costs nothing but time and the discomfort of having your first attempt reviewed in public.
A sensible order to do these in
You do not need all five at once, and trying to would just spread your effort thin. A reasonable sequence: start with a free SkillsBuild course if you want the underlying concepts first, then move to something graded, the Bobathon is a good first graded attempt because it is short and beginner-friendly, then use what you learn about your own gaps to pick your next ProoV project or your first open source pull request. Book the career service appointment whenever you like, it costs nothing and does not compete with the others for your time.
What to skip entirely
Two anti-patterns are worth naming directly, because both are common enough that you have probably seen them in a group chat.
Paying for a certificate mill. If a site's entire business model is selling you a certificate after a short quiz with no real assessment behind it, it is not proof of anything, and a recruiter who has seen a few hundred CVs will recognise it instantly. Money changed hands, but nothing was actually graded.
Listing ungraded course completions as skills. "Completed a Python course" and "can debug a real Python program" are different claims, and listing the first as though it were the second is the fastest way to lose credibility in an interview, the moment someone asks you to actually do the thing.
The common thread across every option above that is actually worth your time: something outside your own claim confirms the work happened and holds up. Chase that, not the badge.
