About Kapil
The personbehind the products.
Web Designer · Full-Stack Developer · Product Engineer · 10+ years
I’m Kapil Sharma — a Web Designer, Full-Stack Developer and Product Engineer with 10+ years of experience designing, building and delivering digital products.
I started in web design and frontend development, then grew into product thinking, full-stack work and delivery ownership. The work I take on still starts with how a product should look and work — then how to build and ship it.
KapilSharma
Web Designer · Full-Stack Developer · Product Engineer
The journey
From web designerto full-stack product engineer.
My career started as a Web Designer at TechCompiler Data Systems, working hands-on with HTML, CSS, JavaScript, jQuery, Bootstrap and UI/UX. The work grew through design engineering, design leadership and customer advocacy at Sriggle.
That path is why I can design the interface, build the product, understand the business requirement and take responsibility for getting it delivered.
How I got here
From Web Designerto Full-Stack Product Engineer.
Feb 2015 – May 2017
Web Designer — TechCompiler Data Systems
Web design and frontend fundamentals — HTML, CSS, JavaScript, jQuery, Bootstrap and UI/UX.
May 2017 – Apr 2018
Design Engineer — Sriggle
Moving closer to the intersection of design, frontend development and product thinking.
Apr 2018 – May 2020
Senior Design Engineer — Sriggle
Taking greater ownership of technical decisions and larger product challenges.
May 2020 – May 2023
Design Lead — Sriggle
Working across products, interfaces and teams while thinking more deeply about the complete experience.
May 2023 – Jun 2026
Principal Customer Advocacy — Sriggle
Seeing products from the other side—understanding customer problems, product adoption and what makes technology genuinely useful.
What experience taught me
Experience changeshow you build.
After enough products, patterns show up: unclear requirements, designs that leave questions, early technical choices that become expensive, and work that looks impressive without solving the actual problem.
I try to understand the problem before reaching for the solution — the people using it, and the people who will maintain it.
What I believe
Good products needdesign, engineering and delivery.
- 01
Clarity
I want to understand the problem before deciding how to solve it.
- 02
Craft
I care about the details because small technical decisions compound over time.
- 03
Ownership
If I take responsibility for something, I don’t wait for someone else to find the problem.
- 04
Collaboration
The best products come from people who communicate openly and challenge ideas when necessary.
- 05
Judgment
Not every problem needs more technology. Sometimes the better solution is the simpler one.
- 06
Delivery
A product is not finished when the code works. It is finished when it is ready to be used.
Working with me
I value trustmore than transactions.
Good work usually comes from enough trust to ask questions, disagree when something doesn’t make sense, and take responsibility when things become difficult.
If we’re working together, I want you to know where things stand — not only when my part is finished.
Beyond a project
I’m interested in relationshipsthat last longer than the first delivery.
Once I understand a product, a business and the way a team works, the next piece of work has more context and less friction. That is why I value relationships with employers, founders, businesses and agencies that last longer than the first delivery.
What I’m looking for
Good people. Interesting problems.Work worth caring about.
I enjoy working with people who care about what they are building.
It could be a remote role, a website or application that needs to be delivered, or an agency looking for a dependable design and development partner.