Cabin4 Professionals: Where It All Started

I joined Cabin4 Professionals in Calicut while I was still finishing my CS degree. This wasn't an internship that turned into a job. It was a job from day one. The team was small, the clients were real, and I was writing code that went into production within my first few weeks. Everything I know about building interfaces started here.

The biggest project during my time at Cabin4 was the website for MES College of Engineering, Kuttippuram. A full institutional website with around 20+ routes covering departments, placements, faculty, governance, hostel info, exam cell, research, library, campus facilities, and more. I built the entire frontend.

• 12 department pages, each with program details, seat counts, HOD info, and NBA accreditation status
• Training & Placement section with recruiter profiles, placement statistics, staff and student coordinator directories
• Governance, statutory cells, affiliations, and NAAC/ISO accreditation showcases
• Student-facing sections: anti-ragging portal, grievance system, online payment integration, NSS, IEDC, alumni network
• Responsive across all pages for students browsing on phones between classes

MESCE was the flagship, but I worked on other projects at Cabin4 too. Each one taught me something different about building for real users.

• Tourecoz: A travel/tourism platform. My first exposure to building product-style UIs with search, filtering, and booking flows. Learned that travel sites live and die by load speed and mobile UX
• Sportzy: A sports-related web app. Got me comfortable with dynamic data rendering, real-time-ish updates, and layouts that need to work across wildly different content shapes
• Several smaller client projects that sharpened the basics: responsive layouts, API integration, cross-browser debugging, and working with designers who hand you a Figma and expect pixel-perfect output

Cabin4 was where I figured out that frontend development isn't about knowing a framework. It's about understanding what the user needs to do and getting out of their way.

• React and GSAP became second nature here. Not from tutorials, but from building things that needed to ship on a deadline with real stakeholders reviewing them
• Working in a small team means you don't get to say "that's not my job." I touched everything from API integration to deployment to client calls. It was messy and it was the best education I could have gotten
• The MESCE site taught me what "scale" means even for a frontend. 20+ pages with different data shapes, shared components, and an admin team that doesn't think in components. You learn to build systems, not just pages
• I transitioned from React to Next.js here because I saw the SEO problem firsthand. The college site was invisible on Google as an SPA. That practical pain made me understand SSR at a gut level, not just a theoretical one