Browse categories
Explore
Fiverr Pro
English
$
USD
I will fix bugs and maintain your java spring boot backend
Gerardo Santana
About this gig
If your Java Spring Boot backend is throwing unexplainable stack traces, endpoints are returning 500 Internal Server Errors, or you simply need reliable code maintenance to keep your system running smoothly, I can help.
I specialize in Java backend development, and I prefer diving into the code, doing proper maintenance, and squashing bugs rather than just building things from scratch and walking away. I focus on finding the root cause of the issue and applying a clean, permanent fix.
What I can help you with:
- Deep Debugging: Tracking down elusive bugs (NullPointerExceptions, infinite loops, weird transaction rollbacks).
- API Fixes: Correcting broken REST endpoints, bad JSON mappings, or HTTP status issues.
- Code Maintenance: Refactoring messy, spaghetti classes into clean, readable, and well-structured code.
- Database & Logic Issues: Fixing JPA/Hibernate mapping errors or slow queries causing bottlenecks.
Crucial Step: Please, send me a direct message before placing an order. Bugs are unpredictable. I need you to explain the issue (and ideally show me the logs or the specific class) so I can tell you exactly which package covers the time needed to fix it. Let's get your backend stabl
Get to know Gerardo Santana
Gerardo Santana
Software Developer
- FromMexico
- Member sinceJul 2026
- Avg. response time1 hour
Languages
Spanish, English
I am a Software Developer with experience in creating REST APIs using Spring Boot and Django, low-code development with Mendix, and Machine Learning solutions using Python and PyTorch. I am passionate about solving complex problems and seek to apply my software engineering and project management skills in dynamic environments. Currently studying my 7th smester of Computer Engineering at UNAM.
FAQ
Do you need access to my entire server/database?
No. Usually, access to the specific source code repository (or just the affected classes) and the error logs/stack traces is enough for me to reproduce the bug locally and provide a fix.
What happens if the bug takes longer to fix than expected?
That's why I ask you to message me first. If we agree on a package and the bug turns out to be much deeper, I will communicate this transparently. You can then decide to use the "Additional hour of work" extra, or we can adjust the scope.
