Customer-facing experience and hands-on cybersecurity research, brought together for a career in security sales.
I’m looking for a Sales Development Representative role in cybersecurity, based in . I haven’t worked as an SDR yet. Below is what I’d bring to the role, and what I’ve built to prepare for it.
We’re covered. We renewed our endpoint contract last year.
That’s good to hear. When an alert fires at 2am, who on your team picks it up?
In hospitality, the part I was best at was the people side: reading a situation, finding out what someone actually needed and putting it right. In security research, the part I enjoy most is understanding how a company works and what could go wrong for it.
Sales development uses both. It means researching companies properly, understanding the business problem behind the security problem, and starting conversations that are worth the customer’s time. It’s a role where both halves of my background are useful at the same time.
Featured project
An account research tool I built to prepare for SDR work. It turns public information about UK companies into an evidence-backed starting point for a sales conversation.
Next.js and TypeScript, with a local SQLite database through Prisma. Data comes from the Companies House API, company websites (respecting robots.txt), GDELT news and RSS feeds. Requests go through a guard that blocks internal addresses and rate-limits each source. Scoring is deterministic: unknown inputs are excluded rather than guessed. The optional AI layer uses the Anthropic API or a local Ollama model, and untrusted web content is isolated from instructions.
I wrote the brief and made the product decisions. I built it with AI-assisted development. It runs locally and is not deployed as a public service.
Watch a short demo, or I’m happy to walk you through it on a call.
How I’d prepare before contacting a large UK enterprise, using only public information. Facts are sourced, guesses are labelled as hypotheses, and nothing suggests the company has a security problem.
Independent research on public programmes on HackerOne, Bugcrowd and Immunefi, within each programme’s rules. One report accepted and rewarded so far. I don’t publish details of reports, in line with responsible disclosure.
A lab built around Wazuh for collecting logs, writing detections and testing them, plus a PowerShell toolkit for system health checks and incident evidence collection.
Running Qwen and Gemma models on my own hardware to test where local AI genuinely helps in security research. Mostly experiments, not finished tools.
Discovery conversations, active listening, handling objections and complaints, building rapport, account research, clear writing.
Web, API and mobile testing (Burp Suite, Caido), smart contract review (Foundry), Wazuh, Linux (Ubuntu) and Qubes OS.
TypeScript (Next.js), Python, PowerShell, SQLite. Learning C and C++.
I’d welcome a short call to talk about the role, and I’m happy to walk you through CyberProspect AI or the Aviva example.
My contact details are included with my referral.
Sales Development Representative candidate, cybersecurity
Customer-facing professional moving into cybersecurity sales. I bring ten years of hospitality experience and independent security research on public bug bounty programmes (HackerOne, Bugcrowd, Immunefi). I haven’t worked as an SDR yet. To prepare, I built CyberProspect AI, an account research tool, and used the same method to research Aviva as a worked example.
Authorised public programmes on HackerOne, Bugcrowd and Immunefi
Self-employed
An account research tool I built to prepare for SDR work. It runs locally; demo available on request.
A short brief showing how I’d prepare before contacting a large UK enterprise: public business signals (a new Group CIO, the Direct Line integration, new FCA incident reporting rules), hypotheses labelled as guesses, stakeholder personas, discovery questions and an example first email. Read it at www.plamenbotev.uk/brief.