Facilitate
    EntrepreneurshipEmploymentEducatorsAccelerators
    Sign inFind your place

    For industry partners: tech companies and corporate teams

    Set a challenge. Meet the builders who rise to it.

    Give a cohort one real piece of your work and two people from your team to mentor it. Builders build it with your tools, your mentors tell them what they think, and the finished work goes on each builder's own record. You meet people through what they made for you, long before a hiring round opens.

    Start a conversationSee how a challenge runs
    Two women in safety glasses adjusting a robot on a workshop bench

    Proven builders

    Your engineering, data or design lead

    One bounded piece of real work: a feature, a dataset, a flow, a support queue. We scope it with you so a cohort can finish it in a term, with the tools your own teams use every day.

    1. 1You set a real challengeOne bounded piece of real work: a feature, a dataset, a flow, a support queue. We scope it with you so a cohort can finish it in a term, with the tools your own teams use every day.
    2. 2Builders take it onYour challenge sits inside a cohort, beside the rest of their work. People pick it because it interests them, and they build in the open, so their educator sees the drafts as well as the finished result.
    3. 3Your mentors respondYour people read the work and answer it: a code review, a critique, a question about a chart. A few hours across a term, on a schedule they set up front.
    4. 4The work goes on their recordWhat they made, what your mentor said, and what they changed because of it. 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. Your first conversation starts 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.

    These are starting points. Most partners bring a challenge of their own and we scope it together so a cohort can finish it in a term.

    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 let it go.
    Your mentors do
    An engineer reviews the change in writing, the way they would for a new colleague.
    What goes on the record
    The change, the review, and what the builder did with it.

    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, then wrote the tests that prove it.

      • Front-end code
      • Testing

      Mentor review on their record

    • 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 their record

    • S. K.

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

      • Interface design
      • Front-end code

      Mentor review on their record

    • 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 every morning.

      • Data analysis
      • Interface design

      Mentor review on their record

    • 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 their record

    • K. W.

      Sorted a month of sample tickets by cause and showed which fix would clear the most.

      • Customer support
      • Data analysis

      Confirmed by their educator

    • E. F.

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

      • Interface design
      • Testing

      Mentor review on their record

    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 your company gets back.

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

    • People who know your tools

      Builders who have already shipped something with them, and can show you what.

    • A shortlist with evidence

      Work you can open and read, with your own mentor's comments beside it.

    • Mentors who grow

      Reviewing a newcomer's work is practice for leading a team. Your people get that practice.

    • A place in the region

      Your name beside work that people starting out near you made, and can point to.

    Your first ninety days.

    1. Days 1 to 30Set one real challenge and name two mentors
    2. Days 31 to 60Builders take it on 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. You will see how builders who choose to can show you what they made.

    Start a conversation

    Too many people finish school able and unseen by the people who can say yes. We are here to end unemployment at the start of working life, one connected region at a time.

    Facilitate
    • About
    • How it works
    • Technology
    • FAQ
    • Careers
    • Contact
    • Legal