Howdy!
v0.5.2 is here, the main focus for this update: resumes built to get past the first filter. Here's the tea:

• A resume layout that parses cleanly
  Tailored resumes and resumes built with the wizard now follow one predictable layout: Your name first, then one plain-text line with your contact details. Links are written out as plain text, not hidden behind clickable words. Standard section names like Summary, Experience, Education, and Skills. Creative headings like "My Toolkit" confuse parsers.
• The match check now warns about knockout questions
  Many application forms ask automatic yes/no questions before anyone sees your resume. They cover things like a required degree, a license, minimum years of experience, location, work authorization, or security clearance. The wrong answer ends the application automatically. resumeBuddy's match check now calls these out.
• Honest job titles and years of experience
  Some systems give a lot of weight to how closely your job title matches the one in the posting. resumeBuddy uses the posting's title in your summary only when your actual titles and scope match it. Otherwise it uses your own.
• The posting's exact words, when they're true for you
  Recruiters filter on exact terms, and most systems don't treat synonyms as a match. resumeBuddy now: Uses the posting's spelling, Shows skills in use, Spells out acronyms once, Puts your strongest matches first. It also refuses to game the filter.
• Cover letters use the posting's words too
  Some applicant tracking systems scan cover letters as well. Cover letters now mention the posting's two or three most important requirements in its exact wording, when you meet them.

• How Workday ATS works: how it parses, scores and ranks your resume (StylingCV)
• How Workday, Greenhouse and Taleo read your resume (ShashiWorks)
• Greenhouse ATS resume format: parser-safe rules (ApplyArc)
• ATS resume optimization: the 2026 guide (The Interview Guys)

v0.5.0 is out.
New feature: Track application.

I could've built a "smart" duplicate-detection feature for the new Application Tracker in resumeBuddy. I didn't — because it would've had to lie to you. Most job boards don't expose a stable ID for a posting. Any "auto-dedupe" feature pretending otherwise is really just guessing, and shipping a guess dressed up as intelligence isn't something I wanted attached to a tool people are using to manage their job search.

So instead: tracking is manual, on purpose. One click after generating tailored materials — "Track this application" — snapshots the job description, the match-confidence verdict, which resume/cover-letter version you used, and the role. From there it's a simple funnel (Applied → Response → Interview → Offer/Rejected), your own notes, and a dedicated view of everything you're tracking.

Same architecture as always: no account, no backend, nothing synced anywhere. It lives in your browser's local storage — extension or PWA, same codebase, same rules. And if you ever want out, there's a real export button. Plain JSON, everything, no waiting on a data request form. "Your data is yours" is easy to put in a privacy notice. An export button that actually works is the only version of that claim I trust from anyone else, so it's the only version I'm willing to ship myself.

I hope you will like it, see you around.

v0.4.2 is here to address an issue where the context will be lost if the sidebar gets closed.
I apologize for this bug, so I will add more testing before releasing future versions.

Thanks for using my extension.

v0.4.0 is out!

Added Ollama as an AI provider: run a model fully locally, no API key needed.
Added a Resume Wizard: a guided six-step alternative to paste/upload for building your master resume.

No new permissions — it's your browser, and I respect that.
More local than ever, thanks to Ollama — because it's your data.

v0.3.0 is out:

I added a "Match confidence" fit-assessment feature, two new document types (elevator pitch, executive bio), a collapsible "More formats" section, and a light/dark theme toggle. Fixed a PDF export bug (tables/dividers rendering as raw text). No new permissions or data collection — still just storage, activeTab, and contextMenus, with no backend and nothing sent to the developer.