Skip to content

Instantly share code, notes, and snippets.

@kneath
Last active November 12, 2018 06:33
Show Gist options
  • Save kneath/6185947 to your computer and use it in GitHub Desktop.
Save kneath/6185947 to your computer and use it in GitHub Desktop.
Growth position

Come help me grow GitHub.com

I've recently started to focus on growth at GitHub, and I'm looking for a partner in crime to help me out.

Growth at GitHub is…

  1. Expanding our business — increasing our revenue and the number of paying customers.

  2. Expanding our audience — increasing the number of people interacting with GitHub.com in a meaningful way.

You would be focused on helping me build out product-level experiments and features to impact growth. Some copywriting, some app-level coding, some front-end coding, and some design. Example projects might be:

  • Redesigning our signup and upgrade flow.

  • Authoring tutorial-like guides for use in our onboarding to help people understand GitHub.

  • Designing and authoring classy follow up emails to re-activate inactive signups.

Traits I'm looking for:

  • You gravitate towards rapid experimentation and production-ready rough drafts.

  • You tend to steer away from lengthy polish, overly beautiful code.

  • You can be comfortable with our .com stack — Ruby, Rails, ERB, SCSS, CoffeeScript, MySQL. You do not need to be an expert in anything, but you should be able to take a general idea and implement it without much hand holding from others.

  • You're curious about why, how, and who the people are that use our site.

So, you're interested?

I'd love to talk to you. Unfortunately there are lot of you, one of me, and I'm horrible at answering email. So I'm going to try something different. Send me ([email protected]) a short email covering the following:

  • What's an example of a great growth tactic you've seen and admire?

  • Can you describe a particular company or growth tactic that you feel was slimy (the opposite of class)?

  • Why do you think you would be great at this position?

Try and keep it under 500 words, the shorter the better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment