Skip to content
Puneet Moger

About

I like the part where it has to actually work.

I am Puneet — a full-stack developer in Bengaluru with a backend lean. I care about the unglamorous half of software: the schema that has to survive real data, the auth check that cannot be skipped, and the empty state nobody designs until a user finds it.

Based
Bengaluru, India
Education
MCA, 2026 — CGPA 8.9
Focus
Full-stack, backend lean
Status
Open to full-stack and backend roles

01 — The short version

I started with a BCA in Bhatkal, moved to Bengaluru for an MCA at Cambridge Institute of Technology, and finished in 2026 with a CGPA of 8.6. Along the way I discovered that I prefer the systems side of the work — the API, the data model, the reason a page is slow — more than the part where you move a button four pixels to the left.

My internship at Sozoq put me inside a real product and a real team for three months. I built and integrated REST APIs with Node.js and TypeScript, translated Figma designs into responsive interfaces, and cut average page load time by 40% using lazy loading and route-level code splitting. More useful than any of those line items: I learned how much of engineering is reading, asking, and matching the codebase you have rather than the one you would have written.

Outside of work I contribute to open-source projects I actually use — ToolJet, LibreDB, Data Peek — and build side projects to test ideas I do not yet have a good intuition for: real-time messaging, background video analysis, LLM-backed journaling, alerting pipelines. The pattern in all of them is the same. I want to understand the whole slice, not one comfortable layer of it.

I am now looking for a full-stack or backend role where the work is real, the code gets reviewed, and there is something hard to pick up.

02 — How I work

Three habits.

The things I find myself repeating when I review code, mine or anyone else’s.

01

Ship the whole slice

I prefer owning a feature from schema to screen — data model, endpoint, state, and the empty states nobody remembers until they break.

02

Make it readable

Code gets read far more than it gets written. Small modules, honest names, and comments that explain why rather than what.

03

Measure instead of guessing

Page load, query plans, bundle size. If I claim something got faster, I want a number and a before-and-after.

03 — Timeline

So far.

  1. Apr 2026 — Jun 2026

    Software Developer Intern

    Sozoq · Bengaluru

    Worked across the full SDLC on production web applications — building and integrating APIs, fixing frontend performance problems, and shipping reusable components.

  2. 2024 — 2026

    Master of Computer Applications (MCA)

    Cambridge Institute of Technology

    Bengaluru · CGPA 8.9 / 10

  3. 2021 — 2024

    Bachelor of Computer Applications (BCA)

    Shree Guru Sudhindra Degree College

    Bhatkal, Karnataka · CGPA 8.3 / 10

04 — Toolkit

The stack.

Languages

  • TypeScript
  • JavaScript
  • Python
  • Java
  • SQL
  • HTML5
  • CSS3

Frontend

  • React.js
  • Next.js
  • Tailwind CSS
  • Responsive design
  • Figma → code

Backend

  • Node.js
  • Express.js
  • Django
  • Django REST Framework
  • FastAPI
  • REST APIs
  • JWT auth

Data

  • PostgreSQL
  • MySQL
  • MongoDB
  • Prisma
  • SQLAlchemy
  • Redis

Tooling

  • Git
  • GitHub
  • Postman
  • VS Code
  • Linux / shell
  • Vitest
  • Playwright

Practices

  • OOP
  • Data structures
  • SDLC
  • Agile
  • Debugging
  • Code review
  • API design

05 — Open source

In other codebases.

  • 2026

    2nd place — Project Showcase

    Placed second among 50+ participants at BMS College of Engineering.

  • 2025

    Git & GitHub workshop

    Ran a hands-on workshop for 25 junior BCA students, recognised by the Head of Department.

  • 2025

    Full Stack Web Development

    Completed the 100xDevs full-stack web development certification.

Next

Hiring for something with a hard part? Good.

Send me the problem, not just the job title. I will tell you honestly whether I can help.