A free way to learn programming and have something real to show in a Werkstudent application: pick one project from the build-your-own-x list, finish it small, and put it on GitHub.
This page is for information purposes only. It is not legal, immigration, tax or financial advice, and StudentHubs does not give individual advice. Rules and processes vary by city and by personal situation, and they change over time. Before you act on anything that affects your residence permit, insurance, money or deadlines, confirm it with the responsible office, for example your Ausländerbehörde, Bürgeramt, Krankenkasse or BAföG office. Translations are AI-generated, and AI can make mistakes in translation. Please be aware of this, and if a detail is unclear or important to you, check it with the responsible office.
Many entry-level IT jobs, including Werkstudent (working student) roles, are filled by people who can show they can build something, not only that they watched lessons. A small project you finished, can explain and can change when someone asks "what if we needed X?" answers most of what an interviewer wants to know.
It also helps if your German is still growing. Code and a clear README speak for themselves, and you can talk through your own project in simple language because you know it better than anyone.
build-your-own-x is a public GitHub list kept by the CodeCrafters community (github.com/codecrafters-io/build-your-own-x). Its idea is to learn a technology by rebuilding a small version of it from scratch. It groups links to tutorials by topic, for example databases, Git, web servers, shells, text editors, programming languages, search engines and games, each in many programming languages.
Two honest warnings. It is a list of links to tutorials written by many different people, so some are excellent, some are outdated and a few links may be broken. And the tutorials themselves are not part of StudentHubs, so check each one before you commit your weekend to it: look at its date and whether it matches the language and tools you want to use.
Web or app development: look at the web server, template engine or front-end framework projects. Back-end or data work: try a small database or search engine. Operations, security or infrastructure: the shell, Git, Docker or network projects teach how the tools you will use at work behave underneath.
If you are not sure yet, a small Git or text editor project is a good first choice. It is easy to scope, you use the result every day, and you can explain it to a non-technical person.
Give yourself two to four weekends and a clear finish line, such as "it handles these five cases". A working small version beats an ambitious one you never finish. Put it in a public GitHub repository with regular commits, so your progress is visible.
Write a short README in English (add a few German lines if you like): what it does, how to run it, what you learned and what you would improve. Be ready to explain one decision you made and one thing you got stuck on. Honest answers about getting stuck read as strength, not weakness.
Do not copy a tutorial and present it as your own idea. Say which tutorial you followed, then show what you changed or added yourself. That is both honest and the part interviewers care about.
Search for terms like "Werkstudent Softwareentwicklung" or "Werkstudent IT". Werkstudent roles are usually limited to about 20 hours a week during the semester to keep the student status for social insurance, and are often more flexible in the semester break. Confirm the exact terms in the offer.
If you are a non-EU student, an off-campus job counts towards your 140 full or 280 half days a year, while on-campus roles such as a HiWi position do not. Read our guide on work hours before you accept, and keep track of your days.
When you apply, put the project link at the top of your CV next to your contact details. Our CV profile and career assistant tools can help you turn it into a German-style CV and cover letter.