The AI Hiring Gap Nobody's Talking About (And Why Indonesian Devs Should Care)

Last month, I was reviewing CVs for a contract role at a startup in Karachi. I noticed something odd: every single global applicant had "AI" or "LLM" plastered somewhere on their resume. The local candidates—equally skilled, if not more—barely mentioned it. I didn't think much of it until I stumbled on a dataset that quantified something I'd only felt anecdotally: there's a massive gap in how AI appears in job listings between the global remote market and what's actually being posted in places like Indonesia.

The numbers hit different when you see them in writing. We're talking about a 28x difference. Not a small variance. Not a rounding error. A full order of magnitude separating what employers are signaling when they hire globally versus locally.

This isn't just noise. This is a real market signal, and if you're a developer in this region—or hiring one—you need to understand what's happening beneath the surface.

What the Data Actually Shows

Someone ran a straightforward comparison: they pulled Indonesian IT job listings from JobStreet and Loker.id (about 1,000 posts) and compared them against 2,500 global remote listings. Then they did a simple title-level scan for AI-related keywords.

The result? Global remote jobs showed AI signals in 8.6% of titles. Indonesian listings? 0.3%. That's roughly 3 mentions in a thousand local postings versus 216 in the global pool.

Now, the methodology has real limitations—this is a title-only scan, not a comprehensive analysis, and it's a snapshot from a specific time. But here's the thing: job titles aren't just descriptions. They're signals. They're what employers use to position themselves in the market and what candidates use to understand what's valued.

The Real Problem: Visibility Creates Reality

I've been in this long enough to know that when markets shift, the signals precede the substance. Title inflation exists for a reason. If global companies are explicitly calling for "AI experience" in the job listing—even if the actual work is tangential—they're creating a perception that AI fluency is table stakes.

In Indonesia, that signal is almost absent. And absence creates its own problem.

When a developer in Jakarta is writing their CV, they see global postings screaming for AI experience. They see their local job market staying silent on it. Naturally, they start to think either: (a) AI doesn't matter as much locally, or (b) employers here don't expect it, so why bother learning it deeply?

Meanwhile, global companies are already pricing AI experience into their offers. They're marketing it. They're making it visible. And that visibility becomes a self-fulfilling prophecy—more people invest in learning it, more employers expect it, more jobs explicitly mention it.

My Take: It's Not Actually About AI

Here's what I think the 28x gap is really measuring: it's a market maturity and signaling gap, not necessarily a capabilities gap.

I don't believe Indonesian developers are 28x less capable with AI tools. What I think is happening is that the global remote market has already commodified AI as a hiring signal, while the local market hasn't. Yet.

That's both a problem and an opportunity, depending on which side of the hiring table you're on.

If you're hiring locally, you have a window. Your competitors aren't explicitly asking for AI experience, which means the talent pool hasn't self-selected into learning it. If you start posting roles that emphasize AI capability now, you'll attract developers who've already made that investment—and you'll be ahead of the curve when the market inevitably catches up.

If you're a developer in this region, the play is obvious: get good at AI before it becomes the baseline expectation. Right now, that's a differentiator. In two years, it'll be assumed.

What I'd Do Differently

The study looks at title keywords, but I'd want to go deeper. I'd break this down by role type—because I suspect the gap isn't uniform. Frontend roles probably show even less AI mention globally than backend roles. The 28x gap might be hiding important granularity.

I'd also want to track this over time. Is the Indonesian market accelerating toward AI mentions, or staying flat? That trend matters more than a single snapshot.

The Real Question

If you're building teams here, what does this mean for your hiring strategy? Are you matching the global market's signals, or staying local? And if you're a developer, are you betting that your local market will catch up, or hedging by learning what the global market is already demanding?

The gap won't stay this wide forever. The question is whether you're going to be ahead of it or behind it.

Source: This post was inspired by "Indonesian IT job posts mention AI 2career, data, indonesia, remote8x less than global remote roles - the data" by Dev.to. Read the original article