SHUBHAM KUMAR PAL

System Architecture

Backend Engineering

Business Solutions

Full Stack Development

Shubham Kumar Pal
PYTHON ✦ JAVASCRIPT ✦ ODOO ✦ FASTAPI ✦ FLASK ✦ NEXT.JS ✦ REACT ✦ HTML5 ✦ CSS3 ✦ TAILWIND CSS ✦ POSTGRESQL ✦ SUPABASE ✦ MONGODB ✦ SQLALCHEMY ✦ GIT ✦ FIGMA ✦ 

How I got here

The curiosity spark

Started tinkering with code not because someone told me to, but because I wanted to understand how things worked. Broke things. Fixed things. Broke more things. That was the whole curriculum.

Building with purpose

Realized that writing code isn't just about making things run — it's about making things matter. Every line is a decision. Every project, a small bet on what the world needs.

The Timeline

Jan 2025joined Odiware as an intern
+2 monthsalready shipping fixes solo
+4 monthshandling client work directly
Aug 2025converted to full-time
Sep 2025Completed end to end ERP build for an international HVAC/AC services client
sincescaled up to a government-integrated solar installation platform

Shipping is the habit

Odoo modules, solar portals, CRM systems, creative tools — I stopped waiting for permission and started shipping. Ugly v1s that turned into solid products used by real people, every day.

Endless Pages

"If I ever write a book on how I see building things, it will have infinite pages. And I'll still be figuring it out."

things I've built

auto-blogging-automation

Final year project · solo build

Problem: Consistent SEO content takes hours of manual research and writing per post — most people either skip it or outsource it.

What I built: An end-to-end pipeline that scrapes Reddit communities for real user pain points, researches SEO keywords, generates matching images via Gemini Flash, and writes SEO-formatted WordPress content in a custom voice via prompt engineering — then auto-injects images with alt tags using a keyword-based search-and-replace system.

Constraint/trade-off: Chose to publish as drafts by default rather than full auto-publish — kept a manual review step to protect quality and voice consistency over full automation.

Before/after: Before: hours of manual research and writing per post. After: a scheduled draft ready for a final read-through.

PythonReddit APIGemini APIWordPress API

odoo-api-debug-console

Odoo Apps · internal dev tool, solo build

Problem: Client APIs weren't IP-whitelisted for local testing — the alternative was hand-building 10-12 separate Postman-style forms, one per endpoint.

What I built: One reusable Odoo module: click a button, get the raw response — no per-API form-building.

Constraint/trade-off: Traded configurability (editable request bodies per API) for speed — a fixed function per endpoint was faster to ship and cover every API I actually needed than a fully flexible form builder would have been.

Before/after: Before: no way to test non-whitelisted APIs without a manual setup per endpoint. After: instant in-app response check, reused across every client project since.

OdooPythonXML

Odiware client work — 5 ERP builds

Full stack developer · production systems, team + solo work

Problem: Each client came with a different operational bottleneck — from long manual data migrations to fragmented sales/delivery workflows to compliance-heavy government processes.

My role: Built or co-built each of these as part of the Odiware team, with direct ownership of specific modules on each project.

Constraint: All five were live client systems with real deadlines, existing data to preserve, and (for the government-linked project) compliance and API constraints outside my control.

What I built, one line each:

  • Construction management module
  • Legacy Odoo 14 data migration
  • Teacher–student exam and notes-sharing platform
  • Apartment/HVAC service ERP (quotation → sales → delivery → commissions → invoicing)
  • Government-integrated solar installation platform for a utility client

the ones I'm proudest of

hereEZTRACKHypeCia

EZTRACK

Problem: Most small businesses nearby still track memberships and invoices on paper — no dashboard, no automated follow-up on dues, no visibility into stock.

My role: Solo — architecture, backend, frontend, and deployment all mine. Used AI for audit and iteration only after the core flow, logic, and UI were built.

What I built: A role-based (owner/staff) SaaS for gyms — member and supplement sales, dashboards, analytics, due-date alerts, low-stock alerts.

Constraint/trade-off: Needed to keep hosting costs near zero for a small-business customer, so I run it on Cloudflare Pages + Render's free tier with a Google Apps Script cron job keeping the backend warm — a deliberate trade of a slightly hacky keep-alive workaround for near-zero running cost. Mid-build, I migrated the stack from Flask/React/SQLAlchemy to FastAPI + Next.js (for SEO) + Supabase — more rework, but the right call for where the product needed to go.

Before/after: Before: paper registers and manual dues follow-up. After: a live dashboard with automated due and stock alerts.

Status: Live, first customer: Revolution Multi Gym.view live →

hypeciaconnect.com

Problem: Hypecia needed to pitch infrastructure and AI security services to tier-1 telecom operators, but their technical catalog spans everything from telecom networks to MEP engineering — scattered and hard to present credibly.

My role: Built the site end-to-end (landed the project through referral).

What I built: A corporate site that organizes the full service catalog clearly and leads with proof rather than feature lists — a flagship 157-site Airtel deployment plus partner testimonials — built specifically to drive consultation bookings, not just look credible.

Constraint/trade-off: Chose to foreground the Airtel case study and testimonials above the fold rather than a full service menu, betting that trust-first beats information-first for a B2B audience with limited attention.

EXPERIENCE

the journey so far

From building production Odoo ERP systems to shipping independent SaaS products — owning features from client requirement to live release.

Aug 2025 - Present

Full Stack Developer

Odiware

India
  • Design and build production Odoo ERP modules end to end using Python, XML, JavaScript, and PostgreSQL for enterprise and government-linked clients.
  • Completed end-to-end ERP build for an international HVAC/AC upgrade services client covering e-commerce, quotation, sales, project management, and PDF invoice generation.
  • Built a government API integrated solar installation platform for a utility sector client, handling the full project workflow from application to installation tracking.
Jan 2025 - Jul 2025

Full Stack Developer Intern

Odiware

India
  • Began contributing independent fixes within the first 2 months and took on direct client facing work by month 4, ahead of typical intern ramp-up.
  • Built ERP module development and automation across real client scenarios under senior guidance; converted to full time based on performance.

RECOMMENDATIONS

what people say about me

A few words from people I've designed with, shipped alongside, and problem-solved next to.

Manager

Amit Desai

Manager,
Odiware

"Shubham is an exceptional developer who truly understands business needs. His ability to own entire features from concept to production made him an invaluable asset to Odiware. His work on the HVAC ERP system alone saved our clients countless hours. He doesn't just write code; he builds solutions."

Tech Lead

Priya Singh

Tech Lead,
Odiware

"Working alongside Shubham has been fantastic. He quickly adapted to our tech stack and consistently delivered high-quality, maintainable code. Whether he was tackling complex integrations or optimizing the frontend, his problem-solving skills and structured approach always stood out."

Client

Michael Vance

Director,
HVAC Services

"Shubham built an end-to-end platform that completely transformed how we manage our sales and installations. The system he developed is fast, intuitive, and handles our complex commission structures flawlessly. He was responsive to our requirements and delivered beyond our expectations."

contactMe

Ready to make a move? Drop an email to
discuss collaborations, or just to say hi.

say hi before overthinking it

(OPENS YOUR MAIL APP — NO FORMS, NO FRICTION)