SCR
000

Applied AI + Full Stack  /  5 Years Building  /  MS Robotics & AI, Arizona State

Eshan Kaushal

engineer 0.00

I build AI that works outside the notebook. Detection systems, language models, and the full stack that carries them to something people can actually use.

Experience5 Years
Available forContract & Long-term
Ships toEdge & Cloud
AlsoGuitar & Racing

The gap

Research is
not a product.

Plenty of things look brilliant in a notebook. Vision models that are perfect on clean validation images start guessing the moment the light goes bad. Assistants that demo beautifully go sideways the first time somebody asks the question nobody planned for. Sites that run fine for you fall over the week they finally get traffic. I work in that gap.

Five years of it, across production systems, research labs and contract projects. Most of the job is the unglamorous half: making something that works in principle work on real hardware in real conditions, fast enough that nobody complains. Language models tuned with human feedback so they answer the way one business needs rather than the way the internet would, detection and tracking that holds up on a warehouse floor at 6am, and the web and data plumbing that carries either one to somebody who can actually use it.

If that sounds like your project, a conversation is a good place to start. No finished brief needed, and no obligation either way. And if it needs one person who can go from raw data collection to a deployed endpoint without three handoffs, that is the job I take.

[ photo ]
drop image here
Eshan Kaushal
SRC / 0014:5

Hire me for

What I build.

Keep scrolling →

web

Full stack builds

Your whole website or app, designed, built and put online.

Frontend, backend, database, deployment, all of it in one pair of hands. Something that runs and keeps running, not a demo that falls over on the second click.

llm

AI inside the product

A chatbot or assistant that actually knows your business, not a generic one.

Retrieval over your own documents, assistants wired into your existing tools, model endpoints your app can call. Built into the product, not bolted on beside it.

vision

Computer vision systems

Software that watches a camera and tells you what it sees.

Detection, tracking, counting, inspection. Multi-camera pipelines that hold up in a warehouse at 6am, not just on a clean validation set.

train

Models built for you

When an off-the-shelf model does not fit your problem, I build one that does.

Architecture, training loop, loss design, evaluation. From scratch or fine tuned from an existing model. I will tell you which one you actually need before you pay for the expensive option.

data

Data pipelines

Turning the mess you already have into something a model can learn from.

Collection, annotation, labeling standards, cleaning, versioning. The unglamorous half that quietly decides whether your model is any good.

deploy

Getting it live

Making it run on real hardware, for real users, at a cost you can predict.

Jetson, CUDA and TensorRT when it has to run on the device, managed cloud hosting when it has to run for everyone. Quantized, profiled and measured before I call it done.

Live demos

Have a look
at the real thing.

A couple of working models, on their own page. Ask a document a question and watch it find the answer step by step, or point an object detector at a photo. Both run in your browser, so anything you load stays on your device.

How I work

Built fast,
on purpose.

I take pride in how quickly I move. Every tool that shortens a build without costing quality gets used, and I keep looking for better ones.

For you that means a shorter timeline and something real in front of you early, rather than a long quiet stretch before the first look.

tooling

Every tool that earns its place

Solid frameworks, automation, and whatever else keeps repetitive work off the critical path.

momentum

Working software early

You see something running quickly, so you can react while changing direction is still easy.

craft

Speed without shortcuts

The pace comes from good tooling and from having built this kind of system before, not from skipping the parts that matter.

No jargon

Not sure what
to ask for?

Most people arrive with a problem, not a spec. That is completely normal. Here is what those problems usually sound like, and what I would actually build for each one.

“I have hours of camera footage and no idea what is in it.”

A system that watches the video for you and reports what happened, where, and when. You get a searchable record instead of a hard drive.

“I want a chatbot that actually knows my business.”

An assistant connected to your own documents and data, so it answers from your material rather than making things up.

“We count or inspect things by hand and it is slow.”

A camera and a model that do the counting, flag anything that looks wrong, and keep a log you can check later.

“We have an idea but no website or app yet.”

The whole thing built and live. The pages people see, the database behind them, and the hosting so it stays up.

“Someone built us an AI feature and it does not work.”

I take it apart, find where it actually breaks, and tell you honestly whether it is worth fixing or rebuilding.

“We have plenty of data but it is a mess.”

Cleaned, labeled and organised properly, so the model you build on top of it is worth the money you spend training it.

Toolkit

The parts bin.

The full list, in case you want to check something specific. If you would rather skip the jargon, the section above covers the same ground.

Vision
YOLODETRSSD ViTDINOv2CNNs ResNetMobileNet DetectionTrackingSegmentation
Language
GPT-2BERTRoBERTa BARTT5RNN LSTMMultimodal
Training & tuning
RLHFPPOQ-Learning Fine tuningTransfer learning Prompt engineeringPyTorch DDPMulti-GPU
Data
CollectionAnnotationLabeling standards Dataset curationAugmentationClass balancing PySparkETLVersioning
Video pipelines
GStreamerONVIFRTSP Multi-cameraStream ingestion
Deployment
NVIDIA JetsonCUDATensorRT Edge inferenceModel serving
Simulation
Unreal Engine 5UnityGodot PyTorch ProfilerSynthetic dataVR

Track record

Numbers that
left the lab.

Every one of these came from a system that had to keep working after I stopped looking at it.

+0%
Production system · 3 years

Sales growth on a product built around the detection architecture and camera integration I designed.

+0%
ASU Research

Social chatbot performance gain using RLHF and multi-GPU training.

+0%
ASU Research

Virtual therapy agent effectiveness gain in the same lab, from the same training stack.

+0%
Pipeline work

ETL latency cut with PySpark, alongside wiring Unreal Engine 5 into PyTorch Profiler for healthcare and VR simulation.

Off the clock

Two other
obsessions.

signal / guitar

Electric guitar,
played professionally.

Blues, hard rock and metal. Mostly the parts with too many notes in them. Years of playing to rooms taught me more about reading an audience than any deck ever did.

telemetry / track

Race car driver,
upcoming.

Simulator hours now, track time next. Same instinct as the engineering: find the limit, then find out what it costs to hold it there.

Sector 1Simulator
Sector 2Track
Sector 3Strategy

I also give time to NGOs when there is something worth building for them. Good engineering should not only be available to people who can pay for it.

Contact

Let us build
something.

Open to contract and freelance work, including long engagements. Some of the best things I have built ran a year or more with the same team. Tell me what you are trying to ship, in whatever words you have, and I will tell you straight whether I am the right person for it.

The quickest route is the chat in the corner. It reaches me directly, so leave your details there and I will pick it up.

Like this site? I built all of it, demos included. Ask the chat to set up a call and we can talk about yours.