I would echo the "Overall, based on what I was told about the interview process, I felt underprepared" feedback someone else wrote. I had a rather negative experience where I had to use a specific coding language for the coding interview, which wasn't communicated beforehand. Nobody mentioned it; it wasn't in the prep guidance given to me. One line is all they needed to add. I had onsite interviews last week at a JavaScript company, a Golang company, a Ruby company, and a Java company. Each team used different languages. Do I assume they all require me to use their specific language? Of course not.
Nobody else in the industry cares what you use -- even Haskell / functional programming companies. That is why I should have been informed -- ahead of time -- that I needed to use their language. Why did I spend an entire hour in a coding interview that -- within the 1st 5 minutes -- I had doomed myself to fail by not using their language? Because the interviewer was extremely friendly but, I think, too agreeable for what the situation required. The right thing to do would have been to stop the interview and tell me I needed to use their language; I would have said I hadn't written in it in months and needed to refresh and re-schedule. If I knew what they wanted and failed, that would be fine. I would have learned something and improved my craft. Instead, hours of my time were wasted talking to them.
I won't give specific questions, I want to respect the company.
The following metrics were computed from 3 interview experiences for the Chainlink Labs Senior Software Engineer role in United States.
Chainlink Labs's interview process for their Senior Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Chainlink Labs's Senior Software Engineer interview process in United States.