Talent Acquisition Services for Cybersecurity companies
What this looks like in your business
Hiring for a security firm is a search for evidence of skill more than for a title. A monitoring analyst who triages alerts calmly at three in the morning, a tester who finds what the scanner missed and a governance consultant who can sit with a client's auditors are different people, found in different places. Owners hand a search to GullyHR when the founders are too busy delivering to source, or when a good tester has just been lost to a rival and the pipeline is empty. GullyHR works from a written brief for each permanent role, screens against the same criteria and presents a shortlist with a reason for each name.
Why security roles are hard to fill
The security talent pool is small, and everyone in it is being approached. Testers and researchers hold several offers at once, and a firm that takes weeks to reply loses them. Monitoring analysts are easier to find but harder to keep, because night and weekend rotas wear people down and a rival offering day work draws them off. Incident responders must be calm, ready to be called out, and trusted with client networks from the first week. Pre-sales and technical engineers need both technical depth and the ability to explain a control to a buyer who is not technical. Job titles mislead. A candidate called a security consultant may have only run scans, while another with a plain title may have broken real systems. Because confidentiality rests on conduct, a hire is also a judgement about character. Founders who screen alone between client deadlines decide too slowly, or on a strong conversation without evidence. A search needs a brief that says what the person must show, not what they must have been called.
What the written brief settles before sourcing
GullyHR will not start a search until the role is written down and agreed. For a security firm, the brief names the team the person joins, whether the role includes night or on-call cover, which client sites or remote engagements it involves, and the reporting line. It states the work in terms a candidate can picture: for example reviewing alerts from client networks and escalating to a named lead, or carrying out testing under a written scope. It lists must-have evidence separately from helpful extras, such as reports written, findings documented or incidents handled. Pay range and location are agreed with the owner before outreach, so no candidate is misled. GullyHR then chooses sourcing channels for the role, not by habit: communities of testers and researchers for one role, referrals and networks for another. Applications and outreach are tracked in one place, and screening uses the same questions for each candidate, so the shortlist can be defended later. A brief that is clear on day one saves the owner several rounds of candidates who were never right for the role.
Shortlisting a tester without the usual noise
Suppose a firm that audits client networks needs a penetration tester to replace one who left. The owner signs a brief: permanent role, remote with occasional client visits, testing under written scope, report writing included. GullyHR screens thirty applicants against the same criteria and finds that two look strong on certificates but show no sample of a written finding. A third has no famous employer but shares a redacted report, with the client removed, that shows clear reasoning and plain language. GullyHR's shortlist names four people, with a reason for each: one for web testing depth, one for report quality, one for network work, and one whose gaps are noted honestly. The owner reads the notes, asks the technical lead to run a practical discussion with each, and decides whom to meet. The shortlist is advice. The owner chooses who to interview, what to offer and whether to hire at all. Candidates also hear back within days, which matters when a tester is holding other offers, and the file shows every reply that was sent.
Handovers, records and the owner's decisions
Once the shortlist is handed over, the work shifts to your own people, and the handover should be clean. GullyHR passes each candidate's file to a named person in your firm, normally the technical lead or the delivery manager, with the screening notes, the questions asked and the answers given. Interview feedback is written on a shared form within a day, so the next conversation does not start from scratch. The owner or director signs off the offer, including pay, notice and joining date, and your adviser reviews the offer letter and confidentiality terms before they are sent. Someone in your firm must own joining: signed terms before the first shift, access given only after, and a first-week plan for the new analyst or tester. GullyHR follows candidates through interviews, the offer and joining, but it does not decide who is hired. It does not supply temporary or contract staff, and it covers permanent roles only. Rejected candidates receive a courteous reply, and their notes stay on file in case a later role fits them better.