Tanium software engineer candidates report a recruiter call, a behavioral conversation, and LeetCode-style technical rounds, including one implementation-heavy problem. Reported timelines ran from about three to six weeks.
$172K
Avg. Base Comp
$241K
Avg. Total Comp
4-5 rounds
Typical Rounds
3-6 weeks
Process Length
Candidates describe the Tanium software engineer loop as a fairly conventional mix of recruiter contact, behavioral conversation and LeetCode-style coding. One Software Engineer II candidate reported a 30-minute phone call, a 30-minute behavioral interview and two one-hour technical interviews. A third technical round was then requested, and the candidate was rejected despite being told the solutions were correct.
The coding questions that candidate recalled were Jump Game III, implementing a left outer join in a language of their choice, and a problem about returning the smallest number from a list after flipping digits. An internship candidate reported two roughly one-hour technical interviews at LeetCode easy-to-medium level, focused on string manipulation and basic data structures. That candidate said the interviewers cared about how they approached and explained the problem. Practice talking through your reasoning, and include at least one practical exercise, such as a join, alongside standard algorithm problems.
Behavioral questions in both reports centered on past projects, team situations and why you want to work at Tanium. Have two or three concrete project stories ready.
Timelines varied. One candidate reported about six weeks end to end, and the internship candidate reported about three weeks from phone screen to final round. Communication after interviews was uneven: the internship candidate heard nothing after the final round, so follow up proactively. Another candidate was told early that an internal hire had filled the role, so it is reasonable to ask the recruiter about the role's status.
Synthesized from 4 candidate 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 | |
|---|---|
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Random SQL Sample | |
| String Shift | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Top 3 Users | |
| Comments Histogram | |
| Raining in Seattle | |
| Minimum Change | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Flight Records | |
| Prime to N | |
| Upsell Transactions | |
| Download Facts | |
| First Touch Attribution | |
| Job Recommendation | |
| Daily Retention Summary | |
| Find the Missing Number | |
| Recurring Character | |
| Scrambled Tickets | |
| Hurdles In Data Projects | |
| P-value to a Layman | |
| Find Bigrams |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report starting with a recruiter call or phone screen after applying online or being contacted on LinkedIn. One candidate used this stage to learn the role had already gone to an internal hire, so it may be worth asking early whether the position is actively open.
One Software Engineer II candidate described a 30-minute behavioral interview, and an internship candidate described a 30-minute hiring manager conversation. Both reportedly covered past projects and why the candidate wanted to join Tanium, so prepare specific anecdotes rather than generic answers.
Candidates report one-hour technical interviews at roughly LeetCode easy-to-medium level. Reported questions include Jump Game III, string manipulation, a digit-flipping problem and implementing a left outer join. Interviewers reportedly wanted to see clear reasoning while the candidate coded.
One candidate was asked for an additional technical round and then rejected by email. The internship candidate was never given a decision after the final round. Reported timelines ran from about three to six weeks, so candidates may need to follow up with the recruiter.
