ThousandEyes interview questions

I got contacted by the recruiter through an introduction from my peers. The whole process was made by four phases: recruiter phone screen, design challenge, technical phone interview, and onsite interview. Recruiter goes through my background and one portfolio piece during the initial phone screen. A design challenge received the next day after recruiter phone call. It is a very interesting and exciting design problem with some necessary contexts and specific expectations. I took 4 days to finish it. After submission, I got a call from the recruiter to schedule a phone interview with VP of Engineering. In this quick technical phone interview, I got asked some behavior questions around how to collaborate with different roles, deal with feedback; Also questioned some of my design decisions in the challenge submission. In the onsite interview, three one-on-one sessions with their designer, VP and CTO. The focus was my portfolio pieces and some critique for my chosen product. An onsite challenge was given after one-on-one sessions with different stakeholders. They picked one workflow in their product I’m interested, and give me some background and current use cases. I'm expected to go through a whiteboard session to show how I proceed the design and communicate concepts. Received the offer the next business day. The whole process is really smooth. The recruiter Steven did a fantastic job to collaborate the process, give me quick responses, and arrange logistics for the onsite interview. He always kept me in loop and help me prepare the interview! Super thanks! The team is quite friendly and shows respect for the candidate in a kind and warm way!

They first asked me for a code sample and some pretty standard intro questions over email. They then offered me a coding challenge that involved putting together a D3 project of medium complexity. I then went onsite to talk to them about my challenge and do some technical interviews in person. I felt that their interview process was both thorough and challenging. I got the impression that they have a high bar for admittance. So when they gave me an offer I accepted. It seems like a lot of people complain about coding challenges like the ones ThousandEyes gives to their applicants. I personally think that coding challenges are one of the best ways to test a software engineer's skill. Its best to evaluate someone's ability to do something by having them actually do it for you.