← All case studies

Case study

What I shipped at QubicGen

Projects, collaboration, and pace in a small team.

Manoj Sravan · 6 min read · Mar 21, 2026

  • Full product delivery
  • Team mentorship
  • Institutional SaaS
  • Embedded consulting
  • Scalable architecture
What I shipped at QubicGen

When I joined QubicGen Software Solutions as a Junior Software Engineer, there was no playbook, no codebase to lean on, no senior on every decision. Just a small early team and problems worth solving. This is an honest walkthrough of what I built there, in STAR form: situation, task, action, result.


QubicGen

QubicGen builds SaaS for institutions and enterprises. As an early member I wasn’t siloed: internal tools, client products, and time embedded with an external partner. You grow fast or fall behind; I chose to grow.


HR & attendance

Situation

No people-ops tooling: attendance on spreadsheets, employee data scattered. As the team grew, it was breaking.

Task

Design and ship a full-stack internal app for attendance and employee management from scratch, with no prior codebase.

Action

PostgreSQL + Prisma for schema and queries; I introduced TypeScript where the org had been on plain JavaScript. Modelled employees, roles, attendance, leave types; REST APIs; HR UI for attendance, directory, and reports.

Result

Replaced manual processes. TypeScript stuck as the default for what followed; Prisma + Postgres became the house standard so future engineers onboarded into established patterns.


School management

Situation

EdTech opportunity: schools needed an all-in-one platform; incumbents too expensive or too generic. No existing product, only a mandate to solve it.

Task

Primary engineer: architecture, MVP, refinement cycles, and mentoring trainees as the team grew.

Action

Multi-tenant microservices: tenant isolation in Postgres via Prisma without per-client infrastructure. Three domains (Administration, Student Management, Teacher Management) with boundaries so services could ship independently. Post-MVP refinements from stakeholders; reviews and pairing with trainees on the why, not just the what.

Result

Shipped a working multi-tenant MVP that proved institutional SaaS credibility. Trainees shipped features independently within weeks. The structure kept the codebase maintainable.


Portfolio website

Situation

The public site didn’t reflect a growing product portfolio: weak first impression for B2B outreach.

Task

Lead a revamp: not only visuals, but how QubicGen presented itself online.

Action

Clarified message, audience, and desired feeling in 30 seconds, then rebuilt: structure, product showcase, performance, full mobile responsiveness.

Result

A credible presence that matched what the team built: supporting institutional outreach and the Melody Mocktail partnership that followed.


Melody Mocktail

Situation

QubicGen partnered with Melody Mocktail, an NRI community platform (rentals, travel companions, legal, insurance). I worked embedded in their team: officially QubicGen, functionally day-to-day with Melody.

Task

Two live products: Deals Mocktail (US deals aggregation) and the in-house housing app behind melodymocktail.com listings and seekers.

Action

Ramped on existing architecture and conventions before large changes. Deals Mocktail: discovery, tagging, trending, category filtering across major US retailers. Housing: listing and seeker flows for rooms, shared rooms, and full properties across cities.

Result

Shipped production features in an external team without a long ramp. Built range across e-commerce-style surfaces and housing marketplaces vs internal enterprise tools.


From QubicGen

I’ll let the company speak here rather than me:

Mr. Manoj Sravan Panchangam was employed with QubicGen Software Solutions Pvt Ltd as a Jr. Software Engineer from May 05, 2024 to January 23, 2025. During his tenure with us, he was an integral part of our team and contributed significantly to various projects. He has demonstrated excellent technical skills, problem-solving abilities, and professionalism. His work ethic, dedication, and ability to collaborate with teams were commendable.

What this adds up to

  • Shipped systems people relied on daily, not throwaway demos.
  • Introduced standards (TypeScript, Prisma, service boundaries) that shaped how the team worked after.
  • Context switching across internal tooling, B2B SaaS, and consumer NRI products: different users, scale, and trade-offs.
  • Mentoring on the school platform: good engineering is also raising the capability around you.

Interested in working together or going deeper on any of these projects, reach out.