Languages
- TypeScript / JavaScript
- Python
- Go
- C / C++
About
Software that
earns its place.
I’m Aman Kumar, a full-stack software engineer from Uttar Pradesh, India. I build products, tools, and systems — and I care as much about the quiet reliability underneath as the interface on top.
I like problems where the interface is simple and the engineering is not.
My work sits across the stack: React and Next.js on the product side, Python and FastAPI in services, Go when the problem is closer to the metal, and PostgreSQL, Redis, Docker, and Kubernetes underneath. I’ve shipped client work, maintained open-source tools, and built systems that need to stay correct when something fails.
I’m currently a Software Developer at INFYSKILL EDUTECH, freelance through Connect Sutra, and finishing a B.Tech in Computer Science. I’m looking for remote roles where I can own meaningful product work, learn from strong engineers, and keep shipping.
Experience
A short
timeline.
Jan 2025 — Present
Software Developer · INFYSKILL EDUTECH
Remote. Building React/Next.js product interfaces, Python/FastAPI services, and automation workflows. Working across frontend and backend to turn requirements into shipped features.
Freelance · Remote
Web Developer · Connect Sutra
Building responsive web experiences for client projects, from implementation to deployment.
Sept 2024 — Sept 2028
B.Tech, Computer Science · Dr. A.P.J. Abdul Kalam Technical University
Lucknow, Uttar Pradesh. GPA 8.0 · computer science fundamentals, systems, and applied software projects.
2026
OpenAI Codex Hackathon · Top 30%
Placed in the top 30% of 2,989 participants.
Capabilities
Tools I reach
for.
Frontend
- React / Next.js
- Tailwind CSS
- HTML / CSS
- Three.js
Backend & data
- Node.js / Express
- FastAPI
- PostgreSQL / MongoDB
- Redis / Supabase
Infrastructure
- Docker / Kubernetes
- Linux / Git
- GitHub Actions
- Prometheus / OpenTelemetry
AI / ML
- PyTorch
- NLP
- Computer vision
- Generative AI
Practices
- API design
- Testing
- Observability
- Technical writing
Principles
How I try
to work.
Ship the smallest honest version.
A working slice teaches more than a polished plan. Start narrow, make it real, then earn the next layer.
Make failure visible.
Logs, metrics, and clear errors are not polish. They are how software stays trustworthy when conditions change.
Leave the next person a map.
Good names, small surfaces, and honest documentation are part of the product, not an afterthought.
Contact
Open to the
right role.
Remote software engineering roles, internships, and thoughtful freelance work.