Java 8 production Bug Fixes
Budget: ₹400 – ₹750 INR
I maintain a production system built on Java 8 and my release calendar is getting tight. I’m looking for another seasoned Java 8 developer who can jump straight into the codebase and clear a queue of production bug fixes, with a strong focus on performance-related issues that are slowing critical paths in the application.
The role is entirely about real-world production cases: you’ll receive tickets that are already reproduced in staging, investigate root causes, implement the fix, and push a merge request that passes our automated tests and basic load-testing benchmarks. If you spot broader optimisation opportunities along the way, that insight is welcome, but the first priority is resolving the existing performance bugs so we don’t miss release deadlines.
You will be working in a standard Java 8 stack (Maven, Git, JUnit); familiarity with profiling tools such as VisualVM or YourKit will make your life easier, though you’re free to use whatever debugging setup you prefer as long as the fix is clean, well-documented, and regression-tested.
Deliverables
• Per-ticket pull requests with concise commit messages
• A short note describing the root cause and the fix for each ticket
• Proof that unit tests pass and that performance has improved or at least not regressed after the patch
If you thrive on squeezing extra efficiency out of Java 8 code and can turn around fixes quickly, let’s get started—I need to clear these tickets as soon as possible.
The role is entirely about real-world production cases: you’ll receive tickets that are already reproduced in staging, investigate root causes, implement the fix, and push a merge request that passes our automated tests and basic load-testing benchmarks. If you spot broader optimisation opportunities along the way, that insight is welcome, but the first priority is resolving the existing performance bugs so we don’t miss release deadlines.
You will be working in a standard Java 8 stack (Maven, Git, JUnit); familiarity with profiling tools such as VisualVM or YourKit will make your life easier, though you’re free to use whatever debugging setup you prefer as long as the fix is clean, well-documented, and regression-tested.
Deliverables
• Per-ticket pull requests with concise commit messages
• A short note describing the root cause and the fix for each ticket
• Proof that unit tests pass and that performance has improved or at least not regressed after the patch
If you thrive on squeezing extra efficiency out of Java 8 code and can turn around fixes quickly, let’s get started—I need to clear these tickets as soon as possible.