The architecture behind this portfolio — one shared WebGL canvas, MDX content validated at build time, and a deliberate rule that adding anything is one file.
- next.js
- architecture
- three.js
Backend & AI Engineer · Hyderabad, India
Founding engineer at Metry AI, where I own the backend architecture and REST APIs behind SOJO — a client-management platform for beauty and wellness businesses across Asia. Outside work I build agent systems and the evaluation harnesses that tell me whether they actually work.
Resolved 2 of 4 multi-turn cases faster than GPT-4o (n=4) — and an eval that's just as honest about where it loses.
Solo — design, build, deploy, evaluate · Python · LangGraph · FastAPI · Qdrant
38 of 50 resolved on the clean run — and 14 of the first pass's 24 failures turned out to be the grader, not the agent.
Solo — design, build, benchmark · Python · LangGraph · Docker · Modal
The cleanest Java in the portfolio — a real security layer, split DTOs, and integration tests, not just a CRUD demo.
Solo · Java · Spring Boot · Spring Security · Spring Data JPA
Four services, two consumer groups, and honest gaps named up front — no idempotency, no DLQ, not yet a production system.
Course project — solo · Java · Spring Boot · Apache Kafka · Spring Data JPA
416 lines below the framework layer — the only project in the portfolio that isn't built on someone else's abstraction.
Solo · C · POSIX sockets · pthreads
Adding a project is one MDX file. The 3D layer ships zero bytes to a browser that can't render it — poster instead of canvas, every time.
Solo · Next.js · TypeScript · Tailwind CSS · MDX
I’m a backend engineer in Hyderabad, currently a founding engineer at Metry AI. I like the parts of a system that are unglamorous and load-bearing — and I build agent systems on the side mostly to find out where they break.
More about meMar 2026 — Present
Remote — async with a Canada-based team
The architecture behind this portfolio — one shared WebGL canvas, MDX content validated at build time, and a deliberate rule that adding anything is one file.
Two out-of-phase trig waves multiplied together — the cheapest displacement that doesn't look like it repeats.
Claims on this site carry a receipt. Click one and you get what backs it and a link to the exact file, so you can check me instead of taking my word for it.
There are 27 of them. 18 point at code, committed benchmark data, or something running. The other 9 come from private work and link nowhere — those are marked — instead of ✓, because a claim you can’t check should not look like one you can.
A script enforces it. It fails the build on unbacked superlatives, on a benchmark percentage without its sample size, and on any claim that says it’s checkable but links nowhere. It’s the same idea as the regression gate on my macOS agent, pointed at my own writing instead of a model.
Email is fastest — I read everything.
cheetiharichandra2@gmail.com