Track Record & Engineering Journey

Places where I was allowed to touch production.

Real systems, real traffic, real edge cases, and real learnings. From scalable backend microservices and transactional APIs in Bangalore to content management systems and booking engines.

May 2023 — PresentEngineering Track Record

Continuous engineering across 4 organizations

4 OrganizationsShipped Real Products

Microservices, real-time booking, media CMS, & web apps

Full StackEnd-to-End Ownership

NestJS, Next.js, TypeScript, PostgreSQL, MongoDB

Work Experience & Track Record

May 2025 — PresentCurrent

Software Engineer

ITProfound Inc.• Bangalore, India

I worked across several products, switching between backend and frontend depending on what needed to be built.

I worked on a food marketplace, rider/fleet platform, OTA product, and HR management system, contributing to features from the UI all the way to the backend services behind them.

› What I worked on:

  • Built and improved features across both frontend and backend.
  • Worked on booking, ordering, user, payment and operational workflows.
  • Learned how real software gets planned and tracked using Jira, epics, stories, tasks and tickets.
  • Worked with deployments and learned what happens after code leaves your laptop and reaches actual users.
  • Fixed production issues and worked on features that had to behave correctly with real users and real data.
  • Worked with different products and learned that every product has its own set of weird problems.
Startup Agile & Extreme Ownership

This was where I first got introduced to ticket-based Agile development. Because it was a fast-paced startup, we didn't follow textbook ceremonies strictly — we just adapted the parts that kept us moving fast.

True End-to-End Ownership:Features were often just described in a few words during a discussion. From there, I had to figure out the technical requirements, design the schema, build the UI and backend, and ship it to production all by myself.
Big “Firsts” for Me Here
  • •First time breaking things in production: Terrifying in the moment, but the best lesson in building resilient, defensive software.
  • •Multi-project parallel delivery: First time actively context-switching and delivering on multiple critical production projects simultaneously.
  • •Zero to Production: Successfully built and shipped 3 enterprise-grade products from absolute scratch all the way to real users.
Oct 2024 — Dec 2024Internship

Frontend Engineering Intern

Nirman Tech Solutions• Remote

One of my first experiences working on a real product team. I mainly worked on turning designs into working interfaces, improving existing UI, fixing frontend issues, and learning how a real application fits together.

I worked primarily with React and TypeScript, with some API integration and application state management using Redux.

› What I learned:

  • How to work inside an existing, living codebase.
  • How designs become reusable UI components rather than one-off pages.
  • How application state is managed cleanly with Redux across workflows.
  • How frontend and backend actually communicate and negotiate contracts.
  • How to debug issues beyond what is immediately visible in the DOM.
  • How product work gets broken down into actual, scoped developer tasks.
Existing Codebases & System Thinking

Coming from college projects where you start with a blank screen, this was my first real lesson in working inside an existing production system. I quickly realized software engineering is 70% reading and understanding existing patterns, and 30% writing new code.

Respecting Existing Conventions:Before changing any component, I had to trace how data flowed from Redux to child components and backend APIs. You learn how not to break things that other developers built before you.
Big “Firsts” for Me Here
  • •First team outside college: First time working alongside a wonderful, experienced professional engineering team.
  • •Real active users: First time shipping code to a project that real people were actively using on a daily basis.
  • •Large codebase navigation: First time learning how to read and respect conventions in a large codebase before editing it.
Jul 2024 — Aug 2024Freelance → Internship

Full Stack Engineer

Malayala Manorama• Kottayam, Kerala

This started as freelance work and was later converted into an internship so it could count toward my college requirements.

I worked as part of a 5-person team building a CMS for a kids-focused organization. This was my first real experience working on the backend, and I ended up contributing to three connected applications:

Guest website • Admin panel • Backend

› What I worked on:

  • Built features across the guest website, admin panel and backend.
  • Worked mainly with Next.js, React and JavaScript.
  • Built content-management features, a video vault and event calendar.
  • Worked on responsive UI and frontend performance.
  • Got my first practical exposure to backend development and API-driven applications.
  • Started thinking about security, authentication and protecting application data in a professional development environment.
  • Worked directly with a team of developers and experienced what it was like to build software for an actual client.
Beyond Localhost & Client Stakes

This was my first time experiencing development outside the comfortable little world of localhost → localhost → localhost. I worked on-site from the client's office, pulled overnight sessions when needed to get things finished, and saw how a team actually transforms an idea into software an actual client can use.

Responsibility Beyond College Projects:This was where I stopped thinking of myself as only a frontend developer. Building software for a real client comes with a completely different level of responsibility:
Frontend → Backend → API → Database → Security → Production
Big “Firsts” for Me Here
  • •First time outside localhost: Stepped into real client-facing delivery, working on-site from the client's office and pulling overnight development sessions.
  • •First backend & full-stack product: Stopped being “frontend-only” and built across the entire pipeline from UI to backend services, APIs, and security.
  • •Real client accountability: Learned that shipping software for someone else requires a completely different standard of data protection and reliability than college projects.
May 2023 — Jul 2023First Internship

Web Developer Intern

Spearmint• Remote

This was my first time building actual projects under the guidance of a mentor.

I was introduced to JavaScript here and built my first projects using just HTML, CSS and JavaScript.

› What I built:

VoiceByte

A small English-speaking practice app where users could practice saying words, record themselves, and receive a score.

NothingButCompress

A simple web tool for compressing files and images directly through client-side browser capabilities.

› What I learned:

  • My first practical experience with JavaScript.
  • How to turn an idea into an actual working web application.
  • How to structure a project beyond individual HTML pages.
  • How to debug code when I was still figuring out what the code was doing.
  • How to receive feedback and improve my implementation through mentorship.
  • Most importantly, how to build something from scratch and actually finish it.
The First Real Step

Before this, I was learning how web development worked in theory. Here, I started actually building things with my own hands.

From Tutorials to Shipping:The biggest milestone wasn't memorizing syntax — it was taking an empty text file, writing JavaScript from scratch, and finishing a working application.
Big “Firsts” for Me Here
  • •First JavaScript projects: Wrote my first real lines of functional JavaScript and browser logic.
  • •Built from absolute scratch: Created VoiceByte and NothingButCompress from 0 to done without templates.
  • •First technical mentorship: Learned how to receive code feedback, iterate, and structure code properly.