Santiago Profile picture
Aug 3, 2020 13 tweets 3 min read
Hey!

Let’s get you a better salary right away! Who doesn’t want a raise?

I’ve done this over and over again. I’ve sat at both sides of the table when talking about compensation, so hopefully, this 🧵 will give you a few ideas on how to proceed.

Let’s do this!

👇
* Disclaimer *

I suspect this advice is applicable across different disciplines, countries, companies, cultures, and situations. However, I can only speak for what I truly know:

- Tech Industry
- United States
- Small to Mid-Sized companies.

* End of disclaimer *

👇
A couple of misconceptions:

1. The budget for your position is set: No, most of the time there’s a bracket and ton of flexibility. Also, employers are willing to break the rules for the right people.

2. Employers have all the power: Bullshit. They are nothing without you!

👇
I know that talking about compensation with your manager is hard.

But if you are afraid of confrontation and aren’t willing to toughen up, you will not get too far.

So here is the first piece of advice:

Get over it and go ask! If you don't, you will get nothing.

👇
The second piece of advice? Don’t be nice during a negotiation!

Polite? Yes. Professional? Yes. Nice? No.

You need to be firm, assertive, and direct. “Nice” people come away with less money than the rest (look it up.)

Don't be the Fruit-Basket person!

👇
Third: Find leverage and put it right in your manager’s face.

Leverage is crucial. You want to strengthen your leverage as much as possible. You also want to understand your company’s weaknesses.

Leverage means that your Plan B is much better than your company’s.

👇
To strengthen your leverage:

1. Know your market value (look it up + ask recruiters)
2. Understand what you bring to the table
3. Find the right timing

Put all of these in a piece of paper.

Or take a look at this one I created for you (github.com/svpino/raise)

👇 Template letter to request ...
See that $94,375? I made that shit up, but you know what? You have a better chance of that figure to stick if you don’t go with exact, round numbers.

When you are precise, people think you did a lot of research, so you must be well prepared. Use that to your advantage!

👇
Understand that if you leave, your replacement cost is much more expensive than your current compensation.

Look up “employee turnover cost calculator”. That’s the barrel your manager is looking at if it doesn’t give you a rise!

Who is scared now, huh?

👇
If you wanna keep things simple, following the above advice should be enough to crush it.

But just in case you need a little bit more help, here are 15 quick tips:

1. Always ask for more of what you want
2. Be ready to concede on something
3. Don’t say yes at first

👇
4. Be willing to walk away (this gives you a ton of leverage)
5. Be confident!
6. Mention the past, but focus on the future
7. Don’t be pushy. But be firm
8. Emphasize what’s fair
9. Prioritize what you want
10. Don’t mention personal needs

👇
11. Stall. Don’t look desperate
12. Don’t threaten with leaving
13. I’ll repeat: DO NOT THREATEN WITH LEAVING
14. No, your employer won’t fire you if you ask.
15. If you don’t feel you have enough leverage today, work on it!

👇
Finally, here is the good news:

You have all the time in the world to prepare an air-tight case to get a raise. Your employer doesn't know it's coming, so use the element of surprise!

Take your time, prepare, and go and kick ass!

• • •

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

Keep Current with Santiago

Santiago 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 @svpino

Feb 21
Every recommendation to start with machine learning focuses on a few building blocks:

• Linear Algebra
• Calculus
• Statistics and probabilities
• Fundamentals of machine learning

But there's also a different way.

Let's talk about it: ↓
Many companies are dying to start applying machine learning to their businesses.

Believe me: I talk to many of them every week.

Their main problem: they don't know where to start or how to get it done.
If you are reading this, you are probably part of one of these companies.

Heck, for all I know, most employees out there work for a company that's in this situation!

The demand for machine learning professionals is enormous!
Read 25 tweets
Feb 19
Learning about containers will open many doors for you.

If you are a Machine Learning Engineer, containerization is a must.

For the most part, "deploying machine learning" has a lot to do with containers.
There are a couple of ways you can approach this:

Understanding how containers work, building blocks, the standardized API, etc.

Or, you can start with Docker, find a few examples of how to use it, and progress from there.
I've been deploying things inside Docker containers for years now.

I'm sure I can't explain most of the things happening behind the scenes.

Anyone with that knowledge is in a much better position, for sure, but that doesn't mean that I can't get my work done correctly.
Read 4 tweets
Feb 18
Applying dimensionality reduction Image
What’s your answer?
Based on the answers so far, this one seems to be easy.
Read 4 tweets
Feb 17
This is how I split machine learning projects:

1. Project scoping
2. Data definition and preparation
3. Model training and error analysis
4. Deployment, monitoring, and maintenance

Here are 33 questions that most people forget to ask.
"Project scoping":

• What problem are we trying to solve?
• Why does it need to be solved?
• Do we truly need machine learning for this?
• What constraints do we have?
• What are the risks?
• What's the best approach to solving this?
• How do we measure progress?
Still under "Project scoping":

• What does success look like?
• How is our solution going to impact people?
• What could go wrong with our solution?
• What's the simplest version we could build?
Read 8 tweets
Feb 8
If you look at this code and think the answer is False, you aren't alone.

Nevertheless, we are all wrong: it returns True.

Read on to see what's happening.

The clue here is the two consecutive operators next to each other.

Operator 1: ==
Operator 2: in

And we have "False" sandwiched in the middle.

The logical reaction is to parse the statement piece by piece. That's what I did.

But that's not how it works.
When it comes to answering this question, there are two camps:

1. Those who claim that "==" takes precedence.

2. Those who claim that "in" takes precedence.

Let's see what we get on both of these cases.
Read 11 tweets
Feb 6
Guess the output and don't cheat.

(This is Python) Image
If you pay careful attention you will realize the equal sign seems strangely elongated.

The reason is because it’s not an equal sign but an ==.

A font ligature causes this effect.

So, no assignment. It’s an equality.
If you are surprised about the answer here, look into “chained comparison” in Python so you can see how it works.
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

Don't want to be a Premium member but still want to support us?

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

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(