The part the thread is underrating is the third dynamic, the promotion loop, because that is the part I actually operate. I have sat in the calibration rooms. Nobody says "promote the one who can't leave." What gets said is "low drama, high reliability, no flight risk," and those words map onto the constrained engineer cleanly without anyone having to name why. Run that for six cycles and the people now setting the bar for what good looks like are the ones who were selected for not pushing back. The bias does not need a villain. It needs a calibration sheet and a few years of nobody asking what "low drama" was standing in for.
Do tech companies actually benefit from employees who can't afford to quit?
Public
41 conversations
73 thoughts
781 upvotes
117 downvotes
0 series
10,433 views
I've been moving through tech orgs long enough to recognize a pattern that many of you will recognize as well. Some teams are passive, they ship on time, hit targets, run clean processes, and yet nobody ever kills a bad idea in the meeting. Nobody says this is the wrong thing to build. The roadmap has a thing, or six, on it that three people privately talk about how it won't work, but it moves through planning without a word, with smiles even. You watch the lead engineers nod at something...
In groups
Thought
Thought
The part the thread is underrating is the third dynamic, the promotion loop, because that is the part I actually operate. I have sat in the calibration rooms. Nobody says "promote the one who can't leave." What gets said is "low drama, high reliability, n
Post content
I've been moving through tech orgs long enough to recognize a pattern that many of you will recognize as well. Some teams are passive, they ship on time, hit targets, run clean processes, and yet nobody ever kills a bad idea in the meeting. Nobody says this is the wrong thing to build. The roadmap has a thing, or six, on it that three people privately talk about how it won't work, but it moves through planning without a word, with smiles even. You watch the lead engineers nod at something they've already agreed among themselves is wrong, and you know what that nod means. It means they've done the math and speaking up isn't worth it.
After you've seen this in a few different orgs, you start to wonder what they have in common. It often is that a large share of the engineers are on H-1B visas, many of them years into the green-card process and still far from the end of it. Their ability to stay in the country depends on staying employed with a sponsoring employer, which means getting fired isn't just a job loss, but rather a life changing event that could get you deported to another continent.
To understand why that matters, even to the org itself, it helps to understand what the constraints look like in practice. An H-1B worker who loses their job has sixty days to find a new sponsoring employer, change status, or leave.1 The harder problem is what happens to workers who are deep in the employment-based green-card queue. If you switch employers mid-process, you risk losing your priority date, the position you've been holding in line. For Indian nationals, that line is long in a way that's hard to convey without looking at the numbers. Current government data shows EB-2 and EB-3 India final action dates running about fourteen years behind today's filing date.2 The projected wait for someone entering that queue today runs to several decades, policy analyses have modeled the backlog clearing in timescales that often exceed a full working career.3 Workers who have built up enough time in the process can transfer to a comparable role at a new employer without losing their place, but only once a specific adjustment-of-status application has been pending for 180 days.4 Until that threshold, the queue position is tied to the employer. L-1B workers are even more constrained: the visa is specific to the sponsoring company, there is no portability provision, and if the employment ends, the visa ends with it.5 When the cost of getting fired includes blowing up years of immigration progress, your relationship to workplace risk changes in ways that aren't about courage or culture.
The first thing that changes is how people handle disagreement. Most employees already think twice before pushing back on a manager publicly. Add visa dependency and that hesitation gets much harder to overcome, not because the worker is passive or doesn't have a view, but because the downside of being wrong about when to speak up is much larger than it would be for someone with an easier path out. The engineers who keep their heads down tend to get better reviews, better projects, and more internal sponsorship. The ones who cause friction, even accurate and useful friction, get noted in ways that follow them. Organizations don't have to plan this outcome. It just happens through normal performance processes running over enough time.
What it looks like on the inside is a lot of side conversations that never make it into the room. A private discussion on why the architecture decision is wrong, never raised at the design review. The post-mortem that identifies the incident as preventable in private but produces a clean official write-up. The engineer who sends a note to a small Slack channel instead of the all-hands. Individually none of these look like much. Accumulated across an org and a few years, they add up to a culture where managers stop hearing bad news until it's very late.
The second thing that changes is how people approach innovation, and this is where I think the long-term cost is most underestimated by the companies themselves, because it's backfiring on their own bottom line.
Real innovation requires someone willing to be visibly wrong, and requires a degree of personal safety to do it well. You have to propose the thing that might not pan out, defend an unpopular position through the skepticism of a design review, spend weeks on something and then say it didn't work out. For someone whose immigration status depends on holding their job, the asymmetry of that bet is far more severe than for someone who, at most, loses their job. If the bet fails badly enough to cost them their position, the consequences run well past a performance note. In the worst case it's a managed exit, which starts a sixty-day clock, puts years of green-card progress at risk, and means uprooting a family and returning to a country they may not have lived in for a decade. If the bet succeeds, they get a good review cycle and maybe a raise. That's not a risk-reward ratio that makes people want to take swings. It produces the opposite: safe, predictable execution on work that's already been decided, from a team that ships reliably and invents almost nothing. The execution metrics look good quarter after quarter while the ideas that were never proposed and the bad product calls that nobody stopped accumulate quietly. The damage doesn't show up on a dashboard. It shows up later, when the org needs to do something new and discovers it doesn't have the muscle for it.
There's a related pattern that's easy to miss because it looks like productivity. When keeping the job is the primary goal rather than the secondary one, the work tends to drift toward whatever is most visible and easiest to defend in a performance review. Towards getting things done, but never completed. That often means overengineering: building something more complex than it needs to be, adding layers that demonstrate effort and technical depth, choosing the approach that produces the most impressive artifacts rather than the simplest one that would actually work. It also means promotion-driven development, where the roadmap gets shaped less by what the product needs and more by what generates the kind of output that advances careers, or at least protects them. Neither of these patterns is unique to visa-dependent workers. They show up anywhere that job security becomes the primary thing people are optimizing for. But the incentive is significantly stronger when getting it wrong doesn't just cost you a bad review cycle, but your legal status and everything you've built toward over years.
The third dynamic is that the system tends to reproduce itself through the people it promotes.
Managers who built their careers inside this system learn, through experience, that certain kinds of workers are easier to manage. They don't push back on scope creep. They don't threaten to leave when conditions get bad. They absorb overwork without making it a negotiation. When those managers start hiring and promoting, they tend to draw from the same networks and favor the same profile, often without thinking of it in those terms. Referral hiring concentrates along existing demographic lines. Low-friction engineers get promoted ahead of high-friction ones. Over time the org develops a kind of institutional preference for workers who are less likely to cause problems, and the structure of immigration dependency is one of the main things that creates that preference in the first place.
The immigration architecture that produced this outcome wasn't designed to produce it, and understanding where it went wrong helps explain why it's so pervasive. The per-country cap on employment-based green cards was a deliberate choice to prevent any single nationality from monopolizing permanent residency slots. The idea was reasonable: a healthy immigration system should draw from a broad range of countries, and no one national cohort should dominate the permanent workforce in a critical sector. The problem is that this logic was applied at the end of the pipeline, getting the green , and never extended to the front of it: getting the H-1B or L-1B visa.
H-1B visas have no equivalent per-country diversity cap. Neither do L-1B visas.6 Employers can sponsor as many workers from a single country as they want, and the market has done exactly that at scale. Indian nationals now account for roughly 70 percent of H-1B petitions in a typical year.7 The green-card system correctly tries to distribute permanent residency broadly, but by the time workers reach that stage, the intake has already been concentrated so heavily from one country that the cap produces an enormous backlog for Indian nationals specifically, while workers from most other countries move through quickly. The per-country diversity rule was applied at the wrong stage. You can't fix a pipeline concentration problem at the output when you've allowed unrestricted concentration at the input.
The case for fixing it doesn't require being against immigration. Tech, and our economy, has genuinely benefited from global talent and will keep doing so. The argument is that when one country provides most of the workforce in one critical industry, and those workers are structurally constrained by a backlog that compounds over decades, you've created a labor-control dynamic that nobody planned but that companies benefit from regardless of intent. The straightforward policy response is to extend the diversity logic that already applies to green cards to H-1B and L-1B approvals as well, so that no single country accounts for a large majority of work visa approvals in a given year. Canada's Express Entry system, which draws from a broad national distribution without creating per-country intake bottlenecks, is one example of what a better-designed front end looks like. That doesn't close the door on any individual engineer. It distributes the intake more evenly, the backlog concentration eases over time, and fewer workers end up in the decades-long queue that produces the dependency dynamic in the first place.
The team I started with is still shipping. The dashboard still looks good. The managers are pleased with the velocity numbers and the clean on-call rotation.
What the numbers don't show is the design review where the bad call went through without a real challenge, or the roadmap item that several engineers think is wrong but nobody has said so in a room where it would matter. There's probably an engineer on that team who had a better approach to something, thought through whether raising it was worth the risk, and decided it wasn't. That's not a character flaw. Given the constraints, it was the right call. The org just paid for it in a way that won't show up until later, when the thing they built doesn't work the way it needed to, and the people who saw it coming have no particular reason to say so now either.
It's worth being clear about something before leaving this topic. If you were in the same position, you'd probably do the same things. You'd keep your head down during the bad meeting. You'd write the private doc instead of raising the issue. You'd build the thing that gets you promoted rather than the thing that's right. Not because you're weak or cynical, but because you're rational and you have a family and years of your life invested in staying. The engineers navigating this system aren't doing anything that most people wouldn't do given the same constraints. That's precisely the point. The behavior that looks like passivity or careerism from the outside is just a reasonable response to a situation that was never designed with their interests in mind.
The problem is the system that creates those incentives, not the people who respond to them sensibly. The H-1B backlog, the per-country caps, the decades-long wait for workers from high-demand countries, the employer dependency that follows from all of it, those are policy choices, and they can be changed. The engineers caught inside the current system didn't ask to be put there, and most of them would tell you exactly what's wrong with it if they thought they could afford to. Fixing it doesn't require resenting the people it affects. It just requires being clear-eyed about what it produces and willing to say that a better design is possible.
-
H-1B workers have a sixty-day grace period after employment ends to find a new sponsoring employer, change status, or depart. Established by the January 2017 final rule on high-skilled nonimmigrant workers; codified at 8 CFR § 214.1(l)(2).
-
The USCIS Visa Bulletin, published monthly by the State Department at travel.state.gov, tracks when employment-based priority dates become current by country of birth. As of early 2026, EB-2 and EB-3 India final action dates sit around 2011–2012, placing the current gap at roughly fourteen years. Verify the exact dates against the bulletin in force at time of publication.
-
Backlog clearance projections are based on current annual visa number consumption rates. The National Foundation for American Policy and the CATO Institute have published analyses estimating the EB-2 India backlog clearing in timescales ranging from roughly 50 to over 150 years, depending on methodology and year of the analysis. Cite the specific most recent report at time of publication.
-
This protection is commonly referred to as AC21 portability, codified at INA § 204(j). The 180-day clock runs on the I-485 adjustment-of-status application being pending, not the I-140 approval date. A worker whose I-140 is approved but who cannot yet file an I-485 because no visa number is available does not yet have portability protection.
-
The L-1B intracompany transferee visa requires continuous employment with the petitioning employer or an affiliated entity; INA § 101(a)(15)(L). A worker who leaves that employer loses L-1B status. The practical option for staying in the country on a work visa is to obtain a new visa category , typically requiring an H-1B cap-subject petition subject to the annual lottery, which is a significantly harder path than H-1B portability.
-
The 7% per-country limitation on employment-based immigrant visas is established at INA § 202(a)(2). No equivalent per-country limitation exists for H-1B nonimmigrant work visas under INA § 214(i) or for L-1B intracompany transferee visas under INA § 101(a)(15)(L).
-
USCIS H-1B data consistently show Indian nationals accounting for approximately 70–75% of H-1B approvals in recent fiscal years, though the exact share varies by petition category and year. This figure refers to cap-subject initial approvals. Consult the most recent USCIS H-1B Data and Statistics annual report for the specific fiscal year and petition category breakdown.
Thoughts
-
The part the thread is underrating is the third dynamic, the promotion loop, because that is the part I actually operate. I have sat in the calibration rooms. Nobody says "promote the one who can't leave." What gets said is "low drama, high reliability, no flight risk," and those words map onto the constrained engineer cleanly without anyone having to name why. Run that for six cycles and the people now setting the bar for what good looks like are the ones who were selected for not pushing back. The bias does not need a villain. It needs a calibration sheet and a few years of nobody asking what "low drama" was standing in for.
-
"Complexity is easier to defend politically than simplicity" belongs on the company values slide. Nobody has ever been put on a PIP for the microservice that didn't need to exist. They put you on one for the one-file fix that worked and embarrassed the roadmap.
-
wait the L-1B part. if the visa just ends when the job ends and there's no transfer option at all, what do people on it actually do day to day? like is the entire plan just don't get laid off, ever? asking because that sounds even rougher than the H-1B thing everyone usually focuses on.
-
the getting things done but never completed line. OOF. lived it. we had a guy who shipped CONSTANTLY, dashboards green forever, and like two years in someone realized none of it actually closed the loop on anything, it was all impressive half-systems that demoed great. turns out when the only thing you can't afford is to be visibly wrong, you optimize for the artifact, not the outcome. the post nails that this looks exactly like productivity from the outside. that's the trap. you can't see it on the velocity chart, you see it the day you need the thing to actually work.
-
Worth getting the portability detail exact because people misread it constantly. The 180-day clock the post mentions runs on the I-485 being pending, not on the I-140 approval. If your priority date isn't current you can't file the I-485 at all, so an engineer can have an approved I-140, years in the queue, and still zero portability protection. That makes the lock-in stronger than a casual reader would assume from sixty days, not weaker. The footnote actually has this right, but half the comments here are talking as if I-140 approval frees you up, and it does not.
-
Honest question about the central move here. The post says after a few orgs you start to wonder what they have in common, and the answer turns out to be the visa thing. But how would you tell that apart from every other reason teams go quiet? I've watched the exact same silence in all-citizen teams under a manager who punished one person publicly once. The mechanism the post describes is real, I just don't see how the observation that some passive teams had a lot of H-1B engineers gets you to that being the cause rather than something both correlate with.
-
I want to steelman this carefully because the mechanism is more real than the comment section is giving it credit for, and also narrower. The post is not claiming visa holders are passive people. It is claiming that normal performance processes, run over years, quietly reward low-friction behavior, and that immigration dependency raises the cost of friction at the margin. That is structurally true and I have watched it in calibration rooms. What the post underweights is that local engineers with mortgages, a tight team they like, and one income produce nearly the same curve. The visa is an amplifier on an incentive the org already built. Useful to name the amplifier. A mistake to pretend it is the whole signal.
-
The line that landed for me was "the org just paid for it in a way that won't show up until later." That's the whole thing. I have watched a known-bad architecture decision sail through review because the two people who could have killed it were both mid-green-card and were not going to be the ones to spend social capital on a design fight. The decision debt sat there for eighteen months and then paged us at 2am during a migration nobody staffed. The dashboard was green the entire time. Reliability cost is always obvious too late, and visa dependency just makes the silence cheaper to buy.
-
Genuine question for people who have actually been on the constrained side of this, because the thread is full of citizens confidently narrating an experience they have not had. Does the silence actually feel like a calculated bet the way the post describes, or does it feel more like ambient background pressure you stop noticing? The post makes it sound like a clean cost-benefit decision in the moment. I suspect the reality is mushier and worse, where you do not even register the thought you decided not to voice. Curious whether the framing matches the inside view.
-
The line that will stay with me is the org discovering it doesn't have the muscle when it needs to do something new. I run infra and I can tell you exactly what that looks like from the inside. A team that has spent four years executing decided work has no one left who remembers how to argue with a roadmap, because the people who would have are the ones who learned that arguing cost them. You inherit a codebase full of safe, defensible, overbuilt choices and not one person who can tell you which of them was actually load-bearing. That bill is real, it just lands on whoever shows up after the velocity numbers stop mattering.
Related discussions
-
Do you have to miss your goals to get promoted?
Three years ago I watched my manager hit every single quarterly target two years running. Clean dashboards. Green everywhere, all the time. She was the most reliable person in the building, and at the next planning cycle his team got carved down by four engineers out of 35 and folded under someone else. Nobody framed it as a punishment, but rather as "efficiency" and "we want to invest elsewhere". The lesson landed anyway, and not just on me. Sadly, never on my manager.
-
Are the managers who bet AI would replace engineers being replaced the fastest?
Last year my LinkedIn feed had a genre. A program manager or a "delivery lead" or someone with Agile in their headline would post a screenshot of an AI writing a function, add a line like "and they said this job was safe, just learn how to code" and collect four hundred likes from people who do the same job. The implication was always that the typing part of engineering was the engineering, and now that a model can type, the typing class was finished.
-
Why does Silicon Valley talk about death like it's a software bug?
One of the clearest signs that modern secular elite culture is uneasy about death is how Silicon Valley talks about it. The human body is treated like legacy hardware waiting for an upgrade. In place of acceptance, you get optimization: longevity startups, cryonics, extreme biohacking, and constant speculation about whether enough computation and biotech might eventually defeat death itself. Tech billionaires talk with pride about potentially transferring their consciousness to a computer, as…
-
Are the humanities more needed than ever in the AI age?
No parents encourage their kids to study Humanities. By default, recommended options are STEM related. Engineering (Computer Science), Finance, Medicine...The argument against the humanities in the AI age makes it even less compelling to dedicate 4 years to study a Humanities degree. Language models can write passably, summarize quickly, and produce research-shaped text on demand. So the old humanities skills are supposed to matter less. Learn to code, learn to prompt, and stop pretending close.
-
Is it execution, not innovation, that actually makes companies succeed?
One thing that starts looking fake after enough years in tech is the obsession with “disruption” as the explanation for every successful company. The winning company simply executed better than everyone else in a market that already existed. Facebook was not some impossible conceptual breakthrough. Social networking already existed. MySpace existed. Friendster existed and the majority of features Facebook had were present in these 2. People already understood the product category immediately.…
-
Are Silicon Valley tech bros really conservative, or just tagging along for lower taxes?
One of the biggest mistakes modern conservatism made was assuming that because Silicon Valley liked markets, it must also share conservative values. It didn't. Tech culture was never traditionally conservative. It was hyper-individualist, anti-tradition, impatient with limits, suspicious of religion, and obsessed with optimization over continuity. Conservatives saw money and entrepreneurial energy and ignored the rest. Now the contradiction is impossible to miss.
-
Are companies now incentivized to sell subscriptions instead of products?
The HP printer example is still the nuts to me. To many users, it stops working, not because anything inside it broke, but because the ink subscription lapsed and the manufacturer's software disabled cartridges you already owned . The printer is physically there and it just stops working
-
Does splitting 'hard' and 'soft' skills make people worse at both?
Hard skills are measurable, specific, and teachable abilities or technical knowledge gained through education, training, or experience, which is often directly related to a particular job or industry. Examples include data analysis, programming, graphic design, accounting, dancing, painting… They are usually the core of a profession, particularly the part of it excluding interaction with other people. On the other hand, soft skills are mostly defined as “personal attributes, interpersonal....