QUESTIONS TIPS FOR ANSWERS

Tell about yourself ● Omit mentioning specific figures, like your age,
years of experience (unless you want to impress
with it) etc.
● Try to end each your answer with a topic that you
would like to be asked about in a next question
● Mention as many details/technologies from you
experience that correlates with the Client’s project
as you can

Example: My name is <Tetiana> and in recent years I’ve

been working as a <Frontend> Software Engineer, mainly
with <React>. I’ve been participating in a lot/a few projects
during my career. The last one, for example, was related
to...

What was the most challenging ● Try to remind really tough task that you might be
task for you recently/on your last even executed not on your own but you know
project/during your career? details of implementation

What is your working style? ● This question is usually asked to check whether
you are initiative or not/ able to ask questions first/
facilitate the process/ provide support when
needed etc.

Example: I can call myself a diligent and result driven

worker. Even though I treat myself as a perfectionist I do
not allow this to turn into the only goal on a project.
I am among those who try to find the most suitable
solution in specific circumstances and not the perfect one
from some perspective.
My work style is extremely flexible — working on so many
different projects required me to be adaptive.

What was/is the team ● Try to find as many parallels with the Client’s
composition on your project as you can - it will make him/her sure that
previous/specific project? you’ll be able to do the same again
● Tell not just the number of people but the roles
involved

What methodology have you ● As usually it is Agile/Scrum, try to point out the
used for the software major parts - e.g., Scrum ceremonies (Daily
development process? standups, Groomings, Plannings, Demos,
Retrospectives etc.) and their rules.
What would you change in the ● This question is usually asked to check whether
existing development process? you see the room for improvement and understand
how the process should work.
● Try to omit anything person- related
● In the worst case, try to use smth neutral, e.g.
introduce a new tool for tests that will help to
increase the coverage percentage etc.

What do you like the most and ● Each job has its pros and cons - the question is
the least about your work? asked to check whether you are idealist or see the
picture clear ‘without the pink classes”
● Among the things you like you may list ‘seeing the
result of your work’, ‘feeling of making somebody’s
life easier/more efficient/ etc.
● Among the things you like you may list ‘sedentary
workstyle’ but be ready to answer the next
question as to how you cope with it :)

How do you entertain/release ● You may tell about your hobbies or just tell how
yourself after work? you usually spend your spare time - walking,
having a picnic with friends, riding a bicycle etc.

How do you treat working ● This is a tricky question - naturally, nobody expects
overtime? that you will tell them how much you admire
working 12 hours per day. The question is rather
asked to check your sense of urgency and
readiness to contribute when it is really needed but
not planned.

Example: Well, I will not probably surprise you when I say

that I would rather not work overtime. But since the nature
of software development is such that it requires
sometimes to go the extra mile I would say that this
happened in the past and naturally will happen in the
future so I am ok with that happening occasionally.

What are your ● Quite hackneyed question but still better be ready
weaknesses/strengths? to answer it.
Denial is one of the worst mistakes you can make.
Everybody has some weaknesses, nobody is ideal.
So take a second and try to find the one at least :)
● Again, try to use something neutral or such that
does not influence your duties directly
For a developer, among weaknesses you may say
e.g ‘Spontaneity (you don't like to work
unprepared)’.
Be ready then to tell how you work on its
improvement.
● As a strength, vice versa, try to remember
something that directly relates to the duties
 expected. For a developer, it may be, for example,
‘attention to details’.
● Be ready to prove your strength with an example
from your past experience!