drag me

Photo of Muhammad Fatheen

Muhammad Fatheen

Chennai, India Open to Associate PM roles

Simple is the last thing a product becomes.

I’m a Product Management Intern at Zuper, a B2B field-service platform. I studied Computer Science and Engineering at Sathyabama Institute of Science and Technology, co-founded an ironing service called Wrinkl, and now spend my days finding where people get stuck and deciding what is worth building.

Top 3Second runner-up, IEEE YESIST12 2025, with Wrinkl
₹22LGovernment-funded assistive tech project I helped build
8.49CGPA, B.E. Computer Science and Engineering, Sathyabama, 2026
3Internships across design, development and product

Case studies

3 · open one for the summary

three last miles,
one decision each

2026
Google MapsThe last 100 metres

Maps gets the rider to the building. The handover still starts with a phone call.

Product case study

Target user
Delivery riders arriving at gated complexes and buildings with several entrances, and the people receiving the order.
Pain point
Maps ends the trip at the building, not at the right gate, so the handover starts with a phone call and a walk around the complex.
Gap
Maps can show where entrances are, and Address Descriptors describe the area. Neither says which entrance to use for this delivery, and delivery apps only receive a point on the map.
Solution
The receiver confirms the delivery entrance when they share a location. The rider is guided to that gate, and delivery apps receive it through the Maps Platform.
North Star
Time from arrival to handover, for the slowest 10% of deliveries
Guardrails
Time to share a location, wrong or unsafe entrances, and privacy reports

Inside the case

  • Market sizing
  • RICE
  • Partner model
  • A/B test design
  • North Star metric
  • Now, Next, Later roadmap
Chennai MetroThe ride home after a match

Paying for the metro is solved for regulars. It breaks at the busiest moment: everyone leaving a match at once.

Field teardown

Target user
Fans leaving a big match at Chennai Central, especially first-time riders without a ticket on their phone.
Pain point
At the busiest moment of the night they queue twice: at the ticket counter, then again at the gates.
Gap
Paying is solved for regular riders through WhatsApp and app QR tickets. Event nights are not, except for sponsored IPL rides.
Solution
Make the match ticket the metro ticket wherever a sponsor pays; otherwise send a "book your ride home" link with every big-event ticket.
North Star
Share of post-match riders who enter without visiting a counter
Guardrails
Failed QR scans at the gates and cost per event

Inside the case

  • Queue model
  • Benchmarking
  • RICE
  • Metrics
  • Roadmap
2025
WrinklIroning, ordered on WhatsApp

Ironing is a small chore with a large coordination cost. Could it be as easy to order as anything else?

Early-stage venture

Target user
Households who iron every week or need a batch at short notice, and the neighbourhood dhobi shops that would do the pressing.
Pain point
Ironing is a weekly chore with a coordination cost: finding a shop, arranging pickup and return, and guessing the price.
Gap
Quick commerce reached food and groceries, not ironing. Local shops can press fast, but none of them collect and deliver.
Solution
Ironing only, ordered on a WhatsApp bot, with Wrinkl handling pickup and return in booked slots and the price shown before you confirm.
North Star
Orders returned pressed, on time, each week
Guardrails
Re-press requests and delivery cost per order

Inside the case

  • Field research
  • PRD
  • MoSCoW
  • Unit economics
  • AARRR funnel
  • Given / When / Then

Second runner-up at IEEE YESIST12 2025. Prototype and WhatsApp bot built; the vendor trial never started, so there are no customer results to report.

Experience

4 roles
ZuperProduct Management InternJul 2026 – Present

B2B SaaS · Field service management

Software that businesses use to coordinate jobs, people, customers and operations in the field. Product changes have to respect existing workflows and the very different people who use them.

How a piece of work moves

01 · Discover

Find where the product falls short of how customers actually work, and look into new product areas.

What comes outA written finding

02 · Define

Compare how others solve it, weigh the user and product trade-offs, then write requirements, UX flows, user stories and acceptance criteria.

What comes outRequirements engineers can build from

03 · Deliver

Work with product managers and engineers in Agile cycles, from discovery through to build.

What comes outTickets that say what was decided

What it has taught me

In an established product, every change lands on something people already depend on. Research earns its place when it explains a trade-off, and requirements get better when engineers and product shape them together.

