FROMCLASSROOMSTO PRODUCTION.
Building enterprise ERP software — before graduating.
THECOMPANY.
Role
Software Development Intern
Development Team Lead (Module Owner)
Company
S.N. Polymers Pvt. Ltd.
An infrastructure and manufacturing company building an internal ERP platform to digitize engineering, project, and financial workflows across multiple departments.
The Mission
I joined the engineering team to help build the company's Integrated Digital Business Platform — replacing fragmented paper workflows with production-grade software. Approval workflows on paper. Budget estimates crossing desks. Material orders untracked. The goal: change all of that.
Duration
June 2026 — Present
Location
Kolkata, India
WHAT IBUILT.
Each module solved a real operational problem.
Authentication & Security
Problem: Sessions were stored client-side, exposing tokens to script attacks.
Solution: Rebuilt auth with HttpOnly cookies, JWT rotation, Telegram OTP, and rate-limited login routes.
Project Cost Estimates
Problem: Paper estimates moved across offices manually — no tracking, no accountability.
Solution: Engineered a Maker-Checker state machine: draft → submit → zonal review → HO approval, with row-level DB locks preventing race conditions.
Daily Progress Reports
Problem: Field engineers reported progress verbally — no visual evidence, no audit trail.
Solution: Built photo-upload APIs with Supabase Storage, validated quantities against approved estimate limits before accepting submissions.
Material Requisitions
Problem: Subcontractors ordered materials freely, leading to budget overruns.
Solution: Designed SQL constraint triggers that reject orders exceeding the cost estimate scope — enforced at the database level, not just the API.
"
Before this internship, I thought good software was about writing clean code. Afterwards, I understood it's about people, processes, and decisions that outlive you.
THESTACK.
Backend
Database
Frontend
Infrastructure
Security
THERESULT.
6+
ERP Modules
shipped to production
40+
REST APIs
designed & implemented
20+
DB Migrations
schema decisions
1
Production ERP
end to end delivered
WHATCHANGED.
Beyond the Code
Understanding the business problem is half the work. The best architecture decision I made wasn't a technical one — it was asking why a workflow existed before I tried to digitize it.
Scale from Day One
Enterprise systems can't be refactored easily. Every schema decision, every API contract, every index I designed had to account for growth I wouldn't personally see.
Real Ownership
Owning a module means caring about what happens after you ship. When your code runs in production, the user isn't a persona in a spec document anymore.
LET'SBUILD.
If you need an engineer who has shipped production software before their final year — let's talk.