Job Radar: Goal and Result
The work got done. The feedback was thin. The direction moves from scale to hit-rate.
Job hunting is itself a repetitive pipeline. The same experience, re-explained for every company; the same question, re-answered for every form. I wanted to measure one thing: hand the whole pipeline to a machine and find out how hard a cold-start job search actually is. Job Radar runs the entire process for me, and then I watch what the real world sends back. Not to spray applications — to measure.
The Methods
- One source of truth about myself, maintained once. Experience, projects, boundaries, reusable answers — all in one
candidate_kb. Every application’s material, form answers, and pitch derive from it. I stop deciding per application. - Automated discovery and scoring. Scan AI labs, startups, fellowships, and builder roles across Greenhouse and Ashby boards, plus founder posts on HN and communities; score against my real positioning; stage the high-fit ones into a queue.
- Gated automated outreach. A Gmail pipeline capped at 30 a day, claim-send-record in three steps with live bounce and reply monitoring; founder DMs and ATS applications run in parallel.
The Result (Real Numbers)
- The scale was real. The system reviewed and scored 29,007 leads across 24,553 companies and mined 36,256 contact channels. On the discovery end, the machine works.
- The volume was real too — but the bounce rate was high. It sent 324 cold emails to 320 people. 93 of them hard-bounced — roughly 29% never landed.
- Almost nothing came back. Of the ~230 that did land, replies from actual humans were in the single digits: one positive, one to follow up, one rejection. Call it a 1% human-reply rate, with positive replies near zero. The safe sendable pool then drained to zero effective unsent, and the volume stopped.
What’s Worth Watching Next
- From cold volume to high-intent channels. Stop refilling a pool just to hit 30 a day; go where the project and the founder’s intent are visible — YC/Wellfound/small-team roles, founder and project-owner channels, Bonjour-style direct applications.
- Tailored proof-of-work outreach. One precise direct application beats dozens of generic sends; only target where intent and my positioning — hands-free agent, voice, ADHD workflow — clearly line up.
- The machine moves to the background; the human only judges. Automation stays on for monitoring; the system handles the mechanical part, and the human only decides whether a target is worth tailoring for.
The takeaway: a machine can push out volume, but it can’t manufacture someone else’s demand. The bottleneck was never scale. It was hit-rate and channel.
Job Radar:目标和结果
工作做了,反馈很少,方向从规模转向命中。
找工作本身就是一条重复的流水线:同一份经历,换个公司要重讲一遍;同一个问题,换张表格要重答一遍。我想测一件事 — 把这条流水线整个交给机器,冷启动找工作到底有多难。Job Radar 替我把全过程跑一遍,然后我看真实世界会回什么。不是为了海投,是为了测量。
用了哪些方法
- 一份关于自己的事实,只维护一次。经历、项目、边界、能说的话、可复用回答,全进一个
candidate_kb。每次申请要的材料、表单答案、pitch,系统从这里派生,我不再逐份决定。 - 自动发现 + 打分。扫 AI labs、startup、fellowship、builder 岗位,横跨 Greenhouse、Ashby 公开招聘板,加上 HN 和社区里的创始人帖;按我的真实定位打分,高匹配的进申请队列。
- 带闸门的自动外联。Gmail 管线每天上限 30 封,claim-send-record 三步加退信和回复实时监控;创始人直接私信和 ATS 申请并行。
结果是什么(真实数字)
- 规模是真的。系统评审打分了 29,007 个线索、覆盖 24,553 家公司、挖出 36,256 条联系渠道。发现这一端,机器完全跑通了。
- 发出去的量也是真的,但退信率高。真正发出 324 封冷邮件、触达 320 人,其中 93 封直接硬退信 — 约 29% 根本没打到。
- 回音几乎没有。落地的约 230 封里,来自真人的回复是个位数:1 封正向、1 封待跟进、1 封拒绝。约 1% 的人回,正向趋近于零。随后安全可发的池子被抽干到「有效未发 = 0」,量就停了。
接下来值得看的
- 从冷量转向高意向渠道。不再为凑满 30/天刷池子;主攻能看见项目和创始人意图的地方 — YC/Wellfound/小团队岗位、创始人/项目主渠道、Bonjour 式直接申请。
- 用作品说话的定制外联。一封精准的直接申请,胜过几十封通用群发;只打意图和我定位(hands-free agent、语音、ADHD 工作流)明确对得上的。
- 机器退后台,人只做判断。自动化留着做监控;系统处理机械部分,人只判断一个目标值不值得为它定制一次。
结论:机器能把量发出去,发不出别人的需求。瓶颈从来不是规模,是命中率和渠道。