
Tanium Security Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 5 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Tanium.
Cloud Security Engineer
So basically, there were three rounds in the interview process. The first round was mostly about getting to know you and your background. Then, the second round was a really technical interview with two interviewers. And the last round was a behavioral interview with the head of the department. Everyone was super professional and smart, even the recruiter threw in some technical questions.
- Can you explain what is happening in this image, which is a screenshot of an Azure debug screen?
Security Engineer
It was 3 interviews. They asked me about security issues, showed me pictures and I responded with secure solutions. No talk about more modern research or CVEs. Just basic stuff like XSS, RCEs, etc. I wouldn't sweat it if you do CTFs and web exploits.
- Can you explain what TLS certificates are?
Cloud Security Engineer
So I got reached out to on LinkedIn by an internal recruiter at Tanium for this Senior Cloud Security Engineer, TDIR role. They laid out the process like this: first, a screening call with the recruiter, then a higher-level chat with the hiring manager. After that, a call with a team member to discuss cloud security concepts, followed by a coding interview with another team member. Finally, a call with the department lead to check for 'culture fit'. The HR folks were super communicative all the way through and gave me feedback after each step. When I asked about salary during the first call, they were upfront, and I was too about my expectations, which were a bit higher than their range, but they said it wouldn't be an issue. The hiring manager and team were all really friendly, no 'gotcha' questions, just pleasant conversations. The coding part was pretty straightforward, covering basic stuff like loops, functions, conditionals, and list/dictionary manipulation. There weren't many questions, and the test itself was quick. The rest of the time was spent talking about CI/CD and IaC. After the coding interview, I got a note saying they weren't moving forward. I asked for specific feedback on why, but never heard back. The interview process itself was good, but the lack of feedback at the end really took away from the positive experience.
- Tell me about detections you've created and how you've improved them.
- Can you describe an incident response scenario you participated in?
- In a hypothetical scenario x, what logs or data sources would you examine during an investigation?
Tanium Security Engineer Interview Questions
Quoted word for word from Tanium interview reports.
“Can you explain what TLS certificates are?”
Read reports →“Can you explain what is happening in this image, which is a screenshot of an Azure debug screen?”
Read reports →“In a hypothetical scenario x, what logs or data sources would you examine during an investigation?”
Read reports →“Can you describe your experience with DFIR in Azure?”
Read reports →“Can you describe an incident response scenario you participated in?”
Read report →“Tell me about detections you've created and how you've improved them.”
Read report →“What makes you a good fit for this position?”
Read report →Formats, difficulty and experience
Across all 5 Tanium interview reports.