Divananda Zikry Fadilla

​I had a great discussion with Muhammad Nur, a veteran QA Engineer with proven experience shipping software in demanding environments. His approach clearly connects the work of quality assurance to product success. ​Two achievements from his background are particularly notable. First, he builds automation that delivers tangible results. At Goto Crypto, he created systems that dramatically reduced the time needed for testing existing features. At DBS, his work identified critical bottlenecks, allowing the product to scale for a major increase in concurrent users. This shows a clear focus on building efficiency and securing performance. ​Second, he is skilled at making sure complex products launch successfully. Working in regulated sectors at DBS and Goto, his comprehensive testing process before a product went live consistently lowered the number of post release bugs. This demonstrates his core understanding that QA’s primary role is to protect revenue and maintain user trust. This is the kind of practical, hard won experience that sets a professional apart. I highly recommend him to any team that needs a QA engineer who measures success in business and product terms.

34

5 Comments

PRD? Yes, but there’s a second step most people are missing. The TDD. Technical design document. When I first started, I would build a PRD. Very detailed through a conversation with ChatGPT or Claude. I always found it best to tell the LLM generally what I was trying to accomplish Then ask it to ask me a single question at a time to get clarity on what I was building. Until it felt like it was close to 95 or 98% clear. Then I would ask it what gaps are there in this and how does this fail? And that would produce me a great product requirement doc. Then I would take that and I’d give it to Claude code and I’d have Claude code start building. But I missed a massively important step… The technical designed document TDD. Not to be confused with test driven development, which is TDD also. I use that as well. This is the document that takes your PRD and breaks it down into all the technical specifications, technical architecture, data architecture, etc. that gives Claude Code clarity on how to build this product. I layer a lot of test driven development strategies into this TDD Then once the TDD is built, I have the planning agent decide what is blocking and what can be built async. Then I do as many loops as possible, asking it where are the gaps and why is this going to fail until it can’t find anything else. Once all this planning is done, I actually begin to build P.S. I am not a developer, so I’m sure this is a no-brainer for some brilliant software engineer. That’s been in the development process for many years. I’m just a hacker trying to figure out how to get great outcomes.

28

3 Comments

𝗚𝗼𝗷𝗲𝗸 𝗘𝘅𝗽𝗮𝗻𝘀𝗶𝗼𝗻 𝗦𝘁𝗿𝗮𝘁𝗲𝗴𝘆 | 𝗣𝗿𝗼𝗱𝘂𝗰𝘁 𝗧𝗿𝗮𝗱𝗲𝟷𝗼𝗳𝗳 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 Dive into a critical product management challenge: Should Gojek prioritize expanding to new cities or deepening services in existing markets? This interview question tests your ability to evaluate growth strategies and effectively allocate resources in a competitive landscape. At NextSprints, seasoned product managers share their approach to tackling such complex trade-offs. Learn how to weigh market penetration against service enhancement, considering factors like user acquisition costs, network effects, and long-term sustainability. How would you approach this strategic decision? Share your thoughts! #ProductStrategy #GrowthDecisions #SuperApp #NextSprints

How I deliver MVPs in just 2 weeks to my clients No meetings. No chaos. Just AI + flow. Here’s the exact system⤵️ 1. Plan fast with ChatGPT (voice mode). Before building, I brainstorm the client idea live. Then generate: → PRD → UI plan → DB schema Use the MoSCoW method to define essentials. Clear scope. No ambiguity. Just build. 2. Skip Figma. Build with Lovable Most devs lose weeks designing. Lovable builds full responsive UIs from text. Connects real data, handles auth, routing. → 70-80% done before I touch any code. 3. If clients want design, I use UX Pilot. It generates hi-fi screens from prompts. Polish in minutes. No pixel-pushing pain. Design optional, not mandatory. 4. Sync to GitHub → open in Cursor. Cursor understands your full repo. It edits, refactors, and writes backend logic. Feels like having a 10x junior dev on standby. 5. Automate backend with MCP + Supabase. MCP lets Cursor talk directly to Supabase. → Auto migrations → Schema sync → Model updates No manual SQL. 80% less backend grind. 6. Run reviews with CodeRabbit Before every push, CodeRabbit checks: ✅ Security ✅ Clean code ✅ Scalable patterns Your AI senior dev who never sleeps. 7. Deploy instantly with Vercel. Auto-sync from GitHub. Global CDN. No config headaches. Client gets live product in week 3. 8. Security checklist before launch. → Enable RLS → Add rate limiting → CAPTCHA → Hide API keys → Validate server-side Fast ≠ careless. Build safe. Result: 30+ MVPs shipped in the past 6 months Scaled my agency to $100k. Clients validate ideas fast without wasting $50k. You don’t need big teams. You need a system: → ChatGPT (planning) → Lovable (UI) → Cursor (AI IDE) → Supabase (backend) → CodeRabbit (reviews) → Vercel (deploy) This is Vibe Coding. Learn it. Apply it. Ship fast.

16

1 Comment

PRD vs FRD — still confusing? Let’s settle this once and for all 🚀 I was recently asked this question (again 😅), so let’s break it down in plain English. 👉 PRD = Product Requirements Document Think of it as the blueprint of dreams. • Focus: What the product should do and why it matters. • Audience: PMs, designers, engineers. • Content: Goals, user problems, must-have features, success criteria. 💡 Example: “The app should let users upload and share photos.” ✨ In short: Vision + Features + “Why are we even building this?” 👉 FRD = Functional Requirements Document Think of it as the manual of reality. • Focus: How the product will actually work. • Audience: Developers, QA/testers. • Content: Detailed functions, system behavior, input/output, data flows, error handling. 💡 Example: “Upload button accepts JPG/PNG up to 10MB, stores in AWS, confirms success in 3 seconds.” ✨ In short: Behavior + Rules + “How does it actually run under the hood?” 🔑 The core difference: • PRD = The What & Why 🎯 • FRD = The How ⚙️ Fun analogy? (With my fav. Example😁) • PRD is like the architect’s sketch of your dream house 🏡 (shows what it’ll look like, why it’s designed that way). • FRD is the builder’s construction manual 🛠️ (exact measurements, wiring, plumbing). ⚡ Quick Reality Check: Some startups merge PRD + FRD into one doc to save time ⏱️. But in larger orgs, keeping them separate avoids chaos and keeps everyone aligned. Now I want to know 👇 👉 Do you (or your team) keep PRD & FRD separate, or do you roll them into one? #ProductManagement #BusinessAnalysis #ProjectManagement #Innovation #Leadership

14

🚀 Product Thinking in Action: PRD on Spotify Listening Behavior 🎧 I’m excited to share my latest Product Requirements Document (PRD) draft, where I deep-dived into a real-world challenge: 👉 Why do new Spotify users often churn within the first 3 months? 👉 How can we increase daily listening time sustainably? 🔍 Based on user surveys, behavioral insights, and product usage data, I identified key friction points and proposed actionable features and success metrics to address them. Some highlights: ✅ Data-backed user segmentation ✅ Journey mapping of new users ✅ Ideas to enhance retention and listening time ✅ Clear PRD structure with goals, scope, and success metrics 💡This project gave me hands-on exposure to translating user insights into product strategy—something I truly enjoy as an aspiring Product Manager. 🔗 Would love feedback from fellow product folks and mentors! (Feel free to check the full PRD draft in the comments or DM) #ProductManagement #Spotify #UserExperience #Retention #ProductDesign #PRD #WomenInProduct #ProductStrategy #ListeningBehavior #ProductThinking

19