Skip to content
Kenil Sangani

05Experience

Co-founder,
Creativity Coder.

I co-founded Creativity Coder with Hitarth Shah. My work there spans the full arc of a product — from understanding the problem to running the system in production.

05.1Professional experience

The work
I do.

Present

Creativity Coder

Co-founder & Technical Architect

creativitycoder.com (opens in a new tab)

Creativity Coder is the systems and product engineering studio I co-founded with Hitarth Shah. We build web platforms, custom business software and workflow automation that businesses run on day to day.

  • 01

    Software product development

    Taking products from problem definition to production, across client engagements and internal builds.

  • 02

    Technical architecture

    Defining system boundaries, data flow and the shape of each platform before implementation begins.

  • 03

    Backend engineering

    APIs, authentication, authorisation and the server-side logic that business workflows depend on.

  • 04

    Database design

    Data models that keep records consistent as products and their rules grow.

  • 05

    Infrastructure

    Deployment, hosting and production operations for the systems we ship.

  • 06

    Engineering decisions

    Choosing the stack and the trade-offs per project rather than per trend.

05.3Technical capabilities

Engineering across
the whole system.

Organised by domain, not by logo. Tools only matter when they serve a decision.

  1. 05.3.105 areas

    Frontend Engineering

    Interfaces that stay fast and legible as products grow.

    • React
    • Next.js
    • TypeScript
    • JavaScript
    • Tailwind CSS
  2. 05.3.205 areas

    Backend Engineering

    The contracts and rules a product actually runs on.

    • Node.js
    • Express.js
    • API architecture
    • Authentication
    • Authorization
  3. 05.3.304 areas

    Data Architecture

    Models that keep records correct under real-world use.

    • MongoDB
    • PostgreSQL
    • Redis
    • Data modelling
  4. 05.3.406 areas

    Infrastructure

    Getting software into production — and keeping it there.

    • Linux
    • Docker
    • Nginx
    • PM2
    • Deployment
    • Production operations
  5. 05.3.504 areas

    Interactive Development

    3D and motion where they explain or delight — not decorate.

    • Three.js
    • React Three Fiber
    • GLSL shaders
    • GSAP
  6. 05.3.604 areas

    AI Engineering

    Models as components inside well-designed systems.

    • LLM integrations
    • Tool calling
    • AI-powered applications
    • Context engineering

05.4Engineering philosophy

Code is the implementation.Architecture is the thinking.The system is the product.

  1. 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.

  2. 02decide early, refactor less

    Architecture before implementation

    Boundaries, responsibilities and data ownership are decided before the first feature, while changing them is still cheap.

  3. 03budget first, optimise second

    Performance by design

    Speed is a product feature. Payloads, queries and rendering strategy are design inputs, not late-stage patches.

  4. 04deny by default

    Security by default

    Least-privilege access, validated input and safe data handling are the starting point — not a checklist at launch.

  5. 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.

  6. 06leverage × judgement

    AI as an engineering multiplier

    AI accelerates research, scaffolding and review. Judgement, architecture and accountability stay with the engineer.