Update index.mdx#17021
Open
Doobles-PostHog wants to merge 2 commits into
Open
Conversation
Updated line 332 to be more clear that during the Talent Interview (former Culture Interview) the candidate should not expect the a 'HR' conversation strictly about culture and logistics. Feedback from candidates was that they did not expect to go into any (technical) detail and they pointed towards the handbook. I spoke with the team and the 'Talent Interview' aligns better with what we actually do. It will also eliminate any confusion between the interview with the recruiter and that with Blitzscale
Contributor
Deploy preview
|
Contributor
|
Vale prose linter → found 23 errors, 59 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!
|
| 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 |
| 242:190 | warning | 'Ashby' is a possible misspelling. | PostHogBase.Spelling |
| 244: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 |
| 248:569 | warning | Use descriptive link text instead of '[this article]'. | PostHogBase.DescriptiveLinkText |
| 252:79 | warning | 'Ashby' is a possible misspelling. | PostHogBase.Spelling |
| 252:369 | warning | 'Ashby' is a possible misspelling. | PostHogBase.Spelling |
| 273:39 | warning | 'Ashby' is a possible misspelling. | PostHogBase.Spelling |
| 273:123 | warning | 'Ashby' is a possible misspelling. | PostHogBase.Spelling |
| 273:319 | warning | 'Coua' is a possible misspelling. | PostHogBase.Spelling |
| 275:33 | warning | 'comms' is a possible misspelling. | PostHogBase.Spelling |
| 275:42 | warning | 'Ashby' is a possible misspelling. | PostHogBase.Spelling |
| 275: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 |
| 277:1 | warning | 'Ashby' is a possible misspelling. | PostHogBase.Spelling |
| 279: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 |
| 279:201 | warning | 'Ashby' is a possible misspelling. | PostHogBase.Spelling |
| 280:183 | warning | 'Ashby' is a possible misspelling. | PostHogBase.Spelling |
| 281:42 | warning | 'Ashby' is a possible misspelling. | PostHogBase.Spelling |
| 283:213 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 283: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 |
| 287:190 | warning | 'Ashby' is a possible misspelling. | PostHogBase.Spelling |
| 289:5 | warning | 'Booking interviews through Ashby' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 289:32 | warning | 'Ashby' is a possible misspelling. | PostHogBase.Spelling |
| 291:31 | warning | 'Ashby' is a possible misspelling. | PostHogBase.Spelling |
| 295:270 | warning | Use American English. Use 'traveling' instead of 'travelling'. | PostHogBase.AmericanEnglish |
| 303:139 | warning | 'Ashby' is a possible misspelling. | PostHogBase.Spelling |
| 307: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 |
| 321: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 |
| 332:5 | warning | '1. Talent interview with Talent' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 334:114 | warning | 'expereince' is a possible misspelling. | PostHogBase.Spelling |
| 334:231 | warning | 'Ashby' is a possible misspelling. | PostHogBase.Spelling |
| 353: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 |
| 353: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 |
| 357: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 |
| 363:5 | warning | '4. PostHog SuperDay' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 367: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 |
| 367: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 |
| 369:328 | warning | Use the Oxford comma before 'and' or 'or' in a list of three or more items. | PostHogBase.OxfordComma |
| 373:136 | warning | 'superday' is a possible misspelling. | PostHogBase.Spelling |
| 385:25 | warning | 'Blitzscale' is a possible misspelling. | PostHogBase.Spelling |
| 386: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 |
| 386:174 | warning | 'Ashby' is a possible misspelling. | PostHogBase.Spelling |
| 386: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 |
| 387:256 | warning | 'Ashby' is a possible misspelling. | PostHogBase.Spelling |
| 387: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 |
| 388:24 | warning | 'Ashby' is a possible misspelling. | PostHogBase.Spelling |
| 388: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 |
| 388:413 | warning | 'Ashby' is a possible misspelling. | PostHogBase.Spelling |
| 390:13 | warning | Use 'ClickHouse' instead of 'Clickhouse'. | Vale.Terms |
| 391: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 |
| 393: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 |
| 399: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 |
| 401:73 | warning | 'Ashby' is a possible misspelling. | PostHogBase.Spelling |
| 416: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 |
| 416:156 | warning | Use the Oxford comma before 'and' or 'or' in a list of three or more items. | PostHogBase.OxfordComma |
| 422:5 | warning | 'How Ashby works for interviewers' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 422:9 | warning | 'Ashby' is a possible misspelling. | PostHogBase.Spelling |
| 424:8 | warning | 'Ashby' is a possible misspelling. | PostHogBase.Spelling |
| 453:136 | warning | Use the Oxford comma before 'and' or 'or' in a list of three or more items. | PostHogBase.OxfordComma |
| 453: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 |
| 459:5 | warning | 'The Process' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 463:109 | warning | 'blitzscale' is a possible misspelling. | PostHogBase.Spelling |
| 465:234 | warning | 'Blitzscale' is a possible misspelling. | PostHogBase.Spelling |
| 476:6 | warning | 'The Post-mortem call' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 480:35 | warning | 'discusssing' is a possible misspelling. | PostHogBase.Spelling |
| 487:6 | warning | 'post post-mortem call' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 489:116 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
couaphang
approved these changes
May 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated line 332 onwards to be more clear that during the Talent Interview (former Culture Interview) the candidate should not expect the a 'HR' conversation strictly about culture and logistics. Feedback from candidates was that they did not expect to go into any (technical) detail and they pointed towards the handbook. I spoke with the team and the 'Talent Interview' aligns better with what we actually do.
It will also eliminate any confusion between the interview with the recruiter and that with Blitzscale.
Changes
Please describe.
Add screenshots or screen recordings for visual / UI-focused changes.
Checklist
vercel.json