Experience Details
Full Stack Developer
SaleBee CRM
At SaleBee CRM, I worked across application development, database-heavy backend logic, deployment handling, and production support. The role pushed me beyond feature delivery and into the kind of engineering work that affects reliability, maintainability, and day-to-day operational confidence.
Overview
This full stack developer role covered a broader scope than a typical frontend position. I worked on the CRM product across UI changes, backend logic, SQL Server procedures, deployment workflows, and server-side operational tasks. A large part of the work involved understanding how production issues actually surfaced in a live business application and then solving them in a way that reduced repeated friction for both users and the team.
Responsibilities
- Developed and maintained features in an ASP.NET MVC based CRM, contributing across frontend behavior, backend logic, and SQL-backed workflows.
- Worked on data-heavy operations, stored procedures, and related backend behavior where correctness and performance directly affected business use cases.
- Handled deployment, backup, and environment management tasks as part of keeping the product stable in production.
Projects And Scope
- Implemented a smart cache-busting mechanism for static assets such as CSS and JavaScript so new deployments would not be blocked by stale browser caches.
- Built a Windows background service for scheduled notifications and bulk email dispatch, integrating RabbitMQ for queue management and FCM for push notifications using .NET Core 8.
Challenges
- Investigated deadlock issues in data-heavy operations and improved behavior by first introducing thread locking and later refining the approach with LazyCache integration.
- Worked within a production-sensitive environment where fixes needed to be practical, low-risk, and compatible with an existing codebase rather than relying on broad rewrites.
Outcomes
- Reduced deployment friction by solving a major browser caching issue that previously caused outdated static assets to remain active after releases.
- Improved operational reliability through deployment handling, backup routines, and PowerShell-based Windows Defender protection for brute-force attempts on RDP ports.
Collaboration
The role required close coordination between product needs and technical constraints. I often had to move between implementation, debugging, deployment, and support contexts, which made clear communication and responsible rollout decisions a necessary part of the job.
Reflection
This experience strengthened how I approach full-stack product work: not just building features, but understanding how systems behave under real usage, how releases fail, and how operational details shape product quality.