For industry partners: tech companies and corporate teams

Set a challenge. Meet the builders.

Give a cohort a real piece of your work and two people to mentor it. Builders take it on with your tools, your mentors say what they think, and the result goes on each builder's own record. You meet people through what they made, long before a hiring round.

Two young women in safety glasses adjusting a robot on a workshop bench
  1. 1You set a real challengeA small, bounded piece of real work: a feature, a dataset, a flow, a support queue. Scoped with us so a cohort can finish it in a term, using the tools your teams use.
  2. 2Builders take it onThe challenge runs inside a cohort, beside the rest of their work. People choose it because it interests them, and they build in the open, where their educator can see the drafts as well as the result.
  3. 3Your mentors weigh inYour people read the work and respond to it: a code review, a critique, a question about a chart. A few hours across a term, on a schedule they agree to up front.
  4. 4The work goes on their recordWhat they made, what your mentor said, and what they changed afterwards. The record belongs to the builder, and they decide who sees it.
  5. 5You meet the ones who stand outBuilders who choose to can show you their record. You start the conversation from something they built with your tools, not from a CV.
  6. Proven builders

What you would be putting in.

One real challenge and two mentors. Each kind of challenge ends in something a builder made, your mentor's response to it, and what the builder did next. Pick one to see who does what.

Ship a small feature

Builders produce
A working change to a sample codebase, with a short note on what they tried first and why they dropped it.
Your mentors do
An engineer reviews the change the way they would review a new colleague's, in writing.
What goes on the record
The change, the review, and what the builder did with the review.

Who you would meet.

A CV tells you what someone says they can do. A record shows you what they made and who checked it. Pick a skill and the builders whose record shows it come forward.

8 sample builders. Pick a skill to see whose record shows it.

  • A. M.

    Rebuilt a sign-up form so it works with a keyboard alone, and wrote the tests that prove it.

    • Front-end code
    • Testing

    Mentor review on file

  • J. O.

    Found why weekend orders looked low in a sample dataset: a time zone, not the customers.

    • Data analysis
    • Technical writing

    Mentor review on file

  • S. K.

    Took a booking flow from seven screens to four, then built the four.

    • Interface design
    • Front-end code

    Mentor review on file

  • R. D.

    Wrote the help article that answered the most common ticket in the sample queue.

    • Customer support
    • Technical writing

    Confirmed by their educator

  • T. N.

    Turned a twelve-tab spreadsheet into one dashboard a shop owner reads each morning.

    • Data analysis
    • Interface design

    Mentor review on file

  • L. B.

    Followed a getting-started guide cold, logged every place it broke, and fixed the guide.

    • Front-end code
    • Technical writing
    • Testing

    Mentor review on file

  • K. W.

    Tagged a month of sample tickets by cause and showed which fix would remove the most.

    • Customer support
    • Data analysis

    Confirmed by their educator

  • E. F.

    Ran the same checkout past five people and recorded where each one stopped.

    • Interface design
    • Testing

    Mentor review on file

Sample builders, for illustration. Nobody here is a real person. On the platform a builder decides who sees their record, so you only ever meet people through work they chose to show you.

What comes back to your company.

A partnership like this has to be worth your mentors' hours. These are the four things partners tell us they came for.

Your first ninety days.

  1. Days 1 to 30Set one real challenge and name two mentors
  2. Days 31 to 60Builders work on it inside a cohort, on the record
  3. Days 61 to 90Meet the ones whose work stands out

Bring us one real challenge.

Tell us which tools you want people to be good with and what a useful small piece of work looks like on your team. We will show you how it runs inside a cohort, and what your two mentors would be asked to do.

Start a conversation

Too many young people finish school able and unseen, while the institutions that want to back them cannot find each other. We are here to end youth unemployment, one connected region at a time.