Waypoint

The best applicant-tracking systems on the market are built for the employer. Nothing on the market is built for the person doing the applying with any of the same rigor.

Waypoint is that system, built the way I would have wanted it when I was the recruiter on the other side of the table.

The instinct

The Moove case study ends on an automation thread — Apps Script matching payroll rows, self-serve interview scheduling, an onboarding workflow rebuilt to eliminate handoffs. Waypoint is the same instinct applied to my own job search: the tool the function should have had, built by the person who runs the function.

What it is

A native macOS application. Not a web app, not an Electron shell — a Swift + SwiftUI project that opens in half a second and behaves like a Mac app because it is one.

• Local-first. SQLite on disk. Your search doesn’t live in someone else’s database.
• LLM tooling, live-validated. The parts that call a model — role extraction, résumé/JD fit scoring, follow-up drafting — are wrapped in a validation harness that runs against real fixtures on every build. No silent regressions when a provider changes behavior.
• Self-contained. 313MB bundle, no external services required to open the app and work in it.

Why the numbers matter

Three of the metrics in the strip above are load-bearing:

• 192 sidecar tests. The core logic — models, queries, LLM adapters, state reducers — has behavioral coverage, not just type coverage.
• 243 harness checks. The LLM-facing surfaces run through a separate harness that treats the model as an unreliable dependency rather than a library call.
• 36/36 roadmap items. Every item on the plan is shipped, tested, and in the running binary. No wishlist masquerading as a changelog.

A résumé claim of “built a macOS app” is worth nothing without the second half of the sentence. These are the second half.

What this is on the site

The reason this page exists on a career site rather than a plugin site: it is proof that the automation thread from Moove is not a one-off. The demonstration is not “look, I can ship.” It is: given a domain I already know end-to-end, I build the software that domain should have had, and I finish it.

That is the pattern the case studies exist to make legible. Waypoint is item four in that pattern, not the first item outside it.

Repo stays private — the app is in daily personal use. Screenshots, architecture notes, and the harness writeup do the work here.