When I started this project, I only wanted one thing.
A resume builder that didn't ask me to create an account or pay before exporting a PDF.
That was literally the whole idea.
After using it for a couple of weeks while applying for jobs, I noticed something.
I barely spent time editing my resume.
Most of my time went into everything around it.
Copying job descriptions into ChatGPT.
Tweaking my resume for each company.
Writing another slightly different cover letter.
Keeping a spreadsheet of where I'd applied.
Trying to remember which resume version I sent.
The resume itself wasn't the problem.
The workflow was.
So I stopped thinking of it as a resume builder.
Now every feature has to answer one question:
Does this remove one repetitive task from applying for jobs?
That's why it slowly became a collection of tools instead of a single one.
One thing I intentionally didn't add was authentication.
Maybe I'll regret that later, but asking someone who's already stressed about finding work to create another account felt unnecessary.
Most data stays in the browser. It makes syncing across devices harder, but it also means people can start using it immediately.
I'm still figuring out where the balance is between privacy and convenience.
Curious how other developers approach this.
If you were building something like this, would you choose local-first storage, or would you require accounts from day one?
If you're curious about the project, it's available here:
👉 https://jobresume.rndhri.com
It's still evolving, and I'm building it based on feedback from people who are actively job hunting. If you have ideas, criticisms, or think I'm solving the wrong problem, I'd genuinely like to hear them.
Top comments (0)