Day-to-Day Responsibilities
Read the programme's scope and rules before testing, and stay inside what the company has allowed.
Map a target's features, pages and APIs to find where flaws could sit.
Test for common weaknesses such as broken access control, injection flaws and insecure settings.
Confirm each flaw is real and can be reproduced, without damaging data or disrupting users.
Write a clear report with steps to reproduce, the likely impact and a suggested fix.
Answer questions from the company's security team and follow the agreed disclosure timeline.
Keep learning new techniques, tools and the rules of each platform.


