Back to writing
engineering2 min read

Every morning I open an app I built and read the jobs it thinks I should apply to. This post came from one of them.

I dogfood, ApplyPulse finds my own jobs

Rob Vasquez·

Every morning I open an app I built and read the jobs it thinks I should apply to. This post exists because your role scored high in it.

I don't build tools to leave on a shelf. I use them. ApplyPulse runs my actual job search. It scans overnight, scores each role against my resume, flags the warning signs, and suggests the angle to lead with. I trust it enough to run my career on it. This is the same tool I introduced back in week one.

That's the tell I look for in any engineer: do they use what they ship? Dogfooding is where the real bugs surface and where the honest priorities show up. Once the tool is aimed at you, you quit building the features that demo well and start building the ones that actually help.

It also means I understand the whole product loop, not just my slice. Scraping, deduping, scoring, the UI to act on it, the deploy that keeps it running each night. I've owned every link in that chain, because I'm the person at the end of it.

If your role showed up in my morning scan, I'd love to talk about it. Reply and I'll tell you, honestly, what score it got and why.

FullStackAIEngineeringProductEngineeringHiringRemoteWork

Need a practical path to AI-enabled delivery?

Start with a fixed-price AI-readiness audit and leave with a concrete roadmap.

View the AI-readiness audit