AI Tutor Platform
Experiment- Problem
- Generic learning tools don't adapt to how an individual actually learns.
- Built
- An AI-powered tutoring/coaching platform exploring personalized learning and tutor-style conversational behavior.
I'm Parth — a full-stack software engineer and Developer Experience engineer with 13+ years of experience turning ideas, business problems and occasionally chaotic requirements into production-ready software.
13+ years · Full Stack · AI · Automation · DevEx · Cloud
I build software end-to-end.
I've spent 13+ years working across frontend, backend, APIs, cloud infrastructure, DevOps, automation and increasingly AI-powered systems.
Sometimes that means building a product from scratch. Sometimes it means taking a messy existing application and making it sane. Sometimes it means figuring out why a server is consuming 100% CPU at 3 AM.
And sometimes it means asking: "Why are we doing this manually?"
The short version Give me a problem, an idea or an existing system. I'll figure out what the software should look like.
Not a resume timeline — an evolution. Each era built on the fundamentals of the one before it.
Complex web applications, dashboards, portals and business systems.
Taking an idea from architecture to MVP to production.
LLM-powered products, AI assistants, RAG systems, intelligent workflows and AI automation.
Tools that make developers faster, happier and less likely to open another browser tab.
Replacing repetitive manual workflows with software, APIs and AI.
Cloud deployments, Docker, Linux, CI/CD, production environments and the things that keep applications alive.
Developer portals, tooling, workflows and systems that make engineering teams more productive.
Tools change. Engineering fundamentals don't.
A mix of real projects, experiments and prototypes — not just polished case studies.
This list changes more often than my package.json.
Technology is not the objective. The outcome is.
Complexity should be earned.
If humans repeatedly do the same thing, there is probably a better system.
A prototype is useful. A reliable product is better.
The stack changes. Curiosity shouldn't.
I've spent years building software. More recently, I've become interested in the systems surrounding developers: tooling, workflows, automation, CI/CD, internal platforms and AI-assisted development.
AI has changed how I think about software development. I'm interested not only in calling an LLM API, but in what happens when AI becomes part of the actual product, workflow or development environment.
A running list of what I'm currently poking at — not everything here ships.
Exploring what can realistically run on consumer hardware.
Training and experimenting with custom models and workflows.
Exploring whether existing Wi-Fi infrastructure can be used for device-free sensing.
Building small robotic systems from individual components.
Running services, tunnels, infrastructure and automation from home.
I'm open to a limited number of interesting projects, consulting engagements and technical collaborations.
Have an idea that needs to become a working product?
Have an existing application that needs attention?
Have people doing repetitive work that software could handle?
Need help figuring out architecture, technology or the right way to build something?
Have an interesting technical idea and want another engineer involved?
If something on this site helped you, you found an interesting project, or you simply want to talk technology, say hello.
Worst case: we have a conversation. Best case: we build something useful. Somewhere in between, I get coffee.