Gokul Rajaram on Product and Hiring

Source: Lenny’s Podcast Speaker: Gokul Rajaram Source URL: https://www.lennysnewsletter.com/p/gokul-rajaram

Key ideas

Join winners: working at the #1 company in a space (not necessarily the top role there) provides better learning, brand, and talent network than a senior title at a tier-two company. The brand halo from winners compounds.
Hire leaders from the lieutenants: when hiring a function leader, identify the best-in-class company for that function in a similar market, build their org chart on LinkedIn, and recruit the second-tier manager — not the head.
First PM from within: the best first PM is an engineer, analyst, or designer already at the company. Cultural fit and trust matter more than PM credentials in the transition.
Delay VP/Director titles: these titles create the most contention and retention-by-title behaviour. Prefer “head of” and “lead” for as long as possible. Square’s example: no director or VP titles produced zero title-driven disgruntlement.
Founder-centrism in investing: invest in founders, not markets. Great founders create or pivot to new markets; the biggest mistakes are sins of omission (not backing someone you know and respect).

Career: serendipity and openness

Gokul’s origin story: Cisco rescinded his offer in 2001; he joined Google as his second choice. Working on syndication, he wandered into a room of engineers building what became Google AdSense. He offered to be their PM nights and weekends. Within three months, the product grew enough for his manager to move him over full-time.

The lesson: deep skills in your primary role + active curiosity about what else is happening at the company. Great careers are not built by grinding promotions in a linear path; they are built by knowing people and waiting for serendipity, then seizing it.

Serendipity also compounds through informal helping: Gokul advised a startup (acquired by Square) without equity. The founder recommended him to Jack Dorsey. That informal helping led to the Square inbound. Paying it forward builds “a reservoir of goodwill that comes back in ways you don’t realise.”

Picking where to work

Three criteria (in order of importance):

Founder authenticity: is the founder solving a problem they genuinely care about, or talking primarily about revenue/wealth? The best founders (Jack Dorsey, Tony Xu, Brian Chesky, Larry Page) treat money as a byproduct, not the goal.
Problem energy: figure out what type of customer you get energy from solving for (small businesses? consumers? enterprises?) rather than optimising for the abstract problem itself. Gokul consistently ended up serving small businesses and individual creators — across AdSense, Square, and DoorDash — because that’s where his energy comes from.
Join winners: work at the #1 company in a space, even at a lower level, rather than being the #1 person at a lesser company. Brand halo, talent network, and learning quality are all higher. Exception: founders you know very well at early-stage companies.

Stage for new entrants: mid-stage companies (~300–500 people, post-PMF, on the path to becoming a platform) offer mentorship, depth of skill-building, and exposure to structured product development that early-stage companies cannot provide.

Product development process by stage

Stage	Planning cadence	Key characteristics
Very early (< 25 people)	Weekly	No separation between company and product strategy; iterate to PMF
Series A–B	Weekly + quarterly	Separate product strategy doc begins to emerge; goals drive sprints
Larger	Annual → quarterly → weekly	Multiple interlocking product strategies; cross-functional docs

The atomic product team: engineers + PM + designer + analyst. Daily standup. Weekly task review. Quarterly goals feed back into weekly sprints.

Common pitfall — feature factory: founder becomes too tactical, tells engineers what to build instead of presenting problems. Team ships features without measuring behaviour change. When a PM joins, they inherit the same dysfunctional dynamic. The correct approach: present the problem (“increase usage from 2× to 5×/week”), let the team brainstorm solutions, choose based on ROI, test.

When and how to hire the first PM

When: when you have ~8–10 engineers and the founder no longer has bandwidth to play PM. Engineers are the most expensive resources in the company; leaving them without clear problem statements and prioritisation is a waste of that investment.

Who: hire from within the team — an engineer, analyst, or designer who already works there. Cultural fit and the pre-existing trust with founders and engineers matter more than formal PM experience.

External PM hires risk “organ rejection” — a process mismatch between the new PM’s training and how the company actually operates.
The right internal candidate already has the PM traits the founder saw: curiosity, customer centricity, communication skills, problem-solving.
Give them 6 months + mentorship. Coach them away from reverting to their original function (engineers gravitate back to building, designers back to designing).

When to wait: when the product team is already operating in an empowered way — taking problem statements, generating options, choosing based on ROI, and measuring behaviour change.

Exception: developer-facing and infrastructure products may never need many PMs. Stripe is the canonical example — small PM-to-engineering ratio because engineers deeply understand the domain.

Team structure and PM reporting

With 1–2 PMs: can report to CEO or a GM.
With 4–5 PMs: should report to a dedicated head of product. Rationale: PMs need a coach and mentor; a GM managing multiple functions cannot do this effectively. The bad PM effect is highly leveraged — one bad PM can derail 10 engineers.

The head of product can report to CTO, CEO, or GM — that structure is less important than ensuring the individual PMs have a functional leader.

Hiring leaders: the lieutenant strategy

When hiring a function leader (e.g., head of marketing), the process:

Find the best-in-class company for that function in your market (not a competitor; a company serving a similar customer type that’s known to be excellent at the function).
Build their org chart on LinkedIn. Ask a contact at the company to fill in gaps.
Target the lieutenant — the person one or two levels below the head. Not the head themselves.

Rationale: lieutenants are available; they are proven operators in the environment you want to replicate; they can grow into your head role as you scale.

Adam Zamos (Square head of people) went further: hired the lieutenant of the lieutenant — the “up and coming” operators who hadn’t yet been promoted to the visible layer.

Title discipline

Strong preference for delaying VP and Director titles as long as possible.

VP and Director titles create the most contention (promotion negotiations, disgruntlement, retention-by-title).
Giving a title early creates an irreversible problem: you cannot later downgrade the title when the company needs a more senior person in that role.
Preferred alternatives: “Head of [function]” and “Lead [function]” — descriptive without creating hierarchy dependencies.

Square example: no VP or Director titles internally. Gokul reports: “I never had a single discussion at Square about what title should be.” Contrast with every other company where promotion cycles focused on director/VP progression.

Angel investing

Founder-centric style: Gokul bets on founders, not markets. Rationale: great founders create markets or pivot to new ones. The biggest mistakes are sins of omission — not backing someone you know and respect because the market seemed small.

What he looks for:

Authentic connection to the problem (experienced it themselves or immersed deeply — not “I read a TechCrunch article about it”).
Two-person founding team with complementary skills (builder + seller / hacker + hustler). Solo founders are possible but higher risk.
Ability to attract talent before having much to offer.

Getting deal flow:

Build an internet brand — publish non-obvious insights in your domain; when people Google you, articles should come up before your LinkedIn.
Tell every investor and operator contact you want to see deals.
Find VC allocations for angels in rounds they lead.

Differentiation question: why should great companies take your money? The best rounds are over-subscribed. You need to know specifically what unique value you add.