Glassdoor users rated their interview experience at ThreatSpike Labs as 50% positive with a difficulty rating score of 2.5 out of 5 (where 5 is the highest level of difficulty). Candidates interviewing for Red Team Operator and Penetration Tester rated their interviews as the hardest, whereas interviews for Red Team Operator and Penetration Tester roles were rated as the easiest.
I interviewed at ThreatSpike Labs (London, England)
Interview
I had an interview with Adam the SDR manager. I felt it went really well and came away feeling extremely excited and positive. I was told I would be put through to the next round. After a week I tried to follow up but received no reply, I tried again a couple of times but was left ghosted.
I applied online. I interviewed at ThreatSpike Labs (London, England) in Jan 2026
Interview
Third interview totally unprofessional. As soon as the call started I was told that the person interviewing me would not be putting the camera on. Interview was stilted, unenthusiastic and uncomfortable. I wanted to end it about 5 minutes in but didn’t want to be rude. Even though I had been through 2 previous interviews to this stage and I knew that I would not have progressed any further I was not given the courtesy of an email outcome.
I applied through an employee referral. I interviewed at ThreatSpike Labs in Jan 2026
Interview
I interviewed with ThreatSpike for a Penetration Tester role around 1/26/2026. The process felt unprofessional and the scheduling was a mess due to the company being London-based and several time-zone misalignments with the US. I joined a panel interview at 6am my time, and only one person was there on time; two others arrived 5-10 mins late, didn’t turn on cameras, didn’t introduce themselves and did not ask questions. The interviewer, who was a recent computer science graduate, led with a rapid-fire series of mostly networking and computer science questions, with no focus on pentesting methodology, AD security, or real-world scenarios. I didn’t receive a clear timeline or feedback after the interview, which left me with many unanswered questions about the role and team structure. When I asked about basic details like whether the position was W2 or 1099, and about junior mentorship or shadowing, the responses suggested a lack of organization and clarity. Overall, the process felt disorganized and shallow for a pentesting role, especially at junior levels. If you’re applying, push for a structured plan, explicit timelines, and a clear description of how a junior would be onboarded and supported.
Interview questions [1]
Question 1
1. TCP vs. UDP
2. How DNS recursion works
3. What is SQLi
4. What is SQL
5. What is O(logn)
6. What is ARP
7. What is a VLAN
8. What is a DMZ
9. What is a firewall
10. Difference between heap and stack memory
11. User Space vs. Kernel Space
12. How User Space talks to Kernel Space
13. Three Types of XSS
14. Recursion vs. Iteration (Dev Perspective)
15. How many usable IPs in a /26 subnet