Software engineering experience you can verify.
Anish helps teams modernize existing applications, ship focused new systems, and connect backend or AI workflows to real work. This page collects the evidence first, so you can evaluate the fit without a sales detour.
Explore projects, case studies, live systems, and source code.
Review retrieval systems, marketplace search, integrations, background processing, and the tradeoffs behind each build.
Open work samples ENGINEERING PROJECT · LIVE SYSTEMGrounded AI search over technical documentationTry a working retrieval experience with source grounded answers, streaming output, and a visible system boundary.
Try the retrieval demo OPEN SOURCEExplore real projects and codeExplore public repositories covering queue processing, database tooling, and model connected developer workflows.
Open GitHub profileEvidence for each engineering capability.
Browse projects, case studies, live systems, and open source work to evaluate fit for your team.
| Claim | Supporting evidence | Verify |
|---|---|---|
| Modernizes and improves existing software | Existing application, search, and integration case studies | Explore work |
| Builds AI and search systems | Working retrieval demo and search architecture notes | Try the demo |
| Understands backend and workflow systems | Live task queue demo: BullMQ, Redis, idempotency, DLQ, Prometheus | Try the demo |
| Uses testing and delivery discipline | Repository test suites, route checks, browser checks, and deployment configuration | Review practice |
Useful in the space between product intent and implementation.
I work across the boundary where requirements become architecture, code, tests, deployment, and documentation. The strongest fit is a team that needs an engineer who can make technical decisions and keep the implementation connected to the business problem.
Incremental modernization, feature work, and maintainability improvements.
Data workflows, integrations, queues, validation, and operational tooling.
Retrieval, source grounding, workflow boundaries, and human review paths.
Source code, setup context, deployment notes, and a maintainable ownership path.
A short path for a serious conversation.
Start with the case studies, live systems, or repositories that match the role.
Look for boundaries, tradeoffs, tests, failure handling, and ownership details.
Email Anish with the role, system context, and the decisions the team needs help making.
No unsupported scale claims or invented client metrics are used here. The evidence is the point.