Anduril Industries
SpaceX
Databricks
OpenAI
Affirm
Roblox
Elastic
AnthropicWhat "auto apply" should and should not mean
Most tools sold as auto-appliers spray one generic resume at hundreds of postings. That is not automation, it is volume, and it is the reason a lot of applications never get read. Every application is taken to the point where it is ready to send: a resume rewritten for that posting, a cover letter that could only have been written for that company, and a fit score. Sending it is then your call, and there are three answers. Press send yourself. Press the button on one application and I fill in that employer's form for you. Or switch on the daily run and I do it unattended, on a limit you set. Two of the boards will only take a form that was filled in on your own machine, so there the filling happens in your browser through a small extension you add once, and the submit button is yours to press. Some employers hold an application back until a code they have just emailed you is typed into the form; where you have connected your mailbox I read that one code out of it and finish, and where you have not the application waits for you with everything else already filled in. What I will not do is invent an answer to a question you have never answered, work around a login wall or a CAPTCHA, or send the same application twice: each of those stops the send and hands you the posting instead.
- Automated: reading the posting, rewriting your resume for it, drafting the letter, scoring the fit, tracking the outcome.
- Automated if you ask for it: the picking. Switch on the daily run and every weekday morning the best few openings are already written up and waiting, on a limit you set.
- Automated if you ask for it: the sending. One button per application, or unattended as part of the daily run. Off until you turn it on.
- Never automated: guessing. A form that asks something you have never answered stops and asks you, rather than putting a made-up answer under your name.
- The cost of the difference: about a minute per application instead of an hour.
How it works for software engineer applications
You give me your history once. Every posting after that is a rewrite of material that is already true, angled at what this specific employer asked for.
- Paste an old resume or a rough brain dump. I pull out the roles, dates, and achievements.
- Paste a stack of job links, or plain "Company - Role" lines. Board links from Greenhouse, Lever, Ashby, and Workable are parsed automatically.
- Each job gets its own resume, with the bullets reordered and the summary rewritten for it.
- Each job gets a fit score out of 100 plus a short note on the strongest overlap and the clearest gap.
- None of that costs anything. The only limit is on sending: 25 applications a week, free.
Why the fit score matters more than the volume
The point of scoring honestly is to stop you applying to things you will not get. A software engineer role that scores below 40 is usually a gap you cannot close in a cover letter, and the hour you would have spent on it is better spent on two roles that score 70.
- Above 70: apply, and lead with the overlap the notes name.
- 45 to 70: apply if you want it, and address the gap directly rather than hoping it goes unnoticed.
- Below 45: usually a pass. If you apply anyway, do it because you know something the posting does not say.
- The score reads your history, not your potential. It is a filter, not a verdict.
What it will not invent for a software engineer
Tailoring reorders and rephrases what is already true. It never adds experience. A posting asking for Python and a candidate who has never touched it produces a gap in the notes, not a new line on the resume.
- No invented employers, titles, dates, or numbers.
- No synonym laundering: TypeScript is not Go because a posting wants the second one.
- No inflated scores. An inflated score costs you a wasted application, which is the thing this is supposed to prevent.
Where the time actually goes
A software engineer search that produces offers is usually twenty to fifty applications. Done by hand at an hour each, that is a part-time job on top of your actual one, which is why almost nobody tailors past the fifth application.
- Setup, once: 10 to 20 minutes to paste your history and check what came out.
- Per application: under a minute of your attention.
- What you still own: which jobs, whether the draft is right, and whether it goes. None of those is a keystroke I can save you, and none of them should be.