Jeevan Gupta

Most engineers pick a lane — backend, data, or the features that connect them. I own the full slice, end to end, and I like being close enough to product decisions that my work actually moves the business.

7 years in, I've taken a SaaS product from 0→1 (Amplytics — architected the OAuth integrations and ETL pipelines behind it, shipped the UI on top with no handoffs), built and led a 3-engineer team, and partnered directly with the CEO on product direction and roadmap priorities. At enterprise scale, I've since run cloud-native data infrastructure (AWS Glue/Lambda/Terraform) for SessionM via 3Pillar.

What I've actually shipped:
✔ Built Amplytics, a B2B marketing analytics SaaS, from 0→1 — architected 9+ OAuth integrations (Google Ads, LinkedIn, Meta, HubSpot), 9+ ETL pipelines, full-stack features in Django + JS/jQuery
✔ Built and led a 3-engineer team — sprint planning, code review, technical direction — while partnering with the CEO on product priorities
✔ Built a 3-part marketing audit tool (Python, Puppeteer, Cheerio, Postgres) — tracks trend shifts, campaign/ad changes, and landing page content changes at 95% accuracy, correlating all three to surface the root cause behind conversion drops
✔ Delivered a conversational analytics chatbot (Azure Bot Service + LUIS), later upgraded with OpenAI API + RAG for faster, more accurate insights retrieval
✔ Migrated ad-hoc data flows to Terraform-managed IaC across multi-region enterprise clients
✔ Use Claude Code, Cursor, and GitHub Copilot daily — not as a novelty, but as a way to move faster across the whole stack

Tools: Python · Django/DRF · FastAPI · JavaScript/jQuery · HTML/CSS · AWS (Lambda, Glue, S3, SNS, SQS, Secrets Manager, Redshift, Athena) · Terraform · SQL · MongoDB · Docker/Kubernetes

Open to remote Lead/Senior Backend Engineer / Data Engineer roles — building something that needs someone who can own a feature end-to-end, from database to browser, not just a ticket. Let's talk.