Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update SuperDay steps #10051

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions contents/handbook/people/hiring-process/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,10 +38,10 @@ We are all-remote, but we have a few limitations on the countries we are able to

| Position | Team | Reporting lead | Interview process |
| ---------------------------- | ------------------------ | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Product Engineers | Multiple teams | Tech Lead | <ol><li>Culture screen with Ops (20mins)</li><li>Technical screen w/ an engineer (60mins)</li><li>Small team screen w/ James (30mins)</li><li>SuperDay - task assessment, peer team interview, and culture and motivation interview w/ Tim (8-10hrs)</li></ol> |
| Technical Account Executive | Sales & CS | Simon | <ol><li>Culture screen with Ops (20mins)</li><li>Technical screen w/ Simon (45mins)</li><li>Small team screen w/ Tim (30mins)</li><li>SuperDay- task assessment, peer team interview, and culture and motivation interview w/ James (8-10hrs)</li></ol> |
| Technical Customer Success Manager | Sales & CS | Simon | <ol><li>Culture screen with Ops (20mins)</li><li>Technical screen w/ Simon (45mins)</li><li>Small team screen w/ Tim (30mins)</li><li>SuperDay- task assessment, peer team interview, and culture and motivation interview w/ James (8-10hrs)</li></ol> |

| Product Engineers | Multiple teams | Tech Lead | <ol><li>Culture screen with Ops (20mins)</li><li>Technical screen w/ an engineer (60mins)</li><li>founder screen w/ James (30mins)</li><li>SuperDay - task assessment, peer team interview, and culture and motivation interview w/ Tim (8-10hrs)</li></ol> |
| Product Manager | Multiple teams | James | <ol><li>Culture screen with Ops (20mins)</li><li>Technical screen w/ Annika (45mins)</li><li>founder screen w/ James (45mins)</li><li>SuperDay- task assessment, peer team interview, and culture and motivation interview w/ Tim (8-10hrs)</li></ol> |
| Product Marketer | Comms | Joe | <ol><li>Culture screen with Ops (20mins)</li><li>Technical screen w/ Joe (60mins)</li><li>Founder screen w/ James (30mins)</li><li>SuperDay- task assessment, peer team interview, and culture and motivation interview w/ Tim (8-10hrs)</li></ol> |
| Performance Marketer | Marketing | Andy | <ol><li>Culture screen with Ops (20mins)</li><li>Technical screen w/ Andy + Charles (60mins)</li><li>Founder screen w/ James (30mins)</li><li>SuperDay- task assessment, peer team interview, and culture and motivation interview w/ Tim (8-10hrs)</li></ol>

</OverflowXSection>

Expand Down Expand Up @@ -232,6 +232,7 @@ The final stage of our interview process is what we call a PostHog SuperDay. Thi

The candidate will be working on a task that is similar to the day-to-day work someone in this role does at PostHog. They will also have the chance to meet a few of their potential direct team members, and if they haven’t already, our founders. This gives the candidate a chance to show off their skills, and for us to see the quality, speed and communication of the candidate. It is a demanding day of work.


We will pay the candidate their 'normal day rate.' If they have done contracting before they will have one, but if not we can use [this formula](https://www.ellwoodatfield.com/day-rate-caluclator) to calculate it. If the candidate is unable to accept payment for the SuperDay, we will donate the amount to a charity of their choice from our [Project list](/handbook/growth/marketing/open-source-sponsorship) of sponsorships.

This day will be _the same_ task each time for a given role, to be shared with the candidate at the start of the day. The task is generally designed to be _too much_ work for one person to complete in a day, in order to get a sense of the person's ability to prioritize and get things done.
Expand All @@ -242,9 +243,11 @@ Overall, the candidate should aim to spend at least 80% of their time and energy

In advance of the SuperDay, we will need to do some additional prep to ensure that the candidate has a great experience:

* Send the candidate, Tim, James, two people from Ops, and the SuperDay buddy (technical roles) or the lead (for all other non-technical roles) a Google calendar invite to remind the team when the SuperDay will take place (mark the invite free and all day or split days)
* Send them an email in the first instance to schedule the SuperDay - we aim to do this as soon as possible, as candidates often will need to book a day off work. Use the Ashby email template for this. If the task involves them doing 'real' work for PostHog, we should ask them to check that their current employment contract permits this - we try to create fake tasks for this reason. For all US candidates there is a requirement we collect a [W9](https://www.irs.gov/forms-pubs/about-form-w-9) from the candidate for accounting and tax purposes (_this doesn't apply if the US candidate decides to donate the funds to one of our sponsored projects_)
* We also send the candidate a follow up email with details of the task, and ask them for their day rate and bank details right away so the candidate can fully prepared what to expect and who they will meet. There is a template for this email in Ashby, depending on the role - this will probably need customising.
* (One day before the SuperDay) Create a private channel in Slack for the candidate and all relevant people - this will be where they can chat to us over the course of the day if they have any questions etc. Invite the candidate as a single channel guest. We might need to add the candidate to one of our systems depending on the role, e.g. Ashby for a recruiter SuperDay, but on the whole this should be minimized.
* For Product Engineer SuperDays, upload the zip file by going into the the [Git SuperDay task](https://github.com/PostHog/superday-interview-test/blob/main/.github/workflows/generate-full-stack-package.yml) then hover over the "Actions" tab and click on "Generate Full Stack Package" and click on "Run Workflow" then name the file under the candidate's first name. Once the zip file has completed, click into the file and hit the download button and upload the zip file into the candidate's slack channel.
* (One day before the SuperDay) Invite the candidate to a kickoff meeting with the hiring manager at the start of the day. On days when we have a company-wide meeting scheduled, invite them along. On days without standup, schedule an informal session with some team members to give them a chance to learn more about our culture. We may also want to have a proper wrap up with them at the end of their day.
* (On the SuperDay) Send the candidate the task - aim to send this before the kick-off session so if the candidate has any questions they are able to go through them during the kick-off session. We encourage the candidate to ask questions throughout their SuperDay, but sometimes it is nice to have any questions answered in advance so they can kick off their task appropriately.
* (On the SuperDay) Give the candidate a warm welcome! Make it clear that the team is here to answer any questions, and they should feel free to reach out any time! Otherwise don't feel like we need to check in with them - let them get on with the task and trust that they will message us.
Expand Down
Loading