The whole thing essentially runs on 1 VM with Playwright, Postgres and a handful of systemd timers. It's several nightly batch jobs (hourly to disperse a growing user-base across many hours, hopefully ;)).

The part that took forever to get right was the workflow for determining if a job was actually live on the company's ATS system. There is SO much garbage on the main job boards. The naive version checks the HTTP status, but a dead Workday or aggregator listing happily returns 200. So I'd get confident LLMs excited to link me to a "this position has expired" page... passing garbage is obviously never ok for this to work. That's why I had to go "real browser". It plays nice in the marketing but that gating is a necessity that the whole thing is kind of built around. It waits for the page to actually render, uses LLM intelligence to read the whole body and fails if it can't confirm the job is real. It's kind of awesome.

Happy to go deeper.

Morning Stack runs overnight. While my users sleep it works through the big job boards (and some niche ones), and then it tries to disprove every listing before it trusts one.

Is the job even real? - It opens the posting in a real browser (Playwright) and checks. There's no API scraping and we don't login to anything. Then, we resolve back to the company's own ATS page so you can apply directly to them. If it can't find it, the job is dropped.

Does it match what you asked for? - An LLM crosschecks the job description against your profile (Resume, Career Story, and Desired Roles, Comp Band, Geography and Benefits). The more specific you are, the less jobs you'll ultimately receive. That's kind of the point.

For the few surviving contenders, it tweaks your actual resume to the job description and drafts a cover letter for each. A separate verifier re-reads those against your actual resume, stripping any facts it can't support. We avoid AI-BS with a 3-strike rule: if it can't support a claim after three tries, it drops the job and moves on instead of shipping something fabricated.

By 7AM, you've got a small stack (up to 3) of real openings with finished packages.

- You see a little bit of good intel on each (company and job info, and any outliers like high-comp or unlimited PTO). - You review them to determine if you're interested. You polish and submit yourself on the company's most direct site.

That's it. It's your reputation; you control it. Here's a few things I deliberately did not build this for:

It never logs in to any of your actual accounts and it never auto-applies on your behalf. This is a really terrible trend in my opinion. I don't think it's working and I don't think people trust it. "Spray-and-pray" isn't the right fit for people who care about the outcome of their career and you will always be the one who submits under your own name.

Opening for a small beta cohort this week. There's a waitlist. The link is above.

Happy to get into the architecture or the ToS reasoning in the comments.

Comments URL: https://news.ycombinator.com/item?id=48533919

Points: 3

# Comments: 1

So my question would be: what's the pitch for teams that have the engineering bandwidth to roll something custom out themselves? I think teams that are early adopters for heavy agentic AI use are also typically pretty security conscious. We do heavy sec reviews before we even consider another vendor in the space. I think, for us, that puts the barrier to adopting this over building and tweaking internally just too high.

And ultimately, the thing that would keep us from reaching for a third-party app for this gap is exactly the concern you flag at the end. I wouldn't want my company's full context (and it would have to be very full for this to be effective) sitting in someone else's single-point data layer. A breach could level our entire business.

Is self-hostable high up on the road map? Personally I think this idea lives and dies by it.