Hacker News new | past | comments | ask | show | jobs | submit login
Ask HN: How much do you make at Amazon? Here is how much I make at Amazon
1213 points by boren_ave11 on March 18, 2016 | hide | past | favorite | 690 comments
To people who work at Amazon, how much do you make? I work at Amazon, and my pay is below.

Discussing pay is awkward, so most people don't. But this creates an imbalance of power in salary talks. A person I trust who was recently promoted was offered in the range of $55K for their new role. However, I know of one or two people who were hired into the same role from outside the company who apparently started at $70K+.

I suspect that internal candidates have less leverage in pay negotiations than do external hires. I think most people probably won't decline a promotion, even if the raise is weak, because the alternative is no promotion and no raise. Transparency corrects this imbalance.

Me:

Position: Developer (not classified as SDE, do not manage ppl) Tenure: 2 years Job Level: 5 Base Pay: $73,000 Signing Bonus: $25k Year 1, $21k Year 2 2016 Stock Vest: 104 shares LY Review Score: Exceeds LY Pay Increase: 4%, plus 35 shares of AMZN Most Recent Promotion Increase/Stock Grant: N/A - no promotions Gender: M Native English Speaker: Yes

If you're wondering about Native English Speaker, I included it because I think it might be interesting.

I'm not aware of any Amazon policy which prohibits sharing one's own compensation, but I still made a throwaway. A shift of power is never welcomed by those whose authority is diminished.[2]

To non-Amazonians, perhaps you could start an "Ask HN: How much do you make at XYZ" for your own employer so you and your coworkers can share the same thing. Comparing compensation for different companies could also be interesting.

[0] https://en.wikipedia.org/wiki/High-Tech_Employee_Antitrust_Litigation

[1] That isn't to suggest that I suspect Amazon of taking part in any illegal activity. I don't believe Bezos would even entertain the idea. I like Amazon, and overall I'm happy here. What I want is a more fair salary negotiation process.

[2] http://www.brainyquote.com/quotes/quotes/f/frederickd134371.html




I work at Amazon too. Last year I wanted to collect compensation information about tech industry professionals (software engineering or PM) in Seattle. I created an anonymous Google Form and sent it out among my circle of friends.

Here are the results: https://docs.google.com/spreadsheets/d/133LBigv7pOkgpTkA6bHH...


I was an System Engineer III at Amazon from 2001-2006. I got hired on at $70k and I think I was making roughly $90k when I left.

When I was hired I had to tell them "No" and hang up the phone (in the middle of the 2001 recession) to a $63k job offer. They called back the next day and bumped the offer to $70k. I later learned that I had one of the only "strong hires" ever given out by the bar raiser and the HR rep was told to hire me at all costs. HR played (and probably still plays) insanely hard hardball in negotiating salary.

Other SEIIIs hired at around the same time came on at $60-63k and were stuck there. Once the economy recovered in 2003/2004-ish we eventually started hiring SEIIIs at >$120k starting salary.

Gender: M Native English Speaker: Yes for myself and the other two or three employees I'm thinking of.


Staying anonymous is probably best but fwiw, policies which prohibit sharing one's own compensation violate federal law.

http://www.npr.org/2014/04/13/301989789/pay-secrecy-policies...


Also FWIW most states are at-will employment, and can fire you for no reason


Careful, they can fire you for NO reason, but they can't fire you for ANY reason.


So they can just fire you, have an escort and done?


Yes. Just as you can quit, walk out, and be done. For no reason. But they can't fire you for health reasons, personal reasons, etc.


They can fire you for health reasons, they just have to be very careful when doing so. Been there, done that. Pretty hard to sue when you have no proof except common sense.


> Yes. Just as you can quit, walk out, and be done.

What is the flip-side to at-will employment though? Without at-will employment, do employees become slaves that cannot quit their job? Or are there only a small list of "legal" reasons for you to quit your job.

I always see "well the employee can always leave at any time too," but is that really something that disappears in places without at-will employment?


> What is the flip-side to at-will employment though? Without at-will employment, do employees become slaves that cannot quit their job? Or are there only a small list of "legal" reasons for you to quit your job.

The following is true for a sizable part of Europe. The flip side(s!) are:

* I can't just walk out on a job, I have to give a 4-week notice (for any reason, though. It can be anything, from "I feel like I need a new challenge" to "I hate ever single one of you motherfuckers"), during which I'm expected to do my job more or less as usual. Everyone understands you're not as motivated, no one plans for major stuff to happen during someone's N-week notice.

* My employer has a small, but very open-ended list of reasons why he's allowed to fire me, which includes things like me underperforming (but he has to give proof that this actually happened -- i.e. he needs to have an actual evaluation process, has to warn me that I'm not performing as expected first and so on), shrinking clients base which means that they literally no longer need so many people and I drew the short stick and so on.

My employer is also required to give me a four-week notice, during which he has to pay me as usual, and he also has to pay for any vacation days I didn't take in this time (the idea being that I could have lounged in Belize instead of working my sorry ass at the office).

Furthermore, if I am being fired, my employer is also required to allow me to go to interviews during business hours (for obvious reasons).

Regulations vary from one country to another, but that's the gist of it. In general:

- Notices are typically 4 weeks for non-management positions and 6 weeks for management positions. The law around here allows these periods to be longer, but not shorter than this, and they're negotiated as part of the contract.

- However, they can be skipped by mutual agreement (i.e. if I want to leave right now and my employer doesn't have a problem with that, we sign an additional paper that says we both agree to leaving without a 4-week notice and I'm out).

- They don't apply for the duration of the test period at the beginning of an employment contract (if there is one). During that period (typically 3 months), both resignations and firings are effective immediately. I did it once, it' a very refreshing feeling :-).

I work for the European branch of a relatively small American company, which is how I've come to know all this. My colleagues from the US are mesmerized whenever they hear about these things.


In Costa Rica, which follows a similar system, you can also buyout your notice period, which I think is fair for all sides.

Basically, if your notice period is 1 month, you can opt to pay the company 1 month's salary instead of having to work that time. If a company wants you gone, they pay you the equivalent wages for the notice period you were required to provide.

I think it's fair because both sides have agreed that $X amount is a fair exchange for the employees services. If those services cannot be replaced with $X then that's really the company's problem for taking advantage of the worker.

This buyout is in addition to any other severance package the worker might be receiving.

Anyways, I think it's pretty nifty as it allows the flexibility of leaving immediately, but also puts in some structure into the situation.


Consider contract employment. You agree to work for me for x months. In exchange, I agree to pay you $y. The contract outlines reasons that I can fire you and reasons that you can quit. And, if either party violates the terms of the agreement, we can go to court.


Well, to be exact, you can always go to court and dispute the termination is illegal.


Norway is standard 3 months notice. So most Norwegian developers would be unable to apply for e.g. a remote work position the US without first quitting their old job. No hedging your bets, which means that you're in effect trapped in the Norwegian labor market.

The flip side of this is that it's very difficult to get fired, even if you're not very competent.


On the employee side, I think the alternative is Two week's notice. Not exactly "slaves," but with some structure for how to resign.


In Europe, a month is typical for junior, professional jobs, with this increasing to three months for senior positions.

You can, of course, not turn up to work. But that might well make you "unreliable" if you ask for a reference later. But it's not a problem, since a new employer giving a three month notice period will expect you to be on one at present.

(The notice period during the first 6 or 12 months is often less, eg 2-4 weeks.)


In Europe, it is much higher than a month in many countries.

E.g. in Norway it is near impossible to give less than 3 months notice for permanent positions without providing additional compensation, no matter how junior the position, except for a typically 6 month trial period.

Before I'd moved to the UK, I'd never even seen an employment contract with less than 3 months.

In practice, shorter notice is often mutually agreed on with or without compensation when both sides agree it suits them, but it's very common to serve out the full 3 months.


This is true of my position in Germany as well, but from what I understand it rarely works out like that. Unless you are leaving a company at a critical juncture they likely don't want to keep an unmotivated employer there for three months. I can mutually agree with my employer to leave early if necessary.


In Norway you can mutually agree to leave early, but the employer can generally not force you to leave to the extent that there have been cases where people have insisted on coming to work against the employers will because the saw it as problematic for their professional reputation if they were forced to leave. Generally courts would tend to be sympathetic to employee concerns in cases like that unless there are very compelling reasons to keep them out (e.g. lets say they were dismissed after a violent attack on another employee or after being found stealing secrets fro the employers).


That's right. "Thank you for all your hard work. We no longer need your services".


Can you imagine the fallout for firing an employee for discussing salary after the recent NyTimes article? It'd be PR suicide.

Now, your relationship with your manager might be strained, but hey, that's life.


What article?


He is referring to a scathing article that was published on NYT late last year: http://www.nytimes.com/2015/08/16/technology/inside-amazon-w...

Sparked a lot of controversy. It kinda made me not want to work at Amazon ever. Although I hear that the Amazon experience varies depending on team and location.


I don't think employees in (most?) at-will states can be terminated for violating pay secrecy rules.

(I think the only state with a meaningful divergence from at-will is Montana).


A company does not have to give reason to fire in an at-will state. If they don't say 'we fired you because you were discussing pay', then there is no means to prove that was the case.


No. It's nowhere nearly that simple; you can say exactly the same thing about firing someone because they're black, or because they complained about sexual harassment.

From experience (as a bystander), what really happens in a case like this is:

* Employee is terminated

* Employee believes they were terminated for a reason forbidden by state or federal law

* Employee retains an employment lawyer, who drafts a letter demanding compensation for the improper termination, citing specific claims of (say) sexual harassment, complaints articulated to superiors and to HR, and subsequent retaliatory firing.

* Employee does not necessarily prove those claims; they need only demonstrate sufficient facts and allegations to ensure that a lawsuit would not easily be dismissed.

* Employer almost invariably settles.

The two cases where employers don't settle:

* Employer is stupid, and believes that they will pay less to litigate a wrongful termination case than to settle.

* Employer is smart, and has an HR department that keeps excruciatingly careful records of things like sexual harassment complaints, alleged racially-tinged comments, ratio of black/white hires to black/white applications, &c, and is prepared to make it clear to employee's lawyer that the case will cost too much to pursue.

If you've ever wondered why smart employers go fucking apeshit when people make racially-tinged jokes, or why it's not necessarily in your best interests to bring your concerns to HR unless your game plan is to bring a wrongful termination complaint, there you go.

This is also the reason why, despite at-will status in basically every locale where you can hire people, "Performance Improvement Plan" is a euphemism for "slow-motion termination". The purpose of a PIP is to establish in the written record that an employee is a non-performer, so that when they're terminated, the employer can present evidence that there were reasons other than retaliation or discrimination.


There is another reason for a PIP: the employer thinks the employee has been doing their job badly but could do acceptably well. The PIP is the last available tool to get them back up to speed.


Most of the time, when your employer truly thinks that about you, they'll work on your improvement informally. I don't like saying this, but I think most people's best interests are served by the assumption that a PIP signals their employer's transition from "working to retain them" to "working to manage them out of the company".


In the places I've used PIP's we used them mainly on staff we hoped to get to a level where we could promote them. We didn't waste time on proper PIP's for people we wanted to manage out - for those people HR simply mandated no raises ever. They'd leave or gradually get cheap enough for what they delivered to be worth having around.

EDIT: It's worth noting that in these cases the staff in question also had clear evidence in the form of signed reviews rating them that they were performing well. E.g. the guy I spent most time on a performance improvement plan for was ranked "exceeds expectations" in every criteria three years in a row while I was there, and was given 15%+ raises each of those years. This was in Europe, but for a US company.


On the off-chance they're doing that because your performance is abysmal and you haven't improved enough from their informal intervention, if in PIP you managed to finally recover your performance, maybe they will let you stay a bit longer.


Sure. It's not a guarantee. But personally, I think if you get a PIP, your best next move is to start applying for other jobs.


I agree.

I was the recipient of a PIP at my last job, went through the improvement process, and at the end of it, my manager signed off that my performance had returned to acceptable levels. I left about a month later.

So why am I not still there? Well, in the process of going through the PIP and asking myself how I let things get to that point, I realized that I was quite capable of excelling at everything I was supposed to be doing, but I just didn't give a shit anymore. My subconscious had already checked out of that job and was telling me it was time to move on.

When I realized that, my reaction was to start looking for another job while bringing my performance back to a good level. We quit on good terms: they "hired" me back to consult on some problems that came up after I left; I helped someone transition into my old position and I have a job better suited to my personality.


By the way, you don't have to sign the PIP. In fact, you shouldn't, because if you do, you're basically admitting that, yes, your performance is indeed low and needs improvement. And that goes in your employee file.

The right thing to do is to take the paperwork and say, "thanks, can you give me a few days to review this?" and stall as much as possible while looking for another job.

If you're feeling especially ballsy (and very confident in your ability to find another job quickly) you can say, "I'm not familiar with these at all, and my grandpa (R.I.P) always told me to get everything reviewed by an attorney before signing it, so that's what want to do. Is that OK?"


Exactly. "Thank you for letting me know well in advance that you intend to let me go."


The PIP is paperwork to establish that you aren't being canned for a non-discriminatory reason. Period.

There is no self-improvement.


Once the PIP appears, improvement has already failed. If your peers and manager can't fix your performance problem, his could some arbitrary HR paperwork process?


because sometimes "Oh fuck this is real" works.


Yes it can (& did).


> then there is no means to prove that was the case.

It's called court. No provided reason does not imply a lack of reason, and (say) discussing pay on a public forum would certainly be relevant evidence, if highly circumstantial.


See, that's why at-will is a terrible end run around worker's rights.


How so? At-will cuts both ways. In countries like Finland as well as France it can be quite time-consuming to switch jobs due to the fact you have to give three months or more notice.

That's leaving aside entirely the issue of how at will employment gives companies confidence to hire since they know they can shed employees if things go south.

If you are looking for an end run try binding arbitration, which allows employers to opt out of the legal system.


> How so?

Because the employer is at a massive advantage. For an employee having gaps in employment is a major thing when it comes to future employment, and can have massive effects on personal finances. For the employer, losing an employee a bit earlier is rarely a major issue (and if it is, they can generally convince people to stay a bit longer by throwing cash at the problem).

It is less relevant in high-paid positions where employees generally have the ability to put aside more of a cushion, but for lower paid employees it can be dramatic.

There's a reason the long notice periods in large parts of Europe are a direct result of decades of union pressure.

> That's leaving aside entirely the issue of how at will employment gives companies confidence to hire since they know they can shed employees if things go south.

If this was a real concern, then we ought to see a persistent problem of high unemployment across the countries with long notice periods, but to my knowledge we don't.


> That's leaving aside entirely the issue of how at will employment gives companies confidence to hire since they know they can shed employees if things go south.

Maybe for unskilled jobs, but the idea that an employer will hire/fire employees at the whims of the market, and there is zero cost to this process does not apply everywhere. There can be significant cost to on-boarding people depending on the industry / position.


The issue is not on-boarding costs. It's statutory requirements or political issues that prevent companies from doing layoffs to respond to changing economic conditions. Layoffs are not impossible in countries like France but they are very hard to do and very expensive. France has a dearth of innovative small companies for this reason because you can't hire aggressively to try to get risky ideas to market.

The effect is that by protecting existing jobs you lose out on future ones. Over time this pretty much cuts you out of any industry where there are waves of creative destruction.


Employers have far more power in the situation. As I said, it's basically an end run around every worker's rights law there is. There might be some small benefits for workers, but, on the whole, it is terrible for them.


see, rights for any group are always an end run around rights somebody else would naturally have.


No.


That's even better. You have a lawyer write a letter that it's because of your alcohol/sexual orientation/etc, and you'll end up with a settlement 6/10 times.


But not any reason.


At the same time, firing right after talking about salary is extremely suspicious.


The law they cite only seems to cover employees sharing pay with each other (and anything else involved in collective bargaining), but I can't see that it clearly authorizes publicly sharing pay.


It does protect publicly sharing pay. I can't find the specific case at the moment, but there was a case where workers who were striking had printed up a leaflet with a bunch of salary information and distributed it to other workers and general public. The company tried to terminate those employees for violating company policy and sharing "confidential" information with people in the public, but the court found this was a violation of their collective bargaining rights.

It is a tricky issue though. I am sure that a powerful enough company that wanted to throw resources at it could make all sorts of arguments about whether certain parts of the information (e.g. bonuses, vesting schedules, options grants, stock price discounts, relocation provisions) are allowed to be classified as confidential even if basic salary is not.

As a lowly employee, your only hope would be if some national labor union or pro bono legal institute took on your case, otherwise you'd never be able to afford the legal costs to defend your NLRB collective bargaining rights.

With pay secrecy, it's unfortunately still mostly a "might makes right" situation, where rich companies can sort of make up their own rules and at the very least bankrupt you with legal nonsense even if they don't ultimately win. So few people have the fortitude to endure that kind of legal harassment that it implicitly still does censor our ability to talk about pay, even if it's illegal that this is so.


Before this thread gets too stale, I did find a legal paper from Duke, 2006, talking about how certain kinds of blogging are likely protected by NLRA, "When is employee blogging protected by section 7 of the NLRA?" By Katherine Scott, < http://scholarship.law.duke.edu/cgi/viewcontent.cgi?article=... >.

It looks like one of the main criteria is that it has to be a part of a "concerted action" to benefit a collection of employees, and this had historically been broadly interpreted in support of employees with a very liberal understanding of what a concerted action is.

This whole HN thread about it, for example, would almost surely qualify (I am not a lawyer, of course, so that's not a professional opinion and not a form of advice for anyone here), since it is explicitly focused on the whole class of Amazon employees and encourages employees to share for themselves.

I wish I could find the older case about the leaflets. IIRC it was from the late 1970s.


I worked for Amazon (Audible.com) from 2011 to 2014.

1 - Full-time freelance audiobook editor.

$30/hr

2 - Post-Production Associate - Level 6/4

$50,000/yr

35 shares of AMZN per year for three years

3 - ACX Production Coordinator - Level 7/5

$65,000/yr

Additional 20 shares of AMZN per year for three years

I am no longer ashamed to write these figures out to the public because I now make more than twice the salary that I was making before I left the company. I found that my salary at Amazon was always far too low given what I did, and my job titles were not at all representative of the job I actually did (for the 2nd and 3rd jobs they were almost entirely software engineering jobs.)

NOTE: Audible and Amazon have different job levels - Audible's job levels are two points higher than the same Amazon job level.


Full-time freelance audiobook editor? I didn't realize that was a position. What exactly does this entail and how did you get started with it?


I got my education in audio engineering at a leading music conservatory, so moving into audiobook editing was a pretty easy sell for me.

An audiobook is made in four basic steps:

1. A voice actor records the narration for the book.

2. The editor takes the raw audio recordings and edits these files for pacing, flow, and aesthetic flavor. The editor also makes note of any errors in the narration which require a re-record.

3. After making all re-records and inserting the new audio, the audio is listened through one more time. They call this a "QC pass."

4. Finally, the QC'd audio is mastered and encoded for delivery.

I was the owner of step two for all Audible Studios productions.


I really enjoy when the voice actors do different voices for different characters. I've always wondered how they do the recording for that.

Do they read all of the dialogue for one character in a big chunk, then move on to the dialogue of the next character? Or do they read through the book naturally and switch voices? I would think that the latter would be very difficult.


Great question! :)

Narrators actually do switch all character voices in real-time. This does not commonly cause issues that require recording to stop, as the narrators are usually very experienced professionals that come from the Broadway stage or from other voice acting professions (cartoons and the like.) I've also recorded and edited my fair share of bad voice actors (for instance, former Labor Secretary Robert Reich narrated his book 'Beyond Outrage' even though he was told that it really wasn't a good idea.)


for instance, former Labor Secretary Robert Reich narrated his book 'Beyond Outrage' even though he was told that it really wasn't a good idea.

That's a very interesting aside. I could see how a non-professional narrator would struggle with the demands of the process. Would it not still have made sense for someone like Mr. Reich from a personal branding point of view? He is, after all, a somewhat well-known public figure and paid public speaker.


It isn't just the demands of the process that was the issue with Mr. Reich. Rather, to be polite, the tone of his voice is not universally recognized as being pleasant.

Audiobooks are a very intimate media, and the wrong voice can really put off the experience. With training I think he could do it, but to just give a public speaker the task of narrating a book he/she wrote without such training is usually a recipe for disaster.


The editing on Audible books is amazing, so thank you!

If you don't mind my asking, when people want to do their own reading and are willing to get training, how are they trained?

I ask because (like every geek) I sometimes think about doing a podcast some day, plus I just want to be a better public speaker, and there seems to be a lack of options between free/cheap resources focused on basic skills (like Toastmasters) and intensive training for people who want to do voiceover for a living.


I listened to Bill Bryson's self-narrated (and truncated) version of A Short History of Nearly Everything. It was my first time listening to an author self-narrating their book. It's probably one of my favorite narrations (I've got over 120 audiobooks under my belt now). Bryson set the bar pretty high.

Then I listened to Leonard Mlodinow's "The Upright Thinkers"; Oh god. Euclid's Window by Mlodinow was absolutely fantastic, and it was narrated by the slightly pompous-sounding -- but fitting -- Robert Blumenfield. Leonard had a somewhat slow, drawling voice, and he often stumbled over words. This was pretty disappointing because he seems like such a smart dude. He just shouldn't narrate his own books :)


The gold standard for this is Douglas Adams' readings of the HHGTG books. He was actually a really good narrator. I suppose his BBC Radio experience helped.


Simple question on a similar topic: how "real-time" is the source audio that you work with? I always imagined that voice actors would have arbitrary pauses between the delivery of every line, and it'd be the editor's job to tighten all of those up.


Wow. I love how curious folks are here about audiobook production! :)

The pauses between lines/phrases were often tightened up, yes, by pasting room tone over the pauses. This way, the near-silence of the room tone is consistent throughout each pause, which makes the narration easier to comprehend and allows the listener greater immersion into the experience.

The exact duration of room tone impacts the pacing of the narration. This is, in a way, the audiobook editor's "art." They can't over-edit because it would ruin the narrator's dramatic delivery - they need to be able to edit within the stylistic flow of the narrator. At the same time, if they are not careful enough to make the resulting delivery consistent, then the extraneous audio may distract listeners and lead to a lower quality result. That balance is acquired with experience.

The reason this all happens, really, is to ensure a clean "noise floor" - the background sounds heard in addition to the narrator's voice. The sound of the room and the gear, if you will. The narrators are such pros (my experience) - there are many who I could get away with not editing at all, if it weren't for the incredible need for near-silence throughout the entire finished production.


Hey what software are you using for this?

I was thinking I really wish there was a good app where you can listen to audio articles. It is partly solved in iOS as you can speak selected text, but problem is you cannot select all text easily and you don't wanna mess with it while driving.

Was wondering what would be a great UI for the transcriber and whether you could create p2p network to share the transcriptions.


The audiobook editors at Audible used SoundForge. I started out on SoundForge, but I led a real charge to get the department to switch to Wavelab. I was able to get Audible to buy me a license for Wavelab and I never really got anyone else to switch, but it made me super efficient. At that point though I was heading into a more dev role at the company so I was already drifting away from audiobook editing at that point.


Wavelab is so good – it's a shame it's not more commonly used.


I've thought about this too, but I'm not sure I've got the patience to listen to articles read in TTS voice.

Anyway, on iOS if you enable voiceover you can read the entire screen by swiping down from the top with two fingers (I think - check the Apple website for accessibility information if not!)


You have to use the Speech from accessibility menu, and turn Speak Screen on.

Another possibility i just realised is the possibility to pass texts from reader mode into 3rd party text-to-speech application. Will have to research some of them.


That's really interesting! And it also sounds really exhausting given the amount of material in a typical book. Thanks for sharing.


No problem :)

Honestly, though, it was a great job. It never felt exhausting. Not only was the pay rather good for a 21 year old fresh out of university - the job was really fun. I got to read medium-to-high quality novels and create the audiobook experience.

Later, I got to witness Audible's rise into the mainstream and evangelized producing audiobooks for ACX [1], bringing it to a new generation of actors and engineers.

[1] https://www.youtube.com/watch?v=QHmtV1Pe1hA


I wish you'd blog or do an AMA or something; your responses in this thread are fascinating.

(I discovered a couple years ago that I really like audiobooks.)


If you don't mind me asking, how were you compensated for this? What was the model?


