Skip to main content
Be Bitwise

Building a Track Record

Bug Bounty Reporting & Career · Bug Bounty track

5 min read

In this module

From First Report to Private Invitations

A bug bounty career is built incrementally. Your first valid report puts you on the board. Each subsequent finding adds to your reputation, opens better programmes, and sharpens the skills needed for higher-impact work. This lesson covers how to build that track record with some intention behind it.

Reputation Metrics

Every major platform tracks researcher performance through quantitative metrics. Understanding these metrics helps you optimise your efforts.

On HackerOne, the two primary metrics are:

  • Signal: measures the quality of your reports. It increases when reports are accepted and triaged as valid. It decreases when reports are marked as not applicable, spam, or informational. A high signal score tells programmes that your reports are worth reviewing.
  • Impact: measures the severity of your accepted findings. Critical and high-severity reports contribute more to your impact score than low-severity findings. High impact demonstrates that you find bugs that matter.

Together, signal and impact determine your reputation score, which directly influences your visibility to programmes and your eligibility for private invitations.

On Bugcrowd, researchers are ranked by a points system that factors in the severity of accepted findings and the accuracy of submissions. Bugcrowd's CrowdMatch technology uses these metrics to match researchers to programmes where their skills are most relevant.

Protect Your Signal Score

Your signal score is your most important metric as a new researcher. Every invalid report (spam, out of scope, not applicable, informational) damages it. Before submitting any report, ask yourself: is this a genuine security vulnerability within the programme's scope? Can I reproduce it reliably? Would a security engineer agree this needs fixing? If you are not confident on all three counts, do more testing before submitting.

The Progression Path

Most successful researchers follow a natural progression through four stages:

Stage 1 — VDPs and public programmes: Start with open programmes. Focus on the mechanics: writing clear reports, handling triage interactions, understanding how the platforms score submissions. Payouts will be modest or zero. That's fine — you're buying education and building signal.

Stage 2 — Paid public programmes: Once you have a solid signal score and several accepted reports, move to paid programmes. Wide-scope targets reward good recon. Start leaning into vulnerability classes where you're consistently finding things.

Stage 3 — Private invitations: Reputation compounds. Platforms and organisations start sending invitations. Private programmes have less competition, better payouts, and often fresher surface. At this stage, opportunities arrive rather than needing to be hunted.

Stage 4 — Live hacking events and direct relationships: Top researchers get invited to time-limited live events, build direct relationships with security teams, and often transition to part-time or full-time work in the field.

Specialisation vs Generalisation

As you gain experience, you face a strategic choice: specialise deeply in one area or remain a generalist across many vulnerability classes.

Specialisation advantages:

  • You develop deep expertise that finds bugs others miss
  • Programmes seek you out for your specific skill set
  • Your methodology becomes highly efficient in your niche
  • Examples: API security, mobile application testing, cloud misconfiguration, authentication bypasses

Generalisation advantages:

  • Wider range of programmes you can effectively test
  • Ability to chain vulnerabilities across different classes
  • Resilience against shifts in technology trends
  • Effective in wide-scope programmes with diverse assets

Many successful researchers start broad, then specialise when they notice they're consistently finding one class of bug. Keep general capability intact while drilling down on one or two areas — that combination tends to outperform pure specialists and pure generalists both.

Live Hacking Events

Live hacking events are invite-only, time-limited competitions where researchers test a specific target alongside other top hunters. Major platforms host these events regularly:

  • HackerOne: H1 live hacking events, held at venues worldwide, with dedicated targets and bonus bounties
  • Bugcrowd: LevelUp educational conferences and community events
  • Intigriti: 1337UP and community events

Events offer several benefits beyond the immediate bounties:

  • Networking: meet other researchers, security team members, and platform staff in person
  • Collaboration: event formats sometimes encourage teaming up, and hallway conversations spark new testing ideas
  • Reputation boost: strong performance at events is visible to the community and to programme managers
  • Higher payouts: event targets often have elevated bounty tables

Invitations to live events are based on your platform reputation and track record. Consistent, high-quality work is the path to receiving them.

Long-Term Reputation Building

Beyond platform metrics, your broader reputation in the security community matters:

  • Disclose responsibly: when you have permission, publish detailed write-ups of your findings. These demonstrate your skills to the community and to potential employers.
  • Contribute to tools and knowledge: create tools, publish methodology guides, or contribute to open-source security projects
  • Engage constructively: participate in security communities, help newer researchers, and share knowledge
  • Maintain consistency: a steady stream of valid reports over months and years builds more credibility than occasional high-profile findings

Your track record is cumulative. Every report, every interaction, every contribution layers into the professional identity that opens doors — in the bounty world and well beyond it.