Personal README · always in progress

I like turning unclear problems into useful things.

I’m Dipak—a product manager who likes getting close to the making, and an independent builder who learns by shipping small experiments.

I’m most at home in the messy middle: finding the useful signal, making the trade-offs visible, and shaping a practical way forward.

Dipak Builds is my public workbench for documenting the products, questions, lessons, and occasional wrong turns that shape how I think.

Product manager who likes getting close to the makingIndependent builder learning by shipping small experimentsCurious generalist looking for the system beneath the symptom

Build log · chapters 01–05

How did I get here?

The useful version of a career story is not a list of titles. It is a record of what each chapter taught you to notice.

01

Build log chapter

Discovering product as a way of seeing

Product work taught me to move between users, business, design, and technology without treating any one perspective as the whole truth.

What changed: I stopped seeing features as the unit of progress and started paying closer attention to the problem a feature was meant to change.

Open the lesson from this chapter

Good product decisions begin with a shared understanding of reality, not a beautifully formatted requirements document.

02

Build log chapter

Learning through user-facing experiences

Working on educational and user-facing products made feedback immediate. People rarely experience a product the way its creators explain it.

What changed: I became more interested in comprehension, motivation, and the small moments that help someone keep moving.

Open the lesson from this chapter

A useful experience respects the distance between what a person intends to do and what the product asks them to understand first.

03

Build log chapter

From features to systems

Platform products and operational workflows introduced more stakeholders, dependencies, edge cases, and consequences.

What changed: I learned to look beyond the visible interface toward incentives, handoffs, constraints, and the systems carrying the work.

Open the lesson from this chapter

The hard part of many product problems is not the screen. It is helping several moving parts behave like one coherent system.

04

Build log chapter

Building with AI, not simply adding it

AI-powered products and evaluation systems made product judgment feel newly important. Capability alone does not create trust, usefulness, or a good decision.

What changed: I began thinking more carefully about uncertainty, evaluation, human oversight, and where intelligence should sit inside a workflow.

Open the lesson from this chapter

The interesting question is rarely whether AI can do something. It is how the product helps people understand, guide, and rely on what it does.

05

Build log chapter

Making my own small bets

Building and deploying independent experiments changed my relationship with ideas. A working version has a way of replacing vague confidence with specific learning.

What changed: I moved from only managing the process of building to regularly making, testing, documenting, and sharing things myself.

Open the lesson from this chapter

Small shipped experiments are not smaller ambitions. They are a practical way to earn better questions.

Open questions · no final answers yet

What excites me?

These are the questions that keep opening new tabs in my head. I am exploring them through products, writing, conversations, and experiments.

01

What happens when software can understand intent?

Interfaces may become less about navigating commands and more about expressing goals, negotiating trade-offs, and reviewing judgment.

See the experiments
02

What should humans delegate to AI—and what should remain human?

The boundary is not only about capability. It is also about agency, accountability, taste, trust, and the kind of work we want to keep practicing.

Read the field notes
03

Can one thoughtful person now build what once required a team?

Small teams and independent builders can move differently when tools compress the distance between an idea and a working product.

Explore the builds
04

How can knowledge become easier to act on?

I am interested in the step after collecting information: turning expertise, research, and learning into useful decisions, tools, and systems.

Browse resources
05

How does the product manager’s role change when making gets faster?

When prototypes and code become cheaper, problem framing, judgment, clarity, and the ability to create momentum matter even more.

See how I think
06

What makes learning feel alive rather than assigned?

Education becomes more powerful when curiosity, feedback, practice, and real consequences meet in the same experience.

Watch and learn

Offline mode · still curious

Beyond work

Products are one way I make sense of the world. They are not the only one.

Open road

Weekend motorcycle rides

A good ride creates enough distance from a problem for the important part to become obvious.

New coordinates

Travel and unfamiliar places

I enjoy noticing how different places organize everyday life—and how quickly my assumptions stop being universal.

Reset ritual

Fitness and swimming

Movement is the simplest way I know to get out of my head and return with better energy.

Story mode

Movies, stories, and unrelated learning

I like subjects that have nothing to do with my current work. They often find their way back into it anyway.

Choose your path · the workbench is open

Explore my work

Different visitors arrive with different questions. Pick the path that answers yours.

See what I build

Projects

Products, applications, and experiments at different stages of becoming real.

See what I build

Read what I think

Articles

Ideas, observations, frameworks, and lessons still being shaped.

Read what I think

Recruiter shortcut · the 60-second version

If you’re hiring

The most useful evaluation is still the work itself. The case studies show how I frame problems, make decisions, and learn from the outcome.

I am a product manager and builder who enjoys working on ambiguous product problems, connecting user needs with business and technical constraints, and helping teams turn complexity into useful systems.

Experience themes

  • Product discovery and strategy for unclear, multi-stakeholder problems
  • User-facing learning experiences, platform products, and operational systems
  • AI-powered product experiences and evaluation thinking
  • Cross-functional product execution from framing through delivery
  • Independent prototyping, building, deployment, and documentation
Discuss a relevant opportunity

Open channel · one unfinished idea is enough

The best conversations often begin before the answer is obvious.

If you are building an interesting product, working through a difficult problem, exploring a collaboration, or found something here useful, I would be glad to hear from you.

Start a conversation