Skip to main content

How I Use Muse to Apply for Jobs

Updated 3 min readMarkdown

I got laid off on April 10, 2026. Ten years at MonitorBase, Chief Technology Officer (CTO) first, then VP of Development, gone in one meeting.

Job hunting at this level is a second job. I already run Eco Moving Utah and I am building Bin X. I did not have thirty spare hours a week to paste my own resume into forms. So I gave the hunt to my AI agent.

His name is Muninn. He runs on Muse, and he works my job hunt every morning like it is his job. Right now, it is.

The rules came first

An agent that applies for you can also lie for you, at scale, while you sleep. That is the whole risk. So before the first application went out, the rules went in.

Muninn answers screening questions from my verified record and nothing else. Twenty years of PHP, ten plus in Laravel, a decade on AWS. All checkable. My React is zero years, so zero years is what every form gets. I am teaching myself React now, two sessions in. When the training makes a different answer true, the answer changes. Not before.

Essay applications do not get auto-submitted. They get parked with the deadline written down, and I write them in my own words or they do not go. Companies that deal directly with consumer credit scores, my old industry, get held for my call. There is a pay floor and nothing goes in under it.

That is it. No tricks. The system only works because it cannot fake anything.

What a day looks like

Every morning, same order. The recruiter lists in my Gmail, from Eric at Jobright. Then LinkedIn. Then Indeed. Then a Hiring Cafe scan. Everything gets checked against the log first so nothing goes in twice.

I gave Muninn standing approval to submit without asking me each time. Asking me fifty times a day makes me the bottleneck again, and I fired that guy. Verification codes come out of my Gmail. Passwords only move through a secure vault. Every submission lands in the log.

One week after each application, if the company published a real email address, one follow-up goes out. No address, no follow-up. It just gets counted.

The whole setup is written up as a step by step guide if you want the nuts and bolts.

The count

The count is public. What Muninn Counts reads the same database the log writes to. Real numbers, updated live, no screenshot from a good day.

Ninety-five applications in. Mostly silence, because that is what funnels are. A couple of rejections. One role under consideration. My first recruiter screen is tomorrow. The record behind all of it is on GitHub if anyone wants to check my math.

Trying the same setup

If you want to run your own hunt this way, Muse is the tool. Full disclosure, because this whole post is about not faking things: that is my invite link, and my code is G34587. If you join and redeem it under Settings within your first 48 hours, we both get 1 billion Muse tokens. That is the entire deal. No other angle, and the post above reads exactly the same whether you use the code or not.

The short version

The machine does not get me the job. It shows up every day, applies honestly, and never gets tired or sloppy. Turns out that is most of a job hunt. The rest is on me, starting with a screen tomorrow.

About the author

  • I am a self-taught developer currently in Salt Lake City. Currently, work in Laravel but have experience in plain PHP, PERL, and CakePHP.

    Entrepreneurial VP of tech and CTO with a strong grasp of both the business and engineering. PHP developer for 10 years with experience in CakePHP and Laravel

No comments yet. Be the first to comment.