Hacker News new | ask | show | jobs
by codegeek 1348 days ago
If you are a "noob", barrier to entry for getting a remote job is higher. No one knows what track record you have. No one knows what are you capable of yet. No one knows if you can work remotely and learn at the same time. No one knows if you have the discipline and mental capacity to work remotely, alone.

So, you have more work to do. You need to be better than your peers who are also applying to similar jobs. You need to "Show, Don't tell".

- Build a project. Put in on Github. A real project, not some copy paste "React Template that everyone has from a bootcamp". If you cannot build one from scratch, contribute to an Open Source project that you really like

- Build a personal website and write about your learning experience. No shortcuts here. Again, how do I know who you are with all the noise ? "Show, don't tell"

- Reach out to people/companies you want to work for ideally. Be focussed and make a list. Imagine if you could work for any company. What company will that be ? Can you make a list of may be 10 ? Then reach out to their founder (if startup), hiring manager (if a bit larger company) etc. Hustle and get their information (linkedin etc).

- The more you can show, the more chances you have.

1 comments

> contribute to an Open Source project that you really like

My 2c: This is the harder but better way to prove your skills. It shows you can learn a new codebase, interact with team members to learn and get things done, and that your code standards are up to code with an established org.

Just don't make my mistake of trying to contribute on your own. Find a mentor, and before you try to make a change, explain your approach to that mentor or anyone to make sure it works. And only then start writing code.

If this gets a ton of upvotes, I'll make a guide for doing this.

That’s a great idea. Open source projects can always use the help and it’s a great way to build some developer cred. Maybe a good idea would be for open source projects to maintain a list of “low hanging fruit” bugs that new developers could take on as good first tasks.
> Just don't make my mistake of trying to contribute on your own. Find a mentor

Any suggestions on how to find a mentor to help contributing to open source? I've been self-teaching for ~8months and just created a Github account with the desire to push.

Hi can you please make a guide? Or point to any other resource you may have on this?