Product for Engineers

What we’ve learned about building AI-powered features

How to choose the right features, implement them the right way, and make them better (for real)

Sep 2 • 

Ian Vanagas

49

3

August 2025

Glue teams vs back-office teams

Don't get this wrong

Aug 19 • 

Michael Matloka

44

2

Failure modes for engineering team leads

...and how to avoid them.

Aug 4 • 

Lior Neu-ner

95

2

July 2025

40 things we’ve learned about marketing for developers

Lessons learned about brand, content, paid ads, SEO, LLMs, and more

Jul 21 • 

Ian Vanagas

57

6

Finding a job as a product engineer

Tactical advice for ambitious developers

Jul 15 • 

Andy Vandervell

60

3

June 2025

You're doing quarterly planning wrong

Don't make our mistakes

Jun 30 • 

Ian Vanagas

45

4

An engineer's guide to vibe design (with prompts)

Engineers move fast. Your design should too.

Jun 16 • 

Lior Neu-ner

113

6

Job interview questions engineers should ask (but don't)

...or how to join the right startup and stand out from the crowd

Jun 2 • 

James Hawkins

 and 

Andy Vandervell

100

May 2025

The hidden benefits of being an open-source startup

How being open source helps us win

May 15 • 

Ian Vanagas

54

6

How to not break up with your cofounder

In this issue of Product for Engineers, James Hawkins shares how he and PostHog cofounder Tim Glaser keep their relationship healthy.

May 4 • 

James Hawkins

52

2

April 2025

What nobody tells developers about documentation

Developers have a lot of misconceptions about docs:

Apr 17 • 

Ian Vanagas

73

5

43 things we've learned about hiring at PostHog

In the last 12 months, we've received 30,000 applications, interviewed 2,000 candidates, and hired 65 people. We learned some stuff.

Apr 10 • 

Charles Cook

91

4