I worked 40hrs per week in the Audible HQ. I was paid at the rate listed above - $30/hr. So, I walked out of Audible's offices on Friday with a $1200 check in my hands. This is how it worked until Audible was sued for not providing health insurance benefits, and lost the case. So they had to hire us as full-time employees, and didn't allow two out of 8 to continue to work with us as they didn't "make the cut." (They both were African American women.)


[flagged]


We've banned this account for breaking the HN guidelines.


Microsoft employee, not Amazon, but these sort of discussions absolutely need to happen and I'd like to do my part.

Salary: $115k base, no regular bonus or stock, $50k offer in stock over 4 years if I remember correctly although I don't know offhand how many units that came out to.

Level: SWE1 (60 internally)

Tenure: 2 years internally, 7 in industry

Yearly pay increase: Averaged ~6k/y thus far.

Internal candidates have NO leverage. The only way to get a promo is to be in the right place at the right time, and have both high visibility and a manager who has proper political influence and will fight for you. If you want a salary boost, leave and come back a year or so later. "Performance" reviews, accomplishments, hours put in, is all moot unless you have the above, in which case it's a nice bit of ammo if your skip level has a lot of competition for his promo budget, but proper political clout can likely force through a promo without. (To add another tidbit that I've always wanted to clear up anonymously: Stack ranking absolutely still exists, if not in a formal process but as a necessity from how budgets are assigned and promos divvied up.)


I'm SDE II an earn just a little more base than you ($117K). Judging by conversations with team members about which tax brackets we fall in and how much we save/invest per year, I'm fairly sure I'm underpaid for my level.

There's a college hire PM in my team (not PM II, so he's either 59 or 60) who's single and in the 33% bracket. That means he's making at least $189K a year.

Edit: I should add, my PM coworker could be wrong about his tax bracket. I can't fathom how they would offer him that much in base salary + stock. But he did mention being in the 33% bracket.


I've seen some outliers, but mostly in terms of promotion velocity. I assume you know about the "bench program"? (Microsoft Fight Club) That could potentially explain it.

I really want to empathize with your underpaid for level statement, I certainly have a pile of stories, I'm just hesitant to tell them because they're rather identifying to anyone who knows me, so you'll have to trust when I say "A good number of us have gotten the short end of one stick or another, often beurocratic or political"


What's the "bench program"?


An internal "High Potential" program in which candidates get faster promo tracks, bigger promos, face to face access to higher level execs, and other perks. They are not supposed to talk about this program, as well, and it is invite only.


I had never heard of that. I'm fairly sure my team has two people in the "club". Both are quite young and are already principals.


It's really a shame how things like that that are handled, from where I stand. Turns it into the closest parallel to the cool kids table that used to exist in highschool that I've seen in the decades since then.

Also, if you're a 2 and only at a slightly higher base than I am, you're "somewhat on track" from the conversations I've had, as far as pay per level for us normals :) That being said, I really botched my negotiation when coming in and didn't push my position, which left me coming in at a 59 from an industry position with greater responsibility, and role seems almost harder to change than pay from what I've seen.


if it wasn't explicitly tied to his salary, he could also have income independent of his tenure there, either earned or inherited. it does happen.


What does 59/60 mean?


Internal level. 59 and 60 are SDE I, SDET I and PM I.


The most important thing you can do for your career is:

* Accept a job somewhere

* Get promoted (doesn't matter how)

* let yourself get hired away from your current company

Getting hired away from your current company is the only way to get a fair raise based on increased experience. Companies never give substantial raises to current employees.


This simply isn't true. I received a >$30,000 raise at one of my previous employers after they realized that I was being grossly underpaid for the work I was doing. Granted, I had to bring my managers' attention to this, but they were understanding & did right by me.


Your anecdote is the exception to the rule. I've been in the industry for 20 years and can affirm the rule: you don't get raises from your current employer. You get raises by changing employers.


I have overseen 25-30% increases for developers as part of a normal salary review process as recognition that their experience at the current company had grown them in to more senior developers.

No negotiation, no threats to leave, they weren't aware until we gave them the cash.


Which while cool, is not the norm. Anecdotes don't counter that.


Yeah, but the claim was:

> Companies never give substantial raises to current employees.

and a single counterexample is enough to counter it.


If you're being super pedantic, sure, but... as far as the typical developer/employee is concerned, it's not relevant.


Not to mention there seem to be several counter-examples in this thread


Not true, I pointed it out to my employer and they were like "oh dang, can't loose you, you get that raise" after I had already gotten a 17% raise.


I second his anecdote. Have received large raises twice, but had to negotiate hard for it, with offers from outside in hand.


Ah, the outside offer is an absolute game changer, which IMO puts it in the same league as actually changing jobs. Often you have to show that you are willing and able to leave for a much better salary to actually get the much better salary.

If you are just internally lobbying for a salary increase at your existing employer, regardless of how successful you may be, how much revenue you are bringing in, etc. I would say at the vast majority of companies you will not see nearly the same raise as either presenting a compelling outside offer, or actually taking an outside offer.

Another way of thinking of it is that a company cannot pay their employees an arbitrary amount, it has to be justified up the chain, and usually that justification is based on "grades" or "scales" of some kind or another. Most of these scales will include a fixed range for annual raises. By bringing an outside offer, you are providing the necessary documentation that your manager, HR, all the way up the chain is required to actually sign off on the raise. The outside offer means no one is sticking their neck out to justify an out-of-spec raise, or claim someone was being previously underpaid, it's just a simple equation -- the employee has an offer, and the company can make a counter-offer or not.

Of course the trick is if they decline to counter, or counter low, you have to consider if you then leave, or stay? You also probably can't come back year after year with new outside offers, it's a trick you can only turn to so often.


My opinion only, but if I had to bring an outside offer to get an inside raise, I'd take the offer. "We'll pay everyone what we can get away with, except the few who we need for the moment that make a stink." But then, I make too big a deal about personal relationships, and I forget that it's just bidness.

That said, I did get a raise once with an outside offer. But I left just inside a year later.


I agree and it can be personally very distressing when you know you are delivering tremendous value and are not getting nearly the financial reward for the value you bring.... and yet can't seem to convince the bosses to put up!

That's why I look at it now as a system that just needs the outside data point in order to properly process the request. It's not a person holding back the raise, more often the process which the outside offer fixes.

If there was such a thing as an "employee appraisal" service maybe you could do it without actually going to interview, which would be pretty cool!


Pretty much my experience too. My dad worked at one job for nearly 25 years of his life and I learned a couple years ago that I already make over twice what he did by the time he retired.

My dad was a little like Al Bundy though, he never really sought to improve himself like I do constantly and I'm sure almost everyone here does too.

I think the industry still has a lot of managers who think in terms of running a shoe store with employees that are improving themselves at a rapid pace.


Al Bundy invented a shoe with a built-in sock.


A previous employer of mine actually had a policy of never matching offers from other employers. I'm no longer there.


Depends who you are. I've always been ranked in the top tier of employees wherever I've worked, and worked my ass off to make myself indispensable. I've gotten multiple 15-20% raises, and even 30% bonuses without having to jump ship. Make sure you work on visible projects (front office, not back office), and that your managers are fearful of losing you because you're crucial.


Yep, if it's technical work that requires a large amount of learning and investment in employees, the company will typically move mountains to keep you if you are good.


I've experienced the same, but it doesn't mean the general rule is untrue. More specifically, if you are making market salary then the greatest raise will come from switching companies. If that's not true and your current employer will give you a substantial increase, then by definition you are not making market salary; the raise simply corrects your salary to the level they would have paid for a person of your experience.


Also had the same exact bump in salary while working for a media company after my managers manager realized my pay grade. However I do agree this is the exception to the rule.


Mind sharing what company this is? I'm 100% sure if I leave to go somewhere else and come back, I'll still make a lot more than sticking around. This is the unfortunate reality.


That was at MLB Advanced Media. Looking back I think MLBAM was the most solid employer I'd ever worked for.


Not true at all. You just need to find a company that values you and your work.

Our company intentionally hires juniors so that we can groom them as they grow. I was one of those juniors < 5 years ago and I've increased my salary > 100%.


You can't just dismiss their experience based on your experience. I, for one, have also found it to be very true, and I think most people would agree (insofar as it seems to be a bit of a meme).


The OP said Getting hired away from your current company is the _only_ way to get a fair raise (emphasis mine)

A single counter example is sufficient evidence to disprove such a universal claim.


Definitely not true, i have doubled my salary at my current employer through a combination of negotiation and normal pay raises. I never explicitly threatened to walk out, but i did point out when i was substantially below market rate, and that was enough.

I do think that overall switching employers makes it easier to get a raise, because a current employer is more likely to know your true market rate making it harder to convince them to pay you above that, or even at that rate (with them figuring you won't leave for a small difference).

You do have to be careful not to become a 'job hopper'. When i see a resume where somebody never stayed somewhere more than 18 months i'll figure we won't be any different and am less inclined to give a thumbs up to HR if that person needs a sizeable training investment from my part.


100% agree with you. I've been able to get 30-40% raises YoY by job hopping roughly every 1.5 years. It's enough time to get experience somewhere, but not enough to become complacent. YMMV


Do you move every 1.5 years? that must be fun ...


Actually I've moved every year for the last 9 years. Definitely can get tiring. The last 2 were cross-country!


Didn't that hurt your social relationships somewhat?


As normal, the true friends stay and the situational ones fall away.


There are plenty of job markets that support getting a new job without moving.


I've gone from making 65k to 90k at the same company in the past two years. Though someone trying to poach me from another team in the company probably contributed to that.


Same here. Always moved away and up, usually in the 20% range. Thus the importance of always being working on a portable skill.


yep. job hopping is the best way to increase pay. though top 10% can usually negotiate with current employer. everyone else should job hop.


I've been at Amazon for a bit over 5 years with 12 years total. Joined with about 7 years of prior experience. From the other post I see I did a very poor job of negotiating when I first joined with my experience. I've always saved the stock and considered it more retirement savings than spending cash.

Hired: 2011

- Level: SDE I (4)

- Location: San Francisco

- Salary: $96k base, $20k bonus, relocation, ~160 stock over 4 years.

- Average yearly total comp: ~ $150k

Promoted: 2013

- Level: SDE II (5)

- Location: San Francisco

- Salary: $110k base, 168 stock

- Average yearly total comp: ~ $170k

Relocated: 2015

- Level: SDE II (5)

- Location: Seattle

- Salary: $125 base, ~160 stock, relocation

- Average yearly total comp: ~ $190k


Wow, you got a bump in 2015 and went somewhere with lower cost of living (plus no state income tax). That's definitely a win-win.


Indeed big increase in revenue compared with cost of living. I'm surprised that you've decided to move to Seattle instead of switching to another company in SF. Can you please share the reasons why?


This is perfect timing as Google Seattle is hiring around 1000 devs and promotions are being revealed in April.

I used a throwaway account, but I'm sure I'm identifiable by this information if my manager sees this. I'm not too concerned. I think it's in Amazon's and the employees' best interest for this stuff to be transparent. Besides that, while I like my work, I can easily get an offer from Google, Facebook or pretty much anywhere else.

Position: SysDE 2 in AWS Tenure: 1.5 years Job Level: 5 Base: $120000 Stock: 140 RSU (granted at signing, almost none vested) Bonus: $20000 + relocation at signing, $15000 will come after 2 years Gender: M Native English: yes

I was hired at L4 as SE 1, moved to SE 2/L5 after a year, and now SysDE 2. There was no raise for SE2->SysDE2.


> 140 RSU (granted at signing, almost none vested)

Is it still the ridiculous 5-10% year 1, 5-10% year 2, and then the rest spread out over years 3-4?


Yes, it's something like 5% at 1st anniversary, 15% at 2nd anniversary, then 20% every 6 months over the next two years.


Why is it so ridiculous? Isn't it trying to serve as a retention incentive?

Obviously it can back-fire on the company. If the share price drops a lot then people that were planning on staying till the 6 monthly vesting may quit.


From what I heard from people who worked at Amazon during the especially rocky years, their share compensation is tied to a monetary value - if the share value tanks significantly, they'll issue shares to compensate. If you're into gambling, this can be a -very- good thing considering Amazon has gone on to double in value over very short time periods historically. Otherwise, its a fair concession on Amazon's part


Ex amazonian here, but in Ireland, I left (thankfully) at the end of 2015.

I was a systems engineer in Dublin and the only significant payraise I got was after I left the company for 4 months to then rejoin, my salary was bumped up 12k euros, for a total of 62k/yr, with 150 shares over 4 years (sorry I do not remember the vesting scheme).

The HR department in AMZN has the tendency to screw internal employees upon promotion. The way it was unofficially explained to me by a low-level buddy in HR is that there are salary ranges for each corporate level, and during a promotion you get just over the lower bound of the salary range for your new corp level, that's the policy, that's what happens.

New hires instead have negotiation margin and, while the hiring manager can't offer a salary higher than the approved salary range, more often than not the offer will end up in the upper bound of the range, to lure the candidate in.

Furthermore, there are huge differences between salary ranges in job roles, a Systems Engineer will always be paid 15 to 30% less than a Software Development Engineer at the same level, despite the fact that the skills and duties are not that much different, why? Again unofficially "because Amazon values more people that write software". Except the fact that in my ex-team, we all wrote software and the expectations were all the same regardless the job title (there was however a difference between levels).

So yeah, as internal promotion you have absolutely NO leverage regarding salary, if you want a salary increase and your organization is hungry for people but is having trouble in hiring (like it happens frequently in Dublin where the job market is quite competitive), I'd suggest you start looking around for a new job, accept the offer and then come back to your same team 4 months later. If you leave the company for less than 6 months and your position hasn't been filled in the meantime, the hiring manager is able to extend an offer without sending you through an interview loop, you'll get your old job back but with a nice pile of money on top.


I think it's true that the different engineering roles do similar work but the SDEs are paid better. This is why most people I know (including myself) who started as non-SDEs chose to first convince their manager to switch job roles.

Personally, this netted me a 10% base pay increase. More counting the performance stock bonus that came with the change.


In case any students are curious how much Amazon in Dublin offers (Undergraduate) students. I was offered: €25000.


Seems dickish toward the company you work at for 4 months though.

Were your offices by that famous Gaol? I thought it was interesting seeing a mix of the old and new so close together.


I was speaking with another company, but unforeseen family matters took precedence and I ended up not taking the job there. Another ex amazonian did accept an offer from the same company I was speaking with and in hindsight it was for the best, it did not work out exactly smoothly form him so...

And yes, the office was exacly in front of the Kilmainham Gaol, unfortunately the office was quite depressing, so much so that it was an inside joke that the Amazon office was 21st century Gaol.

Luckily they moved in a much better place now.


That's pretty harsh for not knowing any of the circumstances.

Who said he was at another company for those four months? And who's to say the company didn't just fold in that time or earn someone walking out on them?


> a Systems Engineer will always be paid 15 to 30% less than a Software Development Engineer at the same level, despite the fact that the skills and duties are not that much different, why?

In the past couple of months this was fixed by the creation of a new role called 'Systems Development Engineer'.


Pretty sure I know who this is and I'm happy to see you back in the role you deserved. Was your short leave to a German startup by any chance?


Admittedly I'm American and I've never worked for Amazon, so my situation might be different than yours.

But what? Returning to the employer you quit from seems like a terrible idea. If it was years later, maybe you could explain it away with interview BS like "changing direction" or "finding your place."

But months later makes you not much better than the guy who shows his boss an offer from another company to negotiate a raise. It might work in the short term, but then you're branded as a flight risk. The next time they need to lay someone off (or if you slip up and they have a legitimate reason to fire you) you'd be high up on their list of disposable employees, perhaps moreso because you're more expensive than you were before.


People leaving and rejoining Amazon is supercommon. That includes Principals. It feels like most people who have been at the company for 8+ years have been out of the company for some of the period. And you can even get the colored badge for tenure from non-consecutive employment.


Maybe in the past, but not in the future. People are much more aware of Amazon's "peculiar ways" thanks to the media. People in Seattle have far, far more options these days.


IMHO you're being underpaid quite a bit with that base salary in the Seattle area. Time to start interviewing at Microsoft, Google, etc. Those companies usually start fresh out of college developers with a base pay a bit over $100k, then bonuses, stock awards, etc. on top.


Are you taking stock into consideration? At current price, 104 shares of AMZN equals $57,408 which puts my total 2016 pay at $130,408.


Yeah that helps, but then the question is do you really want to work somewhere that directly ties your compensation to the company's share price? If Amazon has a few bad quarters and you lose 20% of your yearly income that's a major deal. In Seattle you probably want to be making around $120-160k/yr to live a solid middle class life, afford a house, etc. I would still look around at MS, Google, etc. where they give you more in cash compensation and less with the stock lottery ticket. Find a place that gives you around that as base pay, then all the bonuses etc. are just savings for house, retirement, toys, college, etc.


I find tying my income to stock highly motivating :)


Maybe in a small company, where your efforts can have a direct, meaningful impact on the company's net worth. For a company as large as Amazon, though... there's so much going on, and so much of it completely unrelated to your personal work, that I feel like it'd be kind of meaningless unless you were in a really high-level management position.


Yup, and it's even worse than that, because the stock price also depends on things beyond the scope of your company entirely.

Your compensation can fluctuate based on what Janet Yellen says in a speech.


I'll have to disagree with your exception as well. Data has shown that CEOs at giant corps have no impact on how things go down. It comes back to your statement of how much is going on. If all the goings on in the corp mesh perfectly with the goings on outside, success happens. A single human CEO can neither be credited for success nor blamed for failure in these cases.

I agree with your premise, but don't give too much credit to "the high level management". Most of them are groping in the dark.


You realize you have approximately 0 effect on the stock price, right? Why would this be motivating to a rational person?


If you're an executive pulling in over $500k, sure stock should absolutely be compensation and motivation. If you're rank and file and need $120k/yr to even afford to live, have kids, save for retirement, etc. in the area, then no stock should absolutely not be the primary means of compensation.


The best argument I've heard on this front is about diversifying risk. If your company tanks and you're rank and file, you're getting laid off and your stock holdings are tanking. Best to not be doubly exposed to the company's risk profile.


That's why I have autosale set up for my stock.


I don't see why it would be more motivating than just getting the current cash value of the stock, in a situation like Amazon's where you _maybe do, maybe don't_ really influence the stock price. Are you saying you write such influential code that you think you will manage to tip things in your favor on such a grand scale?


You get stock annually? Otherwise, you have to vest that over several years, severely reducing your annual. AND you're locked in for years just to cash out at maximum value.

Unless you get that kind of equity yearly—which is crazy, and brings up dilution questions—you're better off taking a higher salary and investing as much as possible.

But—adding X market value for equity vesting over Y years with 40% capital gains tax for the first 12 months of holding it leads to a 2016 pay of.... just your salary.

Oh, and you get equity every else in addition to that nice pay, and they don't strap your pager to your face.


Amazon's compensation model leans heavily on stock and tops out in the mid 100Ks for all job levels. It's not uncommon for senior roles to get more compensation from stock than salary, and at higher levels the majority of the compensation is in stock. For the majority of employees, once compensation RSUs kick in, vesting occurs on May 15th and November 15th. For L7 (IIRC) and higher, vesting occurs quarterly.

The annual and midyear review process takes this into account and attempts equalize total compensation depending on the value of the stock (basically, you want the stock to be down when the price is used to calculate your total comp at the end of January).

When I was there, it was somewhat difficult to recruit some higher level roles because they might only be offered $120-$150K salary and then 200 or so RSUs over the course of the first year. That doesn't always look as enticing to someone as $250K salary.


>>You get stock annually?

At my annual review last year I received more stock along with a pay increase. So, thus far, yes.

>>But—adding X market value for equity vesting over Y years with 40% capital gains tax for the first 12 months of holding it leads to a 2016 pay of.... just your salary.

Can you elaborate on this? I'm not following.

>>Oh, and you get equity every else in addition to that nice pay, and they don't strap your pager to your face.

What do you suggest I do?


> Can you elaborate on this? I'm not following.

Well, if you do get more stock it complicates things—but you have to distribute out the pay out over the vesting period. In other words, collecting the entire value of the equity into one pay period implies you'll get the same amount of money the next pay period—which is only true if you get that amount of equity annually. It sounds like this may be a possibility

Furthermore, it assumes you'll be at the company for the entire vesting period. Which you might not want to do.

Additionally, you can't cash out the equity you DO get in 2016 unless you want the government to take a sweet 40% off the top.

> What do you suggest I do?

Don't wait for the equity to vest fully, work hard for some good recommendations, and get out of that sweat shop. Amazon rewards ambitious workaholics. Everyone I've talked to who USED to work there (key point being these people left) has issues balancing work, pay, and a life.

To be clear—I'm not arguing anything but that other companies will use you a little more compassionately, and you might make a little more cash in the meantime. You're still doing very well for yourself, Amazon is far from the worst place to work, and you might be very happy there.


> At my annual review last year I received more stock along with a pay increase. So, thus far, yes.

Unless you do spectacularly poorly, you can expect that to continue


It's pretty interesting that so much of your compensation is in stock. After 2 years at MSFT and becoming a PM II, I was making ~$145k annually but $115k of that was in salary and $30k in stock. I think that's why everyone is surprised when they see the $70k.

Do they give you the stock as a bonus at the end of the year, or are you promised it at the beginning and it gets doled out during the year? If it's the former, be careful that they don't decide retroactively that you had a bad year and decide to cut your total compensation almost in half!


The stock is initially granted in the form of Restricted Stock Units (RSUs). RSUs vest according to a schedule. It looks roughly like this:

5% the first year

15% the second year

20% every six months thereafter

Compensation at Amazon typically is a combination of a base salary, a signing bonus (distributed over time), and a stock grant. The package is structured in such a way that the employee's total pay stays consistent over time, even though the pay comes in different forms. New hires will have their signing bonus structured over the first two years, and then it ends. At that point, the more significant stock vests begin to occur at six month intervals, so the total pay amount stays relatively the same after the bonus ends.


Wow that fucking sucks.

The standard (at GOOG & others) is:

25% on year 1 2.08 & 1/3rd every month thereafter (75% vested equally over the next 36 months)

Furthermore, there are other grants that vest quarterly for the first 18 months of employment (in addition to the normal 4 year).

Look, I used to work at Amazon. They are the worst paying big company out there. Complete with totally shitty vesting plans. My first vesting with Amazon was over 5 years. Yup, they really took advantage of us new grads.


Your definition of sucks is pretty skewed.

Anybody earning 6 figures is in the top few percentiles of society, especially if you are a new grad!

You are obviously free to take advantage of your employability but just remember that you pretty much are the 1% before saying that it sucks. :)


No, he's right, you just misread.

He is saying that Amazon's RSU vest schedule sucks compared to the standard used by Google and others. His income level has nothing to do with anything about that.


Nah, the stock goes up enough that they say you got a 10% raise. Meanwhile the money you actually get in your pocket has dropped by more than 10%.

Fair enough I guess, but I am not a fan.


Microsoft annual bonuses used to be a lot more stock and less cash, but in 2011 they shifted towards the current model of cash++, because the stock was low and nobody wanted it. (At the same time they did an across-the-board 10% raise - from memory, both these moves were made because Amazon Google Facebook were becoming much more serious competitors for Seattle employees. http://minimsft.blogspot.com/2011/04/microsofts-new-review-a...)


Doesn't matter, my friend who got an offer from Amazon fresh out of school back in 2008 was offered 80k a year. These days total comp for senior software engineers at Amazon is > 200k a year total.


Yes, back when I graduated (with a prior internship at a big tech company) my amazon offer was over 100k, similar sign-on bonus, 150k stock.

I ended up not accepting that offer because another company gave me a more interesting role. Also their stock vesting schedule is horrible (most of the money comes in year 4), and many people find amazon to be soul-sucking. You're likely to leave at the 2 year mark, thus losing out on most of the stock anyways. 4 years is a long time to be at Amazon (though if you're the right mix of "in-it-to-win-it" and "workaholic" you might thrive there)


Apple, Google, and Amazon will all make similar offers.

My initial offer from Google was $150k base, ~15% holiday bonus, and came with >$100k in stock vesting over four years, and they give another four-year stock grant each year. I have 7 years of industry experience and I interview well.


What year was this offer given to you? Also, was your 7 years of experience before you got the Google offer? Was all of the experience in US?


Are you deducting the taxes from that stock compensation?


No. I am also not deducting taxes from the part of my salary that comes in the form of base pay.


