Recruiter call - 30 min First interview - 1.5 hrs Second and third interviews - 2 hrs

Usual initial screen.

First round consisted of writing code in Vim. It went very smoothly. We talked about experiences, and then I got to ask one of the devs about their current experience at Arista.

Second/Third rounds went terribly. It was a 2-hour, back-to-back technical round at the end of the day.

The interviewer was late and scrambled to set up the environment while clearly not being interested. They asked me surface-level questions. We rushed through the problem while they kept asking me questions about things irrelevant to the problem and about my experiences. Any question I asked about what they wanted for the API or things to account for was met with condescending remarks and another question.

Third round was right after the second and also started late. Somehow, I made it to the final round. The interview was disinterested and keen on asking "find the bug" tricks with C strings. The interviewer got frustrated as I was trying to find a bug, solved it for me, and then called it quits once it was the end of the day.

Two minutes later, I was told I "won't be getting the offer" by who I later found out was the hiring manager. They showed up late and dropped off the call quickly before I could ask if there was anything I could improve upon.

I mentioned this to the recruiter and was promptly ghosted.

Really poor interview experience, to be frank, especially since they reached out and shotgunned through the process. Churn and burn, I guess.

Implement a ring buffer in C.

Use gdb to debug this code.

Implement a stack without using memcpy() in C.

printf("%s', NULL)

What does this output and why?

Where's the 'a' string stored in memory? Can you print it out with gdb?

Find the bug.

code..

str[0] = "2";

code ...

return 0;