Careers
For crypto and AI/ML reviewers. You write findings a peer can reproduce. We do not run a content mill or a bounty desk.
Open seats
No open seats today. Do not use the request form to apply; that form is for clients. When a seat opens, it will be listed here with the practice and the hiring bar.
What the work is
- You read code, model pipelines, and the glue between them against a written brief, then you try to break it.
- Findings include an exploit path, the assumption that produced it, and a fix a maintainer can apply without a call.
- The same reviewer retests fixes against the same brief and records the result per finding.
- You sit in the daily sync with the other bench. Joins show up in that room, not when you work alone.
What we are not hiring for
- Content. There is no blog quota or thread schedule, and conference talks are not a job requirement.
- Bounty hunting. We review scoped systems against a brief, not open programs for a payout.
- Sales engineering. Scoping calls are run by the people who will do the review.
- Tool operation. Running a scanner and forwarding its output is not a finding.
How to write
When a seat is listed, send one finding you wrote, either a real one or a redacted sample, to careers@hackerbane.com. We read the finding before the CV. We want short sentences, named assumptions, and a path someone else can reproduce. The bar is on /style.