HNHacker News
TopNewBestAskShowJobs

JoshDoody

515 karma · joined June 6, 2014

Salary Negotiation Coach for High Earners: https://fearlesssalarynegotiation.com/coach

...and for Senior Software Engineers and Engineering Managers going to Big Tech companies: https://fearlesssalarynegotiation.com/coach/swe/

Author of Fearless Salary Negotiation: https://fearlesssalarynegotiation.com

Computer & Electrical Engineer, MBA

submissionscomments
JoshDoody··on Ask HN: Need help with job offer negotiation
"I'm not comfortable sharing my current salary. I look forward to this opportunity to add value to your team, and I want it to be a big step forward for me in terms of both responsibility and compensation."

If pressed on current salary:

"I'm not comfortable sharing proprietary information about how my current employer pays people."

If pressed on desired salary:

"I don't have a specific number in mind, and I look forward to hearing what you suggest since you know much better than I do what value someone with my skill set and experience will bring to your team."

JoshDoody··on Ask HN: How can I know what my market rate salary is?
Thanks for letting me know - I appreciate it. And thanks for vouching for my comment - it would be a shame if OP didn't see it. Cheers!
JoshDoody··on Ask HN: How can I know what my market rate salary is?
I devoted a chapter of my book to this topic, so I'll summarize my method here and then share a link to read that chapter for free.

I recommend a three-step process:

1. Estimate your market value in your industry 2. Adjust that estimate for your local region 3. Adjust it again for the specific company you're focused on

Each subsequent step will have less data available, but the data you do find will be more specific to your situation.

1. Your industry-wide market value

Starting at the industry level, there are four places I tend to point people: paysa.com, salary.com, payscale.com, glassdoor.com. Those tend to cover most industries pretty well. You can take an average of averages to get a decent baseline for your industry.

2. Your market value in your region

Once you have that industry-wide number, you should adjust it for your local region if you can. This helps to account for cost of living and local demand differences. You can reach out to peers at other companies or talk to people at local conferences to get this sort of info. (NOTE: Asking people what they make is taboo in the US, but you can ask in a roundabout way that works pretty well: "If someone with this skillset and experience were hired for this job at your company tomorrow, what do you think they would make?" People are more comfortable answering vague versions of the question.)

3. Your market value for a specific company

Finally, if you know someone doing the job you're interested in at the company you're interested in, you might be able to get more detailed information about that specific company's pay ranges. You might also know a hiring manager or recruiter at the company, and you could buy them coffee to learn whatever you can.

Once you've gone through those three phases, you should have a pretty good idea what your market value is.

Read more

You can read the chapter from my book Fearless Salary Negotiation here: https://fearlesssalarynegotiation.com/book/value

You can get a free guide, worksheet and short video course to walk you through the process here: https://fearlesssalarynegotiation.com/how-to-estimate-your-m...

JoshDoody··on Software Developers: how to get a raise without changing jobs
This can be an effective tactic (meaning it could get you a raise), but it's not my preferred method. I prefer to focus on the situation itself without bringing in that sort of leverage because of the impact it can have on the way you're perceived at your company, by your manager, by your teammates, etc.

This strategy can work, but it's a little riskier than focusing on the value and working with your manager to align your salary with that value.

JoshDoody··on Software Developers: how to get a raise without changing jobs
Yep! If you're near the top of your pay grade, then there may not be much room to move up with a raise and a promotion might be the best way to go. Hard to know that without talking to your manager though. Managers will often hint at this by saying something like, "There's just no room to bump you up in your current job." That's a signal that pursuing a promotion might be the better way to go.
JoshDoody··on Software Developers: how to get a raise without changing jobs
This can be true when companies have a "focal" process where everyone is reviewed at the same time. If that's true at your company, your best bet is to shoot for an off-cycle raise (6 months out from that "focal" process) when there's a separate budget or possibly no fixed budget.

I wrote more about this here: https://fearlesssalarynegotiation.com/do-you-have-to-quit-yo...

Sometimes you have to quit. But it's worth pursuing an off-cycle raise and coordinating with your manager to see what's possible.

JoshDoody··on Software Developers: how to get a raise without changing jobs
Just saw a huge spike in traffic from HN and thought I would stop by to see what all the fuss is about. Glad to see people reading the article and having a productive conversation in the comments.

Happy to answer questions if you have them, and I'll hop into the comments as well.

JoshDoody··on Show HN: “How do I know it's the right time to ask for a raise?” (free course)
It's reasonable to look for a decent raise around 1 year in. But that means you should start planning—setting your goal and building your case—about six months before that so you know what you're aiming for and so you can consciously accomplish things to justify that goal.

