Team Paradox —Contradiction,engineered.
PARA
DOX
We design and build thoughtful digital systems across product, web, mobile, AI and security. Five students, one quiet operating system.
We question the obvious.
Prototype the difficult.
Refine what deserves to last.
Six projects in flight. Each a real system with a real lead, a real stack and a real list of limitations.
A small ledger of what we actually do. Click one to filter the studio — no percentages, just the work it touches.
Five builders. Read their discipline, then read their work. What we don't publish is intentional.
- Anshika SinghProduct & Experience · Security ProductOwns product direction, interaction quality and the security surface. Leads Theft Alert and holds the bar for accessible, editorial interfaces.
- Aditya ChaudhariPlatform / Backend / MobileOwns EduPortal platform: roles, scheduling, real-time comms and companion mobile. Backend reliability and PWA/TWA packaging.
- Om Abhishek TripathiRetrieval · Embeddings · Applied AIOwns ARIA — ingestion (PDF/YouTube/GitHub), embeddings, Chroma retrieval, memory and Groq/LangChain orchestration. Labels AI honestly.
- Abhiuday Pratap SinghMotion · 3D UI · Frontend SystemsOwns Perkify interaction layer and motion systems — routes, JWT/auth, Prisma flows, plus FastAPI assistant. Carries the Framer/detail polish.
- Ananya SinghDiscovery · Document Systems · MarketplaceOwns Career Boost and The Local Way — document parsing, deterministic matching/roadmaps, and village discovery/marketplace flows. Spelled Ananya.
A five-step rhythm we return to whenever things get messy.
- Frame
Define the real problem and its non-goals.
- Prototype
Make the smallest thing that can fail usefully.
- Challenge
Break it, measure it, bring dissent.
- Refine
Edit until only the essential remains.
- Ship
Release, observe, own the consequences.
Commitments, not claims of perfection. We aim here. Sometimes we miss. We publish the misses too.
- Evidence over adjectivesWe show architecture, trade-offs and limitations. No invented metrics, testimonials or client logos. What you read is what we can point to.
- Accessible by defaultSemantic HTML, 44px targets, keyboard paths that work, focus that you can see. We test at 200% zoom, not just on our MacBooks.
- Secure boundariesData is partitioned by role, tokens stay short-lived, and we keep secrets out of the client. Security is a constraint, not a badge.
- Tests for critical pathsAuth, payments (when real), ingestion and scoring have tests. We don't chase coverage theatre; we protect the paths that hurt if broken.
- Honest AI labelsRules are called rules. RAG is RAG. We never label a heuristic a 'trained model' and we cite sources or say we couldn't find one.
- Clear ownershipEvery project has a named lead. Questions have somewhere to go, decisions have an owner, and blame has no home.