The advice 'apply to more jobs' is why most job searches feel awful. The advice that works is 'apply to fewer jobs better' — but that requires per-role research, tailored materials, and follow-through, which is exactly the workflow AI eats. This is the four-step recipe: research the company, tailor the cover letter, prep the interview, follow up. If you run it consistently on ten roles, your callback rate typically doubles versus a hundred templated blasts, and the writing gets better with practice rather than worse.
Research the company (5 min)
Goal: Learn one specific, non-obvious thing about the company you can cite naturally in the cover letter.
I'm applying to [Company] for a [Role] position. Search the web and tell me: (1) the last 2-3 public posts by their engineering / product / design leader depending on my role, (2) their most recent product release and what it suggests about their strategy, (3) one specific decision they made in the last 6 months that reveals what they care about. Not a summary of the company — the specific facts I can cite in a cover letter that shows I read them.
Draft the cover letter with the specific
Goal: A one-page letter that opens with the specific fact you learned and connects it to what you'd contribute.
Draft a cover letter for [Company] for the [Role] position. Use the research above. Open with the specific fact I found (not 'I'm excited about your mission'). Middle: one paragraph on the two things I've done that map to the role's specific requirements (I'll paste the JD). Close: propose one specific first-90-days contribution based on what I've read they're working on. No buzzwords ('passionate', 'excited', 'game-changing'). One page.
Interview prep (20 min)
Goal: Prepare specifically for this company's interview style based on what you can learn.
For [Company]'s interview process for a [Role] — based on any Glassdoor or interviewing.io data you can find, plus the company's engineering / product blog patterns — predict: (1) two questions likely to be asked in the first round, (2) the technical or scenario question they lean toward in the deeper round, (3) the two questions I should ask them that would show I understand their business.
Follow-up (5 min)
Goal: One well-timed follow-up per role that keeps you memorable without being annoying.
It's been [7 days] since I applied to [Company] and I haven't heard back. Draft a one-paragraph follow-up email that references something specific from my original application, adds one new specific piece of value (a link, a thought, a question), and does not pressure. Warm, brief, one CTA.
Handoff: One follow-up. If they don't reply to the follow-up, they're a no; move on cleanly and don't burn a reference by pestering.
Repeatability, not cleverness.
What lives where when the workflow finishes.
Each role's materials live in a LADLE Project named after the company. The research doc, the cover letter, the interview prep — all in one place, referenced quickly if they call. At the end of a search: keep the ones from companies that gave you real interviews as a reference library for next time; delete the others.
The same shape, different jobs.
- Career-change variation — Step 2's middle paragraph explicitly bridges the gap between prior domain and target domain.
- Executive search variation — Step 1 pulls board / investor context; Step 3 preps for panel format, not 1:1.
- Contract / freelance variation — replaces cover letter (Step 2) with a scoped proposal PDF including price.
- Recruiter-mediated variation — Step 4 splits: one follow-up to the recruiter (professional), one soft signal on LinkedIn to the hiring manager (memorable).
Try this workflow once. Then decide if it earns a recurring slot.
The value compounds after the third run, not the first.