So I recommend that you start planning for your first raise about 6 months after you start at a new company, and ask for your first raise about 1 year after you start.

Good question!

JoshDoody··on Show HN: “How do I know it's the right time to ask for a raise?” (free course)
Employee performance reviews are coming up early next year, so I wrote this free course to answer common questions people have about how to know the right time to ask for a raise.

I'm happy to answer any questions about getting a raise or about the course. Ask away!

JoshDoody··on Show HN: A class to help you optimize your salary like you optimize your code
If you have any questions, please ask away! I am hoping for constructive feedback on this class idea (that's why it's a "Show HN").
JoshDoody··on You don't have to accept or decline a job offer
This is a pretty common misconception about salary negotiation—that the company will retract the offer if you negotiate. But it's extremely rare and you're much better off negotiating than worrying about such a rare occurrence.

The worst-case scenario is usually just that the company doesn't budge on their offer.

By the time you're far enough into the process to get an offer, the company has invested significant resources to determine if you're a good fit and someone they want to bring on board. They're not going to forfeit all of that investment just because you say, "Thanks for your offer. If you can do [thing you're negotiating], then I'm on board."

I wrote about this and other common misconceptions about salary negotiations here: https://fearlesssalarynegotiation.com/why-you-should-not-neg...

JoshDoody··on Show HN: This guide is all you need to know about salary negotiation
You beat me to this one with a great answer.

I would only add that a big reason not to name a number is that you're guessing at what they might be willing to pay. So even if your plan is to anchor high, you're guessing and you might miss. You might THINK you're anchoring high when you're actually guessing a number that's relatively low in the range of salaries they're willing to pay.

You gain a lot of information by waiting for them to make an offer.

JoshDoody··on Show HN: This guide is all you need to know about salary negotiation
Excellent, thank you for your feedback. I've updated the main Table of Contents so that when you click eg "Chapter 1. How companies manage their salary structures", you're taken to the beginning of the chapter's content rather than an overview of the concepts in the chapter. I see how this is better.

Previous and Next are a little trickier to address, but your feedback helps me see how it can be confusing. Thank you!

JoshDoody··on Show HN: This guide is all you need to know about salary negotiation
Thanks very much for the suggestion. I appreciate it!
JoshDoody··on Show HN: This guide is all you need to know about salary negotiation
Thank you for the feedback - I appreciate this and it gives me some great ideas to experiment with.

I built it this way just because that's how I think of the negotiation process—a series of discrete steps.

Can you elaborate on why it's difficult to find the "next" link? You mean the breadcrumbs make it hard to find the right link? Or placement on the page is challenging? Both?

Thank you again!

