01About me
Curiosity turns
into systems.

I'm Kenil Sangani, a software engineer and co-founder of Creativity Coder.
I work at the intersection of software engineering, system architecture and product development.
I enjoy understanding complex problems, designing the systems behind solutions, and engineering software that is reliable, scalable and maintainable.
My interests include full-stack engineering, backend architecture, database systems, interactive web experiences, AI-powered applications and production infrastructure.
I believe the real challenge in software engineering isn't making something work once. It's building something that continues to work as complexity grows.
- Role
- Software Engineer
- Company
- Co-founder, Creativity Coder
- Based in
- Gujarat, India
- Focus
- Systems · Backend · Product
02Founder journey
Building
Creativity Coder.
I co-founded Creativity Coder with Hitarth Shah. It is a systems and product engineering studio: we build the software businesses run on — web platforms, custom business tools and automated workflows.
My side of the partnership is the architecture — how a system is divided, where its data lives, how it is secured, deployed and kept fast. Hitarth leads interface engineering and client workflows. Most of what we ship is genuinely shared work, and the case studies on this site say so.
Running a studio changed how I think about engineering. A system is only finished when it survives real users, real data and real constraints — and when the next engineer can understand it.
- 01
Web Systems & Platforms
- 02
Custom Business Software
- 03
Workflow Automation & Pipelines
- 04
System Modernization & Performance
- 05
Mobile App Development
Studio practice areas, as published by Creativity Coder.
03Technical interests
Technical interests
- 01Full-stack engineering
- 02Backend architecture
- 03Database systems
- 04Interactive web experiences
- 05AI-powered applications
- 06Production infrastructure
04Engineering philosophy
Code is the implementation.Architecture is the thinking.The system is the product.
- 01problem → model → code
Systems over syntax
Syntax is the easy part. I start with the problem, the people and the flow of data — the code follows from that understanding.
- 02decide early, refactor less
Architecture before implementation
Boundaries, responsibilities and data ownership are decided before the first feature, while changing them is still cheap.
- 03budget first, optimise second
Performance by design
Speed is a product feature. Payloads, queries and rendering strategy are design inputs, not late-stage patches.
- 04deny by default
Security by default
Least-privilege access, validated input and safe data handling are the starting point — not a checklist at launch.
- 05clarity compounds
Maintainability always
Software is read and changed far more than it is written. I build for the engineer who opens the code a year from now.
- 06leverage × judgement
AI as an engineering multiplier
AI accelerates research, scaffolding and review. Judgement, architecture and accountability stay with the engineer.
05Technical capabilities
Engineering across
the whole system.
Organised by domain, not by logo. Tools only matter when they serve a decision.
- 05.105 areas
Frontend Engineering
Interfaces that stay fast and legible as products grow.
- React
- Next.js
- TypeScript
- JavaScript
- Tailwind CSS
- 05.205 areas
Backend Engineering
The contracts and rules a product actually runs on.
- Node.js
- Express.js
- API architecture
- Authentication
- Authorization
- 05.304 areas
Data Architecture
Models that keep records correct under real-world use.
- MongoDB
- PostgreSQL
- Redis
- Data modelling
- 05.406 areas
Infrastructure
Getting software into production — and keeping it there.
- Linux
- Docker
- Nginx
- PM2
- Deployment
- Production operations
- 05.504 areas
Interactive Development
3D and motion where they explain or delight — not decorate.
- Three.js
- React Three Fiber
- GLSL shaders
- GSAP
- 05.604 areas
AI Engineering
Models as components inside well-designed systems.
- LLM integrations
- Tool calling
- AI-powered applications
- Context engineering
06Beyond code

The person
behind the
systems.
The same curiosity that pulls apart a system pulls me toward unfamiliar places.
- Travel
- Journeys that change the scale of things — like this one, to the Himalayas.
- Exploring
- New places, and the new perspectives that come with them.
- Learning
- Continuously — new tools, new domains, new ways of seeing a problem.
- Experimenting
- Independent projects built to answer a question.
- Growing
- As an engineer, as a founder and as a person.

