Open role · AI/ML subsystem lead

Help us teach a farm robot to see

CropScout is an autonomous robot for greenhouses and small vegetable farms: precision spraying and crop monitoring in the rows where a tractor cannot fit. The undercarriage and the sprayer are being built in America. What we don't have yet is the person who makes the machine understand what it is looking at.

Apply below

What we're building

The idea

A robot that sprays less

Most small farms spray the whole field on a calendar. CropScout drives the rows, looks at the plants, and treats only what needs treating: less pesticide on the crop, less cost to the farmer, less run-off into the ground.

Already moving

Undercarriage and sprayer

Designed and built by the team in America: drive, chassis, tank, nozzles, the physical machine.

The gap

Perception and control

Nobody owns this yet: the detection models, the data behind them, and the code that turns a detection into a decision the robot acts on.

The role: AI/ML subsystem lead

You would own the perception side end to end and help program the robot itself. Concretely:

You don't need to have shipped all of this before. You do need to be able to work without someone assigning you tasks, because there is nobody to do that.

The honest version

This is a low-budget startup: not a funded company with a runway, but a small team building a machine because we think it should exist. We would rather lose you at this paragraph than three weeks in.

October
Expenses may be covered from a shared stipend. It is shared, and it is small: treat it as expenses, not pay.
Nov–Dec
Unpaid. No stipend, no salary. This is the part people underestimate.
Equity
We can offer equity. It is a new startup, so that equity is worth nothing today and may be worth nothing ever.
Later
If this works, the role becomes full-time and paid, and you would already be part of it.
Honestly
It may not work out. Join only if you are willing to spend the time knowing that.

People who stay

What has hurt us most is not a lack of skill. It is people who start keen and drift off after a few weeks, leaving a half-finished subsystem nobody else understands. That costs us more than never having started.

So we are looking for at least 20 hours a week from September through December. If you can't see yourself finishing December, please apply to something else with our blessing. Saying no now is more useful to us than saying yes and leaving in October.

Tell us about you

Who you are

This is how we reply.

Only asked because some of our funding is tied to student programmes.

City and country, plus your time zone.

Your work

Optional, but it helps more than a resume does.

PDF, DOC or DOCX, up to 4 MB.

Which of these have you actually used?

Be honest: "none of these yet" is a real answer, and we still read those.

A project, a paper, a model you trained, a robot that half worked.

Time and commitment
Can you commit at least 20 hours a week, September through December?

The number you would still hit in a bad week.

Which part interests you?

Days and rough hours, in your own time zone. We're split across the USA and Uzbekistan, so overlap matters.

Why you

Not why you want a startup: why this one, this robot, this problem. This is the answer we read first.