Loading...
In the US job market, saying 'I know how to do this' is worthless. You have to prove it. Think of your projects as your digital shadow.
What counts as a real project
A real project is not a tutorial you followed on YouTube where you just copied code. If 10,000 other students have the same 'Weather App' or 'To-Do List' on their resume, it's not a project, it's homework. A real project solves a specific problem. If you had to make a decision or fix a bug that wasn't in a tutorial, it's a real project.
How many projects are enough (and when to stop)
Do not fill your resume with ten small, weak projects. It makes you look like a beginner who just dabbles in everything. You only need 2 or 3 high-quality projects. Stop building new things when you can talk for 10 minutes about the challenges of one project.
Turning class projects into portfolio assets
You are already doing work for your classes. Don't let that work die in a folder on your laptop! Most class projects are 'ugly.' To make it an 'asset,' you need to add a 'Presentation Layer.' Take that class assignment, clean up the notes, add a 'Lessons Learned' section, and give it a clear title.
GitHub hygiene (readmes, demos, commit quality)
If you are in a technical field, your GitHub is often more important than your resume. A project without a README file is like a book without a cover. Your README should explain: 1) What is this? 2) Why did I build it? 3) How do you run it? Use clear commit messages like 'Fixed login bug' instead of 'update1' or 'final final.'
Personal website (when it helps, when it doesn't)
If you are in Design, Marketing, or Front-End Development, you need one. It shows your style and your ability to build a user experience. If you are a Back-End Engineer or a Data Scientist, a clean GitHub profile or a well-written LinkedIn article is often better than a mediocre website. Only build a website if you are willing to keep it updated.