Contact

This will be hard.

Nobody has built Proof before.

The technical problems are difficult. The agricultural standard has to work in the real world. The commercial model depends on trust that cannot be bought.

We are building the evidence infrastructure that could give agriculture a lasting memory.

The first five people will have an unusual amount of influence over what it becomes.

See the rolesBirmingham · In person · Equity in every role

Every season, agriculture learns something.

A crop fails.

A field turns a corner.

A product surprises.

A decision works in one set of conditions and fails in another.

A machine records what happened. An agronomist notices something important. A farmer learns a lesson that took an entire season to earn.

Then too much of it disappears.

NotebooksSpreadsheetsMachinery systemsWhatsApp messagesReportsMemory

Proof is being built so that knowledge does not have to disappear. A structured record of what happened, where it happened, what was known at the time, what was done and what happened afterwards.

One record helps preserve a season.

Enough records can help agriculture learn.

Five roles. One founding team.

These are not narrow jobs inside an established organisation. Each person will own a part of Proof that does not properly exist yet.

01CTO / Founding EngineerBuild the technical foundation.There is no mature blueprint to copy.

The role

You will make the early architectural decisions that Proof may still be living with years from now.

Records, permissions, identity, provenance, audit history, privacy, infrastructure and the systems that allow agricultural evidence to remain trustworthy as Proof grows.

You will write code. You will also decide what should never need rewriting.

You will own

  • Technical architecture
  • Engineering standards
  • Security and permissions
  • Record integrity and audit infrastructure
  • Platform architecture
  • Technical hiring
  • The path from working demo to production system

What makes it hard

Proof needs to preserve evidence, protect sensitive farm information and make authorised use possible at scale.

Those requirements have to coexist.

There is no mature blueprint to copy.

02Senior Full-Stack EngineerTurn the model into an exceptional product.A Proof Record can become extremely comprehensive. The interface cannot.

The role

Proof contains difficult infrastructure underneath it. The user should not have to feel that complexity.

You will build the interfaces farms, agronomists, contributors and organisations actually use to create records, follow evidence, manage permissions and work with Proof.

You will own

  • Core product development
  • Record creation workflows
  • Evidence handling
  • Contributor interfaces
  • Commercial product interfaces
  • Front-end quality
  • Performance and reliability
  • Turning difficult concepts into simple interactions

What makes it hard

A Proof Record can become extremely comprehensive.

The interface cannot.

Your job is to make a technically and agriculturally complicated system feel obvious.

03Data and Standards LeadDefine how agriculture gets written down.All of it needs somewhere honest to live.

The role

Proof cannot work if every farm, machine, researcher and organisation describes the same thing differently.

You will help create the structure that makes agricultural records understandable and comparable across seasons, farms and eventually countries.

You will own

  • The Proof taxonomy
  • Record schemas
  • Controlled vocabularies
  • Evidence and provenance standards
  • Measurement structures
  • Agricultural data interoperability
  • Comparability frameworks
  • Standards governance
  • Relationships with technical and agricultural standards bodies

What makes it hard

The standard has to be rigorous enough for serious evidence and flexible enough to represent what actually happens on farms.

Historic records will be incomplete. Modern machinery may generate thousands of data points. A handwritten observation may still matter.

All of them need somewhere honest to live.

04Commercial Partnerships LeadFind the questions worth building Proof around.That requires curiosity before salesmanship.

The role

Proof becomes commercially valuable when organisations have important questions that existing agricultural evidence cannot answer well.

You will work with manufacturers, researchers, supply chains, financial institutions, public bodies and other organisations to turn those problems into repeatable Proof products and programmes.

You will own

  • Early commercial relationships
  • Design partnerships
  • Proof Network opportunities
  • Evidence programmes
  • Commercial validation
  • Product pricing feedback
  • Strategic partnerships
  • Early revenue
  • The path from first customer to repeatable market

What makes it hard

