Add post-mortem process to hiring documentation

[fraserhopper]

Added a section on post-mortems to the hiring process documentation, detailing the process, pre-work, and follow-up actions.

[github-actions]

Deploy preview

Status	Details	Updated (UTC)
🟢 Ready	View preview	Apr 15, 2026 09:31AM

[github-actions]

Vale prose linter → found 23 errors, 57 warnings, 0 suggestions in your markdown

Full report → Copy the linter results into an LLM to batch-fix issues.

Linter being weird? Update the rules!

contents/handbook/people/hiring-process/index.mdx — 23 errors, 57 warnings, 0 suggestions

Line	Severity	Message	Rule
123:99	warning	'misclassification' is a possible misspelling.	PostHogBase.Spelling
125:4	warning	'Hiring Process' heading should be in sentence case, and product names should be capitalized.	PostHogBase.SentenceCase
129:460	warning	Use 'PostHog' instead of 'posthog'.	Vale.Terms
143:5	warning	'The role of the Hiring Manager' heading should be in sentence case, and product names should be capitalized.	PostHogBase.SentenceCase
156:70	warning	'Ashby' is a possible misspelling.	PostHogBase.Spelling
165:60	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
169:75	warning	'Ashby' is a possible misspelling.	PostHogBase.Spelling
173:1	warning	'Ashby' is a possible misspelling.	PostHogBase.Spelling
173:157	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
173:212	warning	'Ashby' is a possible misspelling.	PostHogBase.Spelling
173:233	warning	'Wellfound' is a possible misspelling.	PostHogBase.Spelling
175:8	warning	'Combinator' is a possible misspelling.	PostHogBase.Spelling
177:1	warning	'Ashby' is a possible misspelling.	PostHogBase.Spelling
181:6	warning	'Behance' is a possible misspelling.	PostHogBase.Spelling
182:6	warning	'Dribbble' is a possible misspelling.	PostHogBase.Spelling
186:28	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
204:76	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
239:190	warning	'Ashby' is a possible misspelling.	PostHogBase.Spelling
241:91	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
245:569	warning	Use descriptive link text instead of '[this article]'.	PostHogBase.DescriptiveLinkText
249:200	warning	'Ashby' is a possible misspelling.	PostHogBase.Spelling
270:39	warning	'Ashby' is a possible misspelling.	PostHogBase.Spelling
270:123	warning	'Ashby' is a possible misspelling.	PostHogBase.Spelling
270:319	warning	'Coua' is a possible misspelling.	PostHogBase.Spelling
272:33	warning	'comms' is a possible misspelling.	PostHogBase.Spelling
272:42	warning	'Ashby' is a possible misspelling.	PostHogBase.Spelling
272:131	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
274:1	warning	'Ashby' is a possible misspelling.	PostHogBase.Spelling
276:138	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
276:201	warning	'Ashby' is a possible misspelling.	PostHogBase.Spelling
277:183	warning	'Ashby' is a possible misspelling.	PostHogBase.Spelling
278:42	warning	'Ashby' is a possible misspelling.	PostHogBase.Spelling
280:213	warning	Use 'PostHog' instead of 'posthog'.	Vale.Terms
280:288	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
284:190	warning	'Ashby' is a possible misspelling.	PostHogBase.Spelling
286:5	warning	'Booking interviews through Ashby' heading should be in sentence case, and product names should be capitalized.	PostHogBase.SentenceCase
286:32	warning	'Ashby' is a possible misspelling.	PostHogBase.Spelling
288:31	warning	'Ashby' is a possible misspelling.	PostHogBase.Spelling
292:270	warning	Use American English. Use 'traveling' instead of 'travelling'.	PostHogBase.AmericanEnglish
300:139	warning	'Ashby' is a possible misspelling.	PostHogBase.Spelling
304:361	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
318:16	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
329:5	warning	'1. Culture interview with Talent' heading should be in sentence case, and product names should be capitalized.	PostHogBase.SentenceCase
331:192	warning	'Ashby' is a possible misspelling.	PostHogBase.Spelling
350:121	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
350:185	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
354:5	warning	'3. Small Team interview with an Exec Team member' heading should be in sentence case, and product names should be capitalized.	PostHogBase.SentenceCase
360:5	warning	'4. PostHog SuperDay' heading should be in sentence case, and product names should be capitalized.	PostHogBase.SentenceCase
364:71	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
364:170	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
366:328	warning	Use the Oxford comma before 'and' or 'or' in a list of three or more items.	PostHogBase.OxfordComma
370:136	warning	'superday' is a possible misspelling.	PostHogBase.Spelling
382:25	warning	'Blitzscale' is a possible misspelling.	PostHogBase.Spelling
383:69	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
383:174	warning	'Ashby' is a possible misspelling.	PostHogBase.Spelling
383:340	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
384:256	warning	'Ashby' is a possible misspelling.	PostHogBase.Spelling
384:283	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
385:24	warning	'Ashby' is a possible misspelling.	PostHogBase.Spelling
385:144	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
385:413	warning	'Ashby' is a possible misspelling.	PostHogBase.Spelling
387:13	warning	Use 'ClickHouse' instead of 'Clickhouse'.	Vale.Terms
388:180	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
390:222	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
396:55	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
398:73	warning	'Ashby' is a possible misspelling.	PostHogBase.Spelling
413:138	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
413:156	warning	Use the Oxford comma before 'and' or 'or' in a list of three or more items.	PostHogBase.OxfordComma
419:5	warning	'How Ashby works for interviewers' heading should be in sentence case, and product names should be capitalized.	PostHogBase.SentenceCase
419:9	warning	'Ashby' is a possible misspelling.	PostHogBase.Spelling
421:8	warning	'Ashby' is a possible misspelling.	PostHogBase.Spelling
450:136	warning	Use the Oxford comma before 'and' or 'or' in a list of three or more items.	PostHogBase.OxfordComma
450:177	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
456:5	warning	'The Process' heading should be in sentence case, and product names should be capitalized.	PostHogBase.SentenceCase
460:109	warning	'blitzscale' is a possible misspelling.	PostHogBase.Spelling
462:234	warning	'Blitzscale' is a possible misspelling.	PostHogBase.Spelling
473:6	warning	'The Post-mortem call' heading should be in sentence case, and product names should be capitalized.	PostHogBase.SentenceCase
477:35	warning	'discusssing' is a possible misspelling.	PostHogBase.Spelling
484:6	warning	'post post-mortem call' heading should be in sentence case, and product names should be capitalized.	PostHogBase.SentenceCase
486:116	warning	Use 'PostHog' instead of 'posthog'.	Vale.Terms

[juliaedo]

The only thought I have is whether it's worth also discussing how this person was (1) staffed and (2) onboarded (in case it's not only a "hiring issue" but we simply didn't staff them against a problem they could be productive on from day 1, or if there were any issues or signals during onboarding)

[zbynek-hedgehog]

lgtm! 🙏 I can see us iterating on it once we start putting it into practice

[fraserhopper]

The only thought I have is whether it's worth also discussing how this person was (1) staffed and (2) onboarded (in case it's not only a "hiring issue" but we simply didn't staff them against a problem they could be productive on from day 1, or if there were any issues or signals during onboarding)

Hmm, I honestly haven't ever seen us let somebody go because of this (1) staffing issue, we just tend to move good people into other teams if the problem they are working on isn't making them productive.

Happy to add a look at onboarding into the process but I really think the point of this post-mortem is to look and see if we can keep improving our talent process. We are seeing enough people responding to the direct feedback process, 30/60 day check-in feedback that we know that works pretty well. Again, this is not to relitigate the original hiring process, but to try and improve it all going forward.