Iran, Oil, and the Tech Economy — How Geopolitics Shows Up in Your Job Search

A few weeks ago, Iran declared the Strait of Hormuz closed in retaliation for US military strikes. Overnight, 20% of the world's oil supply was disrupted. Brent crude surged past $115 a barrel — nearly doubling from where it started the year. Gas prices in California crossed $5 a gallon. Goldman Sachs bumped their US recession probability to 30%.

You're reading a developer blog, not a geopolitics newsletter. So why am I writing about oil tankers?

Because if you're a CS student or junior dev looking for work right now, this conflict is already affecting your job search — you just might not see the thread connecting a naval blockade in the Persian Gulf to the rejection email in your inbox.

The Chain Reaction: Oil to Cloud to Your Career

Here's the thing about the modern tech economy: it runs on electricity. Not metaphorically — literally. US data centers now consume 176 terawatt-hours annually, about 4.4% of national power. Wholesale electricity costs near major data center hubs have surged 267% over five years. And that was before a major oil supply shock.

When energy gets expensive, everything downstream gets expensive too. Cloud computing costs were already projected to rise in 2026 — global public cloud spending is heading toward $850–900 billion this year. GPU instances cost 5–10x what regular compute does. Microsoft spent nearly $35 billion in a single quarter on cloud and AI infrastructure capex, up 75% year-over-year. That money has to come from somewhere.

And when companies' operating costs spike, the budget axe swings toward the line items that are easiest to cut. Often, that's headcount — specifically, the roles that are hardest to justify on a spreadsheet. Like the junior developer position that "we'll fill next quarter."

Why oil prices affect tech companies that don't use oil

Oil price shocks ripple through the economy in ways that aren't obvious. Higher energy costs increase the cost of running data centers, offices, and manufacturing. They raise transportation and logistics costs, which affects supply chains for hardware. They reduce consumer spending power, which hurts ad-revenue-dependent companies. They create macroeconomic uncertainty, which makes investors risk-averse, which tightens VC funding, which means startups hire fewer people. The Dallas Fed modeled the Hormuz closure dropping global GDP growth by 2.9 percentage points in Q2 2026. That's not a rounding error — that's a recession-scale contraction.

The Hiring Landscape Right Now Is Brutal — And Getting Worse

Let's look at the numbers honestly. According to Crunchbase, over 150,000 tech jobs have been cut in 2026 so far, and analysts project that number could reach 264,000 by December. Goldman Sachs estimates the oil price surge alone will reduce US payroll growth by roughly 10,000 jobs per month through the end of the year.

But here's what's really worth paying attention to: the market is bifurcating. AI and ML job postings are up 34% year-over-year. Overall tech postings are down 8%. Companies aren't just cutting — they're reallocating, eliminating generalist roles to fund specialized AI positions. If you're a junior dev with no AI exposure, the shrinking slice of the pie is getting even smaller.

Meanwhile, VC funding is concentrating into fewer, larger deals. AI accounted for nearly half of all global VC funding in 2025, with AI deal sizes running 11x larger than non-AI deals. Defense tech hit record highs — $29 billion, nearly triple the 2020 total. The small, scrappy startups that historically gave junior devs their first break? They're getting less funding and hiring fewer people.

The "low hire, low fire" trap

Fed Chair Powell described the current labor market as "low hire, low fire" — companies aren't mass-firing, but they're not hiring either. For junior devs, this is arguably worse than a dramatic layoff cycle. In a layoff cycle, positions eventually reopen. In a "low hire" market, the positions just... don't exist. Roles get absorbed by existing team members, automated with AI tools, or indefinitely "paused." The result is a shadow hiring freeze that doesn't make headlines but absolutely shows up in your application response rate.

What This Actually Means for Someone Like Me

I'll be honest — reading about this stuff while simultaneously applying for co-op positions and summer work is a particular kind of anxiety. It's one thing to intellectually understand that geopolitics affects the economy. It's another to watch oil prices spike and think, "is this why I haven't heard back from that startup?"

But here's where I've landed after sitting with it: understanding this stuff is itself a competitive advantage.

Most junior devs I know have zero mental model for why hiring markets tighten. They think in terms of "is my resume good enough" and "did I practice enough LeetCode." Those things matter, but they exist inside a larger system. When a company's cloud bill jumps 20% because energy costs spiked, and their Series B investors are getting nervous because geopolitical uncertainty is delaying IPO timelines — that's not about your resume. That's macroeconomics.

Knowing this doesn't make the market easier, but it changes how you respond to it. Instead of panicking about what's wrong with you, you can make strategic decisions about where to focus your energy.

So What Can You Actually Do?

Follow the money, not the hype. Defense tech is booming. Energy infrastructure is getting massive investment. Healthcare and logistics are hiring. If you're only applying to consumer SaaS startups and FAANG, you're fishing in the most overfished pond. I wrote about this with the World Cup too — some of the best tech work happens in industries you'd never associate with software development.

Make yourself legible in the AI conversation. You don't need to become an ML engineer overnight. But having a project that uses an LLM API, or contributing to an open source AI tool, or even being able to articulate where AI fits and doesn't fit in a system architecture — that puts you in the growing 34% of the market, not the shrinking 8%.

Think about cost-consciousness as a skill. When cloud costs are rising and budgets are tight, the developer who can optimize a query to cut the AWS bill by 15% is more valuable than the one who ships a flashy new feature. Performance, efficiency, and infrastructure awareness are the skills that matter most in a cost-constrained environment. Learn to read a cloud bill. Understand how autoscaling works. Know what your code actually costs to run.

Build resilience into your career the same way you'd build it into a system. I've talked about infrastructure resilience before — redundancy, graceful degradation, circuit breakers. Apply the same thinking to your career. Don't have a single point of failure. Don't bet everything on one company, one technology, or one market sector. Have fallbacks. Diversify your skills.

Practical steps for a tough market

Some things that have helped me: (1) Track where VC money is flowing — Crunchbase and PitchBook publish quarterly reports. If a sector is getting funded, it's going to need developers. (2) Look at government and public sector tech jobs — they're counter-cyclical and Ontario has a growing GovTech ecosystem. (3) Don't sleep on contract work. When companies are afraid to commit to full-time hires, they still need contractors to ship features. (4) Keep building in public. In a tight market, a strong GitHub profile and a blog that shows you think clearly about technical problems can differentiate you when resumes blur together.

The Bigger Picture

Here's what I keep coming back to: the tech industry has never existed in a vacuum, and pretending it does is a liability. We like to think of software as this clean, abstract world where the only variables are code quality and technical skill. But our industry runs on electricity generated from fossil fuels, funded by capital that flows based on geopolitical stability, serving customers whose spending power is shaped by macroeconomic forces we don't control.

A naval blockade in the Strait of Hormuz. A spike in Brent crude. A nervous VC pulling back on a term sheet. A startup "pausing" its junior dev hiring. These are all nodes in the same graph.

You don't need to become a geopolitics expert. But developing a basic literacy for how the world outside of tech affects the world inside of tech will make you a better developer, a better job candidate, and a more resilient person. The junior devs who understand systems — not just software systems, but all the systems — are the ones who'll navigate this market and come out stronger on the other side.

The Strait of Hormuz will reopen. Oil prices will stabilize. The hiring market will recover. It always does. The question is whether you used the downturn to panic, or to prepare.