Skip to content

Adding a new Q3 goal for Joe #12112

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Adding a new Q3 goal for Joe #12112

wants to merge 1 commit into from

Conversation

joethreepwood
Copy link
Contributor

@joethreepwood joethreepwood commented Jul 8, 2025

Hiring is taking up an incredible amount of my time — and rightly so. We’re hiring four people for the PMM role alone over the next two quarters, plus an illustrator (which @lottiecoxon will lead on, but I’ll support), then a social media manager/CM, and a partnerships manager.

Some weeks I’m already spending 8+ hours just in interviews for the PMM role — we’ve reviewed over 420 applications so far, all of which I’ve personally screened.

This isn’t a complaint — just an observation that, looking ahead, hiring is probably the highest-impact thing I can spend time on. Getting the right people in will help us move far faster than if I try to fill the gaps alone.

So I’m proposing we tweak my Q3 goals: I’ll have two goals, with Hiring as an explicit top priority (like @andyvan-ph has) — and I’ll prioritize it over my current repositioning goal. We’ll only be able to deliver on that properly once these hires are in place anyway.

Checklist

  • Words are spelled using American English
  • Titles are in sentence case
  • Feature names are in sentence case too
  • Use relative URLs for internal links
  • If I moved a page, I added a redirect in vercel.json
  • Remove this template if you're not going to fill it out!

Article checklist

  • I've added (at least) 3-5 internal links to this new article
  • I've added keywords for this page to the rank tracker in Ahrefs
  • I've checked the preview build of the article
  • The date on the article is today's date
  • I've added this to the relevant "Tutorials and guides" docs page (if applicable)

@joethreepwood joethreepwood self-assigned this Jul 8, 2025
Copy link

vercel bot commented Jul 8, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
posthog ✅ Ready (Inspect) Visit Preview Jul 8, 2025 11:34am

@jamesefhawkins
Copy link
Contributor

jamesefhawkins commented Jul 8, 2025

it kind of feels unhealthy to me that you and @andyvan-ph it sounds like have to focus this hard on this and we can't support you better. ie i don't see eng team leads doing this when they're all hiring. we are going to keep scaling and it feels wrong to have people in roles that are doing stuff having to focus so strongly here- ie everything goes well when people are shipping, when they're doing Other Things everything will start to feel worse.

any idea why is this so much more work for you than other parts of the business? can the people team support you more? we are scaling them a lot and they have this type of thing as a goal.

@joethreepwood
Copy link
Contributor Author

joethreepwood commented Jul 8, 2025

Well, I'm not meaning to knock the People team because they're great. But I think marketing hires work a little different.

Marketing roles are unique. We don't need to write a new spec, have a conversation, design a superday, etc, every time we hire a new engineer -- and one engineer can often slot into many teams. But for new marketing roles each one is one-off (e.g. community manager, partner manager, events marketer, illustrator, production designer).

Marketing roles are unicorn-hunts. Every role in marketing tends to be much rarer. It's harder to find a developer who is a good writer, for example, than just finding a developer. This means Andy and I end up with longer, more complicated pipelines -- often with much more subjectivity. That's why he and I screen all applications, unlike engineering team leads.

Marketing roles don't have the same structure. My understanding is that hiring in engineering is split across a lot of people and there's a rota for people doing interviews and superdays. We don't have that, nor the manpower to do it. Instead, Andy and I do every technical interview and every superday. Andy also joins all my peer reviews, and often vice versa.

I think it'll naturally speed up as we make more hires. I saw this with Support, for example, where it was really hard to find @abigailbramble and has sped up a lot since - we just haven't hit the tipping point yet.

@andyvan-ph
Copy link
Contributor

andyvan-ph commented Jul 8, 2025

Off the top of my head, one possible solution would be to hire a talent partner with specific experience recruiting non-technical roles, though I don't if that would make a huge amount of difference.

But, just to add some additional colour and a specific example, with the video post-production role we had to figure out:

  • A totally new job spec
  • Where to advertise since we're less likely to have these come in organically
  • Experiment a bit with want to ask about, since I'd never interviewed this kind of role, and Alex had never interviewed anyone ever before (he's great at it, btw!)
  • A totally new SuperDay task and process. This meant figuring out an editing project that was completable in a day, plus how to send people the assets ahead of time so they could download it. After some experiments, we ended up with a 9GB passworded zip file that we can send candidates to download beforehand, then give them the password on the day.

Anyhoo, TL;DR this was all new stuff we had to figure out just to hire one person, so it just sucks up more energy and time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants