SENIOR / PRINCIPAL OFFENSIVE SECURITY ENGINEER
BreachLock
·Today
- Location
- United States · published
- Workplace
- Remote
- Type
- Full-time
- Department
- Pen Testing
- Seniority
- Lead
- Source
- Workable
Description
ABOUT BREACHLOCK
BreachLock is a penetration testing provider that pairs skilled human testers with a delivery platform, giving clients offensive security testing at the depth of a bespoke engagement and the speed of a product. This role sits on the team that owns the custom, difficult engagements that define the high end of that work.
ABOUT THE ROLE
BreachLock is hiring a Senior or Principal Offensive Security Engineer to join the team that handles our hardest, most custom engagements. This is hands-on testing work. You will spend your weeks inside client networks, applications, and the places where the two meet, finding the paths a real attacker would take and writing them up so a client can act. You will also help set the technical bar for the people around you.
We run the engagements that do not fit a template: the bespoke, high-touch, non-standard work where off-the-shelf methodology runs out quickly. If you want a seat where the interesting problems land on your desk and your judgment is the product, this is it.
The level we hire you at, Senior or Principal, follows your depth and track record. Both are senior individual-contributor roles with room to grow into technical leadership.
WHAT YOU WILL DO
- Lead external and internal network penetration tests, web application assessments, and mobile application assessments from scoping through final report.
- Own Active Directory attack paths end to end: enumeration, credential access, lateral movement, privilege escalation, and the walk back to domain compromise, with a clear account of how each step was possible and how to close it.
- Test web applications against real business logic, authentication and authorization flaws, injection, and the chained issues that a scanner will never find.
- Assess mobile applications on iOS and Android, including the API surface behind them.
- Write findings that a client can use. Clear severity, honest scope, reproducible steps, and remediation that fits the environment they actually run.
- Partner directly with clients during testing and debriefs, explain exposure in plain terms, and walk technical teams through how to fix what you found.
- Contribute to the team's shared toolkit and methodology.
- Mentor less experienced testers and raise the quality of the work around you.