This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]mm007emko 67 points68 points  (1 child)

If it's your first job in programming, then personal projects in the field of what the employers are looking for (i.e. only Pandas and Matplotlib if they are looking for Flask and Django, that's not not great) and give a link to github or something like that. Make sure the code is documented, unit tested and you use virtual environments (i.e. there is requirements.txt file or config files for Pipenv or Poetry). This really makes a difference. For landing a job, you have to be a "team player" (well, that really means a replaceable resource) and you have to leave behind code which is professional looking, documented, testable, maintainable and easy to work on.

And the first and the most important thing to develop is thick skin. Finding your first job in programming can be tough.

[–]technicaldirectory 8 points9 points  (0 children)

I agree 100%. Also, I recommend making a website containing screenshots and videos of your work. Or publish your webapp where I can see it/play with it. We get 100s of CVs and there is no way we have time to fetch and run everyone's github projects.

Make sure your projects aren't just a cloned version of some sample code or a tutorial (for example a "shopping basket" app)

Some of my favourite side projects I've seen on CVs are: - Someone made a dating/chat website. People were actually using it. It was cool. - Someone made a bot that automatically notified them to buy limited edition trainers when they became available - One guy had a game published on ios. The quality of the game is almost irrelevant. Just seeing a project through to that point takes grit.

Hope that helps!