Huge waste of time. The interview process was the recruiter equivalent of "this meeting could've been an email."

Recruiter got back to me soon after I applied via Revolut's website, and we scheduled a phone interview. After breezing through some easy technical questions, I was asked if I was familiar with "SOLID" principles. I said I was not.

Recruiter said they were extremely important, but since he liked everything else I had to say, he said he'd give me time to read up on SOLID, and I could answer questions about it in another phone interview one week later.

So, I researched SOLID. Turns out it's just a bunch of principles of good OOP that I'd already been practicing for twenty years. I just didn't know someone had made an acronym about them.

I scheduled another phone interview with the same recruiter for the following week. I was prepared to be quizzed and tested on SOLID, but we talked about it for only 30 seconds.

Recruiter then pivoted to TDD and asked me if I was familiar with a specific aspect of it. When I told him I was not, he immediately said Revolut wouldn't pursue my candidacy because that experience was very important.

Can you guess which two things weren't even mentioned in the job description? That's right: SOLID and TDD.

Thank you, Revolut recruiter, for stringing me along for ten days. Maybe if you got your shit together, you wouldn't have so many open positions.

Which scales better, n or log(n)?

Is [data structure] linear or non-linear?

What is the time performance of a binary sort?