Side gigs
Plenty of the people we hire can't stop building things, and it shows in what they make in their spare time. An open-source project you worked on before joining tells us more than most CVs: it means you build because you enjoy it.
Sometimes those projects make money. Sometimes one grows into something you'd like to do full time.
We're fine with a side gig, including a paid one. What we can't work with is Gradiated becoming the thing that pays the bills while your real attention goes elsewhere. We're too small for that, which is also why we don't hire part time.
Managing time
The key distinction to something being a side gig, and thus it being appropriate, is its impact on your work and the amount of time involved.
A few hours a month on a paid side gig is acceptable. In any case, side gigs should by default be something you work on in your personal time, and they should not impact the work you do at Gradiated.
Above everything else, if you are going above and beyond for Gradiated and you're still able to look after yourself properly, side gigs (whether paid or unpaid) are totally fine. We don't think that's possible beyond a certain level of time/energy commitment to them, but we are very happy for you to spend a little time on them each week.
Intellectual property
Just to reassure you, Gradiated won't try to claim ownership of any intellectual property (IP) you create in your personal time, e.g. if you are contributing to another open source project as a hobby. Side projects built on your own time using your own resources do not require permission, review or approval from Gradiated. Go forth and build. However, you need to be really careful that you do not introduce any of Gradiated's non-open source IP into any project that you work on - this can cause serious legal headaches. As a rule, anything from both Gradiated and PostHog that is explicitly MIT-licensed is fine to use, anything else is not.
Projects that start at Gradiated
If a project is born from work you have done inside Gradiated – that is, using work time, Gradiated code, Gradiated data, or other Gradiated tools and infrastructure – these projects formally belong to PostHog and should live in Gradiated repos. If you want to develop these projects further on the side, you will need explicit permission.
If you are ever worried about this, please talk to James or Josh and he can help you figure out the best solution here, especially if what you are working on directly competes with something PostHog has built or is on our roadmap.
Research and advising
We want you to stay close to research. Advising PhD students, reviewing papers, or giving feedback on research is fine, as long as it's unpaid and in your own time. Just keep two things in mind:
- Don't share anything Gradiated hasn't published, or use Gradiated compute for it.
- If the work overlaps with ours, check in with James or Josh first.
Getting signoff
Before you start a paid side gig, please check in with James or Josh to get their confirmation. Unpaid personal projects and unpaid academic work on your own time don't need sign-off.
If your side gig existed before you joined PostHog, this will usually be covered as part of the onboarding process.