Skip to content
RemitBridge

Community

Student fellows

Fellows join one of four teams and own something real. The point is to finish work that other people can check, rather than to collect a title.

Library shelves and reading desks

Every fellow ends up on one team, though people help each other out across teams more often than the chart suggests. Each team turns in something concrete every quarter — a test, a dataset, a workshop, a translated guide — and we keep a log of what got delivered.

The four teams

One hue each, and the thing that team hands in at the end of a quarter.

01

Systems

Builds and maintains RemitBench. Designing the tests, running the simulations, keeping the code clean enough that someone else can rerun it.

ShipsA test

02

Economics

Collects corridor fees and exchange-rate markups by hand, tracks pickup charges, and reads up on how the remittance market is actually structured.

ShipsA dataset

03

Community education

Runs the workshops, writes the family guides, and handles talking with partner organisations.

ShipsA workshop

04

Language and evaluation

Coordinates translators and reviewers, and builds the before-and-after surveys we use to check whether a workshop taught anyone anything.

ShipsA translated guide

Where this is going

A three-year plan, written knowing that most of year 3 will probably change.

Year 1Now

Build it and check that it works

  • Get RemitBench 1.0 finished and running.
  • Put the TrueCost calculator online.
  • Hold listening sessions around King County and run the first workshops.
  • Bring on the first 12 to 20 student fellows.
  • Publish the first annual brief.
Year 2Next

Go deeper and see if it repeats

  • Add more scaling setups and more corridors to the testbed.
  • Get the guides into eight or more languages.
  • Set up a proper adult advisory council.
  • Try the workshop kit at two other high schools and see if it works without us.
Year 3Later

Grow, if the evidence holds up

  • Start a chapter network at other schools, with real deliverables attached.
  • Publish an evaluation covering all the sites, not just ours.
  • Present at CS and international finance conferences.
  • Build a student network working on payment access nationally.

Joining one of them

Fellows are chosen from applications, not from sign-ups. Make an account, pick one of the four teams, and say why in a paragraph. A student lead reads every one, and you hear back either way.

Join the lab