"What is your current salary" is one of the most common questions you'll be asked in an interview.

But you should never answer this question and be ready to accept they might not choose you anymore.

Here is what you can do to deal with this question.

🧵⏬
1️⃣ The Reason This Question Is Asked

The reason for this question is pretty simple. Salaries are one of the hugest cost factors for companies, and minimizing those is one of their main goals.

Why should a company pay you 200k if your previous salary was only 120k?
Well, that's at least their reasoning. Especially when your previous and future tasks are comparable, why should you magically be worth so much more?

Having a number at hand makes it pretty easy for them to negotiate with you. A little more salary is okay but too much? Nah!
If you give them a number, they pretty much got you. They'll be able to determine what to pay you to still be attractive for a job switch, and always have a reason for why they won't pay you more.
2️⃣ How To Deal With This Question

Never. Ever. Answer. This. Question. Period.

And never ever lie about your previous salary.

As already said, if you answer this question, they got you, and if they catch you lying, you're done, as well.
Really: Politely deny answering this question.

If they still insist on getting an answer because they "can't go on with the process without an answer" or whatever they come up with, still deny the answer.

Better try to circumvent an answer to this question as best as possible.
Better say something like this:

"Sorry, I can't talk about my current salary, but in my current job search, I look for jobs with a salary range of $x.y k and $z.a k, and I think that the experience and knowledge I bring with me is well worth this investment."
And if you haven't talked about a salary range already, feel free to add: "Does this position provide a salary range that is close to my expectations?".

If the company can't accept you not answering: Be ready to drop out of the process!
It's better to get paid what you deserve and could fairly negotiate for than to accept being underpaid greatly because you simply made the mistake of making your current salary transparent.
3️⃣ Conclusion

This one question is one of the most important ones in an interview, as it can have such a large impact.

In my opinion, it's a huge mistake to ever answer this question as it gives too much power to your potential future employer, and takes away ...
... a lot of your own power.

You won't be able to negotiate for what you're really worth after answering it. Circumvention of this question does, however, often work. It may sometimes not, but then ask yourself: "Is this really a company I want to work for?".

• • •

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

8 Jan
The moving average is a calculation to analyze data by creating a series of averages (from subsets ) of it.

Especially in finance, the moving average is used a lot to give buy or sell signals for stocks.

Let's take a look at it and implement it in JavaScript!

🧵⬇️
1️⃣ The Moving Average (MA)

As you've already read, the moving average is a method to analyze data.

It is, more specifically, usually used to identify trends, especially in finance, but you can also apply it to house prices, or else.
The moving average is calculated over a specific time-span which is customizable to your liking. You can calculate it for 10 days, 20 days, etc.

Common intervals are

- 10
- 20
- 50
- 100
- 200

with a variable unit (minutes, hours, days, etc.).
Read 36 tweets
19 Dec 20
AWS Lambda recently added container support.

We're going to look into what this offer actually includes and how we could build a containerized Lambda function ourselves. 👨🏻‍🏫

Start your IDEs and open your AWS consoles because we're going in!

🧵⏬
1️⃣ AWS Lambda Previous To Container Image Support

Until recently, AWS Lambda only allowed you to write some code and upload a zip-archive containing all files necessary to run your function.

Some frameworks eased up this process, but that's how it went.
Lambda also imposed some pretty strict limits, especially the 50MB default deployment size limit.

You could circumvent this limit, technically, by pulling more deployment dependencies from S3 or by issuing an AWS Service Limits support request. But this wasn't the most...
Read 32 tweets
18 Dec 20
AWS Lambda is an awesome offering. You provide the code, AWS handles the infrastructure and execution for you.

But where is your code actually executed? How does AWS do it?

I recently tried to find it out for myself, and this thread is the result of what I learned!

🧵⏬
1️⃣ Thinking about Lambda

We know that we can write a script that looks like below, and then upload it to AWS while they take care of everything else.

And from simply looking at the code, it doesn't look like the usual API method we'd implement in Express.
We're exporting a function, so something else must take our code, import it, and then handle everything else. 🤔

Conclusion number one:
Something must run our code.
Read 29 tweets
17 Dec 20
Five Node.js web frameworks you could use to build your next API!

🧵⏬ Five Node.js web frameworks you could use to build your next
1️⃣ express

This is the classic and by far the most popular Node.js web framework.
It's fast, has a minimalistic approach, and doesn't get in your way.

You'll find the most tutorials for express, but it's still relatively easy to learn.

github.com/expressjs/expr…
2️⃣ koa

koa is quite similar to express, but tries to give you more freedom and less complexity.

It has a middleware stack that flows in a stack-like manner, allowing you to perform actions downstream then filter and manipulate the response upstream.

github.com/koajs/koa
Read 6 tweets
17 Dec 20
Here are three free ebooks to help you with leveling up your JavaScript skills!

🧵⏬
1⃣ Eloquent JavaScript

Eloquent JavaScript is pretty good at giving you a lot of examples of how to not use JavaScript.

If you try to improve your overall skills and learn how to actually use JS, I can recommend this one!

⛓️ eloquentjavascript.net
2⃣ You Don't Know JS

This is the first (complete) installment of the series, with a second one on the way.

If you're looking for a great book to dive into JS, this one's definitely for you.

⛓️ github.com/getify/You-Don…

⛓️ github.com/getify/You-Don…
Read 4 tweets
14 Dec 20
What actually is a Pod in Kubernetes?

If you ever read at least a little about Kubernetes or followed a simple tutorial, you must have come across the term "Pod".

In case you're still wondering what it is, this thread is for you!

🧵⏬
1️⃣ What is it?

A Pod is the smallest deployable unit in Kubernetes.

It's a group of one or more containers that form a logical local host. They share their storage, their network, are always co-located and co-scheduled.
The most common use case is having a Pod with exactly one container. Having multiple containers within a Pod is usually a pretty advanced use-case.

So, naively spoken, a Pod is often only a wrapper around one container.
Read 20 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!