Shaswat Raj · Forward Deployed Engineer
I ship in the user's environment, with their constraints, on their deadline.
Forward-deployed work is building next to the people who use the thing: unclear requirements, messy data, and a date that does not move. That is how I have worked on every project that had real users on the other side.
Looking for: Forward-deployed, solutions and founding-engineer internships or new-grad roles at startups, where I own a customer problem end to end.
Evidence
What I have done that is relevant
Bitotsav '26 — tech lead for a ~5,000-participant festival
The users were organisers, gate volunteers and college administration. The constraints were no-network zones, bad data and last-minute changes. I built the entry, team, points and admin systems and ran them live during the event.
liveKishan AI — an assistant farmers reach through Telegram
Crop-disease diagnosis from photos, weather, mandi prices and scheme lookup, delivered where the users already are instead of in a new app. Shortlisted in the Top 500 of the AICTE Productization Fellowship 2025.
AI systems wired into real workflows
Debo is a retrieval pipeline over personal notes, links and audio. IndexFast is an MCP server that submits URLs to Google, Bing and IndexNow from inside an IDE.
liveDhwani — delivered for a client, not for myself
The music society's site: requirements from a non-technical team, a fixed event date, design and build end to end.
liveExplaining technical work to non-engineers
I write publicly on Dev.to and have presented system designs to college leadership. Clear writing is most of the job when the user is not an engineer.
Tools I have shipped with
How I work
- Start from the user's day, not from the architecture.
- Ship the smallest thing that works on site, then harden it.
- Design for the failure cases first: no network, wrong data, a changed plan.