CANDIDATES
How it works
1
Explore issues using tech you are interested in or want to learn.
2
Express your interest in a task or get started straight away.
3
Solve the issue in your own time and submit your code.
4
Improve your profile and get real production experience.
1
2
3
4
88%
of companies encourage OSS contributions
Get real production experience
76%
of companies engage with OSS communities
88%
of companies encourage OSS contributions
76%
of companies engage with OSS communities
Get real production experience
THE POTENTIAL
Why open source software is the future of hiring
58% of companies have hired software engineers based on their open-source software contributions.
64% of developers are open to solving a company’s open-source issues as part of the technical hiring process.
Most companies in the world use open-source software, yet very few of them actively use OSS as a hiring strategy.
FAQs
What else would you like to know?
I want to work on an issue but someone else has already started?
We do not limit the number of people that can start work on an issue. You can see the number of contributors from the Issue page and the Issue listing page. If you are concerned that your work might not get seen you can always comment on the issue and ask how the other contributors are getting on.
How do I get paid for my work?
Only issues that indicate a value will result in you being paid for your work. The repo maintainer is solely responsible for the approval of your work and the pay out will be issued following approval. The company responsible for the issue retains the access to money and upon completion will transfer the money through Paypal or their payment provider of choice. In the future we hope to implement a solution in which the money is held in escrow with payments being released when work is merged.
How do I get started?
To complete an issue it’s easy, just find an issue that you find interesting and hit start work. Then follow these steps: Fork the repo, clone the project and you should then find setup instructions in README. Take your time to complete the issue and once it’s ready submit your PR on GitHub and don't forget to link the issue to it. Relax and wait for the maintainer to review your PR. As soon as you start work on an issue the maintainer will be alerted via the WorksHub platform.
Why should I contribute?
Around 80% of the world’s companies run on some open source software. The future of our platform is to use this code as a way to test, engage and build engineering teams. In the meantime, if you want to provide value to your experience (beyond resume buzz words) or learn a new tech using production code then our issues are made for you. We ask all company maintainers to write a repo README that makes it as easy as possible for new developers to set up and contribute.
How do I get started?
To complete an issue it’s easy, just find an issue that you find interesting and hit start work. Then follow these steps: Fork the repo, clone the project and you should then find setup instructions in README. Take your time to complete the issue and once it’s ready submit your PR on GitHub and don't forget to link the issue to it. Relax and wait for the maintainer to review your PR. As soon as you start work on an issue the maintainer will be alerted via the WorksHub platform.
I want to work on an issue but someone else has already started?
We do not limit the number of people that can start work on an issue. You can see the number of contributors from the Issue page and the Issue listing page. If you are concerned that your work might not get seen you can always comment on the issue and ask how the other contributors are getting on.
Why should I contribute?
Around 80% of the world’s companies run on some open source software. The future of our platform is to use this code as a way to test, engage and build engineering teams. In the meantime, if you want to provide value to your experience (beyond resume buzz words) or learn a new tech using production code then our issues are made for you. We ask all company maintainers to write a repo README that makes it as easy as possible for new developers to set up and contribute.
How do I get paid for my work?
Only issues that indicate a value will result in you being paid for your work. The repo maintainer is solely responsible for the approval of your work and the pay out will be issued following approval. The company responsible for the issue retains the access to money and upon completion will transfer the money through Paypal or their payment provider of choice. In the future we hope to implement a solution in which the money is held in escrow with payments being released when work is merged.