You are not selling seats in finished software.

You will be helping define a new category while proving that organisations will pay for it.

That requires curiosity before salesmanship.

05Contributor Network and Customer Evidence ManagerBuild the human network behind the evidence.The exchange has to work for both sides.

The role

Proof only becomes useful if farms, agronomists and other contributors find it worth recording what happened.

At the same time, customer evidence questions have to translate into something contributors can realistically record in the field.

You will sit between those two worlds.

You will own

  • Contributor relationships
  • Proof Accredited Contributor development
  • Contributor onboarding
  • Farm and agronomist engagement
  • Evidence-programme delivery
  • Contributor feedback
  • Record participation
  • Customer evidence coordination
  • Making contribution genuinely valuable to the people doing it

What makes it hard

Proof cannot become a system where organisations ask for data and farms simply supply it.

The exchange has to work for both sides.

You will help make sure it does.

Small team. High ownership.

We are not trying to build a large, average company.

The early Proof team will be deliberately small. That means fewer hand-offs, fewer layers and very little room to hide behind somebody else’s responsibility.

You should expect to make decisions. You should expect those decisions to matter. You should also expect the people around you to challenge them when they think you are wrong.

We value people who

Take responsibility without waiting to be managed.

Move quickly without becoming careless.

Challenge weak thinking, regardless of who it comes from.

Care deeply about the quality of their work.

Say when something is not working.

Help the people around them become better.

Remain curious and difficult to satisfy.

Talent matters. How that talent affects the rest of the team matters just as much.

Build it in the same room.

Proof will have an in-person working culture in Birmingham.

Not because we want to monitor when people arrive or leave. Because the first years of a company involve thousands of small decisions, arguments, sketches, mistakes and moments where somebody turns around and says,

“Come and look at this.”

We want those moments.

We will treat people like adults. In return, we expect ownership, judgement and the willingness to be present when the work benefits from doing it together.

You will not be joining to maintain somebody else’s machine.

Proof is early enough that important decisions have not been made yet.

The technical architecture can still change.

The product can still change.

The standard can still change.

The commercial model can still change.

The culture can still change.

Your judgement will matter.

That creates uncertainty. It also creates the kind of career opportunity that disappears once a company becomes established.

Your work will be visible.

Every founding role carries equity because we want the first team to build Proof as owners, not spectators.

This will not be for everyone.

Proof is probably not right for you if you want:

A tightly defined job with narrow responsibilities.

Remote work as the default.

Several layers of approval before decisions are made.

Somebody else to take responsibility when something fails.

Average work to go unchallenged.

The mission to stop mattering when the job description ends.

There are good companies built differently. Proof will be built this way.

Early enough to matter.

Proof currently has a working demo and is preparing for the next stage of the company.

We are speaking to exceptional candidates before the team is formally assembled because the people we want are unlikely to appear at exactly the moment we need them.

If you need a role that starts immediately, this may not be the right timing. If you would rather get to know the company before deciding whether to help build it, we would rather hear from you early.

Working demoFounding team formingBirminghamEquity in every role

Think you should be here?

Tell us which role interests you. Then tell us about one thing you have built, changed, solved or achieved that you are genuinely proud of.

We care more about evidence of exceptional work than a polished covering letter.

And if none of the five roles quite describes you, but you think we are wrong not to be hiring someone like you, tell us why. That is a perfectly good way to introduce yourself.

Contact Proof

PDF or Word, up to 3 MB. If it will not attach, link it below or email it to ct@proof.ag.

Proof will use your application to assess your suitability, communicate with you and manage the recruitment process. Unsuccessful applications are normally retained for six months. Read the Website, Enquiries and Recruitment Privacy Notice.

This form is protected by Cloudflare Turnstile, which checks your browser and network to prevent automated abuse. See our privacy notice.

Every season, agriculture creates knowledge that should not disappear. Come and help us preserve it.