M S Praveen Kumar

Claims BPM (Business Process Monitoring) — Non-Payments

The platform provides real-time visibility into critical business workflows by capturing events from multiple upstream systems, correlating them into end-to-end process instances, and tracking them against defined SLAs/SLOs.

• Supported onboarding of new applications into an event-driven architecture, integrating Kafka-based event producers into a shared business-process-monitoring pipeline
• Built alerting and threshold-monitoring capabilities to flag SLA/SLO breaches in near real time
• Collaborated with business process owners, architects and delivery managers to define monitoring requirements and validate event correlation logic
• Used Datadog for operational monitoring and troubleshooting of event consumption and remediation flows
• Contributed to designing scalable, decoupled integration patterns so new applications plug into the monitoring platform with minimal custom work

RTB migration work

Led critical version migrations with real breaking-change risk: Spring Boot 3.1 → 3.5 → 4.1, and migrating Kafka Cloud Streams to Spring Kafka. Deployed to production with zero breaking incidents — an ongoing process of careful, disciplined engineering where every release is treated as high-stakes.

Working model

Collaborate directly with onshore clients in the US (Phoenix, Texas) and with peer vendor teams (HCL, TCS) in a distributed offshore/onshore delivery model. Extensive use of Copilot and MCP servers to accelerate day-to-day engineering work.

Module 1 — Automated Database Archiving System (live in production)

RD&D runs their entire business — global client data, engineering designs, drawings, employee details, timesheets — on one monolithic app and one production database. Years of historical data was overwhelming the database and slowing the live application. I built a standalone archiving system that runs annually on January 2nd at 10:00 AM with zero human intervention.

• Pre-flight checks — lists all tables configured for archiving, verifies connectivity and load stats for both the production and separate backup database (different servers)
• Dry run — projects how many records will migrate, how many batches, and estimated duration before anything is touched
• Live run — full snapshot of each table stored as secure .sql files, records older than 3 years copied into the backup database, counts verified between source and destination, and only then safely deleted from production
• Reporting — detailed dry-run and live-run reports generated and emailed to the admin after every run
• Result: 100% automated, zero manual intervention, two independent backup layers (snapshot + queryable backup DB)

Module 2 — Legacy CodeIgniter → Laravel full system migration (delivered 31 July 2026)

The core business system was a large monolithic CodeIgniter application handling attendance, timesheets, tonnage/billing, client data, operational reporting and third-party syncs — with no client-side resource available to explain the existing modules or codebase. Every workflow, role-based visibility rule, report and legacy quirk had to be reverse-engineered from the old code, with zero tolerance for silently breaking billing-critical logic.

• Owned backend architecture, DevOps and the MySQL data layer end-to-end
• Reverse-engineered and re-implemented dozens of modules (attendance, timesheets, tonnage approvals, CO registers, performance/productivity reports, dashboards) with no original documentation
• Designed secure backend authentication and authorization, including full RBAC across Project Manager, Team Leader, Detailer, Estimator, Checker, HR, IT and more — with module-level and row-level permission granularity
• Rebuilt on a modern Laravel + MySQL stack, split into a REST API backend and a server-rendered frontend communicating over OAuth2
• Supported two parallel production lines: Detailing (drawings/revisions in tonnage and hours, routed through team leaders and project managers for billing approval) and Estimation (estimator → checker → project manager QC chain)
• Delivered a fully functional, bug-fixed production system by 31 July 2026; partnered with a separate frontend developer for client-side implementation

Scope

Built and maintained backend systems and data workflows using PHP Laravel, MongoDB, MySQL and Bash shell scripting.