Software Developer

I’m the guy who turns "It’s not working" into "How did you even make it work?" … or it might just not working. You’re welcome!

I’m a backend guy who spends most of the time making things work (or breaking them first and then fixing them). I worked on an in-house payroll system to help things run smoother and reduce errors, using Java Spring Boot and a bit of JavaScript magic. Before that, I was a frontend dev, messing around with different frameworks to see what fits best for production.

Now, I’m all about backend stuff—building APIs, optimizing databases, and making sure things don’t crash (too often). I enjoy learning new things, whether it’s a new tech stack or just a better way to write cleaner code. Still figuring things out, but that’s part of the fun!I’m the guy who turns "It’s not working" into "How did you even make it work?" … or it might just not working. You’re welcome!

I’m a backend guy who spends most of the time making things work (or breaking them first and then fixing them). I worked on an in-house payroll system to help things run smoother and reduce errors, using Java Spring Boot and a bit of JavaScript magic. Before that, I was a frontend dev, messing around with different frameworks to see what fits best for production.

Now, I’m all about backend stuff—building APIs, optimizing databases, and making sure things don’t crash (too often). I enjoy learning new things, whether it’s a new tech stack or just a better way to write cleaner code. Still figuring things out, but that’s part of the fun!I’m the guy who turns "It’s not working" into "How did you even make it work?" … or it might just not working. You’re welcome!

I’m a backend guy who spends most of the time making things work (or breaking them first and then fixing them). I worked on an in-house payroll system to help things run smoother and reduce errors, using Java Spring Boot and a bit of JavaScript magic. Before that, I was a frontend dev, messing around with different frameworks to see what fits best for production.

Now, I’m all about backend stuff—building APIs, optimizing databases, and making sure things don’t crash (too often). I enjoy learning new things, whether it’s a new tech stack or just a better way to write cleaner code. Still figuring things out, but that’s part of the fun!

Work Terms

Hourly Rate:
- My hourly rate is $15/hour.
- Additional work or revisions beyond the agreed scope will be charged at this rate.

Deployment:
- I will assist with deploying the website to a live environment (e.g., hosting server).
- The client is responsible for providing:
1. Hosting account details (e.g., cPanel, FTP, or other access).
2. Domain name configuration (if applicable).
3. Deployment is considered complete once the website is live and accessible online.

Communication:
- All communication will be done via Guru.com messaging
- I will respond to messages within 24 hours on business days.

Ownership & Rights:
- Upon full payment, the client will own the final deliverables (e.g., website, code, design).
- I retain the right to display the work in my portfolio unless otherwise agreed.

Cancellation Policy:
- I reserve the right to cancel the project if the client fails to provide necessary materials or feedback within a reasonable time.

Confidentiality:
- All client information and project details will be kept confidential.
- I will not share or use sensitive data for any purpose other than the project.

Liability:
- I am not liable for any damages, losses, or delays caused by third-party services (e.g., hosting providers, plugins, etc.).
- The client is responsible for ensuring that their website complies with all legal requirements