ThousandEyes logo

ThousandEyes Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 165 interview experiences · FREE TO READ

3.4 Rounds average
Average Typical difficulty
45.5% Positive experience

Which role are you interviewing for?

30 roles · 165 reports

Candidate interview experiences

First-hand accounts from people who interviewed at ThousandEyes.

Showing 4 of 165
ThousandEyes logo
ThousandEyes

Technical Account Manager

Sales · a year ago

Mid Average Positive experience No offer 7 rounds
Interview process
Recruiter call Phone screen Technical screen Take home Technical screen Onsite Panel
Interview formats
Behavioral Technical Coding

First, there was a Recruiter Screen for 30 minutes. Then, a 45-minute Hiring Manager Interview. After that, a 30-minute Team Lead Interview. We were given a Technical Assignment to complete in 5 days. Next, a 60-minute Technical Interview. Following that, a short 15-minute Director Interview. Lastly, a 60-minute Final Panel Interview.

Confirmed questions1 question
  • Can you explain the TCP 3-way handshake?
ThousandEyes logo
ThousandEyes

Software Engineer

Engineering · a year ago

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 logo
ThousandEyes

UX Researcher

Research · more than a year ago

Mid Difficult Neutral experience No offer 3 rounds
Interview process
Recruiter call Phone screen Onsite Panel
Interview formats
Behavioral Technical

First, I had a quick chat with HR over the phone. After that, they set up an interview with the hiring manager, which lasted about 45 minutes. He asked me a bunch about my past experience and my reasons for seeking a new opportunity. It felt a bit like a sales pitch too, as he was trying to get me excited about the role. Next, they scheduled a panel interview with the hiring manager, a PM, and another designer. They were curious about my collaboration skills, the research methods I typically employ, my tenure as a researcher, and my career aspirations. I think they might have expected a presentation of my work, but it wasn't explicitly stated in the invitation, so I didn't prepare anything specific.

Confirmed questions1 question
  • Describe your approach or go-to strategy when you begin a new role as a UX Researcher.
ThousandEyes logo
ThousandEyes

Software Engineering Manager

Engineering · more than a year ago

Manager Average Negative experience No offer 6 rounds
Interview process
Recruiter call Technical screen Onsite Presentation Background check Offer
Interview formats
Technical Coding System Design Behavioral

The interview process included a Hiring Manager interview, coding, design, best practices discussions, and an engineering manager interview, followed by a chat with the VP. The interviewers were highly competent, and while the stages were technical, they were manageable with strong software engineering fundamentals. There were some scheduling issues, with one interview needing to be rescheduled last minute due to illness, which was inconvenient as it was a face-to-face interview requiring travel. Despite these hiccups, the overall experience was positive, with verbal feedback indicating a favorable outcome. However, a chat with the VP, not originally on the schedule, led to a 2-3 week waiting period. Ultimately, the company decided to pursue internal candidates, terminating the process. This was disappointing after investing significant time in the interviews with 6 people. I'd advise candidates to confirm the company's certainty about hiring for the role early on.

Confirmed questions2 questions
  • Can you discuss some basic algorithms?
  • Can you discuss some basic design principles?

ThousandEyes 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

Create a bash script that, when given a directory, will substitute 'foo' with 'bar' in both file names and file contents, and then list the files that were modified.

Read reports

Could you tell me how many packets traceroute sends when it runs by default?

Read reports

Create tasks to measure the total packets transmitted and received on a designated network interface.

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

Write a Twitter-like API/service that allows for at least 4 requests: follow a user, unfollow a user, get a list of people following a user, get a list of tweets of the user (including self-tweets and replies by followers).

Read report

Create tasks to measure the amount of physical memory your specific process is using.

Read report

Formats, difficulty and experience

Across all 165 ThousandEyes interview reports.

Interview formats

Technical 29%
Behavioral 28%
Coding 22.7%
System Design 8.5%
Presentation 8.3%

Interview difficulty

Easy 12.1%
Average 63%
Difficult 24.8%

Candidate experience

Negative 43%
Positive 45.5%
Neutral 11.5%

Reports by job function

Engineering 110
Sales 16
Design 16
HR 6
Operations 5
Consulting 4