01 The work · a fictional example
In Amman, a payments engineer built software to match wallet transfers to invoices, even when two amounts were identical.
Invoice Unconfirmed
“Our model marks both invoices as paid. Who’s dealt with this before?”
Read the brief
- In hand
- One settled payment. Two invoices for the same amount.
- To learn
- Which invoice did the customer pay?
02 How we find people
When a teammate recommends someone, we ask what they saw firsthand. Who designed the test? Who tracked down the fault?
Find your roleWhy this path?
“We worked on payouts together. They found the invoice reference our software kept dropping.”
Built reconciliation tools for merchants
Where you fit
A researcher might need lab time today and become someone’s technical cofounder tomorrow.
People behind the models
Who chose the dialects in a training set? Who spotted the chatbot guessing at a refund policy?
03 Permission
We explain why you might want to meet. Your name and email stay private until everyone agrees.
04 The introduction
The curator checks the wording and sends one email. You both know why you’re meeting and where to start.
- From
- Unbundl curator
- To
- Mina & Ari
Mina, meet Ari. Mina’s model matched one stablecoin payment to two invoices. Ari, which reference would your matching tool check first?
Invite only, for now.
Apply for our next opening. Tell us what you’re working on or who you’d like to meet.