GitHub helped me get not just one job, but two! I used GitHub as my strength in technical interviews for part-time consulting jobs. Similarly, when I applied for my current full-time front-end programmer position at the company, I was asked to provide a GitHub address link. When you are facing an employer, you need to have leverage. Not only do they need to know how much you know about specific languages and frameworks, but it’s important for them to see that you have a comprehensive ability to know more than some programmer who can only write spaghetti code!

See noodle code

GitHub is a place where you can show code. For example, when you learn a new technology, you can create a repository of that technology and upload it to GitHub. There are four benefits to doing this:

• You can demonstrate that you understand the technology, the language or the framework
• People can see that you’ve written good code, you can architecture it to make it clean, you know OOP, you can write SOLID. The recruiter can also show this to other members of the company’s team to decide whether to give you a first-round technical interview
• You have at least basic Git to maintain your repositories on GitHub
• Employers will email you based on the language you use in GitHub’s repository, and the process is automated. I got about 10 of them. So, if your repository is written in C#, you are likely to receive an invitation to interview for a C# position. An email from a recruiter isn’t much, but at least it’s an opportunity. You’re in a situation where employers are coming to you, not you, and trust me, it’s a lot easier

I’ve done that. I received a similar invitation for an interview. However, I did not do this for all projects, and some projects were created in GitLab and only visible to me. I wanted to sell them in the future, but I didn’t finish them. But now I regret not making them public. If I publish them as an open source project and document how they work and look, they can be added to my resume portfolio.

My repositories on GitHub

I have also contributed to a number of Ember related Repositories. Sometimes it’s documentation, sometimes it’s code. Your contributions to some of the big projects will be helpful in your job search. But in terms of this job search, they didn’t help me very much.

My comments on ember.js repository

Stack Overflow account, August 2016.

I’ve written programs in a variety of languages and frameworks. Net & Mono developed the game service list, XNA, Java services, C# WPF programs to write the computer version of the tower defense game. The only thing that might interest me is using the Internet to get and send data.

My strength is ember.js. I started learning it when I was 16 (2013) and then I watched Yehuda Katz’s video at the HTML5 conference in San Francisco — truly remarkable. And that’s when I started learning Ember. I needed more motivation and determination. The words in this video have stuck in my mind ever since I first heard them.

Whatever you do, be passionate about it.

Back to Stack Overflow. In the beginning when I was in the learning phase, I asked questions from above. Then I started answering other people’s questions to get popularity points. I open up all new questions and try to answer them as quickly as possible before they become a hot topic, such as JavaScript. The question about Ember is easier for me. I spent a lot of time writing down my answers and analyzing the complicated questions in detail. Very few people answer these kinds of questions.

Sometimes I was no. 1 for 30 days, so I had followers, and then I got a lot of interviews in the mail. One of them is a remote part-time adviser to ember.js. I got an invitation for an interview for answering a person’s question in Stack Overflow Ember! This is real. This is proof.

A screenshot of the email.

Later I had a technical interview about my understanding of Ember. I passed. Since November 2015, I’ve been working as a technical consultant for Ember.js.

Creating a Stack Overflow career profile page is also important for two reasons:

• You’ll get a cool resume with all the answers you answered on Stack Overflow
• Recruiters will find you on it and send you a private message, and more than two recruiters have contacted me on it, and they were serious enough to send me an interview invitation

My Stack Overflow resume

conclusion

Believe in yourself and try harder. And showcase your skills on Stack Overflow and GitHub. Contribute to a public open source project and create your own repositories. Let people know you. Tell them where you live and how competent you are. Tell them about your passion. In the tech industry, recruiters try to find people like you every day. Make it easy for them to find you.

Thanks for reading. Welcome to share if you like. If you have a different opinion or better story to share, feel free to leave a comment! I welcome any feedback!