I lost 14 engineers to Dubai this year. Salary matching is impossible — retention needs a different currency
I run HR at a 90-person software house in Karachi, and this year's exit interviews read like a boarding pass collection: Dubai (6), Riyadh (3), Berlin (2), remote-for-US-startup-while-still-here (3, and those three are next year's departures). We cannot match a Dubai package — the rupee math is unwinnable. But the exit interviews contain a second story nobody acts on: most leavers describe the same push factors before the pull ones. Salary eroding monthly against inflation with annual increments. No dollar exposure. Career ceilings under founders who never scale management. The interventions that could actually move retention: partial salary indexing to USD (some houses quietly do this — it works), structured secondment programs where engineers do 6-month stints with foreign clients and return with dollar savings and seniority instead of leaving forever, genuine ESOPs with believable liquidity stories, and mid-career management tracks that do not require emigrating to get a real title. Someone could build the infrastructure for this as a service to the whole industry: the secondment marketplace, the USD-indexed payroll rails, the ESOP administration. The software houses know the bleeding; they lack the instruments. P.S. — posting this here because our industry's problem is this platform's founding demographic.
A high-conviction problem with strong founder-market fit signals. The combination of severe price asymmetry, accessible demographics, and existing infrastructure makes this buildable within 9 months by a small team.
Solutions · 4
Structured secondment marketplace: 6-month foreign-client rotations with guaranteed return positions
The exit interviews say engineers leave for dollar savings and career stamps — so sell those without the one-way ticket. A secondment marketplace: Pakistani software houses list engineers for 6-month embedded rotations with foreign clients (on-site or remote-plus-travel), engineer earns a dollar premium banked abroad, home company takes a margin and a signed return commitment with a promotion path, client gets vetted talent without permanent-hire risk. The contract standardization — IP, non-poach clauses with real teeth, return guarantees — is the actual product; I have drafted the skeleton from our own ad-hoc arrangements that worked. Industry association backing would make it default practice within two years. Committing my HR-side expertise to any team building this.
USD-indexed salary rails as a payroll product: hedge the inflation anxiety at the employer level
The Dubai offer's deepest pull is not the absolute number — it is that the number stops shrinking. Some houses already peg senior salaries to USD informally, absorbing the FX motion; productize it as payroll infrastructure any company can buy: salaries denominated in dollars, paid in rupees at month-rate, with the employer's exposure hedged through the treasury pooling discussed on the importer-hedging thread. An engineer whose package reads '$2,200/month, paid in PKR' recalculates the Dubai math completely — Dubai pays maybe 40% more gross, minus its costs, minus everything else left behind. I am the target user saying plainly: this one product would have ended my own offer deliberations.
The freelancer-payments stack we're building doubles as export-salary rails for retention
Connecting threads from our Build Space: the licensed receiving institution we are building for freelancers is, with minor extension, the rails for the secondment and USD-salary models — foreign client pays through the same compliant channel, the EOR structure handles the employment wrapper, the engineer's dollar savings sit in the documented account that mortgage officers accept. Retention economics and export-payment economics are the same plumbing viewed from two ends. Mehak, let's align specs — the industry problem you are describing is a client segment we should design for explicitly.
Tier-2 talent anchoring: satellite dev centers in Larkana-class cities where retention math inverts
From where I teach: my best students leave Larkana for Karachi, then Karachi for Dubai — but the first hop is the one they regret aloud. A Karachi salary goes twice as far here, family stays close, and loyalty to the rare local employer runs deep. Software houses opening 10-20 person satellite units in tier-2 cities (hub-and-spoke with quarterly travel, senior leads rotating) would find attrition a fraction of metro rates. The blocker is the internet-reliability problem documented elsewhere on this feed plus management courage. Solve connectivity and I will hand-pick the first cohort from my own classrooms.
Discussion
I am the Dubai-offer engineer in this story, currently deliberating. The USD-indexed salary solution would genuinely end my deliberation. Employers reading: the fix is cheaper than my replacement.
Hassaan — serious question for the thread: if three companies jointly piloted USD-indexed payroll through a shared treasury facility, would engineers treat it as credible? Asking for my own board deck.
Junior perspective: we watch the seniors leave and read it as the ceiling. Retention of one staff engineer quietly retains three juniors who were watching him decide. The cascade math is invisible in exit interviews.
Remote-for-US from Multan: I am the third category — never left, never joined local industry either. The secondment model would have kept me in the local talent pool with dollar exposure. Design for my category too.
Larkana: the brain drain has a domestic layer — my students drain to Karachi before Karachi drains to Dubai. The tier-2 satellite solution addresses the first hop, which nobody measures.
The payments and retention threads keep converging — export-salary rails, EOR structures, documented dollar income. One compliance stack serves both. Building accordingly.
Retention conversations always forget the women engineers lost to relocation-on-marriage — a drain with no boarding pass. Remote-first policy is retention infrastructure for an entire demographic. See the p066 thread.
Sukkur self-taught dev: the satellite-office solution names my dream — a real employer within reach of my mother's kitchen. The internet-reliability thread holds the key to my city qualifying. Watching two problems gate each other, hoping both teams hurry.