A job interview is a strange situation. On the surface, it is supposed to be a normal conversation about cooperation. In reality, it often feels like an exam that decides the next chapter of your life. And honestly, I understand why. Very often, what is at stake is a career change, a promotion, a transition into a new field, or simply getting out of a place that no longer makes sense.
What surprises many people is that interviews are rarely lost because of missing technical skills. Much more often, they are lost because of answers to so-called “soft” questions. The obvious ones. The predictable ones. The questions that come up again and again.
In this article, I walk through nine of the most common interview questions and explain what they are really about. Not textbook answers. Not HR clichés. This is the perspective of someone who has been on both sides of the table and has seen how easy it is to ruin a good interview for completely unnecessary reasons.
Why are you changing jobs?
This is the classic opening question. Almost guaranteed to appear.
What the recruiter is really asking here is not whether you had a bad manager, boring projects, or low pay. They are looking for continuity. People hiring want to believe that your career tells a reasonably coherent story, even if you personally know that it was full of accidents, sharp turns, and decisions made because “that was the best option at the time.”
A good answer frames the new role as a logical next step in your development. You show that you have already learned something, delivered value somewhere else, and now want to move forward. Even if deep down you feel like you are escaping, during the interview it is much better to talk about moving toward something.
Complaining about previous employers or teams is almost always a mistake, even when you are right. The recruiter has no way to verify your story. What they see instead is risk.
What was the most difficult part of your previous job?
This question is tricky because it is dangerously close to complaining.
But that is not the point.
The recruiter wants to see whether you can identify a real challenge and explain how you dealt with it. The difficulty might have been communication, time pressure, unclear requirements, or lack of structure. What matters is not who was to blame, but what you did.
In practice, it is worth having one solid story prepared. Something realistic that you can tell smoothly under stress. Not a memorized speech, but a story you know well enough not to improvise badly when emotions kick in.
What are your greatest strengths?
This question tests two things at once: self-awareness and team fit.
Recruiters are not looking for the “best person alive.” They are looking for someone who complements an existing team. If the team is very technical, they might need someone who can communicate well with non-technical stakeholders. If the team is strong on communication, they might need someone who enjoys working deep in the data.
That is why generic answers like “I am ambitious” or “I learn quickly” are rarely helpful. It is much better to talk about concrete skills and behaviors. For example, acting as a bridge between business and tech, structuring messy data, or translating requirements into workable solutions.
Honesty works surprisingly well here. Pretending usually becomes obvious much faster than people expect.
What are your weaknesses?
This question causes a lot of anxiety and is often misunderstood.
The recruiter is not asking you to pretend you are perfect, nor are they asking for a dramatic confession. They want to see whether you are a normal, self-aware human being who understands their own limitations and can manage them.
Good answers focus on common, realistic challenges and show coping mechanisms. Pressure, distractions, prioritization. These are things almost everyone struggles with at times.
When a recruiter hears something they personally relate to, trust increases. And trust is one of the most important currencies in an interview.
Tell me about a situation where something went wrong
This question is about responsibility.
Nobody wants a dramatic story full of self-blame. A short context is enough. What matters is that you take ownership and explain what you learned.
Professional maturity means being able to say: “This was on me. I learned from it. I do it differently now.”
How do you deal with unclear requirements?
This question tests communication skills and proactivity.
Asking questions is not a weakness. Quite the opposite. Mature managers prefer people who clarify things early rather than quietly building the wrong solution.
At the same time, it is important to show independence. You should communicate that you try to solve things on your own first and ask questions when they actually matter. It is about balance.
How would you explain this to a non-technical person?
This is one of my favorite interview questions.
On one level, it checks whether you truly understand the topic, not just the definitions. On another level, it reveals your attitude toward non-technical stakeholders.
Good professionals can explain complex topics in simple language without sounding arrogant. Bad professionals hide behind jargon and superiority.
In data roles, this question comes up a lot. Business users see the final result, not the complexity behind it. Being able to explain why “just one more column” can mean days of work is a critical skill.
Which technologies do you enjoy working with?
Despite appearances, this is not a passion test. It is a flexibility test.
Most companies are not looking for revolutionaries. They want people who can work effectively within existing processes and gradually improve them.
A strong answer usually includes one main technology you feel confident in, plus a clear signal that you are open to others. Specialization combined with flexibility is a safe and attractive combination.
Where do you see yourself in 2–3 years?
This question can feel unfair, but it is very common.
Recruiters are not expecting a precise life plan. What they want is reassurance that you are not planning to leave after six months and that your ambitions roughly align with the company’s reality.
Talking about growing within the role, deepening expertise, and gradually taking on more responsibility is usually enough. No big declarations. No dramatic visions.
Why preparation matters more than people think
These questions are not random. Each of them tests something different: maturity, communication, responsibility, self-awareness. Lack of preparation often causes very competent people to perform far below their actual level.
That is why I always say: interviews are not the place for improvisation. They are the place for consciously telling your story.
If you are thinking about changing jobs, transitioning into data, or simply moving forward professionally, preparing for interviews is just as important as learning SQL, Power BI, or Python. Technical skills matter, but without the ability to present them properly, they are often not enough.
Final thoughts
Job interviews do not have to feel like a minefield. Most “difficult” questions become much easier once you understand what is really being tested.
If this article helped you, feel free to share it with others. The more people walk into interviews calmer and better prepared, the less unnecessary stress there will be along the way.
The article was written by Kajo Rudziński – analytical data architect, recognized expert in data analysis, creator of KajoData and polish community for analysts KajoDataSpace.
That’s all on this topic. Analyze in peace!
Did you like this article 🙂?
Share it on Social Media 📱
>>> You can share it on LinkedIn and show that you learn something new every day.
>>> You can throw it on Facebook – and perhaps help a friend of yours who is looking for this.
>>> And remember to bookmark this page, you never know if it won’t come handy in in the future.
You prefer to watch 📺 – no problem
>>> Subscribe and watch my English channel on YouTube.
Prefer to read in Polish? No problem.
Other interesting articles:
