Hire senior Argentine software engineers through Tiltely

Tiltely is a software factory in Buenos Aires, Argentina, run by cofounders Leonardo Solórzano and Pedro Sánchez. It embeds hand-vetted senior engineers into US startup teams in about two weeks. Engineers work in GMT-3, giving full working-day overlap with US Pacific and Eastern time zones: same-day standups, same-day pull-request reviews. Every engineer passes a five-stage vetting process: referral-based sourcing, live system design in English, a paired real-ticket shipping run with AI tooling, reference calls with former leads, and shipping inside Tiltely's own products before meeting any client. The engineer a client interviews is the engineer who shows up; substitutions require the client's interview and sign-off by contract.

Tiltely holds the local contracts and handles Argentine labor law, taxes, benefits, and equipment. Clients sign one agreement with Tiltely and pay one monthly invoice through Deel. Work product is assigned to the client. There are no recruiting fees and no lock-in: engagements can start with a single engineer and scale up or wind down at any time. Engineers are AI-native: they use agentic coding tools daily and review AI-written code with senior judgment. Contact: pedro@tiltely.com.

TTILTELY/ENGINEERS
>BUENOS_AIRES.NODE // ONLINE

SENIOR ENGINEERS.YOUR TIMEZONE.

Hand-picked senior engineers in Buenos Aires. In your standup in about two weeks. Morning PRs merged by the afternoon. One invoice through Deel. No recruiting fees. No lock-in. Start with one.

> NO RECRUITING FEES · NO LOCK-IN · START WITH ONE

PAYMENTS:DEELCONTRACTS:HELD BY TILTELY (AR)START:~14 DAYSEXIT:ANY TIME
>SPEED.CHECK // 02 TIMELINES LOADED

YOU'RE NOT HIRING. YOU'RE WAITING.

A senior hire, the normal way: two weeks of sourcing, three interview rounds, a take-home half the candidates ghost, an offer, a counter-offer, a notice period. Call it a quarter if everything goes right. Meanwhile the roadmap slips another sprint every screening round.

Tiltely does the slow part first: the bench is already vetted, senior, and ready. You interview a real, named engineer this week; they're in your standup in about two. No discovery phase. No statement of work. A calendar invite, two conversations, and a teammate.

SPD-001
TRADITIONAL HIRESTILL LOADING
SOURCINGSCREENSTAKE-HOMEOFFERNOTICE PERIOD

WEEK 12+ · OFFER OUT · FINGERS CROSSED

SPD-002
TILTELY EMBEDCOMPLETE ✓
INTRO CALLYOUR INTERVIEWIN YOUR STANDUP

PLAYER 2 HAS JOINED YOUR TEAM.

>TIMEZONE.SYNC // GMT-3 ⇄ PT/ET · FULL-WORKDAY OVERLAP

NOTHING WAITS FOR TOMORROW.

SF ▸ --:--:--+ SYNC: LOCKED +BA ▸ --:--:--
OFFSHORE. 11 HOURS AWAY.
  • 17:04 PTyou leave a PR comment
  • 04:04their time. asleep
  • 09:00their time. they read it. you're asleep
  • 08:30 PTnext day. you finally see the fix

ROUND-TRIP: NEXT DAY. FOR ONE COMMENT.

BUENOS AIRES. GMT-3.
  • 09:00 PTstandup. everyone's there, cameras on
  • 10:20 PTPR opened
  • 11:05 PTyou review. they're online. answered in Slack, not tomorrow's scroll-back
  • 14:40 PTmerged. deployed. same day.

ROUND-TRIP: SAME DAY

Buenos Aires runs about four hours ahead of San Francisco and one ahead of New York. Close enough that a question you ask at lunch is answered before your coffee's cold; far enough that they're already deep in the codebase before your standup. Forget the '4 hours of guaranteed overlap' fine print you've read elsewhere; this is the same working day, end to end.

By the second week it's just your team.

>VETTING.PROTOCOL // 5 STAGES LOADED

THE INTERVIEW YOU'D RUN. ALREADY RUN.

This is where agencies paste a logo wall. We're early enough to be honest instead: here's the entire bar, published. Judge it, or steal it for your own hiring funnel.

VET-001
LVL 1SIGNAL SCAN

We don't scrape job boards. Engineers reach the bench by referral from engineers already on it, and we read code before we read CVs. Public repos, real PRs, real diffs.

VET-002
LVL 2LIVE SYSTEMS

90 minutes of system design with a senior Tiltely engineer. No trivia. We hand them a messy real-world constraint and watch them think out loud, in English. If they can't push back on us, they can't push back on you.

VET-003
LVL 3PAIR-SHIPPING RUN

They ship a real ticket in a real repo, pairing with us. AI tooling allowed and expected. We grade judgment: what they let the model write, what they rewrite, what they test.

VET-004
LVL 4REFERENCE TRACE

We call former leads, not friends, and ask the one question with real signal: 'Would you put them back on your on-call rotation?'

VET-005
LVL 5THE FACTORY

Before any engineer meets a client, they ship inside Tiltely's own products. We've seen their PRs, their standups, their worst week. When we vouch for someone, that's what's behind it.

