As coldint just started in July 2024, we have a lot of work to do, but not much that is easily delegated, and so we are currently not hiring. Any requests to be on our dev team, or to get hired otherwise, will be redirected to this page.
Why not hiring? I’m good at …
We might reconsider the above position if you are really good and you would be able to do our work, but better. The first and foremost thing we will look at, before even considering hiring someone, is publicly visible contributions to bittensor-related projects in the form of pull requests (PRs).
Why? Didn’t you see my impressive resumé?
Yes, we looked at it, but it doesn’t tell us much. You may have been the pizza guy on that one great project, who knows. Finding, analyzing and properly fixing a bug in an established project that is embedded in a larger ecosystem like bittensor, and subsequently turning it into a PR that actually gets through, requires skills on many levels. It’s those skills that potential employers (like us) want to see.
What do I need to do to get hired?
See the previous answer: start contributing! We will look at your contributions to Opentensor, Substrate, transformers, and coldint, as those are codebases we know by heart. Significant contributions to other projects are generally hard to assess for us, but may also be eligible.
But I did contribute, didn’t you see?
Maybe we missed something. Please send us the link to the relevant pull requests, using the GitHub pull requests filter feature. E.g. our contributions to bittensor: mvds00-filtered-PRs.