I have conducted several interviews with junior candidates, and often when I inquire about their GitHub profile, they respond by saying they do not have one or have not uploaded any projects.

This is not ideal because it puts me in a position where I have to depend on Leetcode problems to evaluate their coding skills.

Here is how your GitHub profile helps me assess your skills.

You Know Git

This is a big plus because I don't have to waste time asking about some git commands. I can directly look at them on your profile. This also shows how well you write commit messages that describe your changes, how you manage branches in a repository, and their pull requests. All of these are very essential for working in a team.

git commit -m "fix #3: median price floating point fixed to 2"

Showcasing Skills

If you already have some impressive projects on your profile then I am not going to ask you any Leetcode problems because I can see that you can do the job. I can directly see how well you manage the state between different components, your understanding of async code, and how well you utilize different life cycle methods a framework has to offer.

 useEffect(() => {

        //Implementing the setInterval method
        const interval = setInterval(() => {
            setCount(count + 1);
        }, 1000);

        //Clearing the interval
        return () => clearInterval(interval);
    }, [count]);

Documentation

A well-documented repository shows that you have good communication skills and can explain technical topics very well. This means that you understand a problem and have the ability to convey it to others on a level that they can understand and help you out.

Code Organization

I can go through your projects and see how well you have organized your code. It demonstrates that you value clean code which is highly desirable when working on large code bases.

Having a GitHub profile is essential for increasing your chances of getting hired and standing out from other candidates during the interview process.