Ask HN: Who is hiring? (December 2025)

Can you drop more info here on how it works. Before we go through sign up process.

Sounds quite easy to come up with such tasks. E.g. prove collatz conjecture. or write an O(log N) worst case sort. So there must be some boundaries.

The pay clearly isnt by hour so how is it worked out?

Yes, of course!

Tasks must be coding problems to complete in a set of open-source repositories. We have eight repositories now and will add more in the future. You can source tasks by identifying merged commits into these repos, and making the following: - A well-defined task description (what should the AI do?) - A golden solution (can be sourced by the implementation in the merge commit) - A test patch (can be sourced from the merge commit, this is a testing suite that verifies whether the AI's solution is correct).

If you can make a task that is hard enough for our AI, you will get paid a fixed amount. That's it!

Once you are approved onto the site, there will be a more detailed tech spec + payment info + a tutorial.

This sounds more like the AI version of mechanical Turk than a job that someone can be "hired" for.

If this is the case, this post doesn't belong here imo

This post certainly does not follow the comment guidelines or format

So this has to be a meaningful PR for the open source repository? You can't just invent arbitrary coding challenges?

This seems like trying to get free code contributions with a weird sort of gambling mechanic attached.

Yes, to be perfectly transparent, this is for a contract work position! However, many of our contributors appreciate the flexibility and transparent payment structure. If you are exclusively looking for full-time roles, this is not for you.

Nothing is free, of course, since we transparently pay per task (and as previously stated, the pay is very generous). There are certainly guidelines for what kinds of tasks you can submit to our platform, but beyond that, you can make any verifiable coding task in any of our qualifying open-source repositories.

We also definitely do not require you to write new code into the repo. As I said, you can adapt existing merged commits into coding tasks.

I don’t think this fits the spirit of this monthly post. This is not “hiring”, it’s paying people for training data to automate themselves out of a job

Ive seen more than one flakey startup do this to fluff adoption metrics and perceived activity. It was frustrating

How do we know in advance if something it going to be hard enough?

For example I have a bunch of closed PRs on my Vibe-Prolog project that took multiple attempts to get right: https://github.com/nlothian/Vibe-Prolog/pulls?q=is%3Apr+is%3...

As a specific example: https://github.com/nlothian/Vibe-Prolog/pull/214 which implements https://github.com/nlothian/Vibe-Prolog/issues/204

I'd be very interested if it is eligible!

Something like this is reasonable. To clarify, we can't support arbitrary tasks yet on our submission platform; the tasks have to belong to a set of supported repositories. But tasks of this difficulty level generally tend to be hard enough.

You can't know for sure what is going to be the right difficulty in advance; however, you can definitely develop intuition for it as you make more tasks and better understand the model's strengths and weaknesses!