

Reactive Resume
Reactive Resume is a minimalistic and straightforward resume builder that focuses on clean design, user data privacy, quick ease of use, and easy resume updates.
Cost / License
- Free
- Open Source
Platforms
- Online
- Self-Hosted
Features
- Export to PDF
- Resume Builder
- Font selection
- Custom templates
Tags
- resume-writer
- cv-maker
- resumes
- resume-template
Reactive Resume News & Activities
Recent activities
gregtannenbaum added Reactive Resume as alternative to SWEResume
ajbelkadi added Reactive Resume as alternative to ResumeCV
Luffy667 added Reactive Resume as alternative to JobWizard
RaghavChamadiya added Reactive Resume as alternative to Thita- ScoutApply added Reactive Resume as alternative to ScoutApply
- corey-Robinson1337 added Reactive Resume as alternative to ProRes
risekraft added Reactive Resume as alternative to RiseKraft
RaymondSWE added Reactive Resume as alternative to Woberry
matcha123 added Reactive Resume as alternative to Matcha Resume
MikeCoreCV added Reactive Resume as alternative to CoreCV.ai
Reactive Resume information
What is Reactive Resume?
A one-of-a-kind resume builder that's not out to get your data. Completely secure, customizable, portable, open-source and free forever. Try it out today!
Reactive Resume is a minimalistic and straightforward resume builder that focuses on clean design, user data privacy, quick ease of use, and easy resume updates. If you are someone who cares about any of these issues, this is for you!
It has a bunch of features such as customizable sections, multiple layouts, unlimited colors, custom fonts, import/export as JSON, and so much more. All focused on one thing, to help you create a better resume. The app works entirely offline, no login necessary, no saving your data to the cloud, air-gapped for your security.








Comments and Reviews
I think it's the best open source resume builder with a lot of functionnalities.
Personally, as a person with no coding experience, getting it set up was rough with the provided documentation, especially given that the NodeJS and Yarn versions used were older - this wasn't mentioned in the documentation. Further, it is unclear how best to deploy the application