wepair.works
Start now
For in-house recruiters

Fill engineering reqs without guessing who passes the technical

We search Latin America for your req, a founder tests each candidate live, and you forward one to three write-ups.

Book a 20-minute intake call
A recruiter's applicant tracker on an iPad, open on a senior backend req. A founder assessed 4 candidates; 2 made the shortlist and the rest are held back with the reason shown. Diego Salazar's write-up is open, gap stated, and the activity log shows the write-ups arriving, the recruiter forwarding them, and the hiring manager asking to interview.
1–3
candidates per req, each with a founder’s write-up
~2 h
of live technical work with a founder, per candidate
$0
to search, interview and decline a shortlist
5
business days to a vetted replacement if a placement stops working

Sound familiar?

Finding engineers is the part you’re good at. Proving they can do the work is where the req stalls.

  • “I can source engineers all day. I can’t tell whether they’ll survive the technical round.”
  • “The hiring manager passed on my last five candidates and couldn’t say why in one sentence.”
  • “My network in Latin America is thin, and this req was due last week.”
  • “Every agency I bring in sends resumes I could have found myself.”

Submitted · Senior backend · payments

0 of 5 to interview

CandidateSentHiring manager

J. Park

Senior backend · Go

Sep 8Pass

M. Okafor

Backend · Node

Sep 11Not senior enough

R. Silva

Senior backend · Go

Sep 15Pass

T. Nguyen

Platform · Go

Sep 19Failed the live coding

D. Kowalski

Senior backend · Java

Sep 24Pass, no notes
Five candidates submitted to the hiring manager for a senior backend role over three weeks. None reached an interview, and the feedback is a pass, not senior enough, a pass, failed the live coding, and a pass with no notes.

What changes when a founder runs the technical round

You keep the req, the hiring manager and the decision. We take the technical round and the Latin American search.

Today

  • Screening on keywords and years of experience
  • Hiring-manager feedback that arrives as a flat no
  • A pile of resumes you have to filter
  • Sourcing a market you don’t know
  • Agencies that want the search to themselves

With wepair.works

  • A founder pairs live with each candidate for about two hours before you see a name
  • A written assessment the hiring manager reads before the interview: strengths, gaps and what to ask
  • One to three candidates per req, and a straight answer if nobody clears the bar
  • Active and passive candidates across Latin America, searched for this specific role
  • No exclusivity: your sourcing, referrals and agencies keep running

What you get on every req

  • Vetting write-up

    Run by Alvaro Aquije

    Senior backend engineer · payments

    Strength
    Systems reasoning
    Named lock contention on the ledger table as the first thing to break. We did not prompt for it.
    Caveat
    Stated plainly
    Has never operated Kafka in production. If the role owns the cluster from day one, he is the wrong person.
    Mistake
    Caught it
    Proposed a covering index that would not have helped, then corrected it himself four minutes later.

    A write-up you can forward as written

    The founder who ran the session writes it, and it reaches you unedited, mistakes included. The hiring manager reads it before the interview and knows what to probe.

    Read a full sample write-up
    • Alvaro AquijePlatform, infrastructure, backend roles
    • Bruno TelloProduct engineering, frontend, mobile roles

    A founder the hiring manager can call

    Founders run every technical session, not outsourced interviewers. Questions about a candidate go to the person who ran it, not to an account manager.

  • Search brief

    Senior backend engineer for a payments team: Go and Postgres, owns the ledger write path, works US Eastern mornings.

    • Active and passive
    • Across Latin America
    • 4–6 h overlap

    Searching for this role

    A search for your req, not a bench

    We look across Latin America for your stack, seniority and working hours, active and passive candidates alike. We place full-stack, AI, cloud and platform and design engineers.

  • Sources

    No exclusivity

    Senior backend engineer · payments

    Your sourcing
    Open
    Referrals
    Open
    Agency
    Open
    wepair.works
    Open
    2 shortlisted, write-ups attached.

    Every other channel stays open

    We never ask for exclusive control of a search. Your sourcing, referrals and agencies keep working the req; we add candidates with the technical round already done.

    Read the engagement terms

How a req runs with us

Your req goes in on a 20-minute intake. Evidence you can forward comes out.

Your time

Ours

  1. 01You: 20 minutes

    Run the intake with us

    Bring the hiring manager: stack, scope, seniority, overlap and what success looks like. Commercial questions get answered on the same call.

  2. 02Us: Latam-wide search

    We source Latin America

    Active and passive candidates, checked for stack, availability, rate and working-hour overlap before anyone is assessed.

  3. 03Us: About 2 hours each

    A founder runs the technical

    About two hours of live work on problems taken from the role, written up as it happened.

  4. 04You: 1 to 3 write-ups

    You forward the write-ups

    Send them on as written. The hiring manager interviews with the evidence in hand.

  5. 05Us: One invoice

    We handle the engagement

    Contract, IP assignment and one US invoice. A founder digest weekly or every two weeks after the start.

Questions recruiters ask first

Twenty minutes. You leave knowing whether we can fill the role.

Tell us the stack, the scope and the seniority. On the call you get a straight answer on whether we can fill it and what it would cost. If we take it on, a founder pairs with each candidate and you get one to three names with the write-ups attached. If nobody clears the bar, we say so instead of padding the list.

Book a 20-minute founder call

Or email . We read every single email.