Lindner:



How you even call git a trend baffles me.

This is not about me, it is just what it is whether you like it or not.

Please tell me again, how would you pick out 20 applicants out of 1000 (without work experience) for an interview? You'll interview all 1000? Or you'll send all 1000 a DSA to complete(as has been mentioned here) and review each?

And I'm not a recruiter.

I'm just wondering, what is the problem people have with committing their codes?

You have no experience, how else do you show someone who doesn't know you and probably thousands of miles away what you can do? Word of mouth?

Plus, almost every team uses git in their everyday activity. This is the tool that you'll most likely be using IF you get hired. Can you even use it? Git and Github is like the most basic tool....

I dont know how else I can emphasize this especially for someone without experience. You have no portfolio and then you have phobia of committing your work so that people can just go there and check you out and reach out to you.

I'm curious what these people send in their job applications. Just resume? We focus too much on the technical aspect of our industry. The professional part is extremely important as well.

Before I learned anything, I learned git first and best practises. Thanks to the advice from mentors ahead of me.

So what is the issue here? No one is saying you should know everything about git. Two commands: "git add" and "git commit" intermittently as you code.

I think people should begin to focus more on being professionally attractive as we are acquiring this so called knowledge.

For emphasis, save yourself the time. NOBODY KNOWS WHAT YOU CAN DO IF YOU DON'T SHOW THEM. NOBODY WILL FIND YOU IF YOU DON'T MAKE YOURSELF "FINDABLE". From the day you start writing "Hello World", create a github account and commit everything.

Seun:
If you can explain to me how you got the job, I'd be very grateful.

Eggovic:

I don't know why I read this screaming. Your points are valid though. It's part of the reason most recruiters ask for your Github link when applying.

Lindner:



Unfortunately, going by the feedbacks on this thread, a lot of people don't give a damn about it. Most of the applications i sent out without getting a response from recruiters was when I had scanty github contributions.

Thank God for mentors, it changed dramatically. I didn't know there was something called job application package specific to software development roles.

1. Completed github profile with solid contributions (Open source projects inclusive). With links to your email, portfolio, linkedin e.t.c)

2. Professional linkedin profile. Also tailored and well crafted for software development.

3. Resume (Tailored for software development roles).
4. Cover letter (Needless to say it should be tailored to a particular role).
5. I even built a solid Angelist profile.
6. Stackoverflow profile.

"Miraculously", these changed the game for me and saved me from blindly applying to jobs without getting any response. Since then, I've worked at multiple projects and orgs (only US orgs).

Plus my experience, now I get an average of four unsolicited invitatitions from head hunters per month.

The reason for this shalaye is that technical knowledge is not enough. Sadly.

Lindner:



Unfortunately, going by the feedbacks on this thread, a lot of people don't give a damn about it. Most of the applications i sent out without getting a response from recruiters was when I had scanty github contributions.

Thank God for mentors, it changed dramatically. I didn't know there was something called job application package specific to software development roles.

1. Completed github profile with solid contributions (Open source projects inclusive). With links to your email, portfolio, linkedin e.t.c)

2. Professional linkedin profile. Also tailored and well crafted for software development.

3. Resume (Tailored for software development roles).
4. Cover letter (Needless to say it should be tailored to a particular role).
5. I even built a solid Angelist profile.
6. Stackoverflow profile.

"Miraculously", these changed the game for me and saved me from blindly applying to jobs without getting any response. Since then, I've worked at multiple projects and orgs (only US orgs).

Plus my experience, now I get an average of four unsolicited invitatitions from head hunters per month.

The reason for this shalaye is that technical knowledge is not enough. Sadly.

Seun:
If you can explain to me how you got the job, I'd be very grateful.

jesmond3945:
ah seun himself dey look for work o

Lindner:


Is this THE SEUN?

Does not necessarily mean everyone on this thread is looking for work though.

Most times I'm on nairaland when I feel like throwing my system through the window or smashing it against the wall out of frustration. Like right now. 15 minutes task has turned to 4 days of bugs from hell.

Lindner:


Is this THE SEUN?

Does not necessarily mean everyone on this thread is looking for work though.

Most times I'm on nairaland when I feel like throwing my system through the window or smashing it against the wall out of frustration. Like right now. 15 minutes task has turned to 4 days of bugs from hell.

