👟 Winning the super week

Simplifying this role, you're working on our documentation content - think of it like a product:

your product = the content of our documentation
your users = speak to everyone that joins slack, as an easy way to do this - just saying you work at PostHog and wondered if they got set up ok in a DM = 70% response rate

Aside from this, follow our values.

We are open source

be transparent
strong written communication is important
asynchronous by default, although some synchronous time is ok

Step on toes

We haven't built our defining feature yet

Everyone codes

Pull requests are greater than issues. Try to get to the root of problems and solve those yourself where you can.

Bias for impact

Make sure you get the work out the door. If you can do it to a standard that it moves the needle, even better.

⚔️ Your quest

You are going to do real life work this week.

Build something

We'd like to validate your technical skill. We'd like to see

you run PostHog locally so that you can...
... build (and document) one app

Improve our docs as you see fit

There are tons of issues in our repos to pick from, just get stuck in.
There are tons of questions in our community slack. Read through them and figure out what you'd improve in the docs.
Our docs for building apps feel weak
0ur docs for existing apps feel weak

Examples

There are too many things to cover, so pick and choose based on the above:

Set up and run PostHog locally
- https://posthog.com/handbook/engineering/developing-locally#get-things-up-and-running
- https://posthog.com/docs/apps/build/tutorial
Create a plugin, document it, update any issues you find in the docs along the way. Suggestions:
- Monitoring plugin
- Workable plugin
- Kafka producer plugin HARD
Fix the PagerDuty plugin
Link to repos from plugin pages in https://posthog.com/apps
https://github.com/PostHog/posthog/issues/7033
https://github.com/PostHog/posthog.com/issues/2427
https://github.com/PostHog/posthog/issues/7528 HARD
Improve https://posthog.com/docs/apps/build (particularly the illustrations)
https://github.com/PostHog/posthog-js/issues/390
https://github.com/PostHog/customerio-plugin/issues/12
https://github.com/PostHog/customerio-plugin/issues/11
https://github.com/PostHog/currency-normalization-plugin/issues/3
Tutorial ideas:
- Update 'Tracking key B2B product metrics' with up to date screenshots (needs an update as we released groups functionality)
- Update 'How to safely roll out new features' with up to date screenshots
- Update 'Visualizing user behaviour' with up to date screenshots
- Update 'How to safely roll out new features'
- Update 'Analyzing your conversion with Funnels'
- How to track B2B product metrics in PostHog
- How to measure product adoption
- How to track daily active users
- How to calculate cohort retention
- How to measure customer churn
- How to combine your CRM with your product analytics - PostHog and Hubspot
- How to combine your CRM with your product analytics - PostHog and Salesforce
- How to lead score your users - PostHog and Hubspot
- How to lead score your users - PostHog and Salesforce
- How to figure out which of your accounts may churn - PostHog and Hubspot
- How to figure out which of your accounts may churn - PostHog and Salesforce
- How to run a product experiment
- How to figure out which marketing channels generate the best users
- How to get more context on your errors - using PostHog with Sentry

💰 Getting paid

Please use this guide to provide us with a contracting rate. If you're uncertain, email coua@ and charles@ posthog. com.

⚖️ Setting expectations

You have done extremely well to get this far already. We get hundreds and sometimes thousands of applications for each role. If we feel it's not working out sooner than the end of the week, we will stop at that point. We will still reimburse you the entire week if this happens. At the end of the week, there is approximately a 50% offer rate.

Ultimately, we are on your side and want you to succeed.

PostHog / meta

Developer Advocate superweek #54