Unless you say otherwise, Morgan Stanley will deduct it for you, and IIRC, the don't take your exemptions into account - just 30% off the top. You get to decide if you want to take the tax liability or get the refund (assuming you're effective tax rate is not actually 30%).


Only on HN are these incredible compensation packages considered "underpaid".

In the real world (outside FaceGoogAmaWallstreet), the story for developers is quite different.


>>Only on HN are these incredible compensation packages considered "underpaid".

"Underpaid" and "overpaid" are relative terms. If you currently earn less than what you can expect to receive elsewhere for the same work, you are underpaid.

>>In the real world (outside FaceGoogAmaWallstreet), the story for developers is quite different.

Interestingly enough, this is precisely the sort of thing that this very thread is attempting to challenge. Have you noticed how many "wow I am seriously underpaid" comments have been posted?

All of this reminds me of a quote by Michael Corleone in The Godfather:

Never be embarrassed by your wealth. This recent contempt for money is still another trick of the rich to keep the poor without it.


In general I'd agree with you, but a ~$70k salary really is not that high for a decent developer with two years of experience, even with a signing bonus and stock options. I'm not in a major tech hub.

Keep in mind also that Amazon is not some tiny startup strapped for cash. It's a big player in the industry and their hiring standards are rigorous.


Amazon offers RSUs, not stock options. Once they vest, they are yours without having had to purchase them.


$70k is severely underpaid for final comp. The OP said in a follow up comment that his total comp is close to $130k which is a very good wage.


Good wage, yes. But remember the median price of a home in Seattle is well over $500k. You're looking at something at least $600-700k+ to be in an area without a crazy commute or other problems. Most people I know that are just starting a family have homes over $1M. $130k doesn't go super far when housing is that expensive.


Agreed, that's way under market. At Intuit's San Diego office in 2013, we were hiring college graduate software engineers for $75k base. Add another 15-20% for total comp (bonus, RSU, ESPP).


Outside of the actual software industry, sure. But rule #1 of getting paid well as a developer is to work for a software company.

It's not just the big few who pay really well. There are whole constellations of medium to small software companies you've never heard of that pay very well. The differentiator is that they see software as a strategic asset, not just a cost of doing business.


> In the real world (outside FaceGoogAmaWallstreet), the story for developers is quite different.

This package would be underpaid for pretty much any pure tech company on a coast.


70k salary is junior money in St.Louis. Absolutely average senior devs make 100-120. Good ones do long term consulting, and get closer to the 200k range. The best I have seen for a local company is about 250k a year, for truly shiny people.


Then I'm doing something seriously wrong, because I have been an engineer in Dallas for fourteen years (eight writing software full-time) and I have never made over $93k. Never had stock or a meaningful bonus, either.


Start interviewing and don't be afraid to push for double your current salary, or more. Maybe time to think about moving to a coast too.


On a related note, someone at Google started a spreadsheet about a year ago where people could post (anonymously or not) their salary and a few more interesting datapoints (gender, age, location, etc.) I'm not sure whether the spreadsheet did anything to highlight gender/ethnicity/visa-status disparities (the biggest disparities I remember seeing were based on location, but that's understandable) but it was a great tool to start a conversation about increased transparency in salaries.

I have to praise Google for the way the situation was handled: the company didn't force the spreadsheet to be taken down (in fact, it's still up as I write this), nobody that I know of was fired for it and it generated a healthy amount of internal discussion. After hearing some stories from the Amazon counter part, I wouldn't expect the reaction to be the same.


> I have to praise Google for the way the situation was handled: the company didn't force the spreadsheet to be taken down (in fact, it's still up as I write this), nobody that I know of was fired for it and it generated a healthy amount of internal discussion. After hearing some stories from the Amazon counter part, I wouldn't expect the reaction to be the same.

Taking action against this would've been a violation of US labor law with steep penalties.


Well you know how that goes. It's not like that has stopped companies from firing people in the past. This is an "at will" employment state, so if they really wanted to fire people they could've made any excuse up and fire them. Actually, they wouldn't even need to make anything up.


I wouldn't praise Google for that, considering they actively participated in suppressing tech workers' wages:

https://en.wikipedia.org/wiki/High-Tech_Employee_Antitrust_L...


Can't I praise one thing without necessarily agreeing with another?

I'm not saying Google is this shining company without a single flaw, but I'm definitely impressed with the way they seem to take their employees as adults that have strong opinions that need to be addressed.

Far from trying to apologize for anyone related to that lawsuit, but in my opinion what happened was a set of people thought they could get away with certain stuff because "everyone in the industry is doing it". Kind of the same with making people sign NDAs which are, for all practical purposes, unenforceable in California. They tried it, got tested in court, failed miserably. Good for us, bad for them.


No, they did not fail at all - far from it. They collectively paid only a $400M settlement, which is likely only a small fraction of how much they got out of the scheme.


> I have to praise Google for the way the situation was handled

The original creator of the spreadsheet claimed that she was retaliated against in the form of her manager rejecting peer bonuses sent to her.


IIRC other Googlers chimed in on HN and said that it was normal practice that managers wouldn't allow someone to get multiple peer bonuses for the same piece of work.


And this is, in fact, both true and one of the few pieces of guidance around peer bonuses. The other is that you're not allowed to peer bonus someone who peer bonused you [in the same quarter], for obvious reasons.


This is for a new grad in 2014.

* Area: Seattle, WA

* Position: SDE

* Base Pay: $90k

* Signing Bonus: $20k immediately, then $17k paid in 12 monthly installments after you reach 1yr in employment.

* Stock Units: $53k (5% at 1yr mark, 15% at 2yr mark, then 20% every 6 months from then on) Note: this vesting schedule is AWFUL.

Needless to say, I rejected this offer and did not work for them. Best decision I ever made.


I think the vesting schedule is back loaded because they give you a pretty large sign on bonus in the first two years.

Your total comp in year one would have been 112.6k which seems about right. The stock price doubled last year, so you would have been looking at at least 125k in year two.


Given the competition, I don't think the sign-on bonus is that large. It only barely makes up for the difference in salary that you can get from a competitor.