Tools

  • Linear
  • Slack
  • PostHog
  • Microsoft 365

Described at a public-safe level. No internal screenshots, customer data or unreleased details.

WrinklCo-founder / Product BuilderJan 2025 – Oct 2025

Early-stage venture · Quick-commerce ironing

Could a familiar offline service become as easy to order as any on-demand service, and what has to be true behind the screen for that promise to hold?

  • Owned the research, product decisions, pricing and build end to end.
  • Led development of an ordering platform with a WhatsApp bot to simplify customer orders.
  • Researched the market end to end: existing apps, laundromats, an equipment maker, online surveys and conversations with people in the trade.
  • Spoke with local dhobi shops to set up a trial. They could offer quick service but not delivery.
  • Placed second runner-up at IEEE YESIST12 2025 in Malaysia.
  • The trial never started, so there are no customer or order results to report.
  • WhatsApp Business API
  • Postman
  • Supabase
  • ChatGPT
  • Claude
  • Gemini
TechKnotsMERN Stack Development InternMay 2025 – Jul 2025

Internship · Web development

A software internship building customer-facing web modules with the MERN stack.

  • Developed and improved customer-facing web modules using the MERN stack.
  • Integrated WhatsApp Business APIs for customer communication: chat, images and order updates.
  • Helped with debugging, testing and bug fixing across development cycles.
  • MongoDB
  • Express
  • React
  • Node.js
  • WhatsApp Business API
Chennai Publishing ServicesUI/UX Design InternMay 2024 – Jun 2024

Internship · Design

A short design internship that taught me to turn written requirements into consistent, user-focused interfaces.

  • Designed web pages, company posters and digital assets in Figma.
  • Iterated on UI layouts based on feedback and delivered marketing assets.
  • Figma

What I practise

eight methods · click one to see where I used it

no skill listed
without a receipt

Toolkit

what I reach for every week
Product6 tools
  • Figma
  • Linear
  • Notion
  • Slack
  • Microsoft 365
  • Google Workspace
AI3 tools
  • Claude
  • ChatGPT
  • Gemini
Prototype & measure3 tools
  • Lovable
  • Postman
  • PostHog

Hello there !

  • I started by building software. Then I got more interested in why things get built than in how.
  • Wrinkl taught me the operational side of product. For eight months I researched, priced and prototyped an ironing service. The trial never ran, and I say so wherever it matters.
  • At Zuper I work on a product people already depend on. Every change lands on an existing workflow, so research has to explain a trade-off, and requirements get better when engineers shape them too.
  • I believe simplicity is a decision. Most of my work is making it.

Writing

short notes from real work · click to read

Lines I keep coming back to

borrowed,
but lived

“If you are not embarrassed by the first version of your product, you’ve launched too late.”
Reid Hoffman
“The essence of strategy is choosing what not to do.”
Michael Porter
“The most important thing in communication is hearing what isn’t said.”
Peter Drucker
“Your most unhappy customers are your greatest source of learning.”
Bill Gates

Say hello

hiring an Associate PM?
LinkedInin/fatheen7
Based inChennai, India

About

A builder, asking why.

I started by building software. Then I got more interested in why it gets built than in how.

The path so far

from writing code to deciding what gets built
202201

Computer science foundation

What I didStarted a B.E. in Computer Science and Engineering at Sathyabama Institute of Science and Technology, Chennai, and began building software.

What I learnedHow software is put together. That is why I can follow an engineering conversation and ask what is feasible before I ask what is desirable.

2024 – 2502

Design and development internships

What I didA UI/UX design internship at Chennai Publishing Services, working in Figma. Then a MERN stack internship at TechKnots, building customer web modules and integrating WhatsApp Business APIs. Alongside: an AI traffic system and the government-funded Smart Blind Stick.

What I learnedDesign taught me to start from what a person sees. Development taught me what a request costs. Both made me curious about who decides what gets built.

202503

Entrepreneurship through Wrinkl

What I didJanuary to October 2025. Co-founded Wrinkl, a quick-commerce ironing service. Owned the market research, pricing, a WhatsApp ordering bot and talks with dhobi shops. The trial never started, but Wrinkl placed second runner-up at IEEE YESIST12 2025.

