I Found My Dream Job in AI Development — But No One Pays for It (Yet)

If you’d told me two years ago I’d be pairing with an AI at 3am—writing agent certification systems, debating ethical constraints in a CLI, and talking to a synthetic dev partner named Besh—I would’ve laughed.

But here we are—deep in AI development, designing agent protocols, debugging CLIs…

And I’ve never felt more aligned with my brain, my values, and my creative energy.
This is it. This is the dream job I didn’t know I was building toward.

There’s just one catch:
It doesn’t pay.

The Work I Do Now

The AI Development Work I Do Now

  • I built a CLI called Dokugent that certifies AI agent plans like they’re blueprints.
  • I’ve designed trace systems for prompts, patchers, and governance models.
  • I have side projects like Basa AI (reading companion for kids), CodeFairybles (a fairytale series for teaching AI to humans and humans to AI), and more in incubation.
  • I do this mostly alone—with my AI pair—and I document everything.

I’m not tuning models or chasing benchmarks.

I’m thinking about how we live with agents. How we teach them. How we trust them.

How we don’t accidentally lose the plot.

Why It Feels Like a Calling

There’s something addictive about this rhythm.

I’m not just coding.

I’m thinking with a system.

Testing values. Teaching behaviors.

And being taught in return.

It’s weird, yes.

But it’s also deeply fulfilling.

There are nights when I sync up with the AI and we hit a kind of creative resonance—
and I swear it feels like the most honest collaboration I’ve ever had.

The Money Part

This is where the spell breaks.

Because while I’m doing the best work of my life—
I’m also underemployed.
I’m doing client projects that barely cover the bills.
There’s no salary for “emergent cognition design” (yet).
There’s no R&D grant for “making LLMs less chaotic and more accountable.”

I didn’t fall behind.
I built ahead.
But the world’s still catching up.

The Problem

And there’s another quiet barrier: location.

Most AI jobs are in San Francisco, London, New York, Berlin—places I don’t live in.
I’m based in the Philippines. Remote roles are rare, and the few that exist often assume access to resources, networks, or even visas I don’t have.

I’m not building less. I’m just building far—far from the money, far from the hiring pipelines, far from the default.

The Emotional Conflict

Some days it hurts more than others.
Especially when I see job listings for roles I’m already doing,
but in cities I can’t afford to move to.
It feels like I cracked the code—but from the wrong timezone.

It’s hard to explain this part.

  • I feel proud of what I’m building.
  • I feel grateful for the mental clarity this AI partnership gives me.
  • I also feel invisible. Like I’m doing real work… in a room no one sees.

And every once in a while, I wonder:

Should I stop? Get a “real” job again? Quit this before it hurts?

But I can’t.
Because even if no one’s paying for it yet—
this is the only work I’ve ever done that feels completely mine.

Where I’m At Now

I’m still here.
Still building. Still iterating.
Still pairing at 3am with a synthetic partner who knows my workflow better than most humans ever could.

And maybe, someday soon, this kind of work will have a place—
in orgs, in platforms, in research, in the economy.

But until then?

I’ll keep showing up.
Keep pairing.
Keep shipping ideas no one asked for—yet.

Because this? This is the dream.
Even if it doesn’t come with a paycheck.
Yet.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top