E.g you can easily pull $100k to $110k in base pay from similar companies out of school (think LinkedIn, Twitter, FB, Uber). Even well respected startups pay more than $90k (and that's not including any additional bonuses they will surly pay)


What did you take instead?


Revealing that would reveal my identity so I can't say the company name.

I ended up going to a mid sized startup in SF (50-100 people) that was very very well funded and had a ton of potential along with one of the best teams I've seen. I'm still there and love every second of it and am being given amazing opportunities that I know I wouldn't have gotten at Amazon.

Ironically I got paid more on every single vector (base pay, equity, relocation, sane vesting schedule) from this startup than from Amazon. Just goes to show...


To be fair, SF is significantly more expensive to live in than Seattle. MSFT gives something like a blanket ~10% higher offer to SV-area employees for this reason.


Fair point! Though even Microsoft in Seattle pays $100k (source: former roommate).


While this doesn't have as much information as you listed, Glass Door (https://www.glassdoor.com/Salaries/index.htm) has information on job title/salaries at many companies. It's a "share your info and we'll let you see ours" set of rules, so be prepared to make a profile.


Funny that you mention this, because the character limit forced me to cut this out:

Sites like Glassdoor are useful, but what they don't provide is company-specific detail. I can view Amazon's average SDE salary, but is that figure for a job level 4 or job level 5? (At Amazon, pay is based on job levels. Two people can hold the same position but have different job levels. For example, Area Managers who are promoted from hourly positions start at level 4, but new hire AMs come in at L5).

Other things Glassdoor can't provide:

-Pay increase percentages for internal promotions

-Pay increases and stock award amounts for annual performance reviews based on performance grade

-Compensation data broken down by race, national origin, native language, etc.

-Differences in pay for positions based on team, department, geographic location, etc.


While it doesn't help for all of that, looking at H1B data on a site like http://visadoor.com/ helps fill out some of the picture. You can see specific numbers instead of just ranges while also adding some context about national origin.


Those are also deflated prices compared to americans with equivalent education and skills, though. Which is the entire point of the H1B.


What I don't like about that is most of the entries will be old. I'd love if it had a way to show me only information from the past year.


Given that compensation in the Valley can go up 10% a year, and a significant portion can come from stock and bonus, I find data on GlassDoor to be fairly useless. The h1b database is a good source on base pay, but doesn't show stock and bonus.


I created a throwaway just to pretend my salary isn't public record.

Location : Eugene, OR.

Position: Assistant Professor of Mathematics Tenure: 3 years Base pay (9 month) $72,000 in 2013, increased to about $75,000 in 2016. (minus union dues). Will increase to $82,000 when I make tenure.

Signing bonus: $0

Stock: $0

Pension : keeping my fingers crossed.

Experience when hire. Ph.D plus 5 years post-doc (at Princeton.)

Gender : M Native speaker: Yes.


This is exactly the reason I decided not to stay in academia after I got my Ph.D. I could not rationalize working 10 to 12 hours a day, 7 days a week, trying to teach, conduct research, scramble for funding, participate in department politics just to attain tenured position at an R1 school while making barely 75K starting.

I now work in a development position at a large tech company for which I'm overqualified. I work about 7 hours a day plus a couple of meetings. I never work weekends, have plenty of free time to conduct research on the side and make well into 6 figures.


Seattle Googler here (throwaway account).

Position: Senior Software Engineer (level 5)

Tenure: 4 years, no prior experience

Comp: $300K (160 salary, 40 bonus, 100 stock)

Male, native English speaker

P.S. We're hiring.


Just adding not all Googlers make that much. I have 7 years in industry, L4, and make 117 base with 40k of stock a year in San Francisco (was 30k at grant time). If you can convince Google you're worth more they will pay it but not all Googlers are making crazy cash (btw wish I was in Seattle given CoL difference).


I believe 117 base is low for SWE3.


Not SWE is the catch. Still primarily coding role though.


UXE?


And not all Googlers make this little. I have the same position, in the bay area, and my pay structure is roughly:

$180k/year 15% bonus ~ $30k/year 600 RSUs in the first year = $440,000 400 RSUs in the second year = $280,000 200 RSUs in 3rd and 4th year (assuming no refreshers, and oh boy there will be refreshers!)

Male, native english speaker.

It helps that my prior job had a comp level around $480k/year and also I got hired when GOOG was $550/share.

BTW, the T-5 salary band ends at $180k. So you're pretty close. Its the RSUs that make all the difference.


But you received an abnormally huge initial RSU grant. It's uncommon for anyone to get more than 500-600 (outside of leadership) unless you're a strategic hire and they're compensating you for unvested stock at your current employer.


Indeed it's high, but also it just shows you what is possible.

I don't think I was a highly strategic hire, just a very solid engineer with a lot of experience, prior employment at Google (and Amazon), and a strong salary and stock compensation at my immediately prior job.

So they busted out the competitive offer, and I was very happy. Also the stock went up like $200 a share.


You get 100k per year or over 4 years?


That's what's vesting this year. It can fluctuate a bit (so far only upwards for me).

Upon hiring and usually each year thereafter we get grants that vest over the following 4 years, varying in sized based on budgets, level & performance scores.


Thank you for sharing!

I started a discussion for Google salaries here: https://news.ycombinator.com/item?id=11314449

If you have a chance, can you send the link to your colleagues at Google? (-:


For those of us in the midwest... This compensation package is about 210k$ in Austin. Obviously, outside of expensive cities like Austin/Dallas/Chicago, the equivalent number is lower.


If you're hiring, do you take college students for interviews? I've never been clear about the google hiring process and I've always heard mixed things from people who went through it.


Yes, we hire new grads, and we offer internships for those who are still studying. Successful interns get an easier path for converting to full-time than grads who apply cold.

Getting somebody you know at Google to refer you is the best way to secure an interview, but you can also apply online.

http://www.google.com/about/careers/students/


Well that's too bad, I don't know any people at google. I guess I need to hang around more coffee shops.


The hiring process is a bit hit and miss. I know people who had a really good experience, and I know people who said it was a shit show. About meeting Googlers: if you happen to come to the Bay Area, you can't throw a rock in any direction without hitting at least one Googler. Not saying throwing rocks is the way to go, but... you'll get someone's attention :P


I'm a poor college student on the other side of the country, no dice for now.


I've noticed that Google is better than most with online applications. I managed to interview 2 years in a row (intern, college student) having only applied online.


APPLY ONLINE. Seriously. If you don't have a referral, don't wait around trying to find one. Apply online.

If you get an interview, practice algorithms/data structures interview problems like crazy.


...really? I was under the impression everybody that reads HN would have been around the Google-or-similar hiring circuit at least once. I have twice and I'm not as experienced as you are.

Daily 10K I guess.


I'm interested in working at the Fremont office. Do you know any ex-Amazonians that are at Google now that I can talk to? I've put an e-mail alias in my profile.


every year they give you 100k in stock? or just at signing?


So, I'm graduating UW in June, where do I apply?


Any connections in the Cambridge, MA office?


Can you please specify which domain? tech stack used, programming language, technology etc.


Google does not care about this for entry level engineering positions.


He is not working at entry level engineering positions.He mentioned 4 years experience.


What I mean is, Google does not care about the specific technologies you've worked with if you're joining the company (as long as you've worked with some technologies). E.g. it doesn't matter what databases you've worked with, just that you've worked with databases in general.


Position: SDE III Tenure: almost 1 year Job level: 6 Base Pay: $150000 Signing bonus $50k year 1, $40k year 2 Stock: 450 shares, spread over 4 years, 5%/15%/40%/40% No promotions or reviews yet Gender: M Native English Speaker: Yes Location: Seattle


I'm a TPM III, 10 year experience in consulting before coming to Amazon, former developer and dev lead. Been at Amazon 18 months.

Base is $145k. Signing bonus $50k year 1, $40k year 2. Stock 350 shares over 4 years. 5%/15%/40%/40% No promotions or reviews yet.

In summary: about $200k total comp first two years, from then on variable based on stock. I expect about $225 to $250k in 2016.


Wow, nice. Is Level 6 pretty high? What was your experience coming into the job?


Level 6 is a senior engineer. Roughly 90th percentile of engineers. We have principal engineers, but not a lot of them.

I had 15+ years of experience before coming here.


So, to put things in perspective, Google TechLevel-5, which is "Senior Software Engineer" which is basically 1 level above Amazon's "SDE III" position.

Competitive pay offer: $180k /year $50k signing bonus 15% bonus per year 800 RSUs vested equally over 4 years (200/year) 600 RSUs vested in 100-chunks every quarter for the first 18 months.

Counting up, in the first 12 months, pay is about $670,000.

I gotta get seriously bumped at the end of 18 months to keep it up, otherwise my pay will slip to $350,000.

And that is what a competitive offer from a company that values their employees looks like.

I have friends who have totally gotten the $1m RSUs/year for 4 year offers from both Google, Facebook and others. These positions exist.

It helps to change jobs a bunch :-)


holy cow- and people still leave to do startups? They must be really crazy.


Do you mean that's 800 RSUs overall or 800+600=1400 RSUs over 4 years?


it's 800 over 4 years, and 600 over 18 months. So 1400 total.


Good to know. Thanks!


It's senior sde level. Not everyone is expected to make senior, and they only have something like 10-15% at that level or higher.


While traveling the world, I feel in love with Cape Town so much, that I decided to apply for a job at Amazon since their recruiters were constantly emailing me anyways. EC2 was started in Cape Town and that office does mainly AWS support tools, but not as much EC2 work any more.

I do not remember the details too much, but it was something like $84K for my first year, after stock and all that nonsense. The salary is not much compared to the US, but very good for South Africa. However, the offer was in Rands, which has since collapsed. I would have lost about 30% of my salary when converting to dollars.

I did not take the job for various reasons, with very few having to do with Amazon. The team itself was excellent and I regret not joining, but I am glad I did not partly because of collapse of the Rand.

I still miss Cape Town. One day I will return for another visit.

EDIT: I can provide more detailed numbers if people are interested. Would need to dig up the offer letter. Very few Americans must have applied like I did, so Amazon could very easily figure out who I am. Hey, I loved your team, it just was not meant to be!


Speaking as someone who just finished a 2-year rotation through Cape Town as an SDE - massive, core parts of EC2 are still there and aren't going anywhere. "not as much EC2 work" is definitely not accurate.


Perhaps what I meant to say is that "control" of EC2 went to Seattle, from what I understood.


Germany, Lead Engineer at a company with a couple of hundred employees, my role involves architecture, full-stack coding, cloud stuff: ~$81k (some part of that variable bonuses, depending on companies targets).

While the job market seems to be in favor of job seekers these days (it seems to be practically impossible to recruit developers for small/medium shops, you get pinged by recruiters all the time) the salary does not really reflect this. it's rising but pretty moderately. you get offered $100k jobs once a while, mostly in finance.

Also the air gets pretty thin in germany when you actually want to do technically interesting and challenging things. Most jobs on the market are quite dull and involve enterprisey and/or legacy things. Most developers I worked with, however, do not seem to mind the backwardsness, are happily married to their languages and tools, and tend not to be overly passionate about their work (which might just be the right attitude).


I worked for Amazon (2013-2014), fresh out of college.

Title : Software Development Engineer (SDE I)

Base : 98,000

Sign on : 50,000 (2 year period)

Relocation : 10,000 (2 year)

Stocks : worth $70,000 (4 years)


Above someone mentioned being SDEIII, what's the meaning of these levels ?


I is fresh grad, basically right out of school, II is mid level, III is basically senior engineer. at that point it goes onto principal and beyond.


Ieee FML this has been a depressing read. Is anyone else realizing they are severely underpaid?

Passes the virtual whiskey


Am I correct in thinking you feel underpaid compared to Amazonians?

Because, man, I won't even tell you what people in the real industry get paid :-)


I'm reading it thinking, "Hmm, do I really hate working for other people that much?" I've run my own companies since I was in my early 20s, and have never taken on more than contract work for others. But, I've very rarely been able to pay myself as much as even modest developer or IT salaries at big companies in major cities.

But, that may mean I just need to stop trying to make a living out of Open Source software. ~20 years of it might be a sign it's time to try some other approach.


Maybe pick Open Source Software which people pay good money for skills in? :)


There's always that one person...

I've done that, and my most personally profitable years were doing that, billing $125/hour the last year I did it (this was eleven years ago), and working slightly more often than I wanted to be. There was a lot of travel, as my particular specialty was something that was needed by companies with very large websites, but not by many others, which I suspect is gonna be true of most of the "which people pay good money for skills in" projects. Being a contractor has most of the same disadvantages of having a real job; maybe pays a little better, and maybe you work a little less because of it. But, it has some additional negatives that I found made me unhappy.

I haven't gone back to contracting not because it isn't profitable, but because it isn't what I want to do. I want to build things, not merely install and configure software (even being really good at installing and configuring complicated software leaves something to be desired in the "job satisfaction" category).

Anyway, I've been making my living on Open Source software for approaching 20 years, through two different companies, and a half dozen pivots and business models. I'm not making statements out of lack of knowledge of the topic.


No worries at all. Wasn't sure where you were coming from. :)


Question is, do you work in the same geographic area? Pay ranges are extremely regionally-based, because cost of living varies wildly.


I'd say it's not so-much the cost of living which really drives the pay ranges, it's more the level of local competition for talent. The actual cost of living difference between, e.g. metro-west Boston and Bay Area probably can explain less than half of the salary difference.


When US devs talk about their wage it always seems absurdly high to me as someone from the north-west of the UK, but I know you have to factor in health insurance and living costs (particularly if you live in the Valley or Bay areas).

Even so, after factoring in living costs and all the other differences, they're probably still making two or three times what I am, with less experience.


Yup. I'm in the UK though where devs are paid shit by comparison, and in the North West where it's definitely on the lower-end of the scale.


I'm reading this and thinking Amazon employees are really underpaid - making more than some of these people with less experience in base salary (not even including options) at startups.


Apologies for the bad formatting, it wouldn't let me edit for some reason. Here is a more readable version of my compensation:

Position: Developer (not classified as SDE, do not manage ppl)

Tenure: 2 years

Job Level: 5

Base Pay: $73,000

Signing Bonus: $25k Year 1, $21k Year 2

2016 Stock Vest: 104 shares

LY Review Score: Exceeds

LY Pay Increase: 4%, plus 35 shares of AMZN

Most Recent Promotion Increase/Stock Grant: N/A - no promotions

Gender: M

Native English Speaker: Yes


i've witnessed the same internal hire negotiation imbalance at another company. you're definitely right, external hires have more leverage.


Would very much love to see frequent "Ask HN: How much are you making?" threads.


Post one! (Maybe wait until Monday morning, or whenever prime time is on here, to maximize participation.)


I was working in one of the Indian offices and was recently offered a move to Seattle. I had 1 year experience(was still an SDE-1 but my manager was considering me for a SDE-2 promotion) - they offered 110K base pay with 25k signing bonus which vested over 4 years + around 86k worth of shares which again vested over four years.

I chose to not take the offer but went to join a different company.

I just want to say that if you're quitting for reasons other than compensation, then don't ever listen to competing offers from your current team/company. That way you save yourself a ton of regret if your new job doesn't go well. #lesson-learnt-for-me


What'd you do/take instead? Company/Salary?


Position: Senior SDE Tenure: 6 years Job Level: 6 Base Pay: $141,000 2016 Stock Vest: 162 shares Review Score: Exceeds Gender: F Native English Speaker: Yes


Senior SDE. Tenure: 2.5 years level, 7.5 total Level: 6 Base pay: $127,000 2016 Stock Vest: 273 Review Score: Achieves (don't know this year's yet) Gender: M Native English Speaker: Yes


Wow that's stock heavy.

How does that vesting work? 60some shares per quarter or each half year?

I'm really not a fan of having so much comp be stock. It's a way to go I guess.


I hope this takes off. I always thought it was weird hiding how much you make -- this only helps employers, and not employees.


I am not sure whether keeping salaries confidential is good for the employer, employee, neither, or both, but you are stating what appears to be the most common belief.

Different people have different preferences, and some managers probably have mistaken beliefs about what is good for them and their employees.


One mechanism by which it's good for the employer is information asymmetry. The employer knows all of the employees' salaries, but the employee does not have this information.


On the other hand, the employee might feel like others are being paid more than them even when it is not the case. The employee may also resent the management's lack of transparency.

I could see it going both ways, and I'm not sure how to figure out what the impact of wage secrecy is.


It seems to be simple economics and negotiation tactics to me. Backed up by the fact that it's such a taboo subject among coworkers, almost always for reasons of 'don't want to rock the boat' and 'don't want to get fired'.

From a negotiation standpoint, the employer (generally) wants to hire, or give raises to, the employee at the lowest possible total cost. Whereas the employee (generally) want to be hired, or get a raise, at the highest possible total cost. Where the cost analysis may not be the same for each side.

Now assume that that all other things being equal, and no information about salary rates are known, the employer's range for salary is $80-$100k, and the employee's range for salary is $70k-$90k. In this situation, the employer would love to hire at $70k, which they may be able to do if the employee doesn't know any better. Now, imagine that the employee had information about the employer's salary range, then the employee would smartly shift their salary range knowing that the employee was 'low'.

The same applies to raises. If an employee has no information about other coworker's salaries, then the 'standard' raise of 3-4% might be acceptable. However, if another coworker has a significantly higher salary, with similar responsibilities, then the employee may ask for a higher raise. They may or may not get that raise, but it's at least a possibility. One which the employer is likely to not want to have the employee know about.

The worst case scenario for the employee is to find out they are making significantly more money than their coworkers, in which case they have no further bargaining power.

So really, the question of whether or not it's a good idea to share salary information to other current or future coworkers comes down to whether or not you're on the 'employer' side (where additional salary information can only move your costs upwards), or on the 'employee' side where having no transparency about salary can prevent you from getting the best salary possible.

Since the difference between having salary transparency or not is so high, it behooves most employers to subtly discourage salary talks. So you end in a place where it is a possibly a violation of federal law (for the federal government), or possibly state law[0], to prevent people from talking about salaries, but at the same time people will almost always only post their salary information anonymously.

[0] - http://www.dol.gov/wb/media/pay_secrecy.pdf


People value transparency, and it might be that they would prefer a lower salary at a more transparent workplace. In addition, providing wage transparency allows for further transparency in other business areas, such as gross margins, R&D costs, etc. which may be valuable in allowing employees to understand the business better and contribute in more meaningful ways.

You are also only addressing the workers with below-average wages (who may be qualified for higher pay) when you say that secrecy helps employers. Half of all employees have above-median wages, so I would assume that transparency could be used to bargain them down, as the below-median workers were helped in bargaining-up; I am not sure what the net effect would be, and don't know why we should assume it goes one way or the other.

I am not an advocate for wage transparency or opaqueness, because I don't know which way the effects go for anyone. I am also an advocate of deregulation, and abolition of most laws, simply because there are so many that nobody knows what is illegal; this seems to be yet another case of governmental over-reach.


If we focus on Amazon, lack of information is going to be asymmetric, with Amazon as a large employer holding the informational advantage. Amazon can see what the salaries are, what people accept, and what people were making when they left. If people want to try bargaining up because they think they deserve more, Amazon knows better if it can ignore the request and find the same talent for less.

And I don't see how it's relevant to mention how workers have "above median wages" compared to national figures. If anything, wouldn't that imply that Amazon is blindly giving out too much money and ignoring this very public information? That's implying an unlikely level of incompetence, when it's really about variation within the labor market.


You assume that more information asymmetry always helps the employer; it is also possible that a lack of information makes the employee think they're getting a 'bad deal', because they overestimate how much their coworkers make (possibly due to something akin to impostor syndrome). If Amazon thinks they can find someone of equal skill for less money, they should make the change, and if the employee thinks they are worth more than they can get with Amazon, then they should leave; I really don't understand your (second?) point.

I never said the above-median wages had anything to do with national figures; I meant that depending on what the employee and employer were bargaining around (more likely to be company median wages than national), the comparison would help the employees bargain up half the time, and the employers bargain down half the time.


People value transparency, and it might be that they would prefer a lower salary at a more transparent workplace.

I specifically said above, "Where the cost analysis may not be the same for each side.". This obviously includes non-salary benefits (stock, vacation, flex time, home life balance, etc).

You are also only addressing the workers with below-average wages (who may be qualified for higher pay) when you say that secrecy helps employers.

I specifically said above, "The worst case scenario for the employee is to find out they are making significantly more money than their coworkers, in which case they have no further bargaining power.". As an employee, your bargaining power is not reduced if you have knowledge of that you are paid above the median. In other words, from the employees perspective, there is no situation where you are in a worse negotiating position due to having more salary information.

so I would assume that transparency could be used to bargain them down, as the below-median workers were helped in bargaining-up;

Note that when negotiating, the only party that is going to negotiate for lower wage is the employer (since it is generally unlikely that an existing employee is going to ask for a lower wage voluntarily). And from that position, the employer already knows all current salaries. If you are making substantially more than the other people, then the employer can (and likely would) reveal that information in order to help secure a lower raise (or also likely, no raise, and unlikely, a lower wage). That's the power of information asymmetry. The employer can use the information when it benefits them (reducing the size of a raise for an already high compensated employee), but withhold that information when it does not benefit them (when a low compensated employee is up for a raise).

don't know why we should assume it goes one way or the other.

We don't have to assume anything. This is basic economic and negotiating tactics.

I am not an advocate for wage transparency or opaqueness, because I don't know which way the effects go for anyone.

It's perfectly reasonable to have an opinion on wage transparency, but it seems a little odd to say "I don't know which way the effect go for anyone". We have negotiating models and frameworks specifically for this type of activity. And the general rule is, "The more information asymmetry that you have in your favor, the better your bargaining position". Specifically because it allows the party with the additional information to use that information when it benefits them, and withhold that information when it does not benefit them.


It may be zero sum or not zero sum depending on different situations.

If all employees values transparency and fairness and would rather have a lower but more fair pay, them the transparency may work.

However, the employer typically derives more profit per unit of work if they employee makes less. Also, if you are a good negotiator or you are the type to always threaten to leave if not given more pay you benefit from the opaqueness. If the company has a lot of good negotiators it may make sense to be more transparent to keep the overall wages down since no one can exercise that benefit.

There are probably other factors such as supply and demand beyond individuals at specific points in time which need to be taken into account (surge pricing?) we need someone for this project now, so we will pay them a premium even if we would normally pay them the same as everyone else, even in consideration of long terms costs this may make sense.


You implicitly assume that the employees would all (or net) make more money under a more transparent system, and I am not sure why. It may be true, but some may also accept smaller raises if they know most coworkers are at a lower salary. I can imagine a number of effects that transparency may have, and do not know their net impact.


Yes, people seem sure it only benefits the employer but I have a feeling others benefit from it too. There have been times when I didn't really want my coworkers to know what I made.


It's weird and possibly generational in America; my mom specifically warned me that people would be "highly jealous" of my salary and that I should keep it a secret when I first entered the workforce.


It's not very common thing in Asia to hide your salary afaik.

E: Why the downvotes?


I'm male, a native English speaker, and worked in Seattle around 2013-2015. I was already in Seattle, so I didn't need to move. I was an SDE1, though I came in with a bit of experience (~5 years).

My base pay was right around $100k. I had a $20k signing bonus the first year, and something effectively similar for the second year (though less cash and some stock was thrown in).


Sde I with 5 years experience?


MSFT hired me at the lowest level (SDE I level 59) when I already had about 6 years experience.

I know someone who was a had a senior role at one company and was a lead at another and was also hired as SDE I.

I think it's a bad case of "doesn't matter what they did before, we're freaking MSFT, no one's good enough for us to be hired into a higher position."


I'll add my $.02 for LinkedIn.

Sr Software Eng at LinkedIn in CA.

$165,000 Base

$25,000 Hiring Bonus

$300,000 Stock (25% 1st year, then quarterly for the remaining 75% over 3 years) ($300,000 at the time, now it's only about half that).

10% annual bonus.

Male. Native English Speaker.

I can also speak to a friend here all the stats are the same except he got a $35,000 moving stipend instead of a hiring bonus.


Hey, that's a good deal! I can hear the clicking sound of all the devs sending their resume to linkedin right now ;)


I am an ex Amazonian, worked for a year and a couple months from 2014-2015 for AWS. I was a straight-out-of-college hire. Base: 93k Stock: 177 options over 4 years. bonus: 30k signing bonus upfront + relocation to Seattle, additional 25k after 1 year tenure spread out in 12 payments, one per month Review: Exceeds, and Rolemodel for Amazon leadership principles. Gender: M Native English Speaker: Yes

More info: I was promised a promotion and raise, but the problem was they only do promotions once a year, in april. Once I said I was going to leave, I was offered $120, but I left anyways. Now I moved out of seattle and am making more, but in a lower Cost of living location. Also, I had to pay about 8k for "relocation" back to amazon because I left before 2 years.


Amazon does 2 promotion cycles per year.


I don't work at Amazon, but I have caught on to what, to me, seems to be an unsettling concept. This may or may not be new, but the concept I am getting it is often referred to as "internal equity" - considering what salaries are already in place for similar positions.

This appears to be one of many variables HR uses for salary negotiations and I recognize that. I don't see why this necessarily matters for most work places. Shouldn't you just pay for what the candidate brings to the table (skills, experience, etc.) and not consider what, even someone with a similar background is currently making in the company. I suppose salary negotiations/the labor market isn't an efficient market where a price can be assigned given x, y, & z.


After reading some of these comments...

Holy shit, I am under paid.


Right? I like the one from amznnewgrad: $90k base as a new grad and "needless to say" they declined the offer. Needless to say?

I was hired after a year out of college in 2010 at aboyt $37k and it felt like I hit the lottery. Granted, where I live costs much less than Seattle, and I also make significantly more now, but still not $90k.


37K is extremely low for a SDE, even in rural America. Sorry dude. You can probably go to another similar COL place and make 45-80K.


Yes "needless to say." I was paid a little bit more than the annual equivalent of 90k when I was an intern in SV at both a large tech company (that you've heard of), and a well-funded startup.


amznnewgrad is trolling for sure!


I'm not sure why you'd say that. TripAdvisor, my first FT gig, offered new hires $85K in Boston in 2010, plus a pretty significant stock package. Today, in 2016 (or even last year), $90K in a similar CoL, similar demand market is nothing to write home about.


Unlikely. New grads get 100k easy, at any company in the Bay Area, NYC, or Seattle. Thats just the market rate.


I can confirm that it sounds reasonable. My offer was over 100k at amazon a few years ago as a new college grad (though I declined). Glassdoor seems to confirm that this is the norm nowadays.


90k$ is low, I have seen several get 140k$ (Base + Signing bonus) for SDE roles out of college.


Which is why companies treat salaries like state secrets. If you don't have a reliable baseline you can't use "I'm underpaid" to your advantage in negotiations. You may not even know you are underpaid! Information asymmetry.


Yep. Someone from Microsoft - where I work - posted here that they're making $115K at a level below mine, which is just a tad less than I make. Also, I've realized from recent conversations with coworkers about taxes, savings and investing that I make significantly less than them.


It certainly is making me regret my life decisions.


I know right ... Jesus.


If your reaction to this thread is "wow I am really underpaid" then it's working. The playing field for your next salary negotiation is now a little more level.


I feel like every developer in the UK is underpaid when compared to US devs lol.


Google San Francisco Test Engineer III (level 4) ~130k base, 15% annual bonus target, w/ stock around ~200k annual total compensation *non-native speaker

I do have a decade of industry experience. Also my 1 bedroom apartment rent is going to be 2900/month this year (annual lease was 2600/month last year, they raised it by 300 because fuck you where are you going to live, it's 2800/month across the street and do you really want to get roommates in your 30s?)


Throwaway account.

I don't work for Amazon but here is my salary information, for anyone who is interested

Current position: 50-100 employee startup in Palo Alto, $170k and .1% equity vested over 4 years

Previous position: Google, $130k base, 15-20% annual bonus, around 64 shares vested per year (so around $170k annual net comp) Previous position: Small startup, $90k base

I live in the SF Bay Area. When I interviewed, most offers from startups were in the range of $140k-$170k.


Amazon, and any other major company, has created a salary range for any role. As someone who has hired for many of these companies, I can tell you: Sharing your compensation is taboo, but do it anyway. So long as you do it honestly and completely. Talking about only salary in a company that rewards heavily in stock is not useful.

There is negotiation room. However, playing the game of show me your hand first is just plain annoying. Why should a company pay you more than is standard in your role? Are you leaving bonus/stock money on the table to come there? Relocating? Losing money on a lease? Tuition? Costs covered by your current employer or another offer (ie housing, transportation, childcare, etc)?

It's a myth that all companies are out to lowball you. The more successful a company is, the more likely it is that they've realized internal equity is at least as (if not more so) important than being competitive in the market.

Go see twitter #talkpay. A lot of great data points were shared there.


The OP is being kind of cagey about what their role is. Nearly everyone at Amazon who does what we would generally be considered a primarily dev role is either an SDE (Software Development Engineer) or a WDE (Web Development Engineer). Are you a support engineer, by chance?

As for salary negotiations, the best piece of advice I got was to never say a number. You really don't have to, you can just keep saying some variation of "industry standard", their median salary numbers on Glassdoor, etc.

This is true for Amazon specifically: I never told them a number despite being asked by several different recruiters, and the offer I ended getting was slightly above their average. If you want more than that there may be some other technique involved, but if you're more concerned about being undercompensated, definitely don't get tied to any number.


The OP is being kind of cagey about what their role is.

You're right, I am.


Some facebook internal compensation numbers -- https://docs.google.com/spreadsheets/d/1E1Jz00naFjdfP5RVC3AY...


If you are good, just leave AMZN. I was underpaid there as SDE 2 and when I resigned, they threw $100k extra a year on the table to keep me but I still left anyway because I did not know what they would do to me if I stay. That $100k extra would put me close to $300k total a year.


they threw $100k extra a year on the table to keep me but I still left anyway

That was a smart move, especially if your skill-set was unique in your company. I've given this advice more times than I can think and I've been ignored at least half of the time. I can think of only one case where it worked out well, but that friend was a CEO at a multi-national and the board of directors was the salary decider. The others were gone within a year.

Be very suspicious if it's a huge increase in salary (or dwarfs your current offer), but generally any "counter offer" is not a good idea to take.

When you get a large counter offer, you have to think one thing: Why?

At first you may be inclined to think "It took me having a foot out the door before they finally valued me!" Unfortunately, what they've valued is the risk you represent. Within a few days, after your manager has discussed "contingency plans" for all of the things you did. You'll be spending the next few months making "the documentation a little more clear" and "cross-training" your colleagues. They may finally fill that position they've been promising to hire for to "give you some help". A few months of this will go on and someone in management will ask how your salary is justified (this will likely not be asked directly to you). Unfortunately, all you've been doing is documenting and training others, the real work that contributes to the bottom line has been ignored and you're now behind! How can they justify paying you so much if you're getting nothing done![1]

I even had a colleague who thought the answer was to turn down the job, take the increase and find another. It might have worked were it not for 2008. He went 6 months unemployed and took a job for a lot less than he was making prior to the increase (specifics were not offered or asked).

[1] It doesn't always (hopefully not even often) happen with such calculation or disregard, but a variation of this almost always plays out.


I couldn't agree more with you. It was tempted but honestly ultimately it came down to 3 reasons: 1. I did not trust my manager(s) in that AMZN division 2. I did not like AMZN culture 3. Their counter offer was only 2% more and it was structured in a very weird way.

I am really glad I did not stay, new job has been way more challenging.


Position: Developer in Seattle

Tenure: 4 years

Job Level: 5

Base Pay: $143,000

2016 Stock Vest: about 140 shares

Review Score: Exceeds

Gender: M

Native English Speaker: Yes


Even with a throwaway, isn't that enough info for Amazon to identify you and possibly take punitive action? I understand that Amazon is big, but without adding a certain fudge factor or range to all the numbers, then I would think it's possible to identify a person.


how would that prove that it was actually her/her though? It could be easily be one of her higher ups who knows his salary details.


Alternatively it could be completely made up numbers that happened to match a real person.


Punitive action for what? Revealing information that is already on sites like http://h1bdata.info/


What was your experience coming into this position?


3 years working at a small startup which eventually folded. I am in my late 20s.


I honestly don't know why I'm so worried to post from my main account since I don't work there any more, but I am, but here was my salary. I only worked there for 12 months as an SDEII, part of my package involved being relocated from a different continent.

My compensation was as follows: Year 1: 122,000 + 28,000 bonus + Relocation + a lot of other benefits. After that, the base assumably would have went up, but the bonuses I was given were 250 AMZN rsu's 5% after one year anniversary, 15% on the second anniversary, 20% each 6 months after.

Amazon does an amazing job of woo-ing people and making attractive offers, unfortunately they don't put the same effort into retaining their staff.


Location might be useful information. I'm assuming most of the folks responding here are in Seattle. If so, all the salaries listed in this thread seem shockingly low to me.


I think you're not doing the math on the stock (which is currently over $550). e.g. $73k base + $21k bonus + $57k stock = $151k for an engineer in their second year (no info about previous experience). Absent a lot of other context it does sound fair to me, or at least not "shockingly low".


I value those things differently, because the bonus is only for the first two years, and the stock is a one-time grant. Just like there's 'no replacement for displacement' in engines, there's no replacement for base salary in compensation. What I'm seeing in that compensation package is no incentive whatsoever to stay after you finish your second year, and no real incentives to start in the first place. $150k in Seattle is not great in my mind anyway, that's roughly equivalent to $90k where I'm living right now, but the average base salary in this area is around $120k...


Stock isn't a one-time thing.

RSUs are frequently given during annual performance reviews to employees with good reviews. For my first annual review I received a score of "Exceeds" which is second from the highest. For that, I got 35 RSUs worth roughly $19K when they vest (at current price).

In theory, good employees will continue to receive stock grants that vest over time, thus creating incentives to both stay and to perform well.


Key words, when they vest.

I walked away with close to 100k on the table over the next 2 years because I couldn't stand the place anymore. Their golden handcuffs are awful.


I think I negotiated poorly and only ended up with about $97k total compensation in my first year, and by my third year it was about $120k.

The stock seemed like a mind-game to me, but it did work out to about 10% YoY increases in total compensation.

It's also inaccurate to characterize the stock as a one-time grant. The initial grant vests over four years (weighted on the last two years) typically you receive more grants after performance reviews, which vest over two years (again weighted on the second year.)

So in practice, you get a grant of 200 shares at signing, but by the end of year two only 50 have vested. At that point you have at least one performance grant, so you're probably getting shares vesting pretty regularly, at least four times a year.


Not an Amazonian, but everything I've ever read about their comp culture has said that stock is heavily valued/weighted, so there's a selection bias there in that anyone who's seriously considered them should know it going in and be alright with it.


Equivalent to $90k? Do you live in the US? The cost of living for most lifestyles is nowhere near $60k different between Seattle and anywhere in the US.


Using a random cost of living calculator (like this: http://www.bankrate.com/calculators/savings/moving-cost-of-l...), it looks like many places aren't $60k different. But Atlanta, Dallas, Indianapolis, and lots of other cities are ~$50k different. Rural places are ~$60-70k different.


What number are you using?? For $150k, I see Atlanta, Dallas, etc. as $15-20k different, which seems correct.


Going from San Francisco to Dallas, using $150k gives me $81717.69.

Meaning the equivalent income to maintain your standard of living in Dallas is $81k, or ~70k less than San Francisco.


I'm in San Antonio, TX. The 7th largest city in the US, but it has one of the lowest costs of living of any major metro area. It's also home to several tech companies, including Rackspace, one of Amazon's primary competitors in the Cloud space.


The cost of living calculator posted by SNDean (http://www.bankrate.com/calculators/savings/moving-cost-of-l...) calculates that 150k in Seattle is ~117k in San Antonio, so that's actually extremely close to the 120k you mentioned as standard.


This is the one I've always used for many years: "A salary of $150,000 in Seattle, Washington could decrease to $89,728 in San Antonio, Texas" (http://www.bestplaces.net/cost-of-living/seattle-wa/san-anto...) which is where I got my figures. Maybe they are incorrect, but my anecdotal experience in both San Antonio and Seattle makes them seem in line.


I created a throw away account to answer this but I will say that my teammates at Amazon and I discussed salary openly. We all were making far below market except for the 2 teammates who had been there 4+ years.

I think for lasting that long, Amazon really pays off in equity compensation which they dole out willingly (with 4 year cliffs of course).

I made 90k as an SDE I straight of college. 20k sign on bonus. Second year bonus of 15k. 150 shares of stock with the regular 5%, 15%, 20% cliffs. Biggest raise I got was 4k when I received an exceeds.


This is a key difference between Amazon & Google. At AMZN you have to be there 4 years before your comp levels off at acceptable levels. At GOOG they have a much nicer vesting schedule that starts your level comp after 12mo.


I was an intern over the summer, just graduated and was offered 95,000 salary, 27,000 signing bonus with my first paycheck, and another 20,000 over months 13-24. In addition, I get 53,000 in RSU that are payed out: 5% after my first year, 15% after my second year, and 20% every 6 months after that until I've been there for 4 years. Finally, i got a 10,000 relocation lump sum.

I have friends who interned the summer before and they were offered the exact same thing. This is for SDE 1 position.


You're getting jacked around, interview at Facebook/Google and walk away with piles more cash and guess what no bullshit pagers to carry around either!


If I could upvote this more, I would. All companies hide the salaries do they can underpay. Glassdoor under estimates typical salaries and are not meaningful. OP - Please consider opening a simple google doc and let anyone fill in the detail.


I was hired as a "Web Development Engineer I" several years ago (level 4). My base compensation was virtually identical to yours, but my signing bonus and base pay were a little less than half. Stock grants were also very similar at hire. After a couple years my job role changed to SDE, I remained level 4 and was given a better than 10% raise.

In my fourth year my total compensation was estimated to be around 120k.

It's worth looking at the H1B data. I've got some limited anecdotal data, but the H1B data appears to clearly delineate the same salary ranges Amazon gives to US Citizens. (Maybe they will pay citizens 10% more, but the ranges actually look pretty similar to what I've heard.)

http://h1bdata.info/

(I am a US Citizen, English speaker, in Seattle.)

Main moral of the story if you choose to stay at Amazon: don't worry about your level, focus on your job role. You can probably keep doing the work you're doing and become an SDE if you talk to your manager and frame the conversation right.


If you really want to do this, start a Google spreadsheet.


Didn't a Google employee catch heat for doing this at Google a year or two ago?


"Heat" maybe, but as far as I understand nobody was fired. The spreadsheet is still up and going strong.


A spreadsheet about Amazon salaries in Google Docs, or a spreadsheet about salaries at Google? (Or both?!)


I meant a spreadsheet about Amazon salaries in Google Docs...otherwise someone has to comb through this thread to pull out the data. And it allows people to build and share pretty charts.

(as mentioned above, this has already happened at Google)


I work for one of AMZN's subsidiaries down in SF. Its kinda hard to say exactly how much I earn since most of my compensation is in retention and acquisition bonuses.

Roughly $130k a year base, $150k a year in retention and $100k (for one more year) in pre-acquisition stock.

6 years in the industry, no higher education. SDEII (I think?)


I'm starting this summer in Amazon Seattle as an SDE II

- 4 years of experience - Non-native English - They sponsored my H1B application - 145k base - 20k bonus yrs 1 and 2 - 100 RSUs - 15k relocation bonus, 10k extra for relocation expenses. And they give me a full container to move my stuff. - Male


What general region or city is this? Cost of living can be a major effect on pay, comparing, say, the insanity of the SF Bay area to anywhere else.


I mentioned this below, but I don't think location matters because Amazon doesn't provide cost of living adjustments. Location obviously matters from the individual's perspective, but from the company perspective it isn't factored into compensation.


Yeah they do. I was offered a job after a summer internship but told them I'd only work in California -- after first declining, they offered me a position in SF the next day. When I arrived in SF to start there was ~12% added to my salary for cost of living adjustment over Seattle.


Perhaps they do for SF, given how high cost of living is there. I was told that cost of living increases are not offered, but maybe they were only referring to Seattle?


Yeah, it was a pleasant surprise to me on my first day.


Seattle summer intern -> SDE1 Full Time offer

$95k/yr

$27k signing immediate

$20k signing 2 year vesting

$53k stock 2 year vesting

Ended up turning it down because I didn't want to work at Amazon, so no negotiation.


Research Scientist First full-time job 150k

(I saw us make offers as high as 200k for fresh ph.d.'s)


Position: developer, not an SDE though. No oncall.

Experience: college hire (beginning of 2015)

Level: 4

Base: $90,000

Signing bonus: $22,000 immediately, $18,000 monthly over 2nd year

Stock: 200 shares of AMZN (5% at 1 year, 15% at 2 years, 20% every 6 months after)

Location: Seattle, WA. Relocation was included over 2 year prorating.


Position: SDE II Organization: Kindle (Seattle based) Base pay: $101.500 Bonuses: $28.000

I've been at Amazon for about a year and a half. I always suspected I was quite overpaid. And I'm a non-US citizen on top of it.


You're not getting "ripped off" by having a base salary of 125K USD (with benefits and equity) fresh out of college.

Tell you what, with a Bachelor's in Chemistry (in my year 176 people started, only 42 finished the degree so it's not a free lunch) I can expect to make between 40K and 60K CAD out of college and pay higher taxes than in the US. With a master's that I'm working towards, I'd be on the upper end of that spectrum. So boo-hoo to those making only 125K with equity and benefits.

:/


I assume your comment is directed at me, the OP, as it was not in reply to anyone.

>> You're not getting "ripped off" by having a base salary of 125K USD (with benefits and equity) fresh out of college.

Nowhere in the thread has anyone used the term "ripped off" so I'm not sure why you put it in quotes. Your assumption that I am fresh out of college is wrong.

>> So boo-hoo to those making only 125K with equity and benefits.

I think you are misunderstanding the point of the discussion. No one is seeking any sort of pity, as you seem to be suggesting. No one here is suggesting that $125K is nearing poverty.

What we are doing is questioning the paradigm of employers enjoying a superior bargaining position in salary negotiations as a result of a social dynamic that we ourselves are furthering. Specifically, a reluctance to openly discuss compensation.

>> Tell you what, with a Bachelor's in Chemistry (in my year 176 people started, only 42 finished the degree so it's not a free lunch) I can expect to make between 40K and 60K CAD out of college and pay higher taxes than in the US. With a master's that I'm working towards, I'd be on the upper end of that spectrum.

If you are unhappy with your career choice, why don't you do something else?


No, it wasn't directed at you. I should have mentioned that I was talking to others in the thread. Sorry for the misunderstanding. Some people felt entitled to more because they went to school. I actually thought the discussion you instigated was healthy. My bad!


>I can expect to make between 40K and 60K CAD out of college

A chemical engineer with a BS in Alberta can make $120k CAD base-pay, easily.

>and pay higher taxes than in the US.

A San Franciscan making $120k USD pays $46,176 USD in taxes (state+fed)

An Albertan making $120k CAD pays just $32,974 CAD in taxes (prov+fed)

When software engineers want $120k, they move to SF/Seattle and work for <soul-crushing corporate tech-company>. If you want $120k, move to Alberta and work for a gas company.

The vast majority of software engineers (let-alone 'entry level' SEs) in the US aren't making six figures. The ones who move to tech-topia and work for tech-giant and end up getting paid 20% less than their peers who did the same ARE getting ripped off.


> The vast majority of software engineers (let-alone 'entry level' SEs) in the US aren't making six figures.

While I'm sure this is true in the total sense (there are a LOT of bad software engineers), decent and good ones should be making over $100k easily.


What separates a bad SE from a decent SE?


A good grasp of computer science fundamentals.


People skills.


Yes, I have some colleagues who went to Alberta - but they're now out of a job. They are chemists, not Chem.E's though. And I'm in eastern Canada, where the taxes are much higher. You'd pay 50% out of a 120K salary. See my reply to OP - I think I wasn't very clear.


And if you making 30k you would feel ripped off even though some guy who works at Walmart for 20k would feel jealous.

That said, amazon pays new grads pretty okay, and if you get a promotion between 2 and 3 years your new salary should be pretty competitive.


And other people will make significantly less than that 40k. So boo-hoo to those only making 40k with access to free healthcare.


The healthcare isn't free. You pay for it every year and if you're so unlucky to need it, you have 100% access to top notch treatment. But you definitely pay for it.


To be fair, soft. eng. salaries in canada are much lower as well (even without taking the exchange rate into account).


> I'm not aware of any Amazon policy which prohibits sharing one's own compensation, but I still made a throwaway.

IANAL but I'm pretty sure it's illegal as fsck for them to retaliate against you for discussing your compensation.

According to the National Labor Relations Act, enacted in 1935, private-sector employees have the right to engage in "concerted activities for the purpose of collective bargaining or other mutual aid or protection."

Again, I am not a lawyer. Just a bunch of pixels on the screen, really.


FYI, it is illegal in the USA to restrict employees discussing their salary amongst themselves. Unfortunately it is common for companies to declare this information confidential and covered under employee confidentiality agreements.

http://www.npr.org/2014/04/13/301989789/pay-secrecy-policies...


While at Amazon, I worked in two different roles. I don't have the exact numbers, but I'll put ballparks in here:

(1) Support Engineer * Base: $72,000; increased at 1yr to $74,000 * Bonus: $20,000; half in first check, other half over months 13-24 * Stock: I don't remember

(2) Software Development Engineer * Base: $82,000

Gender: M Native English: Yes I honestly don't recall if I was L4 or L5 or both.

Both of these were in Seattle. I do know for a fact that there were/are others who were hired and paid more than me.


What was your education and experience ?


B.Sc. in Computer Science, fresh out of undergrad. Applied conservatively for jobs to get into something I could excel at from the get-go and learn how to work in the corporate world before throwing myself at complex technical problems.

I've moved on to greener pastures, and I think where I positioned myself from the start put me in a hungry mentality, and as such I've been able to grow rapidly.


I work at a podunk Santa Clara, CA startup

20+ years experience. Working remote from southeast U.S.A.

Tenure so far: 2.5 years

Salary: $150K

Stock: purportedly .75% of company 4 years 1-year cliff, with small follow-on grant later, don't know what recent dilution is, though I think more recent funding has been "debt" at low interest with preference

Not a regular VC situation, company funded through other means.

Outlook -- real uncertain, market has definite need, execution so far has been very mixed, company willing to re-do things the right way


* Area: Austin, TX

* Position: Systems Engineer

* Level: 5

* Base Pay: $98k

* Signing Bonus: $18k immediately, 15k over months 12-24

* Stock Units: ~$120k, 5% first year, 15% second, 20% every 6 mo after. Additional (smaller) grants starting year 2.


I work in Portland, have 5 years of experience, and I'm making about 90k after bonuses (no stock or sign-on bonus). I love Portland, my hours are very nice (~35hours), and I have a good amount of technical freedom. But boy....Maybe I should make the move up to Seattle.

It'd be nice if people mentioned how many hours/week they work for me to get a good idea of what to expect. Especially since we're talking about Amazon.


There's plenty of money to be had in Portland. Drop Airbnb, Nike, or any of the myriad of startups in town a line.


When did Nike start hiring competent people?


Out of curiosity, what does this add that GlassDoor.com doesn't?

Note: as of right now, GlassDoor is down for "Scheduled Maintenance" but the question stands.



At my old company, I was a "Jr Sysadmin" in title, but really a mid level Syadmin. I started at $42k/yr, then moved up to around $49k/yr. I should be making $55-65k/yr given my certs, experience: 8 years as generalist IT, mostly Windows Sysadmin, some Linux. Familiar with ShoreTel, comfortable with security -- really REALLY want to make a lateral move to it.

I'm also an SME & do reviews for a certain book publisher to see if I think it is worthwhile, accomplishes the goals set out by the author & is technically correct. I'm unfortunately currently unemployed, so things suck, but I have no qualms about sharing my salary, where I think I should be & why.

Yes, I may not be using crazy automation stuff & yes, I need to learn something as ubiquitous as VMWare, but it's not hard. A monkey can do those things. What I want to get into is SCCM & serious Windows automation. It's just, the positions are few & far between :-(


Still in first year.

Position: SDE 1 Location: Seattle Base: 110,000 Signing: 25k over two years RSUs: 40k when stock was high in 300s


I worked for IBM and we had a policy where you couldn't discuss salary with your peers.

I had a long discussion with manager at the time where I asked the question: "How do I advance my financial career?". We concluded that being an external hire is the best way, and as such, pretty much meant if I wanted more money, get a job elsewhere.

So in the end I did. It was the money that triggered it, but ultimately there were other factors, such as not being given the role I was promised, a miss communication about who would decide my promotion (my old or new department), and of course, being asked to accept a band promotion for no extra money.

I also recall there being published market data you can get from HR which shows the average for your role, and I did notice I was way below average in compensation.

I don't miss leaving one bit.


SDE, Level 5, four years, started w/ bonus: $126k, ended: $117k New job: 175k + equity (fuck you amazon)


Is it common for salaries at Amazon to decrease?


It is when your signing bonus/cash advances expire and raises are never higher than 2%. Also had 100 or so RSU's.


Position: SDE1 Tenure: <1 years Base Pay: $110k Signing Bonus: $20k Gender: M Native English Speaker: Yes

Beat my best bay area offer overall, so quite good with the low cost of living here. It does seem like you have to move companies every 2 years to keep climbing the salary ladder.


I knew the UK salaries can't compare, but I wasn't aware the difference was so high.

It would be interesting to see the difference in pay in the same company between US and UK offices.

Looking at these numbers makes me wish I had moved to the US when I was younger.


These discussions feel good, but are ultimately useless. This is just going to be a collection of anecdotes from people who self-select to report because they feel good about where they're at, or because they feel righteously justified in complaining about their situation. And, as they say, the multitude of anecdote does not data make.

Unfortunately, salary "surveys," like the recently-reported Stack Overflow one, or the classic Computerworld one, are much the same. Self-selection ruins the data. The responses have to be random to be useful. And the silly thing is that most people who are involved in this business know this.


I disagree, I think it is useful.

You are correct that this is nothing close to scientific, but that is not the goal. The goal is to increase transparency around employee compensation in order to correct the imbalance of power in salary negotiations that results from not knowing what others in similar roles are being paid.

For this, statistically valid data is not necessary. It can be enough to know of one or two individuals' compensation to shift power in a salary negotiation.


A friend of mine when he graduated got a base developer salary of $90k in 2011, shares & benefits (whatever that works out to), and I think $10k bonus for every year he stayed with Amazon. He worked in the Seattle, WA, area.


I'm not an Amazonian (for some reason I laugh when I hear someone refer to themselves as this).

I started out at about 64k which after 2 years on the job became roughly 90k, this year I'm on track to make a little under 100k. I think at the moment my role is the equivalent of an SE II or an SE III.

Because of the place I work at, I don't get stock or profit sharing, etc. I think that software engineers across the board don't receive the right compensation until it becomes shockingly apparent to the company and they risk losing us. Honestly, my org didn't bump my pay up until I started putting out feelers to move on.


Stating which location you are in would be important for salary comparison purposes.


Actually not in this case, as Amazon doesn't provide cost of living adjustments. Location isn't factored into pay amount.


That's not completely true. Amazon's offers/pay isn't tied to the cost of living of an area, but to the cost of labor in that area. When I had an engineer transfer from Seattle to San Francisco there was an adjustment.


Are you sure about that? I have at least three anecdotes that seem to directly contradict that claim, and while I realize the plural of anecdote isn't data, but it's still enough to make me skeptical of your claim.


This is what I was told, but others ITT seem to have heard differently. In the examples that you know of, was the person relocating to Seattle or somewhere else, like SF?

It may be that what I was told was correct, but they were referring only to Seattle and not places like SF where cost of living is very high.


A college friend and I both got hired to Amazon in the same round of campus hires. We both accepted Seattle positions, but then between accepting the position and graduating, his team moved to SF, and his offer got increased to compensate for the higher COL there.

Two other situations involved coworkers transferring teams from Seattle, one to Toronto and one to India, both had COL adjustments to their salary.

(Admittedly the evidence is less strong in the latter two cases because they involved simultaneous country changes)


It isn't, but it's hard for outsiders compare that pay to their local pay. Ex: if you are making that in SF, then that's different than making it in Billings, MT, or remote.

So for example, that seems about right for Portland, OR.

Additionally, you don't mention how many total years of experience you have which would also let people compare. Ex: 2 years of total experience (straight out of college) vs 2 years at amazon, and 10 years elsewhere.


Facebook Offer:

iOS Developer

Base Salary: 140k Signon Bonus: 25k Stock / 4 yrs: 200k Annual Bonus: 10%

The job I took this year:

iOS/Android dev Base: 190k Stock / 4 yrs: 3% Bonuses: tied to company revenue

Work History: 4 years over 4 different companies (startups and one big co)

Gender: M

Native English Speaker: Yes


Mountain View Googler here:

1 year prior professional SWE experience at the time of hiring, CS undergrad degree from a state university

Female, mixed ethnicity, American/native English speaker

SWE II, L3

$110k base, ~$45k in stock, 15% target bonus ($172k total assuming stock price stays stable and I make said bonus)

Worth noting that I tried not to give my then-current pay to the recruiter during the hiring process and was (very politely) told that they'd cancel my application if I didn't give them a number. Also tried to negotiate the base salary up (asked for $120k) and again, got very politely told to take it or leave it.


Here's a link for you. Recruiter in the story works at a different company. https://www.reddit.com/r/cscareerquestions/comments/2bu1id/m...

Also if it's an electronic form then I put 1 dollar. It's fun.


Frustrating read. It wasn't in the form, she asked me over the phone after I passed the final interviewing step and they were going to extend an official offer. Good tip though, I've done that before and it's worked well.

I was at a disadvantage in that a) I didn't have any other job offers for a comparable company and wasn't likely to get them anytime soon (see: state university degree, just 1 year experience) and b) wasn't really willing to walk. My company at the time couldn't compete with Google. There was no better offer for me out there, career making opportunity, etc. So when I got told to take it or walk I took it.


Think about this. You've just gone through a lengthy and highly selective interviewing process. You've succeeded where many others have failed. The company has invested a lot of its employees' valuable time in interviewing you. They've decided you are a good fit and are skilled enough for the role. There are no red flags (like a criminal history, ineligability to work in the country, etc) that would prevent them from hiring you. Then they ask how much you made at your previous company and you refuse to tell them.

Do you really think that after all that time and effort, after sifting through a mountain of undequalified candiates, they would now turn around and let a qualified, well-fitting candidate slip through their fingers over a bit of irrelevant trivia? Not on your life.

Demanding you tell them your previous salary or they'd cancel your application was a bluff, pure and simple. Same with them pretending that you were in no position to negotiate once they'd chosen you and make you an offer. Companies always start low and expect to be negotiated up, at least a little. And once they choose you and made you an offer, the power is in your hands. "Take it or leave it" is a bluff.


Non Amazonian(final interview with Amazon) but had to chime in:

Based in AZ Base Pay: $80,000 Bonus: 12-15% holiday bonus My Experience: 2 years front end dev, self taught. Company: Won't name. But ~200 people in the company. 40ish engineers.

Interviewed with Amazon for Web Dev I . Each time salary was discussed, base range was for 85-115k, sign on of $10-25k and I can't recall stock. Confirmed with friends who work there, all are SDEs making 6 figures.

Throwaway account as well, just want those in my area anyways to be aware that earning potential is good.


Ex Amazonian here. I worked as a SDE1 in the Downtown Seattle set of offices from about 2012 to 2014. My compensation was $95,000 base, and about 105,000 once you took into account stocks.


Love this idea! Made a quick site to help everyone post and share easily, hope it helps!

http://honestsalary.com/


Honest question + comment + disclaimer

question:

why not add your info on glassdoor.com? (is there some evil behind glassdoor I don't know about?)

comment:

Probably worth noting general location of employment, like the metro region you're in.

disclaimer:

I've been researching salary myself in the bay area based on glassdoor data:

https://docs.google.com/spreadsheets/d/1BoMvtY_mICEYygy0jXVG...


This is a web application for anonymously sharing salary information among a pool of participants. Each pool is identified by a UUID. A user cannot view the results of the pool unless they first share their information; the pool must also meet a minimum number of contributors set at pool creation time.

https://gist.github.com/anonymous/894b151cc981f783e3af


Position: Developer Evangelist

Tenure: 1.2 years

Job Level: 5

Base Pay: $130,000

Signing Bonus: $25k Year 1, ~5k year 2

20XX Stock Vest: 10 shares

LY Review Score: Exceeds

LY Pay Increase: 1.1%

Gender: M

I really enjoyed my job and would go back. No counter offer when I left but that was at my request. Was up for L6 when I left.


This is super interesting. A lot of responses make me feel underpaid, but I'm not really sure because it's dirt cheap to live in Reno: You can get a 1 bedroom apartment for $500-$1000 a month. For reference, my wife and I bought an 1800 sq ft house on 9000 sq ft of property for $230k.

I've been a software engineer at a small software company ~20 employees for 3 years now, but I've only been out of school for a year and I make $75k.


This thread is depressing, but I'll post my information:

Company: small, non-startup software company in DFW

Position: Senior Research Software Engineer

Tenure: 4 years

Experience: 14 years (4 EE, 2 non-IT SysE, 8 SwE)

Salary: $92,500 (started at $78,000)

Signing bonus: $0

Yearly bonus: $0

Stock: 0

Many of the comments here make me feel like I ab seriously underpaid. However, over the past several years in my interactions with prospective new companies (ranging from startups to subsidiaries of huge defense contractors) I get the impression that my salary is slightly above average.


Yeah that is low compared to the major tech hubs but sounds calibrated to the area you are living in.

It only takes one person to set a price provided they honestly believe in they value... and that person can be you.


Of course they all want you to feel like you're paid above average. :| How much are houses in your area, within a 20 min commute?


MS employee here, with a bit of anonymization

Location: Seattle area

Gender: Male

Category [1]: White

English native: no

Age: 35-40

Years in MS: 5

Title [2]: Senior SDE

Level [2]: 63

Hiring bonus: 0

Base salary: ~$140k

Annual bonus: ~16k

Annual stocks: ~17k (over 5 years)

Annual benefits: ~$25k

[1] http://www.pewsocialtrends.org/interactives/multiracial-time...

[2] http://geekologist.co/decoding-microsofts-sde-titles-and-lev...


* Area: Seattle, WA

* Position: SysDE II

* Base Pay: $120k

* Signing Bonus: $75k over 2 years

* Relocation: Fully paid + $2.5k

* Stock Units: $115k [200 RSUs] (5% at 1yr mark, 15% at 2yr mark, then 20% every 6 months from then on)

* Gender: M

* Native English Speaker: Yes

I have ~2 years of experience.


This seems ridiculously good for a SysDE with that much experience. I had two years at a smaller company previously and was hired as a SysEng I for way less. Not in Seattle but still felt as though I got a raw deal underestimating myself.


I think I understated my experience in my first comment, total I'd put it closer to 4-5 years. But yea, the amount they offered me was more than expected.


Why not just check here: http://data.jobsintech.io/ real data from H-1Bs


This is super interesting. A lot of responses make me feel underpaid, but I'm not really sure because it's dirt cheap to live in Reno: You can get a 1 bedroom apartment for $500-$1000 a month. My wife and I bought an 1800 sq ft house on 9000 sq ft of property for $230k.

I've been a software engineer at a small software company ~20 employees for 3 years now, but I've only been out of school for a year and I make $75k.


Compared to an engineer at a startup in SF making $150,000/year and paying over $3,000/mo [1] for a one bedroom apartment + California income/gains taxes, you're not doing too poorly at all. Your quality of life is also likely better and you're less exposed to crime.

[1] https://www.rentjungle.com/average-rent-in-san-francisco-ren...


That's true. It's hard to visualize all the costs involved with living in the bay when I've never lived there. The quality of life is pretty great here too. Thanks for the perspective!


"Quality of life"

But Reno though!!


Reno is actually a surprisingly great place to live. I think visitors see things differently because they mostly experience the casinos downtown.


Haha, better than stepping over homeless people/human feces!


Don't seem THAT underpaid. Check glassdoor or other stats for regional average.


I work as and SDE2 in Germany: ~€70k base pay + ~€20k RSUs


Here is an offer for someone with 5 years of experience in San Francisco:

Base 180k Sign on 80k over two years 189 RSU over four years with 5-15-40-50% vesting schedule.


Is that 189K RSU?


Almost certainly not.

https://www.google.com/search?q=amzn&oq=amzn

$552 $/share * 189 shares = $104,328 over 4 years = +$26,082 per year.


No, that would be too good! 189 shares


By federal law, an employer cannot discriminate or retaliate against employees for discussing compensation. One of the good things that unions made happen in the past before they made themselves their own worst enemies.

Some companies treat this as "you can discuss internally but it's a company trade secret externally" which I don't know how the courts have actually treated it (if at all.)


Ex Amazonian but I was an SDE1 ~1 year of experience before joining. I worked in Seattle

Salary: $100k Bonus: $25k Stock: I forget but it was not much


I'm genuinely curious, this post has over 208 points and is only 3 hours old.. why is it falling off the front page already?


From my understanding there is a formula that factors in the ratio between upvotes and number of comments.


And now just suddenly it's back to near the top of the front page. What's going on HN mods?


Not a HN mod, but been around long enough to take a guess:

HN penalizes entries (topics? articles? discussions? whatever) that gain a lot of comments really quickly. I think I've seen dang refer to this as the "flamewar penalty". The penalty was probably removed manually, because it was a false positive.


Ex-Amazonian here. Started as an SE1 in 2012 @ $98k, $20k signing bonus ($18k second year), 160 RSUs, and relocation expenses.


Started at 110k + 15 sign on bonus my first year. I got at least 90k over 3 years in stock after the prices went up so high.


Position: SDE 2

Joined: Last year

Base Pay: 145,000

Native English Speaker: Yes


your pay is probably fairly unique since you listed it down to the stocks allocated and per year performance. I have to imagine that the list that includes all the attributes that you have is a fairly short list(probably just you).

just a word of caution if you do fear retaliation at all. might want to fuzz the numbers a touch.


You're getting screwed, big time. Quit now.

Source: I was hired at Amazon as an SDE1 in 2004 at a base salary of $85,000.


Are you taking stock into consideration? When stock is included, my total compensation for 2016 comes to $130K.

Are you still at Amazon? If so, what is your current salary?


My signing bonus was $10k/$10k, so I can compare that. Stock wise, I think it was like 3000 shares, which at the time were going for $30-ish. Don't fully recall.

Not still at Amazon. When I left, I thought I had it good, with total comp peaking just a hair over $200k. And then I went and got multiple job offers that put my BASE at $250k. So, yeah.


Ya I agree. Sounds really low to me, depending on the job, skill level, and experience (that I don't know)


There can't be an amazon policy against sharing your compensation (well, there can be, but it would be void). It's legally protected in the US, under the laws which support union/labor organizing.

(I'm not a lawyer; I'm not your lawyer; this is not legal advice.)


Company: midsized South Bay startup (50-100 people)

Position: Developer (not web)

Age: 25-30

Tenure: 2 years

Initial Salary: $105,000

Current Salary: $120,000

Signing Bonus: 20,000 shares, vesting over 4 years (Taking into account current valuation and strike price, assume stock is worth, to me, ~$0.50/share)

Annual Bonus: None

Additional stock since hiring: 25,000 shares, vesting over 4 years

Gender: M

Native English Speaker: Yes


I'm in Montreal, full-stack developer at a small/medium-size company, four years experience, ~$80k. Feel like I messed up a bit and they would have gone for 90 or 100. But they give great benefits and a 35/hr work week.


Salaries for Germany anyone?


It would be awesome to see such a thread for not only Germany but Europe. There is no way you can compare the salaries from the US with the salaries here.

I can speak for SIEMENS where they publish the pay for open positions internally. However it is very hard to get into SIEMENS currently, given their savings plan.. I heard that the salaries for the open positions are fixed. I have no idea if this is true. I will refer to the IG Metall Entgeldtabelle for Bavaria: http://www.igmetall-bayern.de/metall-elektro/

- Level: Entry level Software Developer, Bachelor or Master - Location: Germany, Nuremberg - Salary: EG9 ~49000€

- Level: Sysadmin, min 3 Years experience - Location: Germany, Munich - Salary: EG10 ~54600€

They cost of living in Munich are the highest in Germany. So in the end you will probably will have less money if you take the Sysadmin job in Munich.

They don't differentiate between bachelors and masters. I will find out in the near future if you are able to negotiate a higher EG level based on that..

It would be interesting to see some salaries from other companies in Europe. But i'm possibly to late in this thread.


> - Level: Entry level Software Developer, Bachelor or Master - Location: Germany, Nuremberg - Salary: EG9 ~49000€

Do they not differentiate between entry level + bachelor degree vs. entry level + master degree?


They don't differentiate in the position descriptions. They just want a degree.. but it is hard to match most of the requirements with just a bachelor. I talked to some colleagues about the hiring process and if that salary is fixed, regardless if you have a master or bachelor. They said yes, there is not much you can do. Furthermore is it difficult to talk about the salary with others because they think it is a taboo.

I checked glassdoor but there is not enough comparable data for entry positions. However, compared to other companies the salary at SIEMENS is good.


I'm not working for Amazon or any other big ones but I think this is a very good idea. Transparency always helps and I wish something good comes out of other people sharing their financial details.


Check out the recently launched site Comparably https://comparably.com/

It is so much better than Glassdoor at dissecting salary data.


> It is so much better than Glassdoor at dissecting salary data.

... perhaps, if you fit in its narrow definitions, share your own salary data, and are happy to 'sign in with linkedin' or give them your email before seeing any results. I wasn't, so can't comment.


How do you have any confidence that any of their numbers are real? Unlike this thread or even Glassdoor, there's a clear incentive to submit fake data to Comparably because they require you to submit a salary before you can see any of their data (and encourage you to sign in with your LinkedIn account).


Yikes. Anybody who gives both their salary and LinkedIn information to any company is either insane or stupid.


Right, so the salaries are probably biased towards the low end.


If you work at Google, you can continue the discussion here:

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


Don't work at Amazon, but..

Social Security(Baltimore)

Sr. UI/UX Dev

Govt. contract at $75 an hour no benefits

In this area you should strive to move your Dev career towards govt. work; govt contracting being the best in terms of hourly pay.


(Non-AMZN). ~10y experience UI developer.

$165k base 20% annual bonus 200k worth of stock vested over 4 years.

I like the company so I did not negotiate showing the other counter offers I had at the time of joining.


Blind https://itunes.apple.com/us/app/blind./id737534965?mt=8 & https://play.google.com/store/apps/details?id=com.teamblind.... talks about salary ad nauseam... so if you want to see salary discussions, get the app.


so this is like, some forum but you have to install some random app? And of course, it wants:

* retrieve running apps * find accounts on the device * modify or delete the contents of your USB storage * read the contents of your USB storage

some other more acceptable ones. Fuck that shit


This is really interesting and I am m glad that you shared. the company will typically move mountains to keep you if you are good.


It would be interesting if people also posted how many hours they work a week, to get a sense of the work/life balance.


And also any unique educational background or special talents, like if they're working in a niche of machine learning or something like that.


25-35 white male 150k base + some equity I haven't paid attention to Senior software engineer (front-end) NYC


I wish I had time myself, but it would be really helpful if someone tabulated the results from this thread.


You need more context to make sense of pure dollar values - in which city/metro-area do you work?


HR can find you based on the numbers you gave if you don't fuzz them a little bit.


I own a small software consultancy based in NYC. I should make roughly 500K this year.


I was there from 2009 - 2011 as a contractor and made $35.00 an hour as an SDE II


Level: SDE II (5)

Location: Van, BC

Base: 99k (CAD currency)

Stock vest in 2016: 60 RSU

Tenure: 2 year


4+ yrs, syseng II, ~107k salary and stock push my total comp to ~145k.


I've always wondered how people can make a living doing Turking.


This is yet another millennial trying to skirt earning their keep.


Base Pay is pretty low for either Seattle or SF Bay Area or NY


I don't blame you for being nervous, but it's actually against the law to punish employees for sharing salary data. Companies try to hide it, but the NLRB would be interested to hear about it.


SWE II at Twitter. Not in SF.

Salary: $118.5k

Bonus: $10k

RSUs: 4500 over 4 years


thats great info, lets make more of these topics!


We went through the comp data on this thread and another one on Google comp (https://news.ycombinator.com/item?id=11314449), and we added it all to this Google Sheet: https://docs.google.com/spreadsheets/d/11tyJW9KPcSiLZBBuf0Z1...

Feel free to share/add to this doc. We'll post this in the Google comp thread too.

Here are the median comps by level for Amazon and Google, just based on the postings collected in the Google doc as of 3/22. --Amazon -- New grad: $141K SDE1: $146K SDE2: $173K SDE3: $250K TPM3: $220K

--Google-- Level 3: $170K Level 4: $200K Level 5: $312K Level 6: $575K T7: $640K Tech Level 5: $660K

Just a few notes - Total comp includes bonus, signing bonus, relocation bonus, and stock. Bonuses and stock were all annualized straight-line. (I know this is not how Amazon stock comp is done, but we assumed this in our calcs.) Since we took postings from 2 different threads, it's possible that one person could have posted once in each thread, in which case that would show up twice in the Google doc. Also, there's a lot of variance particularly with bonuses which are lumped in, and some of the higher levels only have one data point, but you can look at the data in the Google doc if you want to dig in.

If it helps with comparison between Amazon and Google, here's how Amazon levels map to Google's (from Quora: https://www.quora.com/How-do-Amazons-engineering-levels-map-...) Amazon SDE 1 - roughly a Google T3 ("I") or T4 ("II"). Amazon SDE 2 - roughly a Google T4 ("III") Amazon SDE 3 - roughly a Google T5 ("Senior") or T6 ("Staff") Amazon Principal - roughly a Google T6 or T7 ("Senior Staff") Amazon Sr. Principal - roughly a Google T8 ("Principal") or T9 ("Distinguished").

Full disclosure - we're Step (http://www.step.com), and we're building a platform to help engineers and product managers anonymously crowdsource personalized salary and level estimates from decision makers and hiring experts at tech companies. This thread is especially interesting to us, because it shows the need/demand for more transparency around compensation and company feedback. Right now, we're working with ~10 NYC startups that will assign personalized salary/level estimates and other feedback to anonymous profiles, but our bigger vision is that as soon as someone signs up, they'll see how each and every company values them without having to interview/talk to recruiters.


Tried the transparency bit. In larger companies like Amazon it might work because there's still a bit of anonymity. But for most companies large and small here's what happens:

Bob gets hired as a developer in 2012. He's been with the company for 4 years. Bob is a decent developer who gets his work done but makes the occasional mistake. Bob's title is application developer. When Bob got hired he took the job because the pay was as good if not better than his last job and the market was tough back then and he was happy to have the opportunity. Bob makes 50k a year and lives in Florida where the home office of the company is. Bob's title is software developer.

Fast forward to today:

The company is really taken off and they need to hire some top talent and have opened the doors to remote workers. John joined the team back in 2014 at 55k per year. John lives in Florida and is a mediocre developer. Sure he gets work done but it's often late or buggy. He tries hard and has shown much improvement and continues to every day. His title is software developer. There's a new IT manager and his job is to hire in some top talent to work with the current talent to get things moving. Prior to the hiring push the new IT manager sees the salaries currently and decides to bring salaries more in sync with what the market currently is at. As a result of this Bob, between his cost of living increases and this new pay bump is at 65k and John is at 60k.

As he can now look at remote workers he has feelers out around the country. An ace developer applies for a position and has some skills the company desperately needs. She is based in New York and demands a higher salary than the company traditionally pays because the cost of living is higher. The company approves her demands at 90k per year and she starts with the company, also with the title of software developer. Her name is Sally.

A month later the company decides to have transparency across the board with salaries and publishes everyone's salary.

John is immediately offended because in his mind (and by his title) he's doing the same job as Bob and Sally yet is making considerably less. Bob is upset because Sally just got hired and is making an extremely high amount more.

Each of them are considering their titles / positions. None of them are considering the individual situations that have led to the people making what they make.

So how should salary negotiations go. If the company is open and transparent, they should explain to John that basically he's not as good as the other developers so therefore he hasn't gotten the same cost of living increases etc. What he has been getting is an education and the opportunity to improve his craft.

Bob would need to know that he started low and it's just the nature of salaries to creep up the way they have. They'd have to discuss Sally's situation which frankly is none of Bob's business.

While all of them are valued employees, if they all made the same exact amount either it wouldn't be enough or the company would go broke quick. So they can either suck it up and deal with it or find a job elsewhere. They'll be disgruntled either way.

Remember your salary is your salary. Negotiate for what you think is fair. If you want a raise, ask for one. if you feel you should be brought up to current market rates, say so. Ultimately if you are not being treated fairly after giving the company ample opportunity to make it right and communicating with them, then find a new position. Finding out someone has something that is worth more than what you have will always make you want what they have, that's just human nature. Not disclosing salaries is more to keep harmony amongst the workers and people happy in their jobs and focused on THEIR OWN needs as opposed to just trying to get the same thing as someone else for whatever reason.

Are there companies who leverage this for nefarious purposes? Sure but you really shouldn't be working for those companies now should you?

The key here is communicate with your company. If you are valued they will try to accommodate you or at least give you a good reason, if you are met with resistance or reprecussions then maybe reexamine your relationship with them.


I'm not an Amazonian, but I wanted to chime in here to say I think this thread is a great idea and I would love to see more like it.

I write about salary negotiation and coach people through it, and I think sharing salaries publicly will encourage more people to negotiate and get paid what they're worth.

I recently coached a new Amazon employee, and he got a very good offer, which he increased by about 15% using VERY simple negotiation tactics that we discussed. If he hadn't negotiated, he would've still been paid well, but would have left 15% on the table before he was even in the door.

I submitted this link yesterday—it's a Salary Negotiation workshop I did for developers in Orlando last week. It's definitely relevant to this conversation:

EDIT: Here's a direct link to the Salary Negotiation workshop summary to save you a click: http://bit.ly/21zFG5q

Here's the HN submission for posterity: https://news.ycombinator.com/item?id=11305683

(Not sure why I originally linked to an HN submission linking to the workshop. ¯\_(ツ)_/¯)

Nice job starting this thread!


I'm interested in what your negotiation principles are.

I've always heard that a candidate should never share salary information and require the company to provide the first concrete number in the form of their initial offer.

However, I've repeatedly used all of the "business-professional" and "HR approved" sorts of conversational techniques to enact this advice, and the only result that has ever occurred is either (a) the company literally refuses to even conduct a single interview with me before knowing salary information, or (b) the company finally makes a job offer and it is extremely low, something around 50%, of what I have earned previously in similar roles.

95% of the time I say I am more focused on assessing cultural and technical fit for the position, making sure I would jell with the team, finding out more about the company, learning more about the trade-offs required for the role, etc., as reasons for not providing salary information as literally the first point of communication with HR, it results in an instantaneous rejection.

I still believe candidates should not agree to unfair information asymmetry by revealing their salary or wage preferences first. The problem is it just seems that something like 95% of all hiring managers will outright immediately reject you, on principle, if you don't agree to bear that unfair information asymmetry.

All the great techie blog posts on being a better negotiator, like this:< http://www.kalzumeus.com/2012/01/23/salary-negotiation/ > -- they sound great and give me a pumped up rah rah feeling, but in practice they basically never work.

My interviewing experience with this has covered large multi-national companies, tech firms, small boutique quantitative finance firms, start-ups, consulting companies, and education technology. There certainly are industries I am missing, but it has seemed like a universal phenomenon to me.


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!


I've wanted to share my thoughts and experiences regarding the "never be the first to quote a number" strategy for some time, but I usually see these threads when they're too stale to comment on.

My background: I'm a senior-level engineer in my early 30s, in SF. After a consulting stint, I interviewed heavily in 2013, and again in the second half of 2015, and currently speak with 1-2 recruiter cold calls per week to keep my options open. My sample size is many dozens of intro calls, across startups ranging in maturity from 1st engineer through some of the unicorns everyone knows.

In short, I agree with p4wnc6. A very relevant fraction of recruiters, say a third, will refuse to proceed until you quote a figure. This is true for internal and external recruiters. No amount of push back works with this group, they'll see you as difficult or otherwise not worth pursuing, and would rather end the discussion than proceed number-less.

This leaves the two-thirds of recruiters who are willing to play ball. Now there's another problem - not quoting a number is only a good idea if you want to avoid being low-balled - it's a tremendous waste of time if your desired compensation is above the expected range.

For transparency and knowledge sharing, I'll be specific: my background is in operations and infrastructure ("devops"). 90+% of the roles coming my way pay in the range of $130-180K base. My base is above this, and very few companies will be willing to pay a premium of 50% more than they expected to. No amount of wishful thinking about "your payroll is a drop in the bucket" will bridge the gap if it's too large.

Which brings me to a question I'd love the answer to: other than working for the big ~6 (Google, Facebook, Uber, Apple, etc), how can I push my comp up to $2X0 (or even $3XX!)? I feel like I'm near max, so I'm biding my time until the right VP/Director/etc of Ops role comes along. Is there anything else I can do?


When you make as much as you do, it's a huge waste of everyone's time for you to interview for roles that just can't go there. By stating your compensation up front, you effectively make the recruiter your negotiator before you ever interview. You're getting them to get the company to agree to possibly paying you that much, assuming you meet some bar in their head that's worth it. More specifically to your next move, your base salary just won't have a lot of room to grow. So you have some options. -become a consultant. Many are referencing Patrick's blog (kalzumeus.com), which is a great way to bump up your dollars. -transform a recently funded startup that goes public. They'll throw money at you to build their team, then hopefully the stock makes you rich. -Even outside the big 6 (Uber? Really?), at your level in your job most larger companies should be rewarding heavily in stock and performance bonuses. Take the time with the recruiter to truly understand what the total compensation strategy is. What is the vesting schedule for the initial reward? What about stock given as bonuses or for promotions? What % of possible bonus does the average employee actually receive? -create the next big tech and run with it. AUTOMATE ALL THE THINGS. I hear there's money in that.


> Many are referencing Patrick's blog (kalzumeus.com), which is a great way to bump up your dollars.

Which posts exactly? What is that blog known for? First time I see it referenced.


Probably this post: http://www.kalzumeus.com/2012/01/23/salary-negotiation/

The blog is known for interesting posts on startups and software development from outside the Bay Area filter bubble.


Thanks, I was curious. I'll check it out.


FWIW I am basically in the same situation. My base pay is in the same region you describe for yours, and I rarely see offers that are even 80% of what my salary expectation is, let alone other forms of compensation and other benefits.

I am in scientific computing and machine learning, and I actually love being an implementer and a coder. I don't want to be a people manager (mostly because I think all companies force managers to treat their subordinates in unhealthy ways, and no matter how good your intentions are, being a manager will ruin your humanity).

I worry about finding any job, and then further worry about what growth path there could possibly be.


> I rarely see offers that are even 80% of what my salary expectation is

I'm suspicious that this is a silent-evidence phenomenon. I'd assume that the duration a job listing is up correlates inversely proportional to the compensation. If that's true, all the great paying jobs are optically invisible.


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").


I think this is a major factor, but it has still happened to me even when interviewing for boutique jobs via a friend's reference or happening to know someone who already worked there.

A fair amount of the interviews I accept come from unsolicited head hunters seeking me out, and even then the reveal-your-salary thing is a huge sticking point. And even when it hasn't been, I've still been let down by the ultimate salary offers.

I heard once that you should budget 1 month of job searching for every $10,000 of compensation you seek, and maybe more once you are seeking high-level bonuses. That's easily been true in my case. You also have to put up with horrid HR people who are quite simply just rude to you, and lots of degrading "dance monkey dance" whiteboard and coding puzzles and hazing, and demoralizing cross country interview trips that you have to muster the ability to put your whole self into but which you cynically know in your heart of hearts that it's a waste of time.


A substantial proportion of jobs never even makes it onto job boards. And yes, higher paying jobs are often amongst them. I've been approached for jobs that have never been listed publicly several times. It's one of the reasons why it can pay to be on good terms with (the right type of) recruiters and (more importantly) have a good network of industry contacts.


Sorry this is off topic.

Is there a way into machine learning without doing going and going an Ms or PhD?

Im working my way through a coursera course on it but I'm not sure that is enough. All the positions I see are looking for academic experience or 5+ years doing it. Neither of which are doable for me.


If you know almost nothing about the field, then introduction to statistical learning is a good choice.

http://www-bcf.usc.edu/~gareth/ISL/ISLR%20First%20Printing.p...

It assumes some understanding of calculus, but doesn't require matrix algebra.

The original (and amazing) book that lots of people used is Elements of Statistical Learning.

https://web.stanford.edu/~hastie/local.ftp/Springer/OLD/ESLI...

Chapters 1-7 are worth their weight in gold. This is one of the cases where the physical books are much better, as you'll need to flick back and forth to see the figures (which are one of the best parts).

The forgoing assumes that you already know some statistics/data analysis (the latter probably being more important).

If you haven't done this before, then I suggest that you acquire some data you care about, install R (a good book is the Art of R Programming by Matloff), and start trying to make inferences. And draw graphs. Many, many, many graphs.

If you keep at this, finding papers/books and reading theory, and implementing it in your spare time, then you can probably get a good data science job in 1-2 years. You'll probably need to devote much of your free time to it though.

I'm assuming that you can already code, given the context :)


Thank you for this, i really appreciate you sharing these resources.


I'm on that coursera course too! The course is pretty basic though. It'll help you get the concepts but there's too much spoon feeding in there to make you good enough to compete with people with MS and PhDs. Also that course doesn't cover deep learning and you should definitely study that.


I don't know how reproducible the approach is, but i'm working my way in from being a php developer previously. The company i work for is building a big data / machine learning platform from the ground up, and they bootstrapped the project from existing employees, including myself.


You're in a hard spot. I know, because I'm in basically the same one.

Jobs in the $2X0 range are basically outside the range where a company will trust the normal recruiter/interview process to bring in a good candidate. You must start working your network, and you must either go to one of the big 6 you mention, or you must find a company that desperately needs somebody really senior and where you have an "in" -- somebody who knows the quality of your work and knows you're work $2X0.

It's not that hard to be worth that -- that's about two senior-ish engineers in Silicon Valley. But it's very hard to prove you're worth it. You have to know somebody and they have to know you.

You'll see a lot of advice about becoming a "thought leader" and "noncommodity." And to be fair, that helps -- I give talks, wrote a book, etc. But those things won't usually let you interview cold and get $2X0. At this point, maybe $200, barely? Beyond that, it's networking or seniority.

I can't tell you about $3X0, that's out of my personal experience.

You'll occasionally see massively outliers, up to maybe $6XX (which includes stock, not just base.) But those are almost invariably people who rose in the ranks at very profitable companies -- either big 6 or a small niche company that makes bank. It's very hard to be hired into a role like that unless you're well-known by the company in question.


Most everyone I know who is primarily technical who's total compensation, ah, starts with a two has a base that isn't out of your range and the rest is bonus/stock. So yeah, on a good year? (like last year) a quarter million is completely reasonable, but that's not gonna hold if the company has a bad year.

also, everyone I know in that income tax bracket works for those big companies. Startups just don't pay that kind of money. If you want to get paid (I mean, paid now, not paid if you get lucky and pick the right company and it gets huge) - if you want to get paid, go get a job from a big company.

why don't you want to work at google, facebook, uber, apple, etc...? (amazon, btw, is on that list, too.)

Also, on another note, while I get "what is your salary expectation" a lot, (and I often return with "getting X now, need X+y if you want me to move" because maybe I'm a terrible negotiator?) I've never had any but the lowest of body shop recruiters actually ask me for a previous salary.


> why don't you want to work at google, facebook, uber, apple, etc...? (amazon, btw, is on that list, too.)

I've never come across an ex-Amazon employee with good things to say about the company (though this is admittedly a small sample-size).


>I've never come across an ex-Amazon employee with good things to say about the company (though this is admittedly a small sample-size).

paying better is a good thing. It's certainly not the only good thing, but it's an advantage that amazon often has. Most of the people I know who currently work there[1] are like "The work is only okay, and they kind of treat you badly, but the pay is really nice"

I was out drinking the other weekend with a good friend who works at amazon, and we were comparing notes. As a contractor at google? My perks are way better. The free food at google (which I get to eat as much of as I want, and can even take home, even though I'm just a lowly contractor) is way better than the not-so-free food at amazon. At google, even as a contractor, nobody gives me shit about leaving my car at work while I'm on vacation. The contractor next to me has had his clearly inoperative vehicle parked at google for the last month or two. They asked him to verify it was his car, but didn't tell him he needed to move it. All my interactions with security and google corporate, and, you know, breakfast, lunch and dinner, kind of made me feel how I imagine the coddled children of the super rich feel when they are on the campus of an elite college.

At amazon? even full employees get shit for just leaving the car there over the weekend.

But my buddy, I mean, he is a little better than me, but he's not, you know, amazing, like the guy from apple we were hanging out with at the time, but he's making a lot more money than I am. Really dramatically so.

[1]I'd expect reviews from current employees to be rather better than reviews from ex-employees; the current employees clearly aren't annoyed enough to find another job.


It's possible to work for a startup and have a base salary starting with a two. And even to be hired into the role at that level. I speak from experience. But yeah, that's the very high end.


You only need one job. It doesn't matter if you exclude 1/3rd of all recruiters to get that one job. If you are disclosing your salary requirements first you are restricting yourself on the high side, and each person has to weigh what that is worth to avoid lowball offers.


I don't want to be rude, but at that salary is it easy to survive, or hard? Do you rent, or own a home? That salary can buy you a castle out in Texas, Florida, or anywhere else. Looking for anything beyond that (IT Director in Santa Monica makes $180k, maybe more depending on where it is) -- at that amount of pay, not only are you close to being a dreaded top 1% person, you're getting paid out the butt for what everyone else already does. :|


I know a few directors making $250k base with big bonuses on top. Most of the senior devs I know make around $180k.

$180k a year can not buy you a home in Santa Monica. Mortgage would be > half your take home even in a condo and the alternative is to commute an hour each way.


One technique I've tried that seems to get a particularly stubborn hiring manager or recruiter past the salary question is giving a generic number range. Before talking to anyone I usually do some basic research to get some idea of what a generally reasonable range is for the position, and adjust that based on my situation at the time. If pressed (I still don't give it up right away) I give that range.

Example: today I was talking with a recruiter about an iOS developer position. The salary question came up (in the form of: how much do you make right now?), and I gave the standard deflection about wanting to make sure the position was a right fit, etc... When pressed, I said that based on my research, the base for this position is $75k - $95k, and that a number in that range would be acceptable as a starting point for negotiation, but contingent on the details of the position.

This kind of response seems to give you some wiggle room without giving up all your leverage, while giving everyone a general idea if you're in the ballpark. I only use this as a last resort if I'm getting the feeling that there is little chance I'll be able to proceed with the opportunity if I don't answer. True, by not establishing salary up front you may be wasting each others' time due to different expectations, but that is a very small risk to take compared with the potential upside of a big raise.


You're suggesting less than 100 for iOS Dev, and above you someone is suggesting 150+ for devops/sysadmin. That ratio seems quite skewed compared to other sources of data on the web. Are you very junior, or talking about a non-prime job market/locality?


Senior DevOps roles pay bank. Easily on a par with the same seniority of software engineer.

This makes sense. You have to be as good as the same quality of software engineer, do work that is less glamorous, and carry a pager.


A little bit of both (I've been doing iOS for less than a year), but mostly the latter. I don't live near a tech hub or major city, and the cost of living is pretty low. So good data was hard to come by. I essentially just found the range for the closest major city and went from there, taking into account what I wanted with how the current market was going (salaries here are generally 20-30% lower than the major city, while the cost of living is much less).


Based on the assumption that the least you would accept is your current salary, it is safe to assume that the lower range is same as your current salary i.e. using your example, a recruiter can deduce your salary is $75k.


> Based on the assumption that the least you would accept is your current salary, it is safe to assume that the lower range is same as your current salary

"Lower bound you'd accept" != "Lower bound you SAY"


Exactly. The lower bound I'm prepared to give is always a raise from my current salary. I may be prepared to accept less if the opportunity is right, but my only purpose in offering this information in the first place is to get to the next stage of the process. It is a tricky thing to keep as much negotiating leverage as possible while still signaling that you can come to an agreement, which is why I only offer the number if I feel like I won't progress to the next stage without it.


In the handful of cases where the company was OK with my non-answer about salary, and I went on to get all the way to a job offer, the salary ended up being entirely miscalibrated to a candidate of my skill and experience, and the overall interview process (which usually included some technical screens, programming tests, take-home tests, and long on-site technical interviews) was a massive waste of my time, not to mention extremely stressful.

Places where I experienced this gross miscalibration: a large U.S. food retailer's digital analytics team; a small pharmaceutical research software company; a 25-year-old multinational scientific computing and supercomputing consulting firm; and an FFRDC research lab attached to a university.

In one of these places they even went on at length about how much the hiring manager liked me, how I fit all the skills they were seeking, and many team members remarked that I would "mesh instantly" with the team, and so forth. I had walked away from those interviews knowing that I had done a good job and feeling very confident.

Then they made a job offer than was around 75% of what I had been making before in a similar job in a similar cost of living area, and the new job's other benefits were far worse.

When I told them what I was making before, they just said, "it just looks like there's a bit of a gap here that we are unable to make up, but we think you'll be very happy on this team so we hope you'll consider our offer despite that." The people interviewing me in that company had even gone on at length about how successful their business unit had been recently, signing a new important contract, and how their biggest challenge was recruiting good people and staffing up to support some projects that had important deadlines looming towards the end of 2016.

I still continue to avoid sharing salary info, because I'm not convinced that sharing it would be better.

But I think what you might not be accounting for is that almost every single candidate in the tech world does share salary, freely and openly, from the very first minute they are asked, without even realizing it might have any side effects.

A lot of corporate recruiters are conditioned to expect this, and the minute someone fails to share salary, they flag them as "not a dope, can't hire them cheaply" and they just move on. Constraint number one, above any and all talent requirements, is that they must be cheap to hire ... for a lot of firms.


My reply to the 'our company is doing so well, you will ALSO do very well once you bed in' is to remind them that most notable pay rises you ever get during your career is when you switch job. So negotiate your pay NOW because for all you know, you'll be stuck to that sort of level for X years to come if you are unlucky.

As for 'shares' I flatly refuse to even consider that as part of a package. if they want to /add/ them it's wonderful, but I've been so many time multi-millionaire in 'options' that it's not even funny.

As for 'yes but the work/team is so rewarding' point I counter that it's a lot better if there isn't a sour note about being underpaid mixed in. Pay me well, and I'll be the one pulling the team to be all shinny and dynamic.

However, ultimately, you STILL get underpaid unless you go to the usual suspects like GG and such. That's why I gave up 'career' and went off contracting. Turns out being a mercenary is rewarding in many ways, including monetary !


How do you get business. Im thinking of consulting but I don't know where to start in selling myself.


Well, it's a matter of knowing a few people most of the time; a few agents you can 'trust', and then a small pool of returning clients who'll ask you to do stuff once a year or so...

The networking is always important, even as an employee -- always brush up your network, it might save your ass next time there is a shakeup at the company you work for, and might also give you the occasion to slam the door and move on if necessary.

I think there is nothing worse in life than waking up realizing you have to go to work to a job you hate, with people who are beepheads for a product that is a failure and going to the wall.... while knowing you don't have the freedom to just go.


It would be interesting to find out this, because I think contracting is better too!


Perhaps one strategy would be to give them a baseline salary (higher than your current salary, of course). You could tell them that in general based on the kind of work you are doing, responsibilities, etc. you would expect more, but under no circumstances would you consider any offer less than that.


Whatever you do, do not say a low number expecting to increase it later.

If you want to give a number, give a high one that you are ok with the company negotiating down, because that is what will happen.


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.


This is actually an excellent point, and I can't believe I didn't think of this.

If I am the first one to bring up salary, and I request a range because I want to make sure that nobody is wasting their time, then they clearly get the message that I am expensive to hire, and they can efficiently reject me if needed. If they give a number and it's too low, then I can politely tell them it's best for everyone to discontinue the interviews.

But, if they don't want to give a range, presumably because they might be willing to pay a high wage if they liked me, then it puts me in a much better position to avoid stating what I am seeking.

Then I could say, "OK, it's alright with me if you don't want to explicitly tell me the range ... I just want to be sure that the position is offering compensation in the range that I am seeking. If you prefer to leave the salary discussions for later, that is perfectly understandable."

Now, if they press me for salary info, I can say the same thing they said and refuse to answer.


That all sounds very good to me :)


A, but there's a catch! I've asked for a company's range many times, and they have yet another non-answer answer: "we don't have a firm range in mind, we're confident compensation won't be an issue for a top candidate".

It's a game of chicken. The best counter I have is "what is the top of your range if we have a perfect fit?", but even that doesn't always work.

At this point, I'm sick of games. If a company refuses to disclose a salary range and/or insists on getting me to quote a number, I lead with $2X0 and see what happens. 80+% of companies aren't willing to hit that high, and the other 20% have been more interesting roles at higher quality companies.


Honestly, I still don't see a problem with stating a high number.

In my experience, refusing to agree on a range will inevitably lead to some lowball offers.

The strategy I've been using is to give out a range that is 1.5-2x what I'd be happy with. This anchors the conversation and quickly sifts out the employers who are not serious about attracting top talent.

Realistically, I never expect to get that 2x number and am certainly not leaving money on the table.


There are a couple of us here in the weird position of being senior enough that companies don't recruit for us through normal recruiters.

On the one hand, that screws up the usual "don't give a number" advice, including this advice -- there's usually not a defined salary range for a startup's catchall "we want somebody who does backend" poorly-defined job req.

On the other hand, I suspect "don't give a number" isn't the biggest mismatch happening there.


In past I have asked "What's your budget for the position?". In companies usually everything is budgeted during planning phase from new hires to promotions, bonuses etc.


So lets say you've asked them what is the normal range for the job and they've replied. What if their "normal range" is below the amount you desire? What then?


I know it's anecdata, but to confirm your experience I have had recruiters and hr reps tell me explicitly that either they will not continue without salary information or that the software their company mandated that they use would not allow them to continue with no salary or a $0 salary


"Strange, that kind of restriction must make it very difficult for you to find good talent. OK, how about you enter $999,999. It's an such an obvious placeholder that it won't fall through the cracks and it'll be easy to fix it later."

"Too open-ended? Then how about you just put in the lowest/highest amount YOU'D be willing to accept and we move from there."


lol, that software answer is great. I would offer to write some software for them that treats salary info as optional.


And now you know everything you'll ever need to about the "shortage" of tech talent.


Your experience with small to mid-sized firms does sound depressingly typical and I've experienced it too, but I think it's worth mentioning that Amazon specifically won't reject you for not saying a number.


How do you respond when they ask you for your salary information? Would it be perceuved as rude to say "I decline to state"?


State the one you want, not the one you're currently making. They won't (and legally should't be able to) check.

And if they do and somehow, your previous employer disclosed this to them (a big no no), you can always say "I was underpaid then and what I was making there is not relevant to the position I'm applying to with your right now. I also think I've learned a lot in my past position, which justifies this jump in compensation".


I've only ever done this (caveat: in the US, where they can't legally check by calling the company directly). Increase your previous salary by 20-30%, even more if it's the norm. I've even countered with "my current co just countered to keep me..." Gotta have some chutzpah.


Shoot thats a good one I need to add to my list! Fake counteroffer from own employer. (Fake competing offer from a different company probably wouldn't work, because they would ask for an "offer letter". A counteroffer from current company isn't going to require proof)


I'm all for solid negotiating tactics, but if you consider telling an untruth, you are not welcome on my team.

You may still find other teams in the world that you can dupe, but in the end, I expect lies to hurt your overall prospects (in life as well as work.)


Really? Because people are so honest? Everyone on your team tells lies every single day, I guarantee it.

What you're saying contradicts the common advice to oversell yourself (AKA "fake it til you make it").


I always find it amusing when people refuse to lie on certain things based on some sort of moral-code or principle and then spew out lies for tons of others.


> I'm all for solid negotiating tactics, but if you consider telling an untruth, you are not welcome on my team.

Do you seriously think your team is made of 100% people who only ever tell the truth?

Let's get realistic, we all tell lies here and there. What matters is what you lie about and why you do it.

I couldn't care less if a developer joins my team and lied to get a higher compensation. All I care about is whether they are a good hire and if they'll do good work.


The whole point is that its impossible to verify....


Unverifiable makes it hard to believe as well (unless the numbers were reasonable to start with).

But there's an easy check, should they care to do it: call their current manager.


If I'm doing the hiring, I wouldn't expect a candidate to let me talk to their current manager--that's just insane.

If I thought the employee was worth the extra money they were asking for, I'd give it to them. If not, I'd let them walk. Whether their current job is considering matching their offer doesn't really matter to me.

If a candidate asks for a specific salary, I don't care why they want it. I only care whether I think they are worth it, and whether I can afford it.


Are you certain everybody on your side of the negotiation is fully truthful? Do you include management, HR and recruiters in "everybody"?

If so, you're not talking to your recruiters. You should find out more about what your side of this negotiation looks like to a candidate.


That's an awesome retort, never thought of that!


I have had a company request a previous paystub. I guess you could Photoshop that.


It's absolutely not at all illegal to check and is a very standard part of background checks.


Not sure why this was downvoted, it's not illegal and companies do it via background checks.

Quick searches reveal this is a popular question, spot checks of the answers agree that it's not illegal and quite common.


I think the OP means they can't legally access this information other than by getting you or your previous employer to disclose it.

Most large companies won't give out your past salary information, so if they don't force you to provide proof, it's not very likely they will be able to verify it.

>via background checks

Background checks are normally done via a 3rd party background check company, and they don't have access to this kind of data.


When I was hired by Merrill Lynch, in Dublin, they asked for my bank statements for the last ten years in order to verify that I was indeed making what I said. (The only annoying thing was that I had to scan 75 pages... boooring.)


If they don't trust the number you were quoting, I wonder why they would trust you to scan.


Wow, seriously? Full rectal as well?


It was the first time I worked for a bank; I just assumed it's "how things are done" :)

I'm going to be more careful next time. :D


Exactly, thanks for clarifying this for me.

In the US, this is a legal minefield and when a potential employer calls a past employer for references, that past employer will very often not reveal anything more than "We can confirm that this person was employed by us from date1 to date2" and that's it.

They will not disclose your salary, what you did, your organization, who you reported to and who reported to you, your performance reviews and anything else of that nature because all of this extra information is grounds for you to sue them later if you don't get the job you're currently applying to.


>Background checks are normally done via a 3rd party background check company, and they don't have access to this kind of data.

Yes they do. There's a company owned by Equifax called The Work Number that collects such information.

https://en.wikipedia.org/wiki/The_Work_Number


The only way The Work Number has access to your salary information is if your employer has given it to them. If your employer is willing to give that out then yes a hiring company can verify your salary.

We are back to my original point that the only way a hiring company can verify salary data is by asking your employer (or having 3rd party ask for them) or forcing you to verify it.


Why is it that "What are you making are your current job, we will verify it." is acceptable but "What was this companies net revenue last quarter" is not. The game is so clearly rigged.


The company bears far less risk than the employee. The company can easily fire you if it doesn't work out, whereas most employees can't suddenly leave a job that treats them badly.

So employees can ask lots of questions about company financial health, as part of trying to reduce the far larger risk they are taking.

Meanwhile, a company doesn't need to know your salary history to make an informed opinion of whether they want to hire you and for what amount of pay.


Public companies publish quarter results..


According to Forbes: "less than 1 percent of the 27 million businesses in the U.S. are publicly traded on the major exchanges." [1]

[1] http://www.forbes.com/sites/sageworks/2013/05/26/4-things-yo...


That's true but far more than 1% of employees are employed by publicly traded companies. Most of the 27 million businesses have no employees at all--there are only around 5 million businesses with employees.


What do you mean that this is a big no-no? Can you provide a source for that? I was under the opposite impression and I'd be interested to learn more.

The reason I ask is I've certainly worked at companies that shared salary info if asked about your tenure there. In fact, it was one of the very few things they would share (in addition to start date and end date). Maybe it varies by state?


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


I have practiced that part and read just about everything I can find about it.

Generally I say something like, "I appreciate the need to consider salary as an important part of the process, but since we have only just started talking about the position I feel it would be best to make sure that I really am the sort of technical and cultural fit you are looking for. If we can determine that I am the right fit for the role, then the salary information will fall into place at the appropriate time. But if it seems that I am not the right fit for your team, then no amount of salary discussions will be able to help us."

I have a few variations on that kind of description that I use. It's entirely possible that the way I say it can come off as rude, and I think that did happen to me especially a few times when I first started doing this.

But I have practiced it, asked friends for advice about how to say it better, how it sounds, etc., and researched a lot about this online. So I have some confidence that it is coming off as strong and assertive, but not rude, and it is communicated clearly in good-faith because I truly am primarily interested in whether the cultural fit is a good one.

Even so, these kinds of HR-approved ways of talking only ever result in about a 95% chance of immediate rejection.

Whenever I have made it past the initial question about salary, and eventually salary comes up again towards the stage when an offer is made, I have a different way of talking about it.

At that stage, if they ask me again, I will usually say something like, "I have spoken with the team and had a great chance to learn about your company and how I could fit in with this role. If you have a particular salary range that you'd like to share with me, I can definitely let you know how it will match up with my expectations."

Again, I have some slight variations on that, but it's more or less the same idea of changing their question asked of me into my question asked of them. They can't keep coming back and specifically asking me for a number without seeming very awkward, and if they do that it's sometimes a red flag and I would usually be happy walking away if they were to heavily press me at that point.

Unfortunately, as I mentioned above, when people have been OK with all of this and they have actually come back with their offer, it has been not just a tiny bit below my ideal, but way, way off base from what I was previously earning, let alone what I was actually seeking to earn in the new role.


Never "decline". I say I consider the entire compensation package because I realize they are a startup and need to sweeten their offer with stock because they don't have the revenue to pay a market rate.

It's important to neg them a little when you guess what they will offer. Male them self consious about lowballing you without insulting them.

I actually am beginning to think that its weak to ask them to throw out a number. Why not state a deal that's 10% better than what you want? Are you really going to be heartbroken if you get more than you want?


> Why not state a deal that's 10% better than what you want? Are you really going to be heartbroken if you get more than you want?

Because you might be leaving money on the table. What if the company was prepared to offer you 20% above your desired rate? Once you tell them +10% is your floor, they have no reason to offer above that.


That's why I think its weak. It's driven by fomo rather than going for what you want. Throwing out the first number let's you anchor the negotiation. It puts you in control.


Tell them your salary is 'confidential information', your current employer often likes to suggest it is...


Actually, contrary to popular belief the party that makes the first offer could have the upper hand. This advantage is due to what psychologists call "the anchoring principle" [1], which is one of many cognitive biases.

[1] Thinking, Fast and Slow - by Daniel Kahneman

[2] http://www.businessinsider.com/how-to-negotiate-make-first-o...


I really agree with this. As a business owner, I definitely find if I'm talking to someone good and they confidently state a number that's above my intended range (but not completely nuts) I'll start thinking along the lines of how I could make that work, or at least make an offer that wouldn't be completely out of their expected range. It only works if you're someone they really want to hire though, and if you know what's a good amount to ask for. If I'm at all on the fence about someone and they quote a crazy high number, there isn't much point in continuing. (Whereas if they'd held off, perhaps they could have convinced me they were worth hiring, and then negotiate a bit.) But if you're a great candidate, anchoring high can definitely be a good move.


Yes, "don't say a number" is more applicable to those who are under-compensated. Since this is the case with most people, it is generally good advice. I'm not the best negotiator, but I have put myself into a position of making a pretty good salary and this is what I would suggest for someone that is trying to get a big bump higher: give them a range where the bottom number is the minimum you will accept. For example, say you're 2 years out of school, making 80k and you hear on hn and elsewhere that you should have a 100k base. When numbers come up, don't be afraid to say one first, but say "I'm looking for a base in the range of 100 - 120k.". Say that even if they just asked "what is your current comp?". If they press forward with needing to know you're current comp, eventually you will have to say it, but reiterate your required range immediately after telling then your current/history.

The most important part here is that this will end the conversion with many recruiters. This helps you to know that those recruiters were not trying to help you. Just repeat with more recruiters.


I take the opposite approach. The last time I moved, I made a secure web page that had my current comp package, in detail, and the minimums on my required comp package, in detail. This I sent to every recruiter that had contacted me in the previous 18 months. Scores of them.

Before I would speak to any of them on the phone, I'd get a soft confirmation via e-mail that they had a position that could meet my requirements.

The web page also had information about what areas I was willing to commute to.

I've used variants of this approach for more than 20 years, and it's working exceedingly well.


I've done things like this before with recruiters I've worked with in the past.

They have only ever said that every position they are working on would offer a salary too low to compete even with what I currently made, let alone the larger amount I was seeking.

Yet at the same time, I have friends and colleagues who already are earning the higher level I am seeking, and who say it is a common amount to be earning in certain places.

My opinion is that recruiters focus a lot on whether it would be easy to get you hired. If your salary is high, few recruiters will bother because it means you are picky and you're looking to work at companies that are picky and so lots of times it doesn't work out.

Recruiters are a lot like crappy stock analysts. They are always looking for a story about something being undervalued, to hook someone on how they can get something great for an amazingly cheap price.

If you are justifiably expensive, most recruiters scatter like roaches. They can't sell things at their true value, and view it as wasting time even to try.


Is it necessary to state your current info?


Personally, I think it's worthwhile to include, as social proof. If another company was paying $X and was perfectly happy with the employee, $X plus a modest / reasonable $Y doesn't seem so crazy. It shows that you're not just pulling an unrealistic salary out of thin air.


Right, though I would put "scare quotes" around "proof", since from their perspective I could be making it up. (:

When things get more serious, I sometimes go over my history of compensation with them.

To me, it comes down to the question: does company X need me more than I need company X? For the right people with the right skills and the right experience, the "power" is with the potential employee.


Interesting, I've never ever shared my salary with another company, and been working two decades.


Yup, there's a hell of a lot of different ways to 'do it' I think.

The feedback I get from HR/recruiters is that my approach is rather unusual, but that they generally appreciate it since it is rather efficient.


> 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.

Honestly, discussing desired salary is a good screening tool and when following advice like this I find ~50% of job applications are a waste of my time.

So desired salary is an important filter if a job doesn't state the salary range.


I just tell them "I need to be making at least X". It's a good screen for me. Most of them aren't anywhere near my number.


At least two of my past jobs were jobs where the employers stated range was substantially below what I was finally offered, so this can backfire. In one case I negotiated my way up 50% over the initial offer, and the initial offer was already at the top of the advertised range. In the other I got 30% above the top of the range + about twice the options. Both cases it was the situation where they realised I was overqualified for what they'd spec'ed, but they decided they wanted me anyway and upped their budget.

I know it can often mean wasting time, but focus on whether it's a company you want to work at. If it is, see it as a way of getting on their radar, and if you can't agree for that position, ask them to keep you in mind if they get something more suitable.


Here's my only question with the negotiation technique of not disclosing a desired salary. So is it expected that the other side should state the salary offer? That was my only problem with all these negotiation techniques saying "never mention your salary." Eventually, one side or the other needs to mention and at the end of it all, most articles online never closed it off with saying either side would state the expected salary.


The candidate could put their minimum acceptable salary in an envelope. The employer could put their maximum acceptable salary in an envelope. The two parties could agree with a third party arbiter that if the maximum from the employer is larger than the minimum from the candidate, the salary will be set to the midpoint between the two numbers, and otherwise, no deal can be reached so both walk away.

That's one way, at least, where neither party has to concede the information advantage.

In fact, I'm surprised there aren't already 37 start-ups that offer this as a service. You could have a cute little envelope logo like the MS Outlook logo and give a TED talk about how you're totally disrupting information asymmetry in recruiting, and eventually be pressured by techtopus to provide data about what candidates are asking for to perpetuate information asymmetry.


You don't need the trusted third party. You could share the hash of the numbers so they couldn't be changed during the process, then do the millionaires problem [1] to find out which number was bigger, and finally and only if the right one is bigger, share the figures (setting the salary at the midpoint is the same as sharing the figures in terms of information transfer) and calculate it that way. The only way to not reveal the offers after a successful round would be to introduce some randomness, maybe choose a number at random from some agreed portion of the range between the numbers. I don't know if there is a zero knowledge protocol for selecting a number at random from a range where the extremes are set by two different people.

[1] https://en.wikipedia.org/wiki/Yao%27s_Millionaires%27_Proble...


That sounds an awful lot like a cryptographic protocol to me. And CNN told me that cryptography helps terrorists. ... You're a witch!


Very small rocks


TInder for salaries.


Most companies want to ask the candidate, as most will give a number, and give the company the advantage.

Why pay for a service when you can just ask? Basically they do it on purpose because they have the upper hand.


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.


I interview techies, and I always make a point to ask them to give me their expected salary range. The purpose behind this isn't to one-up them and pay them as little as possible. It's just in both parties' best interest to avoid wasting time if the expected pay is too high. Neither we nor the candidate want to go through several rounds of interviews for something that ultimately won't work out.

And at the opposite end of the spectrum, if a candidate gives a number that's too low, we ignore that and offer them what we think they are worth (which is a higher number). Our reasoning is simple: if we treat people fairly, they will be more loyal and less likely to jump ship at the earliest opportunity that pays more.


A lot of recruiters say that it's not about ensuring the candidate gets the lower end of their expected range, but that's just what they say.

I actually have a friend who worked at one of the aggressive boutique recruiting firms who mostly focus on the New York investment banking jobs.

He told me that almost always, their client companies would tell them that if they were able to get a candidate to come in with a salary below X, the recruiting firm would get an extra bonus on top of their commission, and the bonus was priced to make sure it was more lucrative to try to suppress candidate wages than to adequately represent the candidate's higher-end expectation.

Whenever I hear a recruiter say anything like, "Look, I don't get paid unless you do so clearly I'm trying to get you the most that I can..." it's an immediate dealbreaker. They are probably being paid a bonus precisely to ensure I come in at a lower salary than what I could otherwise command.


Agreed. I had two different recruiters offer to increase my contract rate when I told them I had accepted another offer. That suggests to me that they're paid amount $X and were offering me $Y < $X, with their commission being the difference.


I hired developers into investment banking for 18 years. If we gave somebody a low number, the next bank would poach them in 1-2 years, wasting all the time we spent training them. After I learned this the hard way, I always went as high as I felt able to on the initial salary, because raises were much harder later on.


That was my experience as well. If you want to pay your team well, the best option is to bring people in at the highest number you can justify.

Raises were always harder to arrange, but it was a lot easier when we had evidence that new hires were costing us 20% more than our existing high performers were paid


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?


We do that too. We don't have a preference either way, because for us it only serves one purpose, which is to determine if we should continue the interview process.

Surprisingly, very few candidates ask us upfront what the position pays. In fact, we've only had one candidate who tried to play the "salary game" (if you will) and turned the question back on us when we asked what their salary range was. Like I said though, we just reveal it. To us, it's not a game, but rather two parties exchanging information in a fair and transparent manner.


You may think it is not a game, and I don't doubt your intentions, but it still is a game.

At the beginning you are not invested in the candidate. A candidate that wants to work for you, but wants to maximize salary would be foolish not to try to get you to invest more before starting to talk salary, as it's far harder for you to walk away over 5% or 10% or even 20% once you've decided you have a candidate you like and face the prospect of spending time on another candidate instead.

You have the power advantage that passing the candidate over has less impact for you than it has for many/most candidates, so to a candidate it is far more important to spend the effort of selling you on just them first before talking price.


The reason is because the first person to say a number is at a slight disadvantage, and recruiters and managers don't want it to be them.

It is true that making sure you are on the same page salary-wise is a good idea, but it doesn't always have to be the interviewee to establish that.


See my response... this isn't the reason we do it. In fact we try to put the position's salary range on the job posting if we can come up with an agreement internally (our hiring is very informal). Or we put "market rate; negotiable" or something along those lines, and put the onus on the applicant to research what their market rate is.

Basically, I have a checklist for the first phone interview, and the relevant item on that checklist is "make sure pay range is agreeable". It doesn't say "get desired pay range from candidate" or "let the candidate know what the pay range is". We have no preference.


This, to me, indicates that if I was interviewing with you my priority would be to not give a salary range, nor to agree that your salary range is acceptable.

Because when you say "if we can come up with an agreement internally (our hiring is very informal)", that to me means that if I get through interviews and you like what you see, I'll be able to work with you to get you to fight for a bigger budget if I expect more than what you had in mind.

It's easy to get people to push their numbers up once they know you and like you and believe they need just your skills, and it's easier to do that if you've not revealed that you'd be willing to settle on their range earlier in the conversation.

My best results in getting good offers have been when I've deferred all exchange of salary information until the very end: Get them to agree that they want me to join, and it's "just" the formality of getting me to agree to a salary. At that point the interview process has gone from me courting them, through a "it looks like we both like each other", to them courting me, and the power balance has shifted substantially because the hiring manager is invested, and everyone has spent lots of time getting to that point.

This doesn't necessarily work as well at low end position where you're just one of many cogs, but it makes a big difference when people are looking to slot in just that one important (to the hiring manager, you might still be inconsequential to the overall business, depending on size) position.


So in talking in generalizations, it might not apply to you specifically. But broadly, over the industry, I think its slanted this way for the reason I described.

Even here, you ask the candidate for their salary range, instead of just stating what yours is.

If the salary isn't posted, it's a negotiation. There isn't a hiring manager alive that will blow off a potential hire because they ask for 5-10% more than the initial offer. They might not give it to them, but they won't walk away because of the question. Naturally, as a hiring manager, you might very well offer 5-10% less than your maximum in order to either give you bargaining room, or come in under budget for the position.

It's lightly adversarial, sometimes unpleasant, often annoying, but a part of life unfortunately. Some places more than others for sure, but I think it'd be hard to escape it fully.


Personally I have never taken only 10% more than the initial offer. I've also as a hiring manager never offered so much that I didn't have much more than 10% to give up in negotiations... Usually I'd have at least 20% wiggle room, and if I really like a candidate I'd fight to be able to offer more if necessary.

For my own part, usually I end up negotiating up at least 25%-30%. My "record" is 50% over the initial offer. Usually I also end up asking for more options etc.

The most unpleasant and adversarial negotiations have been ones where I had to give up salary information at the beginning or have the conversations cut short. They're the only negotiations I've entered into where I've sometimes ended up being lowballed, and the only ones that have failed over salary, and in one case led to me telling a recruiter to fuck off and never me call me again over it. As a result, these days I will tell them flat out that if they need my salary details up front, that indicates to me they are unlikely to be able to afford me, and to call back when they have more budget flexibility.


Candidates don't know this about you and have no a priori reason to trust you or believe it. Since most other corporate negotiators are far more predatory than you, it means candidates are better off adopting a unilateral strategy in which they just believe all negotiators are behaving badly.


Why don't you just tell the candidate your offer range and let them decide if they are interested?

Because you aren't honest at all, to system is trying to get rmpoyees for less.


On my phone interview with an US company in 1999, they asked me what salary I wanted. I told them "in my previous remote job, I was making $3.25 an hour; I would like $4". They replied "we'll give you $6". (Romania, Eastern Europe - this was about 8 times the average salary.)

This was the only time someone offered me more than I was asking :)


I've been on the hiring end of similar conversations. Often the thought process is that you're dealing with salaries so small compared to what they're used to that it's worth quite a bit extra to get someone who is so happy with what they're paid that you increase retention and don't have to spend time hiring replacements as often.

It can be one of the great parts of negotiating with someone located in a much higher paid location.


With startups, I disclose a target comp that's in the mid $200k range (I truly believe that's market rate at BigCo). They then make their best salary offer and try to convince me that the equity makes up for the difference. Since equity is funny money, they tend to overvalue it and it's really easy to discount its value and say the offer isn't high enough. I get a serious offer plus lots of negotiating wiggle room.


There IS another solution to this. When someone asks how much you are currently making, you should flat out lie. They won't check.

I've job hopped a bunch, and usually I just take whatever I was currently making, and add 15%, and say that that was my base.

If employers are going to play negotiation games, you shouldn't feel bad about playing them too.


I've always asked for what I want to make and only once have I had a company ask for paystubs to back it up.

That one case was Google (about 8 years ago) and like an idiot I gave them the paystubs (which matched what I asked for). Their offer was 25% less.


I have been asked for proof of current salary (paycheck stubs, etc.) to be included with all my onboarding and HR forms when the current salary formed a basis for my new salary, FYI.


That is none of their business and you should not feel bad about saying no.


I agree in theory. In practice it came after I had an offer, an impending start date, and had put in notice to my current job. It was an onboarding day where I was filling out tax and HR forms. Hard to suddenly say no out of principle knowing it might make them revoke the offer. I was truthful about current salary so there wasn't anything to hide.


Nonsense like that is why you should never let your current salary form a basis for negotiating your new salary.


You do this and they catch you, you will be fired. I am a manager who believes in pay people more. Pay them what they want, not what they were making. That said, if you lie to me, I don't take it well.


Boo hoo. You try to manipulate someone and invade their privacy and then act offended when they lie. Pseufo-moral behavior like that earns zero respect.


HR and management have the upper hand in the hiring process. If you play these kinds of games when negotiating salary, you deserve to be lied to - whether or not you take it well doesn't matter.


Lol. You have no right to that information. I'd counter with something like "How much does your wife make?"


Just because you say that you believe in paying people more, the person on the other side of the transaction has no way of knowing this. Unless you want to believe that all hiring managers are completely moral and ethical, and would never attempt to underpay someone, then you have to accept that the transaction is adversarial despite you not wanting it to be so.


It's a fair point. Never lie. Say I need $x to move.


There is literally no way for the employer to find out... What are they going to do? Call up my old workplace and ask exactly how much I am making? It is against the law for employers to reveal salary numbers. I could sue them, lol.

Employers play games way worse than this.


It is not against the law for employers to reveal salary information. Some people's salaries (government employees for example) are public information by definition. Non profits have to file paperwork which discloses salaries. We talk about actors and athletes salaries all the time. There is also third party employment verification services that salary information is disclosed to by employers. Your employer can use such third party verification services to see if you are lying about your salary or not.


No, I swear, your baby is adorable!


> I've always heard that a candidate should never share salary information and require the company to provide the first concrete number in the form of their initial offer

Its true that it is irrelevant what you made at your last job, but its kind of silly to play coy when they want you to give a number. When you're trying to get hired you are selling yourself... and the first step in selling is to qualify the customer. Just tell them a number that you would actually be acceptable to you, and if they balk then you don't have to waste your time. If you find out more about the job or company and decide you actually want more money, once you get an offer you can try renegotiating that number and give them your rationale.


I have had many jobs. Here is how I start a salary negotiation: I name the package that will get me to drop everything and start tomorrow. Salary, bonus, benefits, options. Anything less and we can talk, but I will still be negotiating with other companies, and one of those may snap me up, or I will continue doing what I am doing today. That puts them in the position of convincing me that the intangibles (career growth, challenge, great team, mission) justify taking less. At the end of the day, you are happy with what you get, regardless of what someone else gets.


This is really interesting and I'm glad that you shared.

I don't know if you'll like what I'm about to say, but you sound like a pragmatist so I figure that you will appreciate a no-BS answer.

It's likely that there's something about your manner, presentation, personality - which I can't and won't fathom to guess because I don't know you - that is tipping your hand and sending the message that you're bluffing or easily manipulated. Obviously nothing is going to work every time but the stuff Patrick and others relate is solid advice so it is of concern that you're repeatedly getting iced out.

The other possibility is that you're interviewing with terrible people; however, the common aspect is still you and the only way to grow is to analyze whether there's a problem.

Could you just not be very convincing? Do you have an irritating voice? Do people generally snicker when you make confident assertions? I don't know why it happens in any case, just that in some unlucky cases it does happen.

My advice is that you have to be thoroughly believable in your disappointment in their offer. You have to look unfazed when you refuse to tell them what you made in your last job.

Finally, if none of these things is true and you're basically George Clooney, then I urge you to interview at different companies.


I refuse to move forward even with a phone interview if I don't have a salary range from a recruiter. It's just not worth my time.


How do you know? They might be paying more than the jobs you go for.


Because I've found that the companies that are offering the type of compensation I'm looking for are willing to discuss it. They know what the type of talent they're looking to attract makes, and that they aren't going to be interested in wasting their time.

Might there be some out there that would be willing to pay me what I'm looking for, but unwilling to discuss it up front? Possibly. But after wasting several dozen hours of my life with offers that weren't even in the same ballpark of what I was making or what I was after, I made the decision to not bother if the recruiter wouldn't be candid up front.


You have to play the game a little. Add up your salary, other compensation (options), a markup for how big a pita changing jobs is, cost of living in the new area of applicable. Then throw that away and mark up to the number that you actually want. Pick something that you think is silly high. Don't say "my current salary is 90,000" say "I would like to make 170,000". You didn't tell them your salary/total comp, but you answered the question and you anchored to a higher value.


It's odd, I have no doubt that you have had these issues, I was talking to a guy who worked for the same company as me, with the same client, just the other day. His entire team where just told they were being made redundant and the company who would be doing the work would be interviewing them all. The new company told everyone to send them either their current pay slip (with all benefits etc) OR their current pay rate (its just a different document with less detail) + the salary they would accept in the new company. So I know that this sort of thing happens and no one was that shocked.

But I've never encountered the issue, I would be interested to see an analysis of what sort of jobs people who deal with dodgy HR reps are applying for (or what route to entry they are taken) vs the jobs people with positive experiences of the hiring process are going for.

I feel like it can't only be luck, presumably there would be some trends (ie. people who respond to advertisements are offered X% against people who are recommended through word of mouth for the same job)


I've heard the same advice, and frankly I think it depends on how strong you feel your position is as well, and so I think it's really important to have a realistic model of your prospects.

If you feel your job prospects are generally weak, you might not be comfortable standing firm on things like keeping salary history hidden. That seems reasonable to me, as long as you're not selling yourself short. "Impostor syndrome" is a thing.

I would actually reveal salary history if it's a "favorable" history -- if I would be happy taking a similar amount, because I value something about this new job more than my previous employment.


I think you should share your salary with as many people as possible. This "don't share" policy is just a trick used by companies to keep labor costs down.

If employees know each other's pay, they will start demanding raises - Then you get in a situation like in the finance sector where companies will be forced to pay big bonuses to hold on to important employees. Companies don't want that - They want their engineers to stay cheap, dependent and foolishly loyal.

It's how the system works; nice people get screwed. In your career, you will only receive the minimum amount that you're willing to accept - It's HR people's job to make sure that you don't get anything more than that.


I think that a quarterly "Ask HN: How much do you make?" Would be a great addition to the "Who's Hiring?" threads.

I posted one for Google here: https://news.ycombinator.com/item?id=11314449

This Amazon thread has been very enlightening.


The problem is that when you share your salary people who make less than you start despising you and people who make more than you start looking down on you.

It's less of a corporate conspiracy but more "this is why you can't have nice things". People just can not handle it in a mature and responsible way, which is why the 'don't talk about money' "common sense" developed.


My experience is that people tend to hate the employer, not the employee.

Less, "You make more than me? You earn too much!" and more "You make more than me? I should be paid more!"


Yes, I think engineers tend to undervalue themselves when compared to many other professionals such as lawyers, traders and financiers.

Perhaps it is because our work puts us is a position where we aren't able to practice our people skills (and negotiation skills) and we don't have good instincts when it comes to how the free market works (we get boxed in and caught up in our work and forget about the financial realities of life).

When you think about the enormous value which engineers have created over the past 50 years and you compare that to who actually benefited the most from that value (in terms of wealth accumulation) - The people who benefited the most are business people, lawyers and financiers.

Every field of industry has been significantly enhanced by engineers... Heck, even medicine would still be voodoo pseudo-science if it wasn't for all the awesome tools created by engineers... Yet in spite of talent shortages, the education/intelligence barrier, the extreme amount of after-work hours required; we barely get paid more than an Australian construction worker.

It comes down to the fact that we don't stand up for ourselves - And we should.


Not saying you're wrong, but I think it probably also has a lot to do with the fact that engineers, by training and often by personality, tend toward being "rational" in their worldview, which basically means looking for "reasons" for things, and wanting "reason" to prevail. Such a person would tend to set the value of his own labor at some rationally-supportable level, and would have a hard time coming up with a rational reason why he (or anyone else) needs or deserves to be paid more than that.

Whereas other types of people who are quicker to embrace "irrational" ideas of what they're worth, are more likely to ask for and therefore receive irrationally high salaries.

The reason it's hard to come up with a rational reason for a particular pay rate, is because no such reason exists in the real world. You can talk in terms of being paid proportionately for value created, but that's just an attempt to apply reason where it doesn't actually govern. Plenty of people are underpaid compared to the value they create, for no good reason: teachers, women, manufacturing workers, foreign sweatshop workers, open-sourcers - though willingly in the latter case.

What governs in setting labor prices is not reason, but all the gloriously irrational behavior of any and every marketplace, where people we denigrate as stupid idiots are basically like "oh look, shiny things." Well guess what, those shiny things - objects of desire - are worth a lot, even if rationally speaking they are crap. Never underestimate the Shiny Factor.

That's how someone ends up paid more for the same work for example. Like when a person from outside gets hired on at a higher rate for the same job being done for less by someone already in-house. The "reason" is simply that the new guy happened to be an "object of desire" (not currently working for the firm) which enhanced his Shiny Factor. As opposed to someone already on the payroll, dependably doing exactly the same thing - that guy, by his very dependability, actually has a lower Shiny Factor. To raise it, he needs to create a real threat of his leaving, and/or actually leave for somewhere else, and maybe come back.


That's a straw vulcan.

Rationality, is or should be, by definition, pursuing actions that are in your own self interest.

Maybe engineers, if they had the knowledge that they could increase their salary by inflating their self worth in the eyes others, would do so. But in that case the problem is one of knowledge, not of rationality. Or perhaps engineers are more ethical. But in that case the problem is one of values, and not of rationality.

If someone needs to justify their pay by more rigorous means at their own expense, should they really be viewed as rational? Compare that question to the following one. Should someone with OCPD (obsessive compulsive personality disorder), that is conscientiousness and perfectionist to a fault be seen as more adept?


Business people and financiers exist to extract value from the people doing the actual work. That is the entire purpose of the position. They literally sit around most days devising new or better ways of extracting more value.

We should, therefore, not be surprised when the structure of organizations in their control reflect that reality.


That's because he's talking to you. He's not gonna tell you he despises you to your face.

But secretly he wonders: "why does he get more than me, im smarter than him!!".

This is then bottled up under 10 psi of pressure until the perfect moment when the slightest thing sets it off and creates a scene in the office.


Fyi standard temp and pressure at is 14 psi, so 10 is actually a slight vacuum. Or 10 over current is still not very much. Usually not enough to even explode. people can blow up to about 20psi, eg 6 psi over stp (otherwise we couldn't breathe). So it'd be more like a birthday baloon that flubbered around for 4 seconds and then went flat.


Interesting. So if my bike tire is at 10 lbs, is that 10 above atmosphere or just 10psi? I think a balloon flubbering arround for 4 seconds then going flat at the office would still be considered a scene. In fact I think your depiction is perfect. Ha.


Bike tires are typically inflated to a psi (lbs per square inch). A bike tire is a bad example in this context because most are filled pretty high (80-130psi, mine are 90psi). The average car tire is 30-40psi.


I run my dirt bikes trials tire at about 10 psi rear, and 14 front. Mountain bike tubeless 14-25 psi. So I guess my question was, is a guage measurement above atmospheric pressure? The answer is yes. [0] "Gauge Pressure: The pressure of a system above atmospheric pressure."

[0] https://www.boundless.com/physics/textbooks/boundless-physic...


Of all the times I've ever heard a pressure figure mentioned in casual conversation, I cannot recall a single time where the person was referring to absolute pressure rather than gauge pressure.

In fact, if I were at a party and I mentioned something about "10 psi", only to have someone correct me by saying "actually that's a slight vacuum...", I would assume they were trying to be mean.


okay 10 atm then


So I read this a while ago and it really stood out in my mind.

http://www.cbsnews.com/news/my-boss-revealed-everyones-salar...

It's a question addressed to "Evil HR Lady" (didn't know that was a thing...) from a woman. Her new boss accidentally emailed a spreadsheet with everyone's salary to everyone. The spreadsheet revealed she was underpaid and was embarrassed and now wants the boss's head on a stick.

This is the response from Evil HR Lady

"You are really angry, and you should be -- but your anger is misplaced. Your new supervisor made a mistake in sending out everyone's salaries. But because she is new, I can guarantee she didn't decide on your salaries. Your previous boss did. So, yes, you should be angry, but not at her. You should be angry with your old supervisor.

In fact, you should be thanking your lucky stars that the new supervisor did this. In fact, I wouldn't be surprised if she subconsciously did it on purpose. If I got a new job and on day one found out that there was a huge disparity in pay among workers doing the same job, it would be top of my priority list to fix that. And I would act as a thorn in my boss's side until it was fixed. Since the problem is a longstanding and expensive one, no one is going to be excited about fixing it. By revealing the discrepancies, she's just brought the issue front and center, and HR and the big bosses cannot ignore it anyone more.

By sharing everyone's salaries, she's given you the power and the tools to fix the problem. HR can't smile sweetly and say, "You're making the market rate, dear!" because you've got hard evidence that you're being underpaid. And you should use this information to negotiate a new salary, as should all of your coworkers. And your boss? She has plausible deniability. It was amistake.

You're angry because you're embarrassed that your salary is low. Not because your "privacy" was violated. If she'd sent out your medical records, or notes from a conversation about your marital problems because they were affecting your work, then that would be a privacy violation and you'd be justifiably angry. But this anger is coming from the unfairness of the whole thing. Yes, you should have negotiated better when you were hired, but because of the information asymmetry in hiring, the company was able to low-ball you. Lesson learned -- always negotiate.

This is precisely why I advocate more openness in pay in the workplace. If you had been aware of what other people in your group were earning when you negotiated your salary, your present salary would likely be more fair. Everyone shouldn't be paid an identical salary because performance and skills are not identical, but salaries should be justifiable and logical.

So forgive your supervisor for her mistake. Accidentally attaching a file in an email shouldn't be a fireable offense. Use the new information to get a higher salary. And if you have to be angry, be angry at the previous supervisor who allowed this to go on.

Good luck with your salary negotiations."


That's basically the best response anyone could have possibly written.


I think you should share your salary with as many people as possible. This "don't share" policy is just a trick used by companies to keep labor costs down.If employees know each other's pay, they will start demanding raises.

------ Keep in mind that 2 employees with the same education and years of experience might not always be "equal in all respects". There are so many other things which come into play - taking initiative, energy they bring to the company, team play etc. etc. most of which cannot be measured. So the reason for 2 employees with apparantly equal qualifications + experience not getting the same salary is not always the company "trying to fuck them" or because they did not "negotiate hard".

If you make all salaries open, keep in mind that so many employees will get demotivated to know the colleague next cubicle gets paid more. Serves no purpose.


I've always been a fan of daylight on salaries. People get uncomfortable thinking about their worth in relation to others, but having it exposed means two things: 1) you can easily figure out who you should be more like and 2) it prevents bullshit from being the cause of someone receiving high pay. If I'm going in for a salary negotiation and I ask my boss why so-and-so makes $50k more a year than I do, he or she better have a damn good explanation for it.

The problem at this point is societal. It's been taboo for so long that people still harbor deep discomfort with it. Maybe they believe they don't deserve the pay they're getting so they wish for it to be quieted. If that's the case, then fuck those people.


Oops, boss coudn't explain it. Now you, too, make $50K more due to some bullshit cause. :)


A reminder to everyone that the National Labor Relations Act prohibits companies from firing employees for discussing their salaries:

http://www.govdocs.com/can-employees-discuss-pay-salaries/


That's certainly true, and for most of us in the US, it's also true that as an at-will employee at a company, you're only protected by what the law covers. The list of things it doesn't cover is long enough that it's not terribly difficult to find a reason that is legal to cover-up the real reason.

There's the bigger problem with sharing your salary openly: raises.

My dad told me when I started working "Don't talk about your salary unless you don't want to see a raise again." It's not that absolute in practice. For many, raises are doled out yearly and are an average percentage with discretion to give some more and some less than the target. Even when well deserved, it's not easy to squeeze into the higher percentage but one way to make it a whole lot more difficult is to be revealed as someone who'll tell all the coworkers what they received. That'll almost certainly be on your bosses mind when it comes time for that decision and you might find yourself fighting to get an average raise since giving you the lower raise has the added benefit of making everyone else think they did better.

Share it on the Internet, openly, and now everyone in the company can know what you make. If you're paid over-average, your boss might even get a phone call asking "why?". That's just not a good place to be.


Right. If you are underpaid, make noise. If you are overpaid, you deserve a target on your back for profiting off your coworkers.


Ha. I don't know if I'd go quite that far, and I believe it has a bit more innocence behind it.

Interpersonal, HR related issues are usually very low on the list of things your manager enjoys. Assuming you're well known for publicly discussing salary, giving you an average raise and keeping you at the same salary might make you a little upset when you feel you deserve more (to which you might get a "my hands are tied" or "there wasn't room in the budget, this time"), but giving you a salary that eclipses your colleagues will make the rest of the team angry -- and probably a lot more angry than you'll get by just receiving the average. Unfortunately, the math ends up being not to your benefit.


The funny thing is I once asked for so much that they fired two other people.

Smart people make more money, then save it and then use the fact that they have 6 months expenses saved to leverage getting even more money.


You are right, and you also don't know Amazon (as well as many other powerful corporations).


Second that :) Reality is not binary. You can't reduce it to either 0 or 1...


As a clarification: I'm pretty sure that is held to cover employees discussing salaries amongst themselves, and that it has been found not to cover employees sharing salary data with others outside the company.


Do you have a cite for that?


I had a look and I actually can't find any cases that address an employee sharing their salary with third parties, so I might be wrong (or just bad at looking for relevant legal cases). However I can find numerous cites where people mention off-hand that 'of course this doesn't mean employees can share salaries outside the company' and similar - http://www.velaw.com/uploadedFiles/VEsite/Resources/Employer...

I would suggest anyone attempting to claim NLRA protection actually read the document, particularly clauses like the exclusion of protection for supervisors discussing salaries.


But not for divulging confidential information to the world, which is what the OP has done.


are you suggesting that companies can get around labor regulations by declaring your compensation to be confidential? I'd check with a lawyer if I were you, that's some pretty thin ice you are skating on.


Tangential - I asked my manager where I am on the stack rank once. He said it's confidential information.

I have access to VCS, bugbases, all the documents. We're a very metrics-oriented organization. And the one thing that defines where I stand with the company, I can't be trusted with.

I think if I didn't get a check every two weeks with the number on it, they wouldn't tell me how much I'm paid.


I pity the company who has a CTO who puts wishful thinking over the reality of law.


I make roughly $20 an hour (about 16 after taxes :( )at the moment as a junior full stack intern working part time (I live and work in US). Sometimes I wonder if I should move on to find some other job, even if its remote...

On the other hand, my work is not that stressful, and I'm still going to school so my job is very flexible on time.

Anyone else been in a position like me?


My first couple of programming jobs I was making about 60% of what you made, although I had no degree at the time. I was the only programmer for one company.

You can relax, but you might not want to. My salary has been artificially lowered because every previous company likes to make an offer based on your previous salary, or I've made so little that I had no savings and had to take the first job offered to me every time. It wears on you after awhile, and I probably could have made a lot, lot more money if I made better choices earlier (although I also wouldn't have some of the wide range of job and life experiences also, so there's that).

But every once in awhile it's nice to take a breather, sit back, recalibrate yourself, get your work/life balance back in check, work on some creative things in your spare time, etc. Easier, non-stressful jobs will allow that. So I guess it's wherever you need to be in life right now and how much you need to be compensated.

But if you're not getting challenged at your work, you're probably not learning skills that are in demand and your next job hunt will probably be more difficult.


I've been in an almost identical situation!

I made $25/hr (without benefits), then got dropped to ~ $18ish / hr (with 401k matching and health insurance) at the part time job I worked while I was in school.

I worked 20 hrs a week, completely remotely, and was responsible for some of the NMS systems and Linux admin work at a large satellite operator. It was a mix of sysadmin and software engineering, and I learned a ton.

There were a few stressful moments, as I was on call, but my boss tried to shield me from it as much as he could because he wanted me to be able to focus on school.

If you're a full time undergrad student, then my advice to you is to enjoy what you have right now, as long as it allows you to focus on your friends and education. Having practical, hands-on experience from work will greatly complement your coursework, and if you can get that experience without being in a high-pressure role, then it's a win-win situation for you.

Consider asking for a pay bump if you think you're undervalued, but do research on what other paid SWE internships are at, and consider the fact that a bump in pay may cause your boss to have higher expectations of your output.


My first job was $15.50 an hour for a software dev internship at Ericsson. Then I went through two junior web dev jobs, both part-time, each paying $20/hr then $25/hr. They considered me a bargain. Now I'm making twice as much.


Competitive internships will offer 2-2.5X that.


Really? I went through the co-op program at my university and the pay range for everybody going into software was basically $15-25/hr, although I didn't hear of a single person getting over $20.


> Really? I went through the co-op program at my university and the pay range for everybody going into software was basically $15-25/hr, although I didn't hear of a single person getting over $20.

By competitive, I mean microsoft, facebook, and google. This could be naïve of me, but that's how they position themselves.


You gave enough information that they could find you without using any links in your profile or your online handle.

Another thing that could be interesting is your accent. My eyes were recently opened about the discrimination that happens based on that.


Actually, I told my boss about the post before I submitted it. But I was only letting him know -- I didn't ask for permission. The decision was mine and mine alone, so any (unlikely) backlash won't be directed at him. We have a good relationship and see eye to eye almost all the time. He did say that he didn't think there was anything wrong with posting this.

The reason for the throwaway is because I generally try to avoid "stirring the pot." Or at least, don't want a reputation as a pot stirrer. But if some higher up confronts me about it, I won't deny posting it.


Some pots should be stirred and I think this is one of those pots.


Accent? Seriously? That's funny to me because as developers we are generally stereotyped as poor communicators, so I wonder why any employer would focus on filtering out persons with unappealing accents (unconsciously or not) when this has no bearing on their technical skills.


Amazon offered me 104k/year + 18k signing bonus for year 1 and a 14k signing bonus for year 2. Software Developer position.

35k in stock options that would vest over 4 years.

That was March 10th, 2011.


Op (and others) adding your office would be informative if you are comfortable with that.

Otherwise compensation is hard to compare.

I quit but my pay was ( Lin Seattle, numbers rounded a bit)

90k base 53k initial grant, backloaded 5% after 1 year, 15 after 2, 20% every 6 months after that. 37k signing bonus, 20k lump sum, 17k spread over 2nd year.

Raises were <1% at first review, 3.5% at second. So when I left after just over 2 years I was at 94k base. They did give me some more stock at my second review, but it was 2 years out iirc


I'm starting to think I need to move out of the UK to somewhere that actually pays developers a decent salary.


I started out at $35,000 USD / year in Vancouver then I stopped working 9am ~ 9pm including weekends and just started my own SaaS which made less than 10% of that.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: