Bart Stefanski
Published on

🔖 Ideal Github Profile for a Junior Developer


I've checked out a lot of Github profiles of new developers. I've seen that many of them make small mistakes. These mistakes could make it hard to get a job.

Companies are cautious when it comes to hiring junior developers. It's not so much about the lack of experience, but more about the time spent in going through all the applications. This can be expensive.

So, making your Github profile as appealing as possible is crucial. Remember, those reviewing your profile may not spend too much time on it, so it has to catch their eye quickly. Github might not be the only significant part of your resume, but if they're viewing your Github profile, you've already crossed a significant hurdle - the HR screening.

The example of well described github

🚀 No Real Side Projects

If you don't have any public projects on your Github, you might not get the job. Make sure you have some projects using the technology you like. A good profile should have at least 1 big project and a few smaller ones. Your own website or blog may not be the best project to show. The same goes for todo apps, projects from YouTube tutorials, and shared bootcamp projects. Unique projects are better. They show you can create something by yourself, without following the tutorial step by step.

If you're uncertain about what kind of project would make a good addition to your portfolio, feel free to connect with me on LinkedIn. I'll be posting some ideas and guidance on this topic soon!

📝 No or Bad README

In the era of ChatGPT, there's no excuse for not writing a good README for your project. If you don't have one, it's never too late to start. A good README should have:

  • A brief description about the project and links to a live preview
  • Features of the project
  • Some DEMO images (put them in a 2x2 markdown table, not one under another - it makes the README hard to read)
  • A list of technologies used and why you chose them
The example of 2 images in row

📌 No Pinned Repositories

When someone visits your profile, they see six "Popular repositories". But these may not be the ones you want to show. Make sure the right repositories are easy to find. Recruiters don't have a lot of time and won't check every repo.

🎈 No Description for Repositories

A README is important, but before a recruiter sees it, they need to find your repo. Besides pinning it to your profile, add a short description about the project and its tech stack. Keep it short and use emojis if you want. The repository name can also describe the tech stack, like nextjs-banking-app or laravel-crypto-api.

Github's project description modal

📅 New Account

Some people might ignore this, but you should also look at your contributions graph. If your account is very new, they might think you don't know how to use git. It's not a big problem because you can change the date of your first Github commit (I don't recommend doing this). It's also not good if 90% of your contributions graph is empty. It might look like you don't use git or don't understand why it's important.

🖊️ Bad Recent Commit Messages

Nobody will look at all your commits. But... if your commit messages say things like

  • changed something
  • changed Button.tsx
  • update
  • i hate this

you probably won't make a good impression!

Example of bad commits

👤 No Profile Picture and Description

This isn't a big problem, but it might show that you're new to Github and don't know how to change your profile info. Some developers like to create a profile description. This is a good idea, but don't copy your entire resume there. Instead, put information you didn't include in your resume, like recent blog posts or your favorite technologies, socials, etc.

Example of profile

In closing, becoming a junior developer might seem challenging, but having a well-organized Github profile gives you a head start. It's crucial to present your work clearly, stay consistent, and showcase your unique qualities.

If you need more guidance or have questions, don't hesitate to reach out. You can connect with me on LinkedIn or send me a direct message. It's always a pleasure for me to assist new developers as they begin their tech careers. Good luck on your journey and always remember, continuous learning and improvement are key 🖖🫡