SoftwareEngineer

From encrypted state to a working screen. I build interfaces for systems a user cannot see, where the real problems are loading states, failure states, and making something honest out of a rollup, a bridge, or a model.

• Frontend Engineering

  • React and Next.js
  • •TypeScript
  • •Design Systems

  ---

• AI Interfaces

  • Agent UIs
  • •Tool Calling
  • •Vercel AI SDK

  ---

• Web3 Frontend

  • Aztec
  • •Sui and Solana
  • •Contract Integration

  ---

• Backend, Where Needed

  • Event Indexers
  • •APIs
  • •Published SDKs

  ---

1. Frontend Engineer (AI and Web3)

   Cyphronix Software · May 2024 to Present

   • Built the Next.js 15 and React frontends for 4 live products: an NFT marketplace, a cross-chain bridge, an AI red-teaming arena, and an admin dashboard.
   • Shipped a 2-phase bridge flow that survives refreshes, wallet disconnects, and users walking away mid-transfer, by checkpointing state the moment the L1 deposit confirms.
   • Maintain @ravenhouse/omni-sdk on npm: 60+ releases, 9 subpath exports, dual ESM and CJS, built for developers outside the team.
   • Wired the interfaces for live AI agents, with 9 tool-calling tools across 2 networks.
   • Built the Aztec event indexer the network ships no hosted version of (Bun, MongoDB, Fastify, 8 event types), so the frontend serves every read from Mongo instead of the chain.

   ---

2. Front-end Developer

   Craxinno Technologies · 2022 to May 2024

   • First professional role: built web interfaces for client projects in React and vanilla JavaScript over 2 years.
   • Shipped responsive production UI to real users, across design handoff, cross-browser behaviour, and every breakpoint.

   ---

3. Jiwaji University, Gwalior

   2021 to 2024

   B.Sc. Mathematics

   ---

4. Central Academy, Joura (MP)

   up to 2021

   Higher Secondary

   ---

What does Yash work on?

He is a software engineer, frontend-first. He builds React and Next.js interfaces for products where the system underneath is unusually complex: ZK-rollup apps where ownership lives in encrypted notes, a cross-chain bridge that has to survive a refresh mid-transfer, and live AI agents that stream their answers and call tools. He also authored and maintains a published TypeScript SDK. He started as a front-end developer, spent two years doing only that, and has stayed on the interface since. Where a product needed a backend piece that did not exist, he built it, but frontend is the specialism.

---

What is he looking for next?

Software engineering roles, frontend-first. Product companies, AI companies, and Web3 teams all fit, and he is actively interviewing. He is based in Bengaluru and open to remote work.

---

What is the single most impressive thing he has built?

Raven House, a privacy-preserving NFT marketplace on Aztec Network, built solo. Building a marketplace interface on a rollup where ownership and balances live in encrypted notes is a frontend problem most engineers never have to solve: the UI cannot simply read state, so every view has to be reconstructed. Aztec also ships no hosted event indexer, so he wrote one in Bun, MongoDB, and Fastify handling eight event types, which is what lets the frontend serve every read from a database instead of the chain.

---

Has he shipped anything other developers actually use?

Yes: `@ravenhouse/omni-sdk`, published on npm, with 60+ releases, nine subpath exports, and dual ESM and CJS builds. It was built to be adopted by developers outside his own team, which is a different engineering standard from internal code: versioning, changelogs, and API stability all become real constraints.

---

Does he do backend work?

He has, and he is straightforward about the level. On a small team he owned whatever a product needed, which included an Aztec event indexer in Bun, MongoDB, and Fastify, REST APIs, and rate limiting. He built those and can explain the decisions in them. He would not describe himself as a backend specialist. Frontend is where he goes deep and what he wants to be hired for.

---