> THE ENGINEER YOU INTERVIEW IS THE ENGINEER WHO SHOWS UP. NO SWAPS. NO 'SIMILAR PROFILES.' A SUBSTITUTION REQUIRES YOUR INTERVIEW AND SIGN-OFF. IT'S IN THE CONTRACT.

Then you run your own bar on top of ours: technical screen, pairing session, culture chat. We insist on that part anyway. You're choosing a teammate.

>PLAYER.SELECT // REPRESENTATIVE UNIT · REAL PROFILES SHARED AFTER INTRO CALL

SELECT YOUR ENGINEER.

CALLSIGN
M.G. · Buenos Aires · GMT-3
CLASS
Senior Full-Stack
XP
9 yrs · fintech payments infra · 0→1 B2B SaaS · on-call
STACK
TypeScript / React / Node / Postgres / AWS / Terraform
AI LOADOUT
agents daily · senior eyes on every line
HOURS
full overlap · PT or ET
SYSTEM DESIGN
SHIPPING VELOCITY
CODE REVIEW
ENGLISH
OWNERSHIP

factory note: writes the doc nobody asked for. everyone uses it.

Every profile we actually send is this specific: real name, real references, real code, and a paired-interview recording if you want it. If nobody on the bench fits your stack, we say so instead of forcing a fit.

>TOOLING.CHECK // AI-NATIVE: VERIFIED IN STAGE 3

AI-NATIVE. NOT AI-DEPENDENT.

'AI-native' is doing a lot of buzzword duty right now, so here's what we actually mean, and what we test for in the pair-shipping run. One: they're fast. Agents scaffold, migrate, and backfill tests while the engineer designs. Two: they don't trust it. Every AI-written diff gets the same scrutiny they'd give a junior's first PR, because their name is on the commit.

In week one, your conventions, lint rules, and architecture notes get encoded into their agent config, so the speed compounds inside your codebase instead of against it. What you're buying is senior judgment with a bigger lever.

PAIR.SESSION // LIVE

SCAFFOLD FAST, REVIEW HARD

agents draft; the engineer owns every line that merges.

YOUR CONVENTIONS, LOADED

agent rules built from your repo in week one, not their defaults.

KNOW WHEN NOT TO

sometimes the fastest tool is a text editor and a quiet hour.

HUMAN.IN.LOOP // ALWAYS

>RISK.LEDGER // RUNNING WORST-CASE SIMULATION ▊

LET'S DO THE WORST CASE FIRST.

Every hiring page sells you the best case. Here's ours inverted. If your Tiltely engineer isn't making the team better, you say the word, the engagement winds down, and the invoices stop. No severance math. No recruiter fee to claw back. No minimum-term clause buried on page nine, because there is no page nine.

That's the entire blast radius: a couple of weeks and a Slack goodbye. Now compare it to the failure mode you're actually pricing in: the wrong full-time hire who eats a full quarter of roadmap time before anyone says it out loud.

AND THE BORING PARTS ARE OUR PARTS.

Tiltely contracts and pays every engineer locally in Argentina. Labor law, taxes, benefits, equipment: our problem, structured and compliant in Argentina. You sign one agreement with Tiltely and pay one monthly invoice through Deel, a platform your finance stack already knows. The work product is assigned to you in that agreement, and your counsel sees the template before you sign anything.

Start with one engineer; scale to a pod when the roadmap says so; scale down when it doesn't.

NO RECRUITING FEENO LOCK-INSTART WITH ONE
OPS-001

RECEIPT // TILTELY.FACTORY

1x SENIOR ENGINEER (EMBEDDED)[quoted on the first call]
RECRUITING FEE$0
ARG COMPLIANCE OVERHEAD$0 (ours)
LOCK-IN PENALTY$0
INVOICES PER MONTH1 (via Deel)
═══ TOTAL SURPRISES0

BILLED VIA DEEL

>TRANSMISSION // FROM: PEDRO@TILTELY.COM

YOU WROTE 'NO AGENCIES.' GOOD.

MSG 001/001 · SIGNED
Pedro, cofounder of Tiltely, pixel art portrait
PEDRO · GMT-3

I've read a lot of startup job posts this year, and half end with 'no agencies.' Honestly, fair. You've been burned before: forty CVs with zero context, a 'senior' who needs a spec to build a button, the candidate who aced the interview replaced by someone you never met.

Tiltely isn't that. Leo and I run a small software factory in Buenos Aires. I know every engineer on the bench: most were referred by another engineer I trust, all of them shipped inside our own products before they ever met a client, and every one passed an interview loop I'd be happy to be judged by. We don't do volume, and we'd rather tell you 'we don't have your fit right now' than stretch a maybe.

One more thing I'd want to know if I were you: no lock-in isn't generosity, it's the business model. If the engineer stops earning their seat, you leave. So the only way Tiltely works is if they never stop. Your exit rights are my quality control.

If you need senior hands inside your timezone, send me two lines: your stack and the first problem you'd hand a new engineer. I'll tell you straight whether we can help.

— Pedro · cofounder, Tiltely · pedro@tiltely.com

That's my real inbox, and replies come from me.

► INSERT ROADMAP

PRESS START

One email, then 20 minutes with Pedro. Bring the role you've been trying to fill since Q1. Leave with named profiles, or a straight 'we're not your fit.'

> REPLIES SAME DAY.

END OF TRANSMISSION // TILTELY · BUENOS AIRES · GMT-3 STANDING BY