ThousandEyes Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 67 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at ThousandEyes.
ThousandEyes
Software Engineer
Senior Difficult Negative experience No offer 6 rounds
Interview process
Recruiter call Phone screen Onsite Onsite Onsite Background check Offer
Interview formats
Technical Coding System Design
It was a long and confusing process that didn't align with the prep materials I received. The recruiter suggested I was eligible for multiple roles, but the interviewers seemed unaware of this. My questions weren't really answered, and the interviewer kept interrupting during the screen. The question was very long and about tech I rarely use. I'm not sure my solution worked because the interviewer was confusing, and I have no idea how I got to the onsite. Onsite 1: The interviewer wasn't a good communicator, which would have made me hesitant to accept an offer since he would have been a teammate. Onsite 2: We went 30 minutes over due to technical difficulties. The person was nice, but usually, I have many interviews, and luckily that day went okay. Onsite 3: They asked a lot of theoretical questions. When I asked for a reminder on how a specific Java feature worked, they weren't helpful. Only one person was actually from the teams I was interviewing for. I definitely wouldn't interview with this company again.
Confirmed questions5 questions
- What are your thoughts on designing our product?
- Can you use a custom tree to solve this problem?
- Here's a LeetCode company-tagged question for you.
ThousandEyes
Software Engineer
Entry Difficult Neutral experience No offer 5 rounds
Interview process
Technical screen Technical screen Technical screen Technical screen Onsite
Interview formats
Coding Coding System Design Behavioral
Had an initial Leetcode-style interview, then an on-site. The on-site had another coding round, systems design, and behavioral. I wasn't in a good headspace and bombed the first coding round. They let me schedule another coding round to "make up" for failing the first one (even though I passed the initial coding round). The "make up" round had a really vague question without example inputs/outputs, and even when I tried to talk to the interviewer about it, he gave me another requirement for the problem that totally changed my solution approach just 5 minutes before the end.
Confirmed questions2 questions
- Tell me about a Leetcode Hard graph problem, like Djikstra's with modifications.
- Can you design an "x"? This is a coding/DS&A question, not systems design.
ThousandEyes
Software Engineer
Senior Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite Background check Offer
Interview formats
Behavioral Technical Coding System Design
The interview process was super smooth, and everyone was really nice, which is great 'cause interviews can be stressful. I got feedback fast after each step, usually the same or next day. First, I had a casual chat with an engineering director about the company, a good chance to ask about the culture, projects, tech, and product. Then, there was a 1-hour remote interview with a coding exercise on data structures. The final stage was onsite, a full interview loop. I had to write code again, similar to the phone screen. The coding interviews were mostly about problem-solving skills rather than specific algorithms. They also included a system design interview with lots of follow-up questions, plus some behavioral and background questions. It was a really good experience overall. I got to see the office, had lunch with the team, and really felt the vibe at TE. They even gave me a t-shirt! I had other offers with similar pay, but I chose ThousandEyes because I liked the culture (friendly people, fun vibe), the tech stack (I got to ask tons of questions about frameworks, practices, and processes), the product (networking is something I want to learn more about), and the team's enthusiasm (which shows they like working there).
Confirmed questions8 questions
- Questions about data structures, algorithms, system design, and your background were asked.
- Tell me about your background.
- What are your thoughts on data structures?
ThousandEyes Software Engineer Interview Questions
Quoted word for word from ThousandEyes interview reports.
“Create a function to check if an IP address falls within a given subnet.”
Read reports →“Given a character matrix and a Dictionary.isWord(String s) API, return all valid horizontal/vertical words (not diagonal). For the matrix ['a','b','c','d'] ['t','p','q','x'] ['a','m','a','t'] ['d','a','c','d'], the output should be ["am", "dam","cat"]”
Read reports →“Implement depth first search and explain how to detect loops in a graph.”
Read reports →“Create tasks to measure the total packets transmitted and received on a designated network interface.”
Read reports →“Create tasks to measure the total virtual memory size and its current utilization.”
Read report →“Create tasks to measure the ICMP ping latency to a specified server (e.g., google.com).”
Read report →“Create tasks to measure the Time to establish a TCP connection to a server (e.g., google.com on port 80).”
Read report →“Create tasks to measure the amount of physical memory your specific process is using.”
Read report →“Could you implement a new data structure that supports set(key, value), get(key), last(), and delete(key) operations?”
Read report →Formats, difficulty and experience
Across all 67 ThousandEyes interview reports.