2.
1 When starting a new project, do you prefer to jump
straight into coding or do you spend time planning the
architecture first? Why?
A: "Being a 'Plan-First' person is a huge plus. It saves the team
from a lot of messy bugs and 'technical debt' later on."
• B: "It’s smart to focus on Architecture first. It might feel slow
at the start, but it makes the actual coding so much
smoother."
2.2 How do you choose which tools or technologies to use
for a project, and how do you handle the decision-making
process within a team?
• A: "Very professional. You’re choosing what actually works
for the project instead of just picking the 'coolest' new tool."
• B: "I like that you talk it out with the team. It’s better to weigh
the pros and cons together than to just decide alone."
3.1 In your opinion, which communication method works
best for team collaboration: using chat apps like Slack or
meeting in person?
A: "Using Slack or Discord for daily updates is a great time-
saver. It keeps the workflow fast and organized."
• B: "Good balance! Chat for the quick stuff, and whiteboards
for the big ideas. That's the best way to keep everyone on the
same page."
3.2 How do you explain complex technical concepts to team
members or stakeholders who don't have an engineering
background?
• A: "Good strategy! Focusing on outcomes instead of code
helps keep people interested and not confused."
• B: "I love the use of visuals. Most people understand a
picture much faster than a technical explanation."
4.1 If you notice an error in a senior's or a manager's work, how
would you approach them to provide feedback?
• A: "Using a 'Code Review' style is very smart. It keeps things
professional and focuses on the work, not the person."
• B: "It shows you have high integrity. You care more about
fixing the problem than being afraid of a boss or senior."
4.2 Do you work better with a boss who gives you a clear goal
and autonomy, or one who provides a detailed to-do list for
you to follow?
• A: "It’s great that you want autonomy. This mindset is perfect
for roles where you need to innovate and find better solutions."
• B: "You sound like someone who enjoys a challenge. A boss
who trusts you with a goal is usually the best kind of leader for
an engineer."
5.1 What strategies or techniques do you use to manage your
time and ensure projects are delivered on schedule?
• A: "Using the 80/20 Rule and Task Boards shows you are very
organized. Breaking things into 'Sprints' is a pro move."
• B: "I like that you try to avoid 'crunching' at the last minute. It
shows you know how to manage your energy for the long run."
5.2 When faced with a difficult problem near the end of the day,
do you prefer to stay late until it’s fixed, or rest and tackle it
with a fresh mind the next morning?
• A: "I totally agree. 'A tired brain leads to buggy code' is a
famous truth in engineering. It's better to be efficient than just
busy."
• B: "This shows you value quality. Coming back with a fresh
mind usually solves a problem in minutes that would take
hours at night.
6.1 How do you handle situations where team members have
different technical opinions or perspectives than yours?
A: "A very mature approach. Listening without bias is the key to
a healthy team environment and better technical results."
• B: "I love that you see different views as a way to avoid blind
spots. It shows you’re a team player who cares about the best
solution, not just being right."
6.2 Looking back at your journey in tech, what is the most
important lesson you have learned that will help you stay
relevant in this field?
• A: "Spot on! The 'Ability to Learn How to Learn' is the most
sustainable skill in a fast-moving field like tech."
• B: "That’s a great mindset. Technology changes, but having
the confidence to master new tools will keep you relevant
throughout your career.