From a posted brief to a released milestone.

Cross-border engineering work fails for predictable reasons: skills that cannot be verified, scopes that mean different things to each side, and payment terms that force one party to simply trust the other. Every step below exists to remove one of those failure modes — skills are tested instead of claimed, scope is structured before any money moves, and payment sits in escrow until work is approved.

The same flow protects both sides. Employers never pay for work they have not approved; engineers never start work that is not already funded.

Hiring in six steps

From the moment you describe the job to the moment funds release, every checkpoint is designed so you commit money only against verified people and inspectable deliverables.

1. 1
   Post your project — in your own language

   Describe the machine, the control platform, the site and the deadline in whichever of the platform’s 9 supported languages you work in. Posting costs nothing, and you don’t need to translate anything — the platform handles language from here on.

2. 2
   AI structures it into a scope and milestones

   The platform’s AI reads your description and turns it into a structured technical scope with a milestone plan — deliverable by deliverable — so both sides negotiate against the same document instead of a vague brief. Payment checkpoints end up mapped to concrete engineering outcomes, not calendar dates.

3. 3
   Match with certified engineers — and choose

   You are matched to engineers by track, platform and region, ranked by verified screening scores and ratings — and only engineers holding a valid platform certification can be officially assigned to your project (in the track you specify, if you require one). You review the matches and decide who to work with; nothing is committed until you choose.

4. 4
   Fund the milestone into escrow

   You fund each milestone through Stripe Checkout. It is marked funded only after the payment actually clears, and it stays in escrow until you approve the deliverable — so the engineer starts knowing the money is secured, and you start knowing it cannot move without you.

5. 5
   Delivery with an evidence trail

   For on-site work, the engineer checks in by GPS against a server-side geofence — the location cannot be faked client-side — and submits QC completion photos that attach to the milestone. Remote progress is logged in the project workroom, where messages are translated between your language and the engineer’s.

6. 6
   Approve and release

   Funds move only on your approval — never on a timer. On release, the platform fee is deducted from the milestone: 15% standard, or 5% for founding clients on their first 5 orders. That fee is the only charge; there is no separate markup on the engineer’s rate.

Joining in five steps

The path from application to first payout is built around one idea: prove skill once, properly, and let that verified record — not marketing — win you the work.

1. 1
   Apply — it’s free

   Create your engineer profile with your tracks, platforms, region and rate. Applying costs nothing, and there is no bidding treadmill afterwards: projects are matched to verified skill, not auctioned to the lowest quote.

2. 2
   Pass the practical AI screen

   As part of onboarding, you complete a hands-on AI technical interview in your discipline. It scores real engineering judgment — the kind that doesn’t show up in résumé keywords — and that score becomes the verified score on your profile, feeding your ranking in browse and matches.

3. 3
   Get certified — L1 to L3

   Certification is what unlocks assignments. Each exam is 10 questions — a mix of multiple-choice, scenario and deep-analysis items — in a 40-minute window, with a pass mark of 70. AI grades the paper and a human admin reviews every pass before a certificate is issued; a failed attempt carries a 7-day cooldown before retake. Levels run L1 to L3, and each level requires holding the one below it.

4. 4
   Get matched

   Employers’ projects are matched to certified engineers by track, platform and region. When you are matched, you see the structured scope and milestone plan up front — and the milestone is funded into escrow before you start, so you never begin work on a promise.

5. 5
   Get paid through Stripe Connect on release

   When the employer approves a milestone, escrow releases to your connected Stripe account minus the platform fee — no invoicing chase, no net-60 terms. Where Stripe payouts are not yet available in your country, the platform processes a manual payout instead.

Three gates between an applicant and your project

Matching is only as good as the vetting behind it. Three independent gates stand between someone applying and someone being assigned to your project — each enforced by the platform, not self-reported, and each with its own page explaining exactly how it works.

The dispute path is built into the escrow

If a delivery is contested, the money does not move while you argue. Either party can trigger a process with a fixed evidence window and a human decision at the end:

1. 1
   Open

   Either party opens a dispute on a funded milestone. It is immediately frozen to “disputed” — no funds can move while it is under review.

2. 2
   Evidence

   Both sides have a 5-day window to submit evidence. Each party’s side is recorded server-side from their role in the project — it cannot be spoofed.

3. 3
   Admin review

   A platform admin reviews the milestone spec and both evidence submissions before any funds move — the decision is human, made against the written scope.

4. 4
   Resolution

   The admin rules for the engineer, for the employer, or a split. A ruling for the employer refunds the full escrowed amount to the original payment method; a split refunds the balance not awarded.

Full detail on escrow, disputes, identity verification and the on-site evidence chain lives in the Trust Center. Read the Trust Center →

Frequently asked questions