Waste Management & Logistics
2026

Waste Management & Logistics Multi-Tenant SaaS Platform

Role

Backend Software Engineer

Client

Sprinting Software (Product Company)

Duration

10 months

Context & Goals

Enterprise backend platform for waste management operations, logistics scheduling, contract management, invoicing, and regulatory compliance across multiple tenants

Constraints & Challenges

Waste management companies relied on fragmented manual processes for shift scheduling, contract pricing, invoicing, and regulatory reporting. Shift planners spent hours manually creating schedules, pricing conflicts caused billing errors, and financial reports lacked accuracy for audit compliance — leading to revenue leakage and operational inefficiency.

Solution & Approach

Built a modular, multi-tenant backend with strict tenant isolation at database and API layers, event-driven async workflows using Laravel Redis queues (Jobs/Events) with idempotency safeguards and retry/backoff logic, and domain-driven service architecture. Implemented automated shift generation with conflict detection, price list overlapping protection, surcharge line item modeling, and financial reporting pipelines.

Delivered a scalable SaaS backend serving multiple waste management companies from a single codebase, featuring event-driven shift generation, real-time pricing validation, accurate invoice line reporting, document template generation, and integrations with third-party financial systems (Exact Online, AFAS, Multivers).

Technology Stack

Laravel
PHP
PostgreSQL
Redis
Swagger
Puppeteer
ElasticSearch
AWS S3
Docker
CI/CD

Results & Impact

Automated shift scheduling eliminated hours of daily manual planning across multiple locations

Price list overlapping protection prevented billing conflicts and revenue leakage

Fixed financial report query logic ensuring accurate debit/credit reconciliation for audits

Built surcharge line item data model from scratch enabling dynamic pricing capabilities

Contributed 172+ commits across 26+ feature tickets in 10 months

Event-driven async workflows with idempotency safeguards and retry/backoff ensuring reliable background processing

Interested in similar outcomes?