Gokul Rajaram on product development, hiring leaders, and angel investing

Executive overview

Most founders become a bottleneck by dictating tactics instead of presenting problems — this turns engineering teams into feature factories. Gokul Rajaram, drawing on Google, Square, and DoorDash, shares frameworks for structuring product development, hiring PMs and leaders, and building an angel investing practice.

Great careers are built on serendipity, not linear promotion — but serendipity must be actively cultivated.

Picking where to work

• Join a company that can become the number one player in its segment, not the most senior role at a tier-two player.
• For new joiners: target 300-500 person companies that have product-market-channel fit and are transitioning from product to platform.
• Founders must be authentic to their mission — those constantly talking about revenue rarely build large companies.
• 40-50% of new customers should come from organic channels; over-reliance on paid is a structural fragility.
• Know what type of customer energises you — small businesses, consumers, or enterprises — not just what problem you're solving.

Product development process by stage

• Very early stage: weekly plans only; a simple spreadsheet beats complex tooling.
• Post-Series A: add quarterly goals that weekly tasks work back from; annual planning comes later still.
• The atomic team — engineers, PM, designer, analyst — meets daily and reviews tasks weekly.
• Product strategy becomes a separate document from company strategy around the 25-person mark.
• The biggest pitfall: founders become too tactical, dictate solutions, and disempower teams. Engineers ship features without knowing impact — the feature factory trap.

When and how to hire your first PM

• Hire at 8-10 engineers, but only if the founder can no longer care for and feed the engineering team full-time.
• The best first PM is almost always an internal hire — an engineer, analyst, or designer who already has the team's trust.
• An external PM risks organ rejection: the body can reject a new process if it doesn't match the culture.
• Watch for the new PM retreating into their old role (engineer/designer instincts); coach them toward customers and problem-framing.
• If engineers are already taking problems, proposing solutions, and running tests autonomously, you may not need a PM yet.
• Infrastructure and developer-facing products (e.g. Stripe) need far fewer PMs than consumer products.

Structuring and scaling PM teams

• Once you have 3-4 PMs, they should report to a dedicated product leader — not a GM managing multiple functions.
• A bad PM can neutralise the work of 10 engineers; hiring well here has outsized leverage.
• The functional product leader's job: mentoring, culture-building, attracting talent, and sharing best practices across ICs.
• GM models can work early, but transition to functional reporting as the PM team grows.

Hiring leaders: the lieutenant playbook

• Identify the 3-4 best-in-class companies for the function you're hiring (not your competitors — companies serving the same customer type).
• Don't recruit the head of that function. Recruit their lieutenant — the up-and-coming number two.
• Build an org chart of those companies via LinkedIn; ask contacts to fill in gaps.
• Avoid giving senior titles too early — general counsel, VP Engineering, or VP title at a 25-person company locks you in and creates upgrade problems later.
• Prefer "lead" and "head of" over director/VP; they describe scope without creating title inflation.
• Delay director and VP titles as long as possible; they generate the most contention and retention-by-title problems.

Recruiting process

• Founders at early-stage companies should spend roughly 2 hours a day on hiring: 1 hour on outreach (low-mental-load, schedulable), 1 hour on meetings (2 x 30-minute conversations).
• Set up the process and messaging first — direction matters more than speed.
• Always be meeting great people even when not actively hiring; warm relationships create future optionality.

Angel investing: getting started

• Be founder-centric over market-centric — great founders create or pivot into markets; markets alone don't create great founders.
• Sins of omission (not investing) cost more than sins of commission — you lose the relationship, not just the return.
• Invest in founders across their first and second companies; unsuccessful first attempts often precede successful second ones.
• Prefer two-person founding teams with complementary skills (builder + seller); solo founders are a red flag.
• Vet authenticity: the founder should have deeply experienced the problem, not read about it on TechCrunch.
• Look for evidence they can attract talent before funding.

Building deal flow and an investing brand

• Three sources of deal flow: (1) build a public brand through writing, (2) tell your network you're investing and reinforce it constantly, (3) get allocation from VCs leading rounds.
• Your differentiation must be clear — oversubscribed rounds don't need your capital unless you add something unique.
• When someone Googles you, the first result should be something you wrote or said, not your LinkedIn profile.
• Your brand can be domain-specific (payments, risk, crypto) — niche expertise is valuable and searchable.
• Timebox investing to 2-3 hours per day maximum; if it exceeds that, become a full-time investor.