"Why should we hire you?"

This is another of those questions everyone interviewing hates.

It spread from traditional jobs into the tech world, and even software developers have to deal with it.

But you can turn this into a huge win. Let's see how.

A thread. ↓
1. Why is this question asked?

Like any of those pretty cliché questions regularly asked in interviews, interviewers try to find out whether you are a good fit.

Your hard skills might have been assessed already or will be soon, but this one is about your character.

1/32
Even before the term EQ (emotional intelligence) became popular, there was more to employees than only the skills they brought with them.

People are human. They have a character. And they need to get along with other people.

2/32
What interviewers try to assess here is how good you can sell yourself.

And even more, they want to find out HOW you sell yourself.

Interestingly, it can tell you a lot about someone else when you listen to how they talk about themselves.

3/32
Is the candidate super arrogant? Are they introverts? Don't they find the words to describe themselves? Do they only speak in superlatives?

Yea, you are somehow being profiled when you are asked to answer this question.

4/32
With the answers you give, experienced HR managers can create a rough profile of you.

They see whether you fit into the company culturally and how well you would fit into certain teams.

5/32
It also tells a lot about how interested in the company itself you actually are.

If you only talk about how awesome you are but never even mention how awesome your work would be for the company and how much you would like to contribute, you make a bad impression.

6/32
2. How to deal with this question

If you want to make the most out of this question, you should do these two things:

1. Prepare yourself before the interview
2. Listen to the interview(s) closely, up to the point this question is asked

7/32
-> Prepare yourself before the interview

Your goal is most likely to get this job or to see at least whether it is really something for you.

No matter what your motivation is, prepare yourself as if you really wanted to get this job.

8/32
If you find out that you actually want this job during the interview, you might be unprepared for a question like this and thus not come up with a great answer.

No one likes missed chances. Especially not if they could have been avoided.

9/32
What you should do:

1. Write down what you really look for in a job
2. Double-check the job ad and see how good of a fit you are
3. Check the company's background: What do they do? What do they tell about themselves?

10/32
4. Look for company reviews on the internet, both from customers and employees
5. Use a table or another form of notation to compare who you are with what the company is
6. Craft an honest story that references the most important points where you and the company match

11/32
This might seem much now, but let's go over it:

You should first make clear for yourself what you are really looking for.

- What would make you go to work every day?
- What would keep you motivated?
- What does a job have to offer you, so you are happy?

12/32
Then see what the company states it is looking for. This is usually the job ad.

Keep in mind that those are never really perfect and should not be taken as the whole truth. But they are a good indicator.

13/32
Next, look up what the company really stands for.

- How do they represent themselves?
- What image do they present, and what do they do for society?
- What are their values?

You want to make sure that your values align with theirs.

14/32
Marketing is one thing, but the truth usually lies deeper.

A company can write anything they want on their website and in press releases. But what do customers and employees say when they review the company? Is there more you can learn about them?

15/32
The next step is a little more difficult.

You should somehow try to find out how well the company and you align.

Do you match their criteria, and do they match yours?

16/32
A table, like a pro/contra list, can help. But perhaps there is something that works better for you.

Just make sure you have something written somewhere, black on white, so you don't try to cheat yourself.

17/32
With all this information at hand, you can craft a story about why exactly YOU are a good fit for the company and why they should hire exactly YOU.

This story should answer:

What do you bring to the table that helps them, and what can they do for you?

18/32
Feel free to write multiple sentences already. This helps you learn the core of it up to the point that you could also answer this question freely during the interview.

If bullet points serve you better, that's also fine.

19/32
-> Listen to the interview(s) closely, up to the point this question is asked

Interviews usually bring up a lot of additional information you didn't know about previously.

Perhaps you couldn't find it online, or it simply wasn't there.

20/32
I can only recommend you take notes during an interview.

This way, you have all this information at hand when you need it.

Perhaps the interviewer tells you about an employee education program that they didn't list on their website.

21/32
Or perhaps they tell you about their engagement in local communities, or even better, a new field they want to get their feet wet in.

If something is interesting for you in it, definitely use it to your advantage.

22/32
As soon as the question of why they should hire you comes up, you can use exactly this as one of the reasons they should hire you.

You can sell them your honest interest in a certain topic as a reason to hire you.

Why? Because it shows your ambition.

23/32
--> An example

"I can give you several reasons why you should hire me. First of all, I tick many boxes regarding hard skills as I have some extended experience. For the rest, I can assure you that I will quickly catch up with these.

24/32
I've already shown that I am a fast and avid learner in the past and I plan that this won't be any different at your company.

The next reason is that I deeply care for the cloud. Most of my personal work is based on it.

25/32
I would love to bring my expertise in this field into the company and see whether I can help you advance there further. I would even go so far as to say that I am very motivated to become a core contributor to this field in your company within the next two years.

26/32
Another reason is your engagement with your local community. I also regularly engage in my local community and think that our values align perfectly here. Perhaps I could help with my expertise and could equally learn from yours.

