A while back I built an LLM prompt for generating résumés and it worked really well! It could generate a very respectable technical résumé completely bespoke for an individual job posting. But it relied on a massive career history database that had to be constructed manually, and that could take literally days of manual writing, depending on how long your career history was. So pretty quickly I started working on automating that component as well with a story generating prompt. And eventually I reorganized everything from a single prompt to a collection of prompts and references that combine together form a whole LLM tool. Which I've now posted to github.
https://github.com/TravisLlado/resume-generator
This is designed to be used by anyone, but especially engineers. And I will warn you, it produces really good results after it's fully initialized, but that initialization process can take a while. Like between hours and days. Here's how it works:
My key insight last time was that creating a bespoke résumé from a deep, detailed career history database produced tremendously better results than simply modifying an existing résumé. And that means each user needs to create their own unique deep, detailed career history database. So I created a prompt to do exactly that. Download the tool, have an LLM read and run the initialization prompt, and grab a drink and sit down and tell all of your stories. The more depth and detail the better. The story generator prompt acts like an interviewer, quizzing you to fill in any gaps and details that might be relevant to a future résumé. When you feel like you've given enough history, then you switch to the résumé generator prompt and give it a job posting and a few minutes later it spits out a PDF demonstrating how you're the perfect person for that role. Of course this process collects a lot of personal career information, but that information is saved to your local hard drive, or whatever repo you push it to. (The tool is prompted to strongly suggest that you not push your private info to public repos.)
Here's an example. This job posting
combined with my career history produced this résumé
Is it perfect? No. Could I have done a better job myself? Yes. There are some phrases that don't really make sense. like one that says a dev tool I created was "adopted fleet-wide". Dev tools are used by devs, not cars, so "department-wide" would make sense, not "fleet-wide". There are few imperfections like that. But it's pretty good! And a résumé is just an introductory attention getter. But it's always a good idea to proof-read before submitting.
I hope this be will as useful for other people as it has been for me! It's an enormous time saver, after the initial ingest. But of course, after you write out your entire history, you have it saved and you can use it again for any future résumés. All I have to do from now on is add and update my most recent stories.