wepair.works
Start now
For CTOs and founders

Know how an engineer works before your first interview

A founder runs a two-hour live session before you meet anyone. You get one to three engineers, each with written evidence.

Brief a founder on your role
A founder's live session with a senior backend candidate, one hour and forty-two minutes in. The candidate's ledger code is on screen with the balance update highlighted, and the founder's notes read: went to the write path first and named lock contention unprompted; proposed an index that would not help and caught it himself; wrote a failing test before fixing the bug; caught a generated backfill running outside a transaction.

Sound familiar?

Hiring lands on the person with the least spare time on the team.

  • “I lost three evenings to first-round calls with people who couldn’t walk me through their own pull request.”
  • “The agency sent fourteen resumes. I needed one engineer.”
  • “Our last contractor built exactly what the ticket said, and nothing we actually needed.”
  • “I have no idea who screened them, or what they were tested on.”

Your week

Hiring, after hours

Mon

Tue

Wed

Thu

Fri

  • Standup
  • Sprint planning
  • 1:1s
  • Standup
  • Architecture review
  • Customer call
  • Standup
  • Incident review
  • Roadmap
  • Standup
  • 1:1s
  • Pairing
  • Standup
  • Demo
  • Board prep

6:00 pm

  • 7:00 pmFirst-round call
  • 8:00 pmFirst-round call
  • 9:30 pmTriage 14 agency resumes
  • 7:30 pmFirst-round call
  • 7:00 pmFirst-round call
  • 9:00 pmTake-home review
  • 6:30 pmFirst-round call
A five-day calendar. Every working day is full of standups, planning, reviews and customer calls, so first-round calls, resume triage and a take-home review all land after 6 pm.

What changes when a founder runs the first round

You still make the call. You make it with evidence instead of a resume.

Today

  • A stack of resumes to triage between meetings
  • Your evenings spent on first-round technical calls
  • “Trust us, they’re senior”
  • The vendor disappears once the contract is signed
  • A rotating pool you can’t name

With wepair.works

  • One to three engineers per role, each with a written technical record
  • A founder runs a two-hour live session before you see a name
  • Strengths, gaps and mistakes, written by the person who watched them work
  • The founder who vetted them keeps reading their work and reports back in writing
  • One engineer in your standup, your repo and your review queue

What you read before you spend an interview slot

  • A write-up from the session, not a scorecard

    Every shortlisted candidate arrives with what we saw, where they needed prompting and what to probe next. Two rows from a real, published write-up:

    Vetting write-up

    Run by Alvaro Aquije

    Senior backend engineer · payments

    Systems reasoning
    Excellent
    Given 4M events/day on one Postgres box, he went to the write path before the read path and named lock contention on the ledger table as the first thing to break. We did not prompt for it.
    Code he defends
    Acceptable
    Explained why he chose a token bucket over a sliding window, then said he would use the sliding window now because the burst behaviour caused a support load he had not predicted.
    Read the full write-up
    • Alvaro AquijePlatform, infrastructure, backend roles
    • Bruno TelloProduct engineering, frontend, mobile roles

    A founder runs every session

    Alvaro or Bruno pairs live with each candidate for about two hours. No outsourced screener, and you can call the person who made the recommendation.

  • 1–3

    names per role

    One to three names

    Small on purpose. If nobody clears the bar, we tell you that instead of padding the list.

  • We keep reading the code after they start

    A founder reviews the engineer’s actual work weekly or every two weeks and writes you a digest: what shipped, what stalled, what they picked up without being asked, and where they pushed back on your plan, or should have.

    Read a sample digest

  • 5business days

    A replacement, not a restart

    If a placement stops working, we present a vetted replacement within 5 business days at no new placement fee. In the first 30 days you can cancel without notice.

  • Your teamEngineer
    4 to 6 h overlap

    Inside your process, not beside it

    Your repo, your board, your standup, with four to six hours of overlap with US working hours. No project manager or account manager sits between you and the engineer.

How it runs from your seat

Twenty minutes to brief us. After that, you read before you interview.

Your time

Ours

  1. 01You: 20 minutes

    Brief a founder

    Twenty minutes on the stack, the scope, the seniority, the hours you need to overlap and what success looks like.

  2. 02Us: Latam-wide search

    We search for the role

    Active and passive candidates across Latin America, matched to your stack, seniority and working hours. Not a bench.

  3. 03Us: About 2 hours each

    A founder pairs with each one

    About two hours of live work: unfamiliar code, debugging, architecture, AI-assisted development and how they explain a decision.

  4. 04You: 1 to 3 write-ups

    You read, then interview

    One to three write-ups with the gaps stated. Our assessment narrows the guesswork; the decision stays yours.

  5. 05Us: One invoice

    They start, we stay

    We hold the contract, the IP assignment and one US invoice. The digest arrives weekly or every two weeks.

Questions founders 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.