paraskapoor.com

Founding Engineer · Production AI

Paras Kapoor — Founding Engineer · 0→1 Product Architect

I take products from zero to production.

Founding engineer on the official Atomic Habits app. Now I build autonomous AI agents and RAG systems that ship to real users — not demos.

currently — leading engineering at Spoon, an AI-native back office for restaurants
Atomic Habits app/Telkomsel Indonesia/Hay House/AWS Certified Solutions Architect/−80% latency/RAG · Agents · LLMs/0→1 founding engineer/Atomic Habits app/Telkomsel Indonesia/Hay House/AWS Certified Solutions Architect/−80% latency/RAG · Agents · LLMs/0→1 founding engineer/

01 — Selected Work

Things I took from idea to production.

02 — Philosophy

Production is the only truth.

01

Define what must never happen.

Before any code, I write down the invariants — the things that must always hold, no matter the load or the timing.

Proof · Mint Dentistry →A slot can't be booked twice became a reservation hold. Zero double-books.

02

Assume it runs twice.

Retries, queues, and webhooks all deliver more than once. Every handler should be safe to replay.

Proof · SwipeHealth →Every Stripe and RevenueCat webhook reconciles to one ledger, so a replay can't corrupt state.

03

Time is a correctness problem.

Timezones, retroactive edits, and schedule changes are where naive timestamps quietly break products.

Proof · Atoms →Device-local check-ins normalized to UTC, with retroactive check-ins and snoozes handled explicitly.

04

Fix the cause, not the symptom.

A restart clears memory. It doesn't explain why memory grew. I trace problems to the root before calling them fixed.

Proof · FiveForty →Traced container memory pressure to BullMQ jobs piling up after TTL cleanup failed.

05

Measure, then optimize.

Find the hot path first, then fix it with the right tool — not with a guess.

Proof · Hay House Audio →Redis caching and a dedicated search engine cut search time 85–90%.

06

Constraints choose the architecture.

Service and model availability, data residency, and the existing footprint shape the design as much as preference does.

Proof · FiveForty →Region chosen by where the required Foundry models and Azure Redis were available.

03 — About

I build products that survive production.

Software engineering isn't just writing code. It's making thousands of technical decisions that determine whether a product remains reliable, maintainable, and scalable long after it's shipped.

I enjoy working where engineering meets product — owning it end to end. From backend systems and cloud infrastructure to AI and the frontend people actually use, I help turn ideas into production software that solves real problems.

I believe technology should create business value, not unnecessary complexity. Every architectural decision is a trade-off between reliability, performance, cost, and developer experience.

9+ years in, my recent work focuses on backend platforms, cloud-native systems, AI applications, and building software that teams can confidently operate, evolve, and scale.

I also invest in the team around the code — interviewing for architect, DevOps, and AI roles, building onboarding roadmaps for new engineers, and setting up release governance so shipping stays boring.

  • AWS Certified Solutions Architect – Associate

    Amazon Web Services

  • MCA · Gold Medalist

    Panjab University, Chandigarh · 2017

Explore how I think→

04 — How I work

From a blank page to a system that runs without me.

  1. 01

    Frame it.

    Problem, constraints, invariants, and failure modes — written down before any code.

  2. 02

    Decide in writing.

    Compare two or three designs. Make reversible calls fast, irreversible ones carefully, and record why.

  3. 03

    Ship the simplest v1.

    Observability, idempotency, and failure paths from the first commit — complexity only when a requirement proves it.

  4. 04

    Hand it over operable.

    Runbooks, dashboards, and alerts, so the system runs without me online.

05 — Contact

Building something that has to work?

I'm not job-hunting — but I'll always make time for a hard problem, an early-stage product, or a conversation worth having.

hello@paraskapoor.com↗