Hello fellow developers,
First off, I want to say a big thank you from the bottom of my heart to everyone who has written to me, donated, raised bug reports or issues, contributed translations, or even just used Reactive Resume over the last three years in all its variety of versions and makeovers.
As of today, Reactive Resume has about 970,000+ users and over 1.3 million resumes. Never in my dreams would I have expected this little side project of mine to reach such great heights, and it gives me all the joy in the world to help bring you a new version, one that I'm pretty proud of, but also one that I hope will bring you a lot of luck and success in your job search.
It's a difficult time for everyone, with the job market being what it is. Resumes have become more important than ever in getting your foot in the door. And yes, while it's always nice to create a resume bespoke to who you are, these days it's more important to be working on your skills and adding things to your resume than to be worrying about actually building it. That's why I feel Reactive Resume has a place in the current world, and I hope it continues to help many more people for years to come.
The New Chapter
I've been hard at work on a new version of Reactive Resume that I hope will excite and please everyone. It comes with a lot of much-needed bug fixes, feature requests, and safety guardrails to prevent things from breaking in production.
I've been monitoring the GitHub Issues board since the beginning of the project, and some major issues have always kept resurfacing:
- Difficulty in self-hosting
- Lack of good documentation
- Issues with the printer service
- OIDC/OAuth2 integration
- And most importantly, multi-page resumes
While I'm not the smartest developer out there, I do want to give it my best. This version tries to fix all of the above and more, while bringing in a fresh coat of paint to change with the times.
A Note on GitHub Issues
I'll be closing all open issues for now, just so it's easier for me to manage any new issues that come along and triage them correctly. I apologize to anyone who has to re-submit their issue because the bug or feature request they reported still exists in the new version, but I'll make sure to do whatever I can to fix it the right way this time.
Migration & Backwards Compatibility
All users and resumes will be migrated to the new version, without any hindrance to you. Your resumes will stay the same, your passwords and login methods will stay the same.
But for those who do face issues on the new version when it comes out, or if you feel your work on the current version (v4) isn't done yet, the current version of Reactive Resume will still be accessible at v4.rxresu.me for as long as I can keep paying for the servers.
Looking for a Community Manager
I'm not the greatest at community management or keeping the Reactive Resume sub-reddit and Discord server active, so I'm exploring the opportunity of hiring a Part-Time Community Manager (or maybe even more than one) to help with reaching out to the community, consolidating bug reports and feature requests, and ensuring there's a friendly face around to help whenever anyone needs assistance with Reactive Resume.
This will be a paid position. I don't expect anyone to work for free (well, except me).
If you're interested in the role and have some experience with social media or community management, please reach out to me at hello@amruthpillai.com. I really need all the help I can get.
Support Reactive Resume
If you've found yourself using Reactive Resume for some time and find value in it, please consider donating. This will help with hiring community managers, paying for beefier servers so the service doesn't go down during bursts of traffic, and keeping me motivated to continue building this little project of mine.
Migration Timeline
I plan on moving all users and resumes to the new database by the end of the month of January 2026. You can expect a small downtime of the website during that time, but once it's back, it will be better than ever. I assure you of that.
I'm super excited to show you what's in store. I hope you are too!
Hello fellow developers,
First off, I want to say a big thank you from the bottom of my heart to everyone who has written to me, donated, raised bug reports or issues, contributed translations, or even just used Reactive Resume over the last three years in all its variety of versions and makeovers.
As of today, Reactive Resume has about 970,000+ users and over 1.3 million resumes. Never in my dreams would I have expected this little side project of mine to reach such great heights, and it gives me all the joy in the world to help bring you a new version, one that I'm pretty proud of, but also one that I hope will bring you a lot of luck and success in your job search.
It's a difficult time for everyone, with the job market being what it is. Resumes have become more important than ever in getting your foot in the door. And yes, while it's always nice to create a resume bespoke to who you are, these days it's more important to be working on your skills and adding things to your resume than to be worrying about actually building it. That's why I feel Reactive Resume has a place in the current world, and I hope it continues to help many more people for years to come.
The New Chapter
I've been hard at work on a new version of Reactive Resume that I hope will excite and please everyone. It comes with a lot of much-needed bug fixes, feature requests, and safety guardrails to prevent things from breaking in production.
I've been monitoring the GitHub Issues board since the beginning of the project, and some major issues have always kept resurfacing:
While I'm not the smartest developer out there, I do want to give it my best. This version tries to fix all of the above and more, while bringing in a fresh coat of paint to change with the times.
A Note on GitHub Issues
I'll be closing all open issues for now, just so it's easier for me to manage any new issues that come along and triage them correctly. I apologize to anyone who has to re-submit their issue because the bug or feature request they reported still exists in the new version, but I'll make sure to do whatever I can to fix it the right way this time.
Migration & Backwards Compatibility
All users and resumes will be migrated to the new version, without any hindrance to you. Your resumes will stay the same, your passwords and login methods will stay the same.
But for those who do face issues on the new version when it comes out, or if you feel your work on the current version (v4) isn't done yet, the current version of Reactive Resume will still be accessible at v4.rxresu.me for as long as I can keep paying for the servers.
Looking for a Community Manager
I'm not the greatest at community management or keeping the Reactive Resume sub-reddit and Discord server active, so I'm exploring the opportunity of hiring a Part-Time Community Manager (or maybe even more than one) to help with reaching out to the community, consolidating bug reports and feature requests, and ensuring there's a friendly face around to help whenever anyone needs assistance with Reactive Resume.
This will be a paid position. I don't expect anyone to work for free (well, except me).
If you're interested in the role and have some experience with social media or community management, please reach out to me at hello@amruthpillai.com. I really need all the help I can get.
Support Reactive Resume
If you've found yourself using Reactive Resume for some time and find value in it, please consider donating. This will help with hiring community managers, paying for beefier servers so the service doesn't go down during bursts of traffic, and keeping me motivated to continue building this little project of mine.
Migration Timeline
I plan on moving all users and resumes to the new database by the end of the month of January 2026. You can expect a small downtime of the website during that time, but once it's back, it will be better than ever. I assure you of that.
I'm super excited to show you what's in store. I hope you are too!