You’re in for a technical interview. They ask you a question, and you have to build a system or to write some code, either on a whiteboard (brr!), on a piece of paper, or on a laptop at home. And then you discuss it with the interviewer.
Some enjoy it, and some dread it. But if you are going through it, it means the end of the process is near! And you really want to show the best side of yourself.
I led more than 120 interviews. Here are some common mistakes I noticed the candidates make.
Continue reading “11 Mistakes To Avoid On A Technical Interview”
Many developers tell what they have done. They used Kafka, RabbitMQ and Kubernetes. They sharded, scaled and clustered. They moved the logic from monoliths to microservices. They built castles and teared down mountains.
What they often don’t say is why they did it.
I often ask this question on interviews:
“What is the most interesting or challenging task you have ever done?”
The answer tells me a lot.
Continue reading “How to answer the question “What’s the most challenging task you have ever implemented?””
How to understand if this company is a good fit for you? Why, ask them questions, of course!
I’ve been on both sides of interviewing for a while now. As a candidate – for 9 years, and as an interviewer – for 90 interviews. (What a beautiful round number!)
So I decided to write down questions which I usually ask the company when considering their position.
Continue reading “Top Questions Every Candidate Should Ask on An Interview”