Skip to content

Hire early-career developers by the work they’ve shipped

Branchout students build production-style projects in small teams, review each other’s code and, when they choose to, lead a pod. If you hire for early-career roles, you can post them here and see that work directly.

  • Free to post roles
  • Every posting reviewed
  • Students choose to apply

What Branchout students practise

The parts of the job tutorials skip.

A team meeting in a bright office, one person pointing at sticky notes on the wall

Shipping as a team

Pods of up to six take a brief from plan to deployed project, splitting the work into pull requests the way product teams do.

Reviewing code

Every change is reviewed by someone else in the pod before it merges, so students learn to give and take feedback on real code.

Leading

Some students choose to lead a pod: planning the work, unblocking others, and keeping a small team moving.

What a candidate can show you

Not a certificate alone: the project their pod shipped, the pull requests they wrote and reviewed, and what they’d change next time.

Have a candidate’s code? Verify a certificate to see their project, its dates and what the mentor said.

Example hand-in

What a pod hands in

  • The live app, deployed
  • The repository, where every change went through a reviewed pull request
  • A README and a retrospective: how it works, the trade-offs, and what the pod would change
  • Each student’s part: the pull requests they wrote and the ones they reviewed

An illustration of the format, not a real student’s project.

How recruiter access works

  1. Create a Branchout account

    It takes a minute and uses the same sign-up as students.

  2. Request recruiter access

    From your dashboard, tell us your company, your job title and what you are hiring for. We review every request.

  3. Post your roles

    We review each posting before students can see it.

  4. Review who applies

    You see the applications students send you. An optional AI-assisted ranking can suggest how well each application matches your description. It never rejects anyone automatically.

What we ask of employers

Branchout is an educational program first. These rules keep it that way.

  • Students choose. No student is ever obliged to apply to a role or share their work with you.
  • No free work. Project briefs are for learning. Students don’t do unpaid work for your company through Branchout, and briefs are never your live product work.
  • Honest postings. Describe the role, its pay and its location accurately. Every posting is reviewed before students see it.
  • No guarantees either way. Branchout doesn’t promise students a job, and doesn’t promise you candidates.

Not hiring? Other ways to help

Lend a mentor

Engineers on your team can volunteer a little time to answer questions and review student code.

Suggest a learning brief

Solved an interesting problem your team would be happy to share? Tell us. It could become a brief students learn from.

Hiring early-career developers?

Create an account, request recruiter access, and post your first role once it’s approved.