I will fix bugs in your node js nestjs or backend API


About this gig
Backend acting up? I'll find the root cause and fix it cleanly. I'm a software engineer with 5+ years in backend (Node.js, NestJS, Express, PostgreSQL). I don't just patch symptoms I diagnose the real cause, fix it properly, and tell you plainly what was wrong and why.
I can help with API errors and crashes, database & query bugs, async/race conditions, queue issues (BullMQ/Redis), auth & integration bugs, failing tests.
How I work: share the repo & a clear bug description, I reproduce it, fix it, and send it back with a short note on the cause. Fast turnaround, clear communication, no drama.
Not sure I can help? Message me first I'll tell you honestly before you order.
Get to know Omer Habib
Senior Software Engineer From 2020 till Present
- FromPakistan
- Member sinceAug 2019
- Avg. response time1 hour
- Last delivery4 years
Languages
Urdu, English
FAQ
I'm not sure how many bugs I have or which package to pick. What should I do?
Just message me first with a short description of the problem. I'll tell you honestly which package fits before you order — no guessing, no upselling.
What do you need from me to get started?
Access to the code (repo link or zip), a clear description of the bug (what you expect vs what actually happens), steps to reproduce it, and how to run it locally. The clearer the info, the faster the fix.
What if you can't fix the bug?
I'll always assess it upfront via message before you order, so this is rare. If I take it on and genuinely can't resolve it, I'll be honest with you quickly — I won't waste your time or money.
Which stacks and technologies do you work with?
Node.js, NestJS, Express, TypeScript, and databases like PostgreSQL, MySQL and MongoDB. Also queues/async (BullMQ, Redis), auth, and third-party API integrations. Not listed? Message me and I'll confirm.
Is my code safe and confidential?
Absolutely. Your code stays private, is used only to diagnose and fix your issue, and is never shared or reused. Happy to work on a private repo or a branch you control.
How will we communicate, and will I get updates?
Through Fiverr messages. I keep communication clear and give you a plain update as I diagnose and fix — including a note on what actually caused the problem.
What happens if the same bug comes back?
On the Premium package I include an automated regression test specifically so it can't come back. On any package, if my fix didn't fully solve the reported issue, the revisions cover it.

