Software Engineer focused on backend systems and database architecture
I'm a B.Tech Electronics & Communication Engineering student who builds backend systems the way I'd want to defend them in an interview: with the design written down before the code, and the security and correctness claims backed by tests rather than assumptions.
My work spans two directions that inform each other — a multi-tenant SaaS product where tenant isolation is enforced by the database itself, and a continuous, publicly-committed practice record in data structures and algorithms. I'd rather ship less and be able to explain every decision than ship more and hand-wave the parts I didn't think through.
- B.Tech Electronics & Communication Engineering, LNMIIT Jaipur
- Building a multi-tenant SaaS product with database-enforced tenant isolation
- 250+ solved DSA problems across two long-running practice repositories
- Primary interests: backend architecture, PostgreSQL, and system design
A multi-tenant SaaS platform where businesses train an AI support assistant on their own documentation and embed it on their site via a cross-origin widget, billed only for the questions it actually answers.
Private flagship project — architecture walkthrough available on request.
| Aspect | Detail |
|---|---|
| Architecture | Tenant isolation is enforced by PostgreSQL Row-Level Security — enabled and forced on all 14 tables — rather than by application-layer filtering. Background jobs are enqueued through pg-boss inside the same database transaction as the state change that triggers them, so a state change and its job either commit together or roll back together. |
| Database security | A four-actor access model (user, widget, worker, system) is checked inside the policies themselves, not just at the application boundary. Two tightly scoped SECURITY DEFINER functions handle the two cases where that boundary must be crossed; everywhere else, the absence of a policy is the enforcement. |
| Testing | The security-critical test suite runs as the actual least-privileged database role against a real PostgreSQL instance, not a mock. The repository has more test code than application code, and that suite has already caught and fixed two real policy gaps before they shipped. |
| Process | Built across eight milestones, each gated by a design document reviewed and approved before implementation starts. Thirty-one architecture decisions are recorded individually, each with the alternative that was rejected and why. |
| Stack | TypeScript, Next.js, PostgreSQL, Drizzle ORM, pg-boss |
| Status | Tenancy and authentication shipped; asynchronous ingestion pipeline in progress; chat, embeddable widget, and billing are designed and scheduled |
The platform this profile links to is not a static page — it's a small full-stack product I built and maintain. Content is stored as schema-validated JSON and edited through a purpose-built admin panel; an AI assistant answers questions about my work by retrieving from that same content, with automatic fallback across providers if one is unavailable.
| Aspect | Detail |
|---|---|
| Backend | FastAPI with Pydantic-validated content models — the server will not boot on invalid data |
| Frontend | React, with route-level prerendering and a keyboard-driven interface |
| Notable engineering | A retrieval-grounded AI assistant with automatic multi-provider fallback; a production contact pipeline with rate limiting and a durable fallback path if email delivery fails |
| Stack | React, FastAPI, PostgreSQL/MongoDB, Tailwind CSS |
| Status | Deployed and live |
Four repositories, not maintained for a single showcase-worthy number but as a continuous record of practice. The value here is consistency over time, not any individual result.
| Repository | Focus | Verified scale |
|---|---|---|
| DSA-CPP | Daily C++ practice across arrays through graphs, with a dedicated dynamic-programming track | 300+ solutions, 90+ days |
| DSA-CPP-STRIVER | The Striver A2Z curriculum worked end to end | 250+ solutions, 60+ days |
| DSA-LC-Weekly | LeetCode Weekly Contest solutions | 5 consecutive contests |
| DSA-LC-BiWeekly | LeetCode Biweekly Contest solutions | 2 consecutive contests |
- Design precedes code. SupportPilot's eight milestones each start with a written design that is reviewed before any implementation begins — deviations discovered while building are surfaced, not silently patched in.
- Claims are backed by tests, not assumptions. Database security is verified by a test suite that runs against a real database as the real runtime role; nothing about tenant isolation is taken on faith.
- The naive solution is written down, not skipped. Across the DSA repositories, the brute-force approach is kept alongside the optimized one, because the optimization is only meaningful once the baseline is explicit.
- Decisions are recorded with their alternatives. A design choice without the rejected option next to it isn't a defensible decision — it's a guess that happened to work.
Languages
Backend
Frontend
Databases
Infrastructure
Tools
| kotaharshil2906@gmail.com | |
| linkedin.com/in/harshil-jain-543940317 | |
| Portfolio | harshiljain.online |
| GitHub | @harshiljain2911 |