About GitHub
GitHub is the world’s leading platform for agentic software development - powered by Copilot to build, scale, and deliver secure software. Over 180 million developers, including more than 90% of the Fortune 100 companies, use GitHub to collaborate, and more than 77,000 organisations have adopted GitHub Copilot.
Locations
In this role you can work from Remote, United States
Overview
GitHub is transforming how the world builds secure software, and we are looking for a Staff Bug Bounty Manager to lead and grow GitHub's Bug Bounty program. Bug Bounty is one of the most visible parts of our security posture: it's how thousands of external researchers engage directly with GitHub to find and responsibly disclose vulnerabilities across all our products.
This is a hybrid role: part program manager, part security researcher. You will own the strategy, scope, SLAs, and vendor relationships that make the program run, while also rolling up your sleeves to triage incoming reports alongside the team and engage directly with the external researcher community as a credible technical peer. You'll partner closely with Incident Response and Product Security teams remediation and with Engineering teams across GitHub's product surface as vulnerabilities are found and fixed. You will be equally comfortable triaging security findings, managing a team and building a community of security researchers.
Responsibilities
Program Ownership and Strategy
- Own the Bug Bounty program's strategy, scope definition, and rules of engagement (in-scope products and domains, reward tiers, safe harbor terms), keeping them current as GitHub's product surface grows.
- Own vendor relationships and contracts, including renewal, researcher payout operations, and escalation when platform or contractual issues block payouts.
- Define and drive the program's KPIs (triage SLA performance, time-to-first-response, time-to-payout, researcher satisfaction, submission-to-valid-finding ratio), using them to identify where process or staffing investment is needed.
- Manage payout tiers and severity calibration using CVSS and GitHub's own impact criteria, ensuring consistent, defensible payout decisions across the team.
Hands-On Triage and Research
- Triage incoming bug bounty submissions alongside the team: validate severity and impact, reproduce findings, and make initial disposition calls on contested or ambiguous reports.
- Maintain the technical depth to engage credibly with sophisticated external researchers, including on novel attack classes relevant to GitHub's platform and to AI/Copilot-adjacent surfaces.
- Apply diagnostic expertise across GitHub's technologies to identify how findings interact with existing controls, and contribute to root-cause and trend analysis across submissions.
Researcher and Community Engagement
- Serve as GitHub's primary point of contact for the external researcher community: build and maintain trust, communicate program changes, and represent GitHub at security research conferences and forums as appropriate.
- Develop feedback channels with researchers and translate that feedback into program and product security improvements.
- Partner with Product Security and Incident Response teams to hand off validated findings cleanly into incident response and remediation tracking, keeping the triage/remediation boundary clear as both teams scale.
Collaboration and Communication
- Translate technical vulnerability findings into clear guidance for non-technical stakeholders, including Engineering leadership and Legal/CELA.
- Partner with Legal/CELA on payout terms, safe harbor language, and disclosure obligations tied to bug bounty submissions.
- Coordinate with Engineering teams across GitHub's product surface to ensure findings are routed, prioritized, and remediated.
People and Team Building
- Hire, develop, and manage the Bug Bounty team as it matures and evolves.
- Build the operational rigor (staffing model, SLAs, on-call/triage coverage) and automation that keeps the program sustainable as submission volume continues to grow.
Qualifications
Required Qualifications
- 7+ years experience in security analysis, security research, cyber security, security engineering, or relevant area
•
- OR Associate's Degree AND 6+ years experience in security analysis, security research, cyber security, security engineering, or relevant area
•
- OR Bachelor's Degree AND 5+ years experience in security analysis, security research, cyber security, security engineering, or relevant area
•
- OR Master's Degree AND 3+ years experience in security analysis, security research, cyber security, security engineering, or relevant area
•
- OR Doctorate AND 1+ year(s) experience in security analysis, security research, cyber security, security engineering, or relevant area
•
- OR equivalent experience.
- 3+ years experience in bug bounty operations, vulnerability disclosure programs, or security research, including direct platform experience (e.g., HackerOne, Bugcrowd).
- 1+ years direct experience triaging vulnerability reports for severity, validity, and impact, including use of CVSS or comparable severity frameworks.
Preferred Qualifications
- 2+ years people management experience, or demonstrated readiness to take on people management as the program and team grow.
- Credited author on 1+ published article(s)/paper(s), or speaker/presenter at a security-related conference.
- Experience owning a vendor/platform relationship and contract (e.g., HackerOne, Bugcrowd), including payout operations.
- Familiarity with GitHub's products, platform, and developer ecosystem, including GHES, GHEC, npm, and Copilot.
- 1+ year(s) experience working with GitHub and/or open source software.
- Certified Information Systems Security Professional (CISSP), GIAC Certified Incident Handler (GCIH), Offensive Security Certified Professional (OSCP), or other relevant certification.
Compensation Range
The base salary range for this job is USD $127,800.00 - USD $339,000.00 /Yr.
These pay ranges are intended to cover roles based across the United States. An individual's base pay depends on various factors including geographical location and review of experience, knowledge, skills, abilities of the applicant. At GitHub certain roles are eligible for benefits and additional rewards, including annual bonus and stock. These rewards are allocated based on individual impact in role. In addition, certain roles also have the opportunity to earn sales incentives based on revenue or utilization, depending on the terms of the plan and the employee's role.
This position will be open for a minimum of 3 days, with applications accepted on an ongoing basis until the position is filled.
GitHub values
- Customer-obsessed
- Ship to learn
- Growth mindset
- Own the outcome
- Better together
- Diverse and inclusive
Manager fundamentals
Leadership principles
- Create clarity
- Generate energy
- Deliver success
Who We Are
GitHub is the world’s leading AI-powered developer platform with 150 million developers and counting. We’re also home to the biggest open-source community on earth (and 99% of the world’s software has open-source code in its DNA). Many of the apps and programs you use every day are built on GitHub.
Our teams are dreamers, doers, and pioneers, leading the way in AI, driving humanitarian efforts around the globe, and even sending open source to Mars (and beyond!). At GitHub, our goal is to create the space you need to do your best work. We’re remote-first and offer competitive pay, generous learning and growth opportunities, and excellent benefits to support you, wherever you are - because we know that people flourish when they can work on their own terms.
Join us, and let’s change the world, together.
EEO Statement
GitHub is made up of people from a wide variety of backgrounds and lifestyles. We embrace diversity and invite applications from people of all walks of life. We don't discriminate against employees or applicants based on gender identity or expression, sexual orientation, race, religion, age, national origin, citizenship, disability, pregnancy status, veteran status, or any other differences. Also, if you have a disability, please let us know if there's any way we can make the interview process better for you; we're happy to accommodate! Program Ownership and Strategy
- Own the Bug Bounty program's strategy, scope definition, and rules of engagement (in-scope products and domains, reward tiers, safe harbor terms), keeping them current as GitHub's product surface grows.
- Own vendor relationships and contracts, including renewal, researcher payout operations, and escalation when platform or contractual issues block payouts.
- Define and drive the program's KPIs (triage SLA performance, time-to-first-response, time-to-payout, researcher satisfaction, submission-to-valid-finding ratio), using them to identify where process or staffing investment is needed.
- Manage payout tiers and severity calibration using CVSS and GitHub's own impact criteria, ensuring consistent, defensible payout decisions across the team.
Hands-On Triage and Research
- Triage incoming bug bounty submissions alongside the team: validate severity and impact, reproduce findings, and make initial disposition calls on contested or ambiguous reports.
- Maintain the technical depth to engage credibly with sophisticated external researchers, including on novel attack classes relevant to GitHub's platform and to AI/Copilot-adjacent surfaces.
- Apply diagnostic expertise across GitHub's technologies to identify how findings interact with existing controls, and contribute to root-cause and trend analysis across submissions.
Researcher and Community Engagement
- Serve as GitHub's primary point of contact for the external researcher community: build and maintain trust, communicate program changes, and represent GitHub at security research conferences and forums as appropriate.
- Develop feedback channels with researchers and translate that feedback into program and product security improvements.
- Partner with Product Security and Incident Response teams to hand off validated findings cleanly into incident response and remediation tracking, keeping the triage/remediation boundary clear as both teams scale.
Collaboration and Communication
- Translate technical vulnerability findings into clear guidance for non-technical stakeholders, including Engineering leadership and Legal/CELA.
- Partner with Legal/CELA on payout terms, safe harbor language, and disclosure obligations tied to bug bounty submissions.
- Coordinate with Engineering teams across GitHub's product surface to ensure findings are routed, prioritized, and remediated.
People and Team Building
- Hire, develop, and manage the Bug Bounty team as it matures and evolves.
- Build the operational rigor (staffing model, SLAs, on-call/triage coverage) and automation that keeps the program sustainable as submission volume continues to grow.
Required Qualifications
- 7+ years experience in security analysis, security research, cyber security, security engineering, or relevant area
•
- OR Associate's Degree AND 6+ years experience in security analysis, security research, cyber security, security engineering, or relevant area
•
- OR Bachelor's Degree AND 5+ years experience in security analysis, security research, cyber security, security engineering, or relevant area
•
- OR Master's Degree AND 3+ years experience in security analysis, security research, cyber security, security engineering, or relevant area
•
- OR Doctorate AND 1+ year(s) experience in security analysis, security research, cyber security, security engineering, or relevant area
•
- OR equivalent experience.
- 3+ years experience in bug bounty operations, vulnerability disclosure programs, or security research, including direct platform experience (e.g., HackerOne, Bugcrowd).
- 1+ years direct experience triaging vulnerability reports for severity, validity, and impact, including use of CVSS or comparable severity frameworks.
Preferred Qualifications
- 2+ years people management experience, or demonstrated readiness to take on people management as the program and team grow.
- Credited author on 1+ published article(s)/paper(s), or speaker/presenter at a security-related conference.
- Experience owning a vendor/platform relationship and contract (e.g., HackerOne, Bugcrowd), including payout operations.
- Familiarity with GitHub's products, platform, and developer ecosystem, including GHES, GHEC, npm, and Copilot.
- 1+ year(s) experience working with GitHub and/or open source software.
- Certified Information Systems Security Professional (CISSP), GIAC Certified Incident Handler (GCIH), Offensive Security Certified Professional (OSCP), or other relevant certification.