JoshDoody··on Show HN: This guide is all you need to know about salary negotiation
After my recent discussion with @patio11 (https://news.ycombinator.com/item?id=11830598) and the great we got, I decided to make my book free to read online.

I'm happy to answer any questions you may have. Cheers!

JoshDoody··on Salary Negotiation
Excellent question. I have lots of thoughts, so I'll try to summarize.

1. This is just the reality of negotiation: sometimes you'll find out you're pretty far apart when they finally make an offer. The value of your time matters, but in general I think the payoff when you DO command top dollar at a good company is worth the time investment. (Think of this from a Sales perspective - they deal with hundreds of leads, often narrowing them down to the best-qualified leads and closing only a few deals. That time working with unqualified leads is not wasted per se, it's an investment to get to the good leads where they make their money.) 2. Signaling is important and you should continuously do this throughout your interview and negotiation process. My one-sentence strategy summary for interviews is "You're telling them a story about how their company will be better if you're a part of it." Your job in the interview processes not to save time—it's to get the best job offer possible so you can negotiate or walk away if it's not a good fit.

I realize this is controversial, but I think it's best to not think of interviews that don't lead to job offers as time wasted, but as time invested in finding a good fit. If you're interviewing for a huge volume of jobs that always end with an offer far below your range, you may want to evaluate whether you're applying to the right jobs. But if you occasionally interview and find out that they can't met your pay requirements, you can just move on to the next opportunity.

One last thing: Make sure you're doing market research to determine the value of your skillset and experience in your industry. If your market research confirms your salary expectations, then keep interviewing. If it doesn't, then it's possible you're at a company that really values your work and you might consider the opportunity cost of leaving.

Does this help? If I can clarify anything, let me know!

JoshDoody··on Salary Negotiation
I completely understand what you're saying: This is exactly why I wrote my book and courses, and why I offer 1-on-1 coaching. And I focus very heavily on providing real tactics, templates, worksheets, scripts, and examples to make the process as transparent as possible.

For example, we talk about "The Dreaded Salary Question". Here's an article I wrote that discusses this question in detail along with what to expect and exactly how to respond: https://fearlesssalarynegotiation.com/the-dreaded-salary-que...

And we go into more detail in this episode.

To put a finer point on it: A lot of the reason I created Fearless Salary Negotiation is specifically to address the factors you mentioned. It's why a lot of my examples in the book involve software developers and related topics.

If I can clarify or elaborate on anything that was vague in the episode, please let me know so I can give more detailed information!

Thanks for your comment!

EDIT: I am on the fence about this, but I think it's extremely pertinent here. I mentioned I coach people and this is a big reason why. If you're a software engineer and you're tentative about negotiating, I can help you. https://fearlesssalarynegotiation.com/coach

JoshDoody··on Salary Negotiation
I don't mind one bit. Thanks for posting this!
JoshDoody··on Salary Negotiation
Hi everyone! That's me you hear talking to Patrick ;) If you have any questions about the episode or salary negotiation in general, ask away! As you can probably tell, I love talking about this stuff!
JoshDoody··on Salary Negotiation Counteroffer Calculator and Sample Script
Just wanted to say thanks for the kind words about the book. I'm glad you liked it!
JoshDoody··on Salary Negotiation Counteroffer Calculator and Sample Script
Good question.

- The main assumption is you should counter and we're just figuring out the right amount. - It's assuming that you will not take the job for less than your "minimum acceptable salary", so that's basically the floor for your counteroffer. - It's assuming you'll counter between 10% and 20% above the job offer you receive. This is based on my own experience negotiating salaries and my background working with companies to develop and leverage their compensation structures.

It accounts for the two 0–10 questions to dial in your specific counter in that 10–20% range I mentioned above.

Once you hit the big "Show my counteroffer!" button, it also updates the "3. Prepare for your final discussion" section of the page to reflect your preferences (like which benefits you value most).

The idea is you could literally be on a call and get a job offer and then use this tool to calculate your counter and navigate the negotiating process.

JoshDoody··on Ask HN: How much do you make at Amazon? Here is how much I make at Amazon
That all sounds very good to me :)
JoshDoody··on Ask HN: How much do you make at Amazon? Here is how much I make at Amazon
This response makes me wonder why you don't just tell the candidate the range you're willing to pay and let them tell you if that works for them.

I definitely understand the need to be efficient with everyone's time, but "have the candidate share their desired salary" is only one way to do that.

I have heard this reasoning from recruiters many times, but haven't heard a good explanation as to why they don't just tell the candidate the range they're willing to pay.

(This is a genuine question) Why not just tell the candidate your range if your concern is to respect everyone's time?

JoshDoody··on Ask HN: How much do you make at Amazon? Here is how much I make at Amazon
Yes. Wait for them to make you an offer. It can be difficult, but the reward for your persistence will be more money in the form of a higher base salary (the gift that keeps on giving).

You have very little unique information when you enter the negotiation (you know your current salary, your desired salary, and how badly you need the job—that's about it). They have tons of information that you don't have (what they're willing to pay, what they're already paying others to do the job, how badly they need to fill the position, how badly they want you in particular).

By waiting for them to make an offer, you retain the unique information you have AND you wait for them to reveal some of the information you didn't have. When they make you an offer, you now know approximately what they're willing to pay you to do the job. This is a very big gain for you and allows you to negotiate much more effectively and increase your salary.

JoshDoody··on Ask HN: How much do you make at Amazon? Here is how much I make at Amazon
It's tough to decide where to leave this reply, and this seems like a good place to address a few things I've seen in the replies to my comment.

Usually, my advice is "don't share you current or desired salary", but the one exception I've discussed with some people is when they're concerned they'll be low-balled. In those cases, I've suggested it might be better to just disclose your desired salary.

I've been rethinking this lately. I think a better tack might be to ask the company to share the salary range they're offering for the position. (You're only doing this if you're concerned you'll go through the interview process and get an offer so low you can't even counter with anything reasonable.)

In this case, you have virtually nothing to lose: either they'll tell you the range and you'll know if you're wasting your time, or they'll refuse and now you're both refusing to disclose the "desired" salary component. In the latter case, you can choose to continue with the process or not, depending on your general feeling about the opportunity.

The more I think about it, the more I suspect you should _never_ reveal your desired salary because it can basically only cost you money. When you do reveal your desired salary, you're basically guessing and gambling. You're guessing at the range they're offering, and gambling that you don't undershoot and cost yourself money. (See this clip on why I think it's so important to protect the few pieces of information you have in a negotiation: https://youtu.be/ndrY2UI-fyU TL;DR, you have only two or three unique pieces of information that the company doesn't have; the company has oodles and oodles of information that you don't have; they have a significant informational advantage in your negotiation and this is bad for you, but it's worse if you give away the few pieces of unique information that you have.)

This is a worse gamble than simply interviewing to see what they're best offer is, IMO. If you go all the way through the interview process and find they can't afford you, you wasted a few hours of interview time. If you guess and gamble by disclosing your desired salary, you're risking thousands of dollars of base salary over several years. Odds are, the opportunity cost of your time isn't anywhere near the potential downside of guessing wrong with respect to the base salary they're willing to pay.

(I'm going to sleep on this, but it feels right) So, my suggestion is don't disclose your desired salary, even if you're afraid their offer will be way too low or if the recruiter says they won't continue without it. If you're dealing with a very persistent recruiter OR you're afraid they can't afford you, ask them to tell you the salary range they're offering so you can tell them if it meets your requirements. If they won't tell you, then you can choose to continue and possibly get a low offer, walk away, or the recruiter may end the conversation (this is rare, in my experience, but I'd be open to seeing data to change my mind).

All of these outcomes are preferable to the alternative, which is risking thousands (or tens of thousands) of dollars of base salary by guessing at their range and gambling by disclosing your desired salary.

The bottom line is the company has something you need: a job. BUT you have something the company needs: skills and experience that can help them make money. Don't be fooled into perceiving a salary negotiation as a one-sided affair.

JoshDoody··on Ask HN: How much do you make at Amazon? Here is how much I make at Amazon
This is my standard recommended answer:

"I'm not comfortable sharing that information [my current salary]. I'd prefer to focus on the value I can add to your company and learn more about this opportunity.

I want this to be a big step forward for me in terms of both responsibility and compensation."

You can obviously adjust it for your own situation, but the idea is "I'm not comfortable telling you my current or desired salary. Let's keep going, please."

I call this "The Dreaded Salary Question" and you can see a better clip and a lengthy Q&A on this specific question in this salary negotiation workshop I did in Orlando last week: http://bit.ly/21zFG5q

JoshDoody··on Ask HN: How much do you make at Amazon? Here is how much I make at Amazon
This seems very, very plausible to me. Jobs in this experience level and pay range aren't generally posted publicly, and don't stay posted very long if they do go public. This reminds of the same sort of phenomenon with "the good houses"—they never make it to market because someone knows someone knows someone who wants a house like that, so they get first shot at it.

These sorts of jobs are best found through one's network. Not only does this open up better opportunities, but this sort of "back channel" opportunity usually comes with more details than a public job listing (such as the "I think they're probably paying $YYYk or so").

JoshDoody··on Ask HN: How much do you make at Amazon? Here is how much I make at Amazon
One of my negotiation principles is "Don't disclose your current or desired salary" during the negotiation. With persistence, the recruiter or hiring manager will usually just move on.

Another principle is that you should always counter.

So I'm _extremely_ surprised to hear that 95% of the time, people have refused to continue talking with you. I can't refute your experience, but I can say this has never happened to me or anyone that I've worked with to negotiate a starting salary.

Patrick's writing, which you alluded to, was a big inspiration for me to write and think more deeply about this subject. He knows what he's talking about.

If you watch the Salary Negotiation workshop (linked in my original comment), you'll see a section on "The Dreaded Salary Question" and there was a 15-minute discussion on it in the Q&A. (Both are linked in the notes below the embedded video.) You might watch those segments to see if anything jumps out at you that yo haven't' tried before.

Thanks for the question!

JoshDoody··on Ask HN: How much do you make at Google?
I don't work for Google either, but I write about and coach people on salary negotiations, so I keep an eye out for these threads (I learn a lot from them).

There's a very similar thread going for Amazon right now:

https://news.ycombinator.com/item?id=11312984

It's a mix of salary sharing and salary negotiation advice that could be very relevant to your bigger question of "How much do senior software engineers make [at the big tech companies]?"

Also relevant is this Salary Negotiation For Developers workshop I did last week in Orlando: http://bit.ly/21zFG5q

As I said over there: I love these threads and I hope more of them get started. The more people know about what they're worth, the more tools they have to get paid what they're worth.

Thanks for starting this thread!

← PreviousPage 2 of 3Next →