A note on this archive: an earlier version of this site was lost in a migration, with no surviving backup. This piece is a good-faith recreation of our writing from this period, not a recovered original; its date reflects the period it represents. See about this archive.
If your hiring plan for this year runs through an H-1B visa, the last couple of months probably gave you heartburn. The annual cap filled almost as soon as the window opened, premium processing got suspended, and a new executive order told the agencies to tighten how the program works. If you were counting on bringing someone in that way, you're now refreshing a status page and hoping.
Here's the uncomfortable truth: that's not a paperwork problem. It's a planning problem.
A roadmap shouldn't depend on a coin flip
You can do everything right — sponsor a great candidate, file on time, pay for the expedite — and still lose them to a lottery, or get them half a year later than you needed. When the thing your roadmap depends on is decided by a random draw and shifting policy, it isn't really a plan. It's a wish with paperwork attached.
And this isn't a one-year blip. The cap has been oversubscribed for years, because it sits downstream of something we keep coming back to: there aren't enough senior developers to go around. Everyone reaches for the same scarce people through the same narrow pipe. The visa squeeze is a symptom of the shortage, not a separate problem.
A visa is one door, not the only one
Here's the part that gets lost in the scramble: a visa is just one way to reach talent that doesn't already live in your city. It is not the only way.
If a developer does excellent work from where they already are, you don't need a visa, a relocation package, or a lottery ticket. What you need is a way of working together across distance — which, as we've written, is a discipline you can actually learn. The companies that have built that muscle aren't sweating the cap this spring, because their access to good people was never tied to it to begin with.
Build the plan that doesn't depend on a draw
You don't have to abandon the visa route. You just shouldn't bet the roadmap on it. A few things help:
- Treat "where" as a variable, not a constraint. The moment you're open to a developer working from where they are, the lottery stops being your only option.
- Have a remote path ready before you need it. A denied or delayed petition shouldn't be the thing that stalls a quarter.
- Plan capacity around what you can control. Build your timeline on people you can actually start, not on a draw you might lose.
To be clear, this isn't a take on whether the policy is right or wrong — that's a different conversation. It's a take on a simpler thing: your ability to ship shouldn't hinge on something entirely outside your control. Widen the map, and it doesn't have to.