Kabir Kenth — Brampton, Ontario
I build systems that stop and ask before doing anything they can't undo.
Software engineer in Brampton, Ontario. Three systems shipped end to end — a live LLM application platform that won't submit anything without human sign-off, a weekday news-sentiment pipeline built so a rerun can't double-count, and a two-sided logistics prototype. B.Eng. Software Engineering, McMaster, November 2025.
- Now
- Open to entry-level software engineering roles — Brampton / Toronto / remote
- Shipped
- ApplyTron — live multi-user platform at app.kabirkenth.me
- Weekdays
- A Claude news-sentiment pipeline that grades its own calls in public
- Degree
- McMaster B.Eng. Software Engineering — graduated Nov 2025
Selected work
Three systems, written up the way I'd hand them to a teammate.
LLM job-application platform with a human approval gate
Multi-user Next.js app. Adzuna ingest, Claude scoring, generated PDFs — and nothing submits until a person approves it.
- Next.js
- Supabase
- Claude API
- Playwright
News sentiment to a graded next-session call, every weekday
A Railway cron upserts prices and headlines into Supabase, so a rerun can't double-count. Claude scores the news, a Random Forest makes the call, and a live dashboard grades it.
- Python
- Supabase
- Claude API
- Railway
- Vercel
Two-sided load matching for truckers and shippers
The project I could only have designed because I did the job. A swipe deck over a freight board, with the reconciliation problem built into the schema. Deployed — open the demo without registering.
- React
- Express
- Postgres
- Prisma
- Vercel
The short version
It took me eleven years to finish a five-year degree.
I started at McMaster in 2014 and graduated in November 2025. I stepped away more than once and came back. That wasn't a straight line, and I'd rather say so here than have you count backwards from the dates.
I worked the whole way through. Five and a half years running the books for my family's business, a summer as an operations manager building forecast models, a summer of inventory at Costco, and a summer at a trucking company keying freight documents into systems with no shared identifier between them.
One word keeps repeating across all of it: reconciled. The books, the daily cash, the freight records. I've spent about a decade being the layer between systems that didn't agree with each other.
That's where the headline comes from. ApplyTron won't send a document until a person approves it. The market pipeline upserts instead of appending, so a retry can't double-count. Both are built so nobody has to do what I spent a decade doing.
What I reach for
Backend & data
- Python
- Node.js
- Express
- PostgreSQL
- Prisma
- Apache Airflow
- BigQuery
- ETL / ELT design
Cloud & infra
- GCP
- Docker
- Vercel
- Railway
- Supabase
- Firebase
Frontend
- TypeScript
- React
- Next.js
Working practice
- REST API design
- JWT auth
- Idempotent pipelines
- CI/CD
- Scrum