27/32
During our interview, you mentioned that you currently try to rebuild your education program. As a content creator on the internet, I would really love to help with my expertise. I think I can contribute a lot to this area.

28/32
And lastly, I believe that we have had an awesome interview so far and seem to align quite well. For me, we seem like we fit well culturally, and I'd love to be able to thrive in the one that you carefully built."

29/32
This is only an example, but it should give an interviewer nearly anything they could ask for.

1. It gives them not one but multiple reasons to hire you
2. It shows your ambition
3. It showcases your interest to contribute
4. It states you listened to the interview

30/32
Keep one thing in mind: Your answer doesn't need to be perfect. But it should tick many of the boxes interviewers are looking for.

Sell yourself as the best hire and make sure they understand that you think they are the best company for you right now.

31/32
3. Thread end

That's it for this thread. You made it to the end. 💛

I hope you learned something useful for your next interview! 🙏🏼

If you enjoyed reading this thread, leave a like, retweet the first tweet, and follow me (@oliverjumpertz) for more content like this.

32/32

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Oliver Jumpertz

Oliver Jumpertz Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @oliverjumpertz

21 Jul
"Why do you want to work here?"

"Well, I am a web developer, and you are looking for one. Additionally, I need the money."

Some interview questions are stupid. But giving answers like the one above doesn't help.

Let's see how to tackle this one effectively.

A thread. ↓
0. Foreword

I've interviewed quite a few times in the last few years, and I also had the honor to interview a few outstanding software engineers.

I witnessed this question many times, although I never asked it myself.

1/23
I don't particularly like this question, and I love companies that simply throw such questions into the bin.

But, there are still companies out there asking questions like this one.

And this is why you should be prepared for it and the reason I share this with you.

2/23
Read 24 tweets
20 Jul
"How would you rate your JavaScript (or XY) skills on a scale of 1-10?"

This one is another tricky question that can cost candidates in job interviews some nerves.

Let's face it, most of us find it dumb.

But you can turn this question into a massive win for you.

A thread. ↓
1. Why is this question asked?

You could go ahead and call it dumb now, but there is more to it than only the sheer will to bring candidates to sweat during interviews.

It serves a purpose.

1/38
Such a question might not be the best question or even way to get this kind of information, but it exists, and from time to time, you will have to face it.

And if you want this job, you need to deal with it.

You somehow have to tackle it and deliver a satisfying answer.

2/38
Read 39 tweets
18 Jul
Did you know that Math.max() < Math.min() in JavaScript?

It's a fun fact about the language that is periodically brought up, but do you know why this actually happens?

Let's take a quick look at Math.max and Math.min to understand the issue.

A thread.
1. Is this a quirk or a bug?

No, it is neither a quirk nor a bug.

There are two things you need to realize first:

1. Math.max and Math.min are functions
2. JavaScript is dynamic

1/21
-> Math.max() and .min() are functions

Both functions are actually not meant to return any maximum or minimum displayable value for numbers.

Both are meant to find the max or min value from:

1. Two arguments
2. An array of values

2/21
Read 22 tweets
18 Jul
Did you know that calling yourself something like "Junior JavaScript Developer" on your CV and socials is one of the worst things you can do for your career?

It immediately strips away a lot of your credibility and can often even close some doors.

A thread.
1. What is wrong with this title?

It might seem perfectly fine to call yourself what you think you actually are, but it is not.

It describes yourself too specifically, and it shuts some doors for you.

1/15
This title is one of the first things a recruiter or an interviewer sees on your CV, and it already tells them a lot about you.

This is your description. It is a short, concise statement about who you are and what you do.

It should state: "This is who I really am."

2/15
Read 16 tweets
17 Jul
"Where do you see yourself in five years?"

This is still a common job interview question.

But do you hate it as much as I do and would love to stand up and simply leave immediately?

Don't.

Here is how you can turn this question into a huge win.

A thread. ↓
0. Foreword

I've interviewed countless times in the last years and had the honor to interview some amazing engineers myself.

I never used this question myself but had to witness HR ask exactly this one.

1/40
It took me a good amount of time to understand that, while being a question most interviewees hate, it's an HR trick to gather valuable information.

2/40
Read 41 tweets
17 Jul
Debugging 101

1. Start your debugger
2. Trigger an action
3. Skip the first 10 breakpoints you forgot to remove last time
4. Realize you forgot to set a new breakpoint
5. Abort
6. Set a new breakpoint
7. Retrigger the action

👇🏻
8. Sigh because you need to skip the 10 first breakpoints again
9. Realize you accidentally also skipped your new breakpoint
10. Retrigger the action
11. Skip and remove each of the first 10 breakpoints you forgot to remove once again
12. Stop at the right breakpoint

👇🏻
13. Stare at your screen and think
14. Realize you should have set the breakpoint earlier
15. Abort
16. Set a new breakpoint
17. Retrigger the action
18. Stare at your screen again
19. Think and cry a little
20. Take a break

👇🏻
Read 4 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!

:(