I build the knowledge layer AI agents work from.
Founding engineer at Pavo AI. Before that, seven years scaling recommendation at ShareChat from one million users to two hundred million, then code search at Sourcegraph. I write about what agents lose between finding something and using it, and I design interfaces on both sides of an agent: the ones people use to direct and check it, and the ones it works through.
Papers at WWW, RecSys, SIGIR and CIKM Keynote at FIRE 2023 Open source: crewlore
What I believe about building with AI
- Evidence is only useful if it survives every handoff. 1 Retrieval Is Not Delivery Of the excerpts one agent had read, 22% reached the next agent intact. A structured record, with the changes around it, took that to 60%.
- An agent is finished when it can prove it, not when it says so. 2 Completion Is a Proof, Not a Status A tool call can end while the command it started is still running. Four clocks have to settle first.
- Measure how much a benchmark moves before claiming it improved. 3 Your Eval Has a Noise Floor One unchanged configuration scored 33, 27, 17 and 25 claims out of sixty.
- Choosing what an agent sees is a ranking problem. 4 Agent Context Is a Recommendation Problem Picking a small, ordered set under a hard budget when nobody asked is a close cousin of what recommenders have worked on for twenty years.
- An agent forgets things it is still holding, so write them down when it sees them. 5 Context Aging An agent read a two-step rule in its first minute and drafted it, more than twenty minutes later, as one step.
- A person’s correction should outrank the agent that wrote the draft. 6 Reviewing what an agent wrote In the review prototype, the agent can flag a sentence someone corrected and propose a change, but only a person can make it.
Writing
All writingDesign
All designOpen source
GitHub- crewlore
A local-first compiler that turns coding-agent sessions and agent-authored pull requests into a plaintext, citable team-knowledge book in your git repo. Every claim quotes the exact source line it came from, and records whether the team adopted it or tried it and declined. Alpha, on PyPI:
pipx install crewlore. - agent-relay
Multi-agent workflows that learn from their own past runs. Plans, reviews, build logs and audits live in your git repo as markdown, and
relay distill --llmturns past reviewer rejections into lessons the next planner reads. Alpha.
Papers
Google Scholar- Dimension Mask Layer: Optimizing Embedding Efficiency for Scalable ID-based Models
- Crafting Tomorrow: The Influence of Design Choices on Fresh Content in Social Media Recommendation
- Real-time Event Joining in Practice With Kafka and Flink
- Monitoring the Evolution of Behavioural Embeddings in Social Media Recommendation
- Formulating Video Watch Success Signals for Recommendations on Short-Video Platforms
- MEMER — Multimodal Encoder for Multi-signal Early-stage Recommendations
- Data Science: Uncovering the Reality
- Computer systems and methods for representatives to monitor and intervene in robot conversation
Speaking
All talksCareer
- 2025–now Pavo AI, founding engineerThe knowledge layer AI agents work from; building the founding engineering team across the US, London and India.
- 2024–2025 Sourcegraph, machine learning engineerLLM-driven ranking and retrieval for code search over large codebases.
- 2017–2024 ShareChat, staff machine learning engineerScaled the recommender system from one million users to two hundred million; led a team of 18 to 20 engineers across ranking, moderation and feature pipelines.
- 2016–2017 Fidelity Investments, data scientist
- 2011–2016 IIT Kanpur, BS and MS in Mathematics and Scientific Computing
Get in touch
Email srijanskt@gmail.com, or message me on X or LinkedIn. I'm glad to talk about agents, retrieval, evaluation, and interfaces for AI.