Blog post on AI-native hiring practices for Ops teams#16884
Open
fraserhopper wants to merge 14 commits into
Open
Blog post on AI-native hiring practices for Ops teams#16884fraserhopper wants to merge 14 commits into
fraserhopper wants to merge 14 commits into
Conversation
Ok this is my first blog, so go easy. I still need to upload an image for this but wanted to get some feedback on this first, as I prob need to re-do some parts. Alternatively, we just stick this in the shredder immediately.
Contributor
Deploy preview
Push a fix or re-run the workflow to try again. Common culprits
|
…-ai-native-and-heress-why.md
Contributor
|
Vale prose linter → found 5 errors, 29 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 |
|---|---|---|---|
| 22:92 | warning | Use 'AI' instead of 'ai'. | Vale.Terms |
| 23:34 | warning | Use 'AI' instead of 'ai'. | Vale.Terms |
| 23:61 | warning | Use 'AI' instead of 'ai'. | Vale.Terms |
| 23:71 | warning | 'jd' is a possible misspelling. | PostHogBase.Spelling |
| 23:94 | warning | Use 'AI' instead of 'ai'. | Vale.Terms |
| 23:171 | warning | Use 'AI' instead of 'ai'. | Vale.Terms |
| 26:115 | warning | Capitalize 'Workflows' for PostHog's product. Use 'workflows' for the general industry concept. | PostHogBase.ProductNames |
| 32:331 | 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 |
| 34:142 | warning | Use 'AI' instead of 'ai'. | Vale.Terms |
| 36:126 | warning | Use 'AI' instead of 'ai'. | Vale.Terms |
| 45:10 | warning | 'Sourcer' is a possible misspelling. | PostHogBase.Spelling |
| 46:17 | 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 |
| 52:5 | warning | Use 'AI' instead of 'ai'. | Vale.Terms |
| 52:273 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 52:290 | 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 |
| 54:1 | warning | 'Shoutout' is a possible misspelling. | PostHogBase.Spelling |
| 60:193 | warning | Use the Oxford comma before 'and' or 'or' in a list of three or more items. | PostHogBase.OxfordComma |
| 60:260 | warning | 'Ashby' is a possible misspelling. | PostHogBase.Spelling |
| 64:1 | warning | 'Shoutout' is a possible misspelling. | PostHogBase.Spelling |
| 66:23 | 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 |
| 68:120 | warning | 'financials' is a possible misspelling. | PostHogBase.Spelling |
| 68:260 | warning | 'financials' is a possible misspelling. | PostHogBase.Spelling |
| 70:414 | warning | 'andand' is a possible misspelling. | PostHogBase.Spelling |
| 72:1 | warning | 'Shoutout' is a possible misspelling. | PostHogBase.Spelling |
| 74:4 | warning | 'Have you really solved hiring forever, spoiler alert: no' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 78:67 | warning | 'signoff' is a possible misspelling. | PostHogBase.Spelling |
| 79:52 | warning | Use American English. Use 'judgment' instead of 'judgement'. | PostHogBase.AmericanEnglish |
| 81:72 | warning | 'claude' is a possible misspelling. | PostHogBase.Spelling |
| 81:135 | warning | Capitalize 'Workflows' for PostHog's product. Use 'workflows' for the general industry concept. | PostHogBase.ProductNames |
| 81:149 | warning | Use American English. Use 'artifacts' instead of 'artefacts'. | PostHogBase.AmericanEnglish |
| 97:459 | warning | 'chatgpt' is a possible misspelling. | PostHogBase.Spelling |
| 103:162 | warning | Use 'AI' instead of 'ai'. | Vale.Terms |
| 103:347 | 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 |
| 105:46 | warning | Use 'AI' instead of 'ai'. | Vale.Terms |
ivanagas
reviewed
May 19, 2026
Contributor
ivanagas
left a comment
ivanagas
left a comment
There was a problem hiding this comment.
I think the piece overall is looking good (content is good), mostly made some broad suggestions about framing.
I will do another line edit pass once you're ready.
Comment on lines
+22
to
+24
| In Q2 2026, we finally caved and admitted what we knew for a while. That AI-native candidate are the preferred candidate when it comes to hiring our Ops & Finance roles. Whilst we’d been very pro AI-native candidates for a long time in both our technical & non-technical roles, we finally hit the point where it’s no longer a toss up between seniority & slope, it was all-in on the AI-pilled hiring plan. | ||
|
|
||
| AI-native sounds lovely, and it also sounds like a buzzword, so this is meant to show you what we mean by AI-native and how I am implementing it into Ops & Finance. We’ll also cover the reality that it’s not perfect. |
Contributor
There was a problem hiding this comment.
I think we should focus more on the AI-native vs experience bit here. Just start forcefully with that and we can give a lot of the context (like ops and finance) later.
Ops & Finance is the example we will use throughout, but the "AI-native vs experience" is the main bit.
| 3. Years of experience do still matter and often correlate to stronger candidates. | ||
| 4. Years of experience are now used as a tiebreaker between ai-native candidates rather than a moat | ||
| 5. The person still needs to actually be an [insert job] they can’t just be an ai junkie who fancies being an accounting manager | ||
| 6. This isn’t bullet-proof, there are still downsides |
Contributor
There was a problem hiding this comment.
This isn't really a "why", it's more a "what"
Could we just roll some of the important points into the intro? We already include "Years of experience do still matter and often correlate to stronger candidates." and could add "Years of experience are now used as a tiebreaker between ai-native candidates rather than a moat" too it.
These two might be good to include (but the below section also covers them well)
- AI-native means a team member treat agents and LLMs as their default. This is where they cook.
- Every role we have in Ops & Finance now has to be using AI and automation in their daily workflows
I think "The person still needs to actually be an [insert job] they can’t just be an ai junkie who fancies being an accounting manager" could go below.
Also, we can probably just remove "this isn't bullet-proof" as we don't need to hedge without context.
Comment on lines
+106
to
+108
| ## Where is this all heading? | ||
|
|
||
| The practical result: PostHog's hiring plan for the next 2-3 years is smaller than it would have been a year ago. Not because we're growing slower. Because each ai-native hire is cracked enough that we need fewer of them. What we don't yet know is what people do with the time. The optimistic version is the 3 hours a day you save get reinvested — into building, into learning the fundamentals, into finally writing your own python. the pessimistic version is Parkinson's law eats it and we all just have more meetings. |
Contributor
There was a problem hiding this comment.
This is more the "why hire AI-native", do we have any stats on how much more productive they are? Are we ahead of schedule on the roadmap or something?
Contributor
Author
There was a problem hiding this comment.
added a little bit of ops team composition size within the business
|
|
||
| A traditional excellent Ops manager is a hero. They are everywhere, they are the glue. Lots of people don’t know why they are great but they know they are important. This person is successful because they care and they are reliable and they can go really wide on tasks but most of it is manual, they think of everything that needs to go on an onboarding checklist, tags the right people and chases them up continually until it’s done. Everybody loves this person. However, things fall through the cracks and they get blocked whilst waiting for others. | ||
|
|
||
| The ai-native ops manager spins up a slack bot that pushes tasks to owners, nudges them when something's due, and escalates when it's overdue. They build an offer-letter generator for the talent team that hooks into employment contract generation across the 30+ countries posthog hires in — fully automated, end to end. |
Contributor
There was a problem hiding this comment.
We can see how this looks, but maybe a list will be better (and copy that format across each role)
Co-authored-by: Ian Vanagas <34755028+ivanagas@users.noreply.github.com>
Co-authored-by: Ian Vanagas <34755028+ivanagas@users.noreply.github.com>
Co-authored-by: Ian Vanagas <34755028+ivanagas@users.noreply.github.com>
Co-authored-by: Ian Vanagas <34755028+ivanagas@users.noreply.github.com>
Co-authored-by: Ian Vanagas <34755028+ivanagas@users.noreply.github.com>
Co-authored-by: Ian Vanagas <34755028+ivanagas@users.noreply.github.com>
Co-authored-by: Ian Vanagas <34755028+ivanagas@users.noreply.github.com>
fraserhopper
commented
May 19, 2026
Removed unnecessary bullet points and clarified the definition of AI-native candidates in hiring practices.
Added insights on the characteristics and impact of AI-native hires on company operations and hiring plans.
Co-authored-by: Ian Vanagas <34755028+ivanagas@users.noreply.github.com>
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.
Ok this is my first blog, so go easy.
I still need to upload an image for this but wanted to get some feedback on this first, as I prob need to re-do some parts.
Alternatively, we just stick this in the shredder immediately.