A strong fit when
- The work crosses product, frontend, backend, integrations, and operations.
- You need practical tradeoffs, direct communication, and steady delivery.
- Someone needs to own the outcome from an unclear brief through production.
About × Harith Zahid
Product engineering,with the whole operation in view.
I build software, but I’m most useful when the work extends beyond the code—clarifying the product, connecting systems, shipping it, and keeping it running.
I learned product work by owning products.
I’m Harith, a Malaysia-based product engineer and indie maker. Since 2018, I’ve designed, built, launched, sold, supported, and eventually sunset my own software products.
Some found real users and paying customers. Most ran their course. Together, they taught me how product decisions, engineering tradeoffs, customer support, and reliable operations affect one another.
- 2018
- Started shipping products
- 3,500+
- Registered users
- 300+
- Paid customers
- 6+
- Products released
Registration and customer figures are lifetime totals across earlier products, not traction attributed to the newly launched Journeys.
My range is broad.
Software is the centre of it.
- 01Shape
- Clarify the problem, scope the useful version, and make product and UX decisions.
- 02Build
- Create web and mobile applications, backend systems, and AI workflows.
- 03Connect
- Integrate payments, APIs, automations, and the services around the product.
- 04Operate
- Deploy, observe, debug, support, and improve what is running in production.
I do my best work where ownership matters more than a narrow job boundary.
That usually means a lean product team or small agency where the brief is still taking shape and one person needs to keep the whole product in view.
Less suited to
- A deeply specialized role contained within one technical layer.
- Ticket-only implementation with little room for product judgment.