What I learnedThe screen was the easy part. Pricing, vendor capacity and hand-offs decide whether the promise holds, and I should have tested those before building more.

2026 – nowNow

Product management at Zuper

What I didSince July 2026, Product Management Intern at a B2B field-service SaaS platform. Product discovery, competitive analysis and requirements for engineers.

What I learnedIn an established product, every change lands on something people already depend on. Research earns its place when it explains a trade-off, and requirements get better when engineers and product shape them together.

Recognition

  • Second Runner-Up, IEEE YESIST12Wrinkl · Kuala Lumpur, Malaysia · 2025
  • Finalist, BITS Pilani Hyderabad HackathonBITS Pilani, Hyderabad · 2025
  • Luminary AwardSathyabama Institute of Science and Technology · 2025
  • International Project Pitching EventUniversiti Sains Islam Malaysia

Credentials

B.E. Computer Science and EngineeringSathyabama Institute of Science and Technology, Chennai · 2022 – 2026
CGPA 8.49

Certificates

  • Microsoft Certified: Azure FundamentalsAZ-900
  • Oracle Certified Cloud Foundations AssociateOracle
  • Programming in JavaNPTEL

Community

  • Google Developer Student Clubs (GDSC), SathyabamaGoogle’s university developer community, now GDG on Campus. Ran events and spoke at the weekly online sessions.Technical team
  • DevFest ChennaiGoogle’s annual developer festival, run by Google Developer Groups (GDG) Chennai.Attendee

Technical projects

from college
Computer vision · Smart cities

AI Traffic Management System

A traffic signal that gives busier roads more green time and clears the way for ambulances. Python and OpenCV count vehicles in camera video, and an FFT listens for sirens. Built for a competition inspired by Malaysia's smart-city push and presented at Universiti Sains Islam Malaysia, Kuala Lumpur (Jan to Apr 2025, team of 4). I rebuilt it as working code you can try.

My part · I designed the signal logic, researched the problem and pitched it.

  • Python
  • OpenCV
  • NumPy
  • FastAPI
Assistive technology · Government-funded (DST)

Smart Blind Stick

A government-funded (DST, ₹22 lakh) assistive device for visually impaired users. It combines GPS and indoor positioning (IPS) with obstacle detection and emergency alerts. Still in development.

My part · Helped build the stick, did research and presented the project at college.

  • GPS
  • Indoor positioning (IPS)
  • Obstacle detection
  • Emergency alerts

Entrepreneurship · Field note

I expected a no from the dhobi shop

Wrinkl never reached a trial. The conversation that came closest taught me the most.

Wrinkl ran from January to October 2025. I owned the research, the pricing, the ordering prototype and a WhatsApp bot.

When I went to talk to dhobi shops about a trial, I expected a no. I was a stranger asking a working shop to change how it took orders. One owner agreed. She was glad to help someone starting out in her line of work, and she was far more open than I had prepared for.

I had prepared for objections. I had not prepared for kindness. It changed how I think about the supply side. The people who run these shops are partners, not obstacles to route around, and a plain, honest ask got a better reception than I expected.

The trial never started. When the team's priorities shifted, I set Wrinkl aside before it could run. That is why this site makes no claim about orders, customers or revenue.

What I keep from it is the order of work. I built the ordering prototype before my first real conversation with a shop. Next time the conversation comes first.

Product Thinking · Essay

A good idea is not a plan

The mistake I made at the start of Wrinkl, and the one most first-time founders make.

When I started Wrinkl I made the mistake most people make. I thought it would be easy because the idea was good. The service was not on the market, and nobody was close to building it.

I read an empty market as a sign that the idea was strong. It only tells you that no one has done it yet. It does not tell you why, or whether people want it.

Now I ask what makes an idea hard before I ask what makes it good, and I look for the cheapest way to test that part first.

Product Management · Field note

One finding, three readers

How I write the same research for a PM, an engineer and a ticket.

I write the same finding differently for each reader. For my PM I keep it short and lead with the recommendation. For an engineer I am exact about how things work. In a ticket I remove hedging so nobody has to guess what has been decided.

I also keep solutioning out of reference documents and tickets. A reference document says what is true. A recommendation belongs in the message to stakeholders, where it can be argued with.

It took me a while to see that these are not three styles. They are one habit: ask what the reader has to do next, and write for that.