Tanium Software Engineer interview typically runs 5 rounds: phone screen, behavioral, technical, technical, and an extra technical round. It took about six weeks and was longer than a standard loop.
$196K
Avg. Base Comp
$271K
Avg. Total Comp
5
Typical Rounds
6 weeks
Process Length
Our candidates report that Tanium is less interested in flashy algorithm tricks than in whether you can move comfortably between classic LeetCode patterns and real implementation work. One interview included Jump Game III, but another shifted into writing a left outer join in the candidate’s language of choice, and a third asked for reasoning through digit-flipping logic on a small list. That mix tells us the bar isn’t just correctness — it’s whether your code feels usable, readable, and grounded in how engineers actually build software.
A recurring theme is that the behavioral side is not treated as filler. Multiple candidates noted questions about prior projects, specific anecdotes from their work, and why they wanted Tanium, which means vague career summaries won’t carry much weight. We’ve seen that the strongest signal is a candidate who can connect past work to the company’s environment in a concrete way, especially in a cybersecurity context where ownership and judgment matter.
The non-obvious part is the persistence of the process itself. Even when interviewers said solutions were correct, candidates still reported being pushed into additional technical evaluation before a final rejection. That suggests Tanium may use interviews to compare candidates very tightly rather than simply clear a minimum bar. Our read: consistency across rounds matters as much as any single strong performance, and candidates should be ready for the process to probe depth even after a seemingly solid showing.
Synthetized from 1 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Tanium process.
The part that stood out most to me was how long the process dragged on. Mine went from a 30-minute phone call to a 30-minute behavioral, then two 1-hour technical interviews, and after that they even asked for a third technical round before ultimately rejecting me. It took about six weeks total, which felt way too long for what was basically a standard software engineer loop.
The early rounds were pretty straightforward. The behavioral interviews focused on my previous projects, specific anecdotes from my work, and why I wanted to work at Tanium, so it helped to have a few concrete stories ready instead of generic answers. The technical rounds were all LeetCode-style, but one of them was more implementation-heavy than I expected. I was asked Jump Game III, then had to implement a left outer join in my language of choice, and in another round I got a problem about returning the smallest number from a list after flipping digits, like taking [12, 13, 91] and reasoning through the flipped values. Even though I was told my solutions were correct by the interviewers, they still requested an extra technical interview and then sent a rejection email saying they went with other candidates. My main takeaway is to prepare for both classic coding problems and a more practical coding exercise, and to have polished project stories ready for the behavioral side.
Prep tip from this candidate
Be ready for LeetCode-style coding plus at least one implementation question like a left outer join in your language of choice. For the behavioral rounds, have specific project anecdotes and a clear answer for why you want Tanium, since that came up directly.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Tanium
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Empty Neighborhoods | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Rolling Bank Transactions | |
| Customer Orders | |
| String Shift | |
| Top 3 Users | |
| Comments Histogram | |
| Closest SAT Scores | |
| Random SQL Sample | |
| Prime to N | |
| Upsell Transactions | |
| Monthly Customer Report | |
| First Touch Attribution | |
| Raining in Seattle | |
| Job Recommendation | |
| Size of Joins | |
| Minimum Change | |
| Hurdles In Data Projects | |
| Cyclic Detection | |
| P-value to a Layman | |
| Address Schema | |
| Download Facts | |
| Permutation Palindrome | |
| Longest Increasing Subsequence | |
| Google Maps Improvement | |
| Radix Addition | |
| Delivery Estimate Model |
Synthesized from candidate reports. Individual experiences may vary.
An initial phone call to discuss your background, interest in Tanium, and overall fit for the software engineer role. This stage appears to be a standard first touchpoint before moving into the rest of the loop.
A behavioral conversation focused on your previous projects, specific work anecdotes, and why you want to work at Tanium. Candidates should come prepared with concrete stories rather than generic answers.
A LeetCode-style coding round covering algorithmic problem solving. One reported question was Jump Game III, with emphasis on writing a correct solution under interview conditions.
A second technical round that mixed classic coding with a more implementation-heavy exercise. Reported prompts included implementing a left outer join in a chosen language and solving a problem about returning the smallest number after flipping digits.
In at least one case, Tanium requested a third technical interview after the first two technical rounds. This extra round extended the process before the final rejection decision.