ABOUT · MALTA / EUROPE

I design products that make the next step feel obvious.

Product designer, 5 years in. My work runs from regulated e-commerce in Rome to a marketplace I co-own as product owner, civic tech, internal tools and consumer mobile. The constant: I don't hand off and hope. I carry design into working code.

Ranjith Rajshekar, Product Designer
RANJITH RAJSHEKARFIG. 01 · PORTRAIT
HOW I THINK

Design is a decision discipline.

Every project on this site started the same way: a problem that wasn't a design problem yet. Waste reports arriving over WhatsApp. Yoga sessions abandoned at the planning step. A marketplace that needed 2 sides to trust each other. My first job is framing, deciding what the product must do before deciding how it looks.

I hold user needs and business goals in the same hand. On Surf I own the roadmap, so every screen has to earn its build cost. On Nadif, the "user" was 5 different audiences with 3 languages, the system had to work for the least-served one. Balance isn't compromise; it's sequencing.

And I think in systems, not screens. Flows, states, components, naming, the parts that survive contact with engineering. 2 design systems and 184 screens taught me that consistency is a feature users feel even when they can't name it.

AI WORKFLOWS

AI doesn't replace the judgment. It removes the distance between judgment and shipping.

RESEARCH

Faster synthesis

Interview notes, policy documents, competitor teardowns, clustered and interrogated in hours, not weeks. On Nadif this turned Malta's waste rules into 5 audience segments I could design against.

PROTOTYPING

Working, not clickable

I prototype in real code. React Native on a live backend for Sahaja, including a MediaPipe posture-guidance spike. Real data kills bad ideas faster than any mockup.

ITERATION

Cheaper second drafts

When a variant costs minutes instead of days, you explore honestly. Flows get rebuilt, not patched, and the version that ships is the third idea, not the first one polished.

DELIVERY

Design that survives handoff

I take my own designs into working front-end code, write the PRDs, and make backlog calls, so what ships is what was intended, not a translation of it.

TRAJECTORY

5 years across different product environments.

Regulated commerce, marketplaces, internal tools and consumer products—each context strengthened a different part of how I research, design and ship.

2021–2022

Regulated e-commerce, Rome

Designed compliant e-commerce journeys at 420 Group, building my foundation across user research, UI/UX, usability testing and release QA.

2023–2024

Independent product design

Worked with early-stage ventures and SMEs across different products, owning research, user flows, prototypes and delivery from end to end.

2024–2025

MMY Malta, product designer

Joined a newly established Malta venture and designed its web, mobile and internal product experiences while building the design system from the ground up.

2024–2026

Surf Marketplace, part-time product owner

Owned the product vision and UX for a bootstrapped two-sided marketplace, designing 184 screens and 63 flows while directing a three-person development team through launch.

2025–NOW

Product strategy, internal tools and AI workflows

Lead product and design work at Sheltons across digital experiences, internal tooling, automation and AI-enabled delivery.

2025–2026

Independent product builds

Designed and built products across iGaming, civic technology and wellness—including VantageBet, Nadif Malta and Sahaja—outside my full-time working hours.

PRINCIPLES

4 rules I don't break.

01

Complexity is a design failure, not a user failure.

If a resident needs a manual to report a dumped mattress, the product is wrong, not the resident.

02

Shipped is the only done.

A beautiful file that never reached users is a sketch. I measure my work by what's live.

03

Honest evidence over polished claims.

Real numbers where I have them, "confidential" where I can't share, and no invented metrics anywhere.

04

The system outlives the screen.

Name things well, define states, build components, so the tenth screen is faster and better than the first.

NEXT

Have a product problem worth solving?

Let's make the next decision clearer.