Open Source Lead at Twitter
Boulder, CO, US / Seattle, WA, US / Boston, MA, US / San Francisco, CA, US / United States of America

Open Source has been baked into Twitter’s DNA since the very beginning. Our microservices, developer tooling, QA frameworks, machine learning, design systems – even our twemoji – are built on, with, or released open source. Our Open Source Program Office (OSPO) partners with stakeholders inside and outside of the company to help them work together to solve real world problems. Twitter doesn’t just release and maintain dozens of open source projects, we sponsor Free/Open Source foundations and nonprofits, we host and organize meetups and conferences, and we directly support open source organizations and contributors.

What You’ll Do:

You will lead our cross-functional efforts aimed at making it simple to trust, ship, and grow Open Source at Twitter. 

  • You’ll work with Engineering, Legal, Security, Comms, and Recruiting teams to architect an OSS strategy that accelerates our business initiatives and provides lasting benefits to our stakeholders.
  • You’ll ensure we inbound and outbound open source software via a mature process and best practices that build healthy communities, empower engineers, align with our business goals, protect our intellectual property, and manage our compliance.
  • You’ll up-level our engineering teams on how they consume and contribute to OSS.
  • You’ll advise our leadership team and help them assess the impact of OSS on our software supply-chain, business decisions, M&As, and multi-year technical roadmaps.
  • You’ll represent Twitter Engineering with open source organizations, standards bodies, conferences and meetups, on GitHub, and beyond.
  • You’ll amplify our recruiting efforts and help create a channel for attracting top-notch talent to Twitter.
  • You’ll manage a small team of OSS technical leads and together you will help model OSS best-practices into automated workflows.
  • You’ll directly shape the culture of open source at Twitter.

Who You Are:

  • You have the passion for open source, you get why it exists, why it works, and where it makes the most sense.
  • You dig creating sustainable systems and communities that continue to exist long after you are gone.
  • You are no stranger to the infrastructure around open source projects - both the technical aspects like repository/project management, and the human aspects like community relations and governance.
  • You understand the differences between the most common open source licenses, and basics around IP/Trademarks in the context of open source.
  • You are proficient with Software Development Lifecycle and the various tools, practices, and technical concepts that go into creating high-quality, maintainable software.
  • You have experience with software supply-chain assurance, dependency management, and risk analysis.
  • You are pragmatic, iterative, and customer-driven. You focus on where you can add the most value and automate/delegate the rest.
  • You’re organized, self-starting, and resourceful. You get stuff done.
  • You know how & when to ask for help. You can influence without authority.
  • You have excellent written and verbal communication skills.
  • You are comfortable within distributed work environments, collaborating across time zones and cultures.

You Have Experience With:

  • Building and growing developer communities.
  • Organizing, promoting, and running large developer-focused events.
  • Open-source licenses and general open-source compliance issues.
  • Multiple programming languages/environments, such as Python, JavaScript, Java, Scala, or Go (technical competence).
  • Open source dependency management tools.
  • GitHub and open-source CI tooling (e.g. Travis CI, Coveralls, CircleCI).
  • Managing sustainable organizational programs with many distributed stakeholders.
  • Working with, coaching, and advising both leadership and individual contributors.
  • BA/BS in Computer Science or a related technical field (MS is a plus) or equivalent work experience is strongly preferred, but not required.