Lindner:



Unfortunately, going by the feedbacks on this thread, a lot of people don't give a damn about it. Most of the applications i sent out without getting a response from recruiters was when I had scanty github contributions.

Thank God for mentors, it changed dramatically. I didn't know there was something called job application package specific to software development roles.

1. Completed github profile with solid contributions (Open source projects inclusive). With links to your email, portfolio, linkedin e.t.c)

2. Professional linkedin profile. Also tailored and well crafted for software development.

3. Resume (Tailored for software development roles).
4. Cover letter (Needless to say it should be tailored to a particular role).
5. I even built a solid Angelist profile.
6. Stackoverflow profile.

"Miraculously", these changed the game for me and saved me from blindly applying to jobs without getting any response. Since then, I've worked at multiple projects and orgs (only US orgs).

Plus my experience, now I get an average of four unsolicited invitatitions from head hunters per month.

The reason for this shalaye is that technical knowledge is not enough. Sadly.

Grandlord:


True.

Many companies don't do whiteboard interviews. It's straight up project-based.

I think there's a subreddit where companies in that category are listed.

Xinjin:
as a working dev, do you get a fixed time to complete a task?

Xinjin:
Your points are valid. I had an interview last week, and was asked why my github didn't match my years of experience, lol I had to pause. since then I stop applying and now focus on updating my github.

Lindner:


Sure.

Most tasks have a deadline and other devs depend on your output as well.

Lindner:



Unfortunately, going by the feedbacks on this thread, a lot of people don't give a damn about it. Most of the applications i sent out without getting a response from recruiters was when I had scanty github contributions.

Thank God for mentors, it changed dramatically. I didn't know there was something called job application package specific to software development roles.

1. Completed github profile with solid contributions (Open source projects inclusive). With links to your email, portfolio, linkedin e.t.c)

2. Professional linkedin profile. Also tailored and well crafted for software development.

3. Resume (Tailored for software development roles).
4. Cover letter (Needless to say it should be tailored to a particular role).
5. I even built a solid Angelist profile.
6. Stackoverflow profile.

"Miraculously", these changed the game for me and saved me from blindly applying to jobs without getting any response. Since then, I've worked at multiple projects and orgs (only US orgs).

Plus my experience, now I get an average of four unsolicited invitatitions from head hunters per month.

The reason for this shalaye is that technical knowledge is not enough. Sadly.

Nabi2000:
Just to add to this topic that there’s no one size fits all in every aspect of life, and nobody knows the defined path, I got a job in about two months after actively applying, actually I got about 6 offers in the space of the 2 months and I still get offers till today. My commits are very minimal, in fact I only make a commit when I’m done with a personal project, I do however have a portfolio that speaks for me and even though I didn’t have experience I was/am still headhunted. If GitHub counts are the metric behind getting jobs then that is a really shallow way of employing people.

ovanda:
Good day All. Please seniors, help me become a standard java programer. I know Java and I just finished learning Spring,I am moving on to spring boot now. Before now I thought I was going the right way until I stumbled on this post. My plan was that after learning spring boot, I'd also learn spring cloud,microservices, spring security and Docker,in that order. After learning all these,I also intend to brush up my skills in HTML and CSS,I used to be good with until I left it. I also planned to brush up on JavaScript,I used to know that one too , and then I would go ahead and build myself a portfolio, update my LinkedIn profile. But with talk to GitHub I saw here,I don't know if I am going in the right direction. Please,I beg you guys someone should please point me in the right direction plzzzzzz?

Lindner:


If only you used a bit more effort to read through the post, you'll have seen where I referenced "solid repositories" and I'm sure I mentioned "before recruiters go into the detail".

Good luck getting a job with 50 commits as a beginner without experience. Most times, you'll only get to Data Structures and Algorithm stage IF you don't get screened out with your 50 commits.

I never did Data Structures based interview even as an entry level applicant. Thats not to say its not relevant though. Many organisations are adopting take-home "real" application development.

tensazangetsu20:


Honestly when I was searching for my first job I had just like 50 commits on GitHub.

Your projects are what will give you job interview. Then you need data structures and algorithms to ace the coding interview. Once you are sure your projects are good and up to standard you are better off spending time on leetcode and solving questions everyday.
.