About Me
Front-End Developer. Product thinker.
I build web interfaces for products that are actually used — dashboards, club management platforms, e-commerce systems, and growth tools. My work sits at the intersection of frontend engineering and product thinking.
I started with design before I wrote a line of code. That background shows up in how I approach every component — understanding why something needs to exist before building it, and knowing when the spec is wrong.
Good frontend work is invisible. It loads fast, behaves predictably, and never makes users think. That's the bar I hold my work to.
Why Teams Hire Me
What I bring to every engagement.
Product-minded Frontend
I think in features and flows, not just components. Building an interface means understanding what it needs to accomplish — and asking the right questions when the brief doesn't add up.
Clean Execution
Consistent naming, clear component APIs, no unnecessary abstraction. I write code with the next developer in mind — because clean code ships faster and stays maintainable.
Design Advantage
I started with design before code. I catch usability gaps early, communicate fluently with designers, and build interfaces that feel considered — not just technically correct.
Real Business Context
I've shipped into live products with real operators and real users. I understand that a daily-use admin panel has different requirements than a marketing page — and I build accordingly.
How I Build
Four principles I don't compromise on.
Clarity First
Every component, prop name, and layout decision should be obvious. If something needs explaining, it needs rethinking.
Reusable by Default
I write components with reuse in mind from the first commit — consistent APIs, predictable behaviour, no hidden dependencies.
Performance Matters
Fast is a feature. Core Web Vitals, bundle awareness, and image optimisation are part of building — not a post-launch audit.
Details Build Trust
Spacing, transitions, loading states, empty states. Product quality lives in the gaps between features.
Product Experience
Sectors I've built real products for.
Sports Platforms
Club management, membership ops, booking flows
Admin Dashboards
Multi-role interfaces, analytics, permissions
E-commerce
Storefronts, checkout flows, product catalogues
Healthcare
Patient-facing UI, clarity-first design systems
Marketing Sites
Conversion-focused landing pages, agency delivery
Core Capabilities
The tools I work with daily.
Frontend Stack
UI & Design
Tooling & Integration
Experience
Two roles.
Real products.
One role shipping production interfaces. One role teaching others how to build them well. Both sharpen different things.
Front-End Developer
CurrentProduction frontend work on sports club management platforms and multi-tenant dashboards — the kind of interfaces that real operators depend on every day.
- Built responsive interfaces across multiple club brands using React, Next.js, and Tailwind CSS
- Converted Figma designs into production-ready components with high implementation fidelity
- Integrated REST APIs and handled dynamic data rendering across club management modules
- Worked within a multi-tenant architecture serving Kode Club, Ryze Clubs, O West Club, and Kayan Club
- Contributed to product design and UX decisions — not just execution of the spec
- Collaborated closely with designers and backend developers across the full delivery cycle
Full Stack Mentor
Kimit Innovation Technology
Teaching and mentoring the next generation of developers — which demands a level of clarity and depth that shipping code alone rarely requires.
- Taught HTML, CSS, JavaScript, and React from first principles through to real-world application
- Guided students through project-based learning — building and shipping actual products
- Reviewed code with specific, actionable feedback focused on correctness and long-term maintainability
- Explained full-stack concepts: frontend architecture, backend integration, and API design
- Supported debugging sessions and reinforced strong development habits and best practices
- Helped students understand end-to-end product development, not just isolated syntax