Salary can already be transparent to employers because equifax may sell your salary history. That may offer direct salary information which allows asymmetric salary negotiations. I've read, but can't cite, that many companies contract with consultants, where they share salary bands and get other companies salary bands in return which likely offers a form of soft collusion. We've also seen companies like apple and google cartel-ize the labor market.
My current company touts (internally at least) that they use "market data" to determine how competitive we are with salaries. We're near the top so everyone thinks its "justified" ¯\_(ツ)_/¯
Yet another surprisingly fantastic reason to hate Equifax:
- no security
- no competition
- no privacy
- no recourse
- unsubscribable spam
- terrible phone processes force having an online account… which has no security
And the other credit bureaus are just as bad (┛ಠ_ಠ)┛彡┻━┻
Not sure I'm reading this right. You went from making $634K per year to $72/hour???
I can't understand why any company would pay so much money for a software engineer and I especially can't understand why someone would quit such a job. That is life-changing money. It's like winning the lottery.
Half that compensation is in equity grants. Google generates millions of dollars in revenue per employee. The real question is why are Google’s salaries so low? The answer is the same as it is for other jobs: because the labor market isn’t the same kind of market that your econ 101 supply/demand curves model. There is too much information asymmetry and individual laborers’ motivations aren’t all aligned bedsides.
> because the labor market isn’t the same kind of market that your econ 101 supply/demand curves model.
Well, sure it is. The information asymmetry/individual motivation that you speak of doesn't make things somehow magically different, it merely helps determine, along with a myriad of other factors, the values for supply and demand.
> The real question is why are Google’s salaries so low?
Because that is where supply and demand meet, just as illustrated on the your econ 101 supply/demand curve. Quite simply, they don't have to pay more because supply is sufficient at that price to satisfy the demand.
Supply is sufficient at that price is just another way of saying it’s because workers don’t organize to demand more (in relation to the ambitious extent that their employers do coordinate to minimize wages)
Sure, I suppose. Supply and demand doesn't care as to what conditions establish the values of supply and demand. It is merely a hindsight observance what what conditions did occur.
> The real question is why are Google’s salaries so low?
The real question is - why are they so high? There are literally tens/hundreds of thousands of qualified candidates that Google rejects in their hiring process. This makes the remaining candidate pool small enough that they have to offer half a mill to get them. If Google's hiring wasn't so restrictive, they could pay much less. However, since they're basically printing money, there's no incentive to go there yet.
There are lots of people with the technical skills to work at Google. Only a subset of them have the right personality to work at Google. It is a very unique culture.
I could believe it as a big tech guy working at a different company
Google's internal culture sounds awful to me*. Tons of kool-aid chugging, shadowy political battles, people obsessed with tech for the sake of tech... plus they don't generally interview for a specific position, instead you interview for Google at large and then have to find a team that wants you once you pass the bar.
Passing the bar is also obnoxious. Maybe there are a lot of transcendent super-geniuses out there who can do it without studying, but IMO the Google bar is tuned to baseline-assume that you can crank out a Leetcode Hard problem in a few minutes, then they throw extra twists in on top of that.
So you have to spend months of your precious free time cranking away at coding practice just to get an offer, and then hope that you can find a job you like once you're in. OR you can go to Facebook, Amazon, Apple, Uber, etc and make just as much money.
* I can appreciate how it'd appeal to a lot of people though. One man's "Kool-aid chugging" is another's "Pursuit of social justice", one man's boondoggle is another's cool tech, one man's "shadowy political battles" are another's "Engineer-first Meritocracy"
Based on the number of quality job applicants they get and the relative randomness of their current hiring processes, they could make salaries much lower and they wouldn't notice any decline in engineering quality... They might even notice a significant increase in quality if they dropped salaries and improved hiring processes.
Yeah, it's not like it was a couple of months for that kind of money; it was years. More than enough to change your life and start working for fun or charity instead of for money.
> I can't understand why any company would pay so much money for a software engineer and I especially can't understand why someone would quit such a job.
Imagine how much money can be saved by shaving 5 percent off an annual AWS bill of 10 million dollars. (dont forget to factor in present value of future year's savings!) Now imagine a company like Google that spends way more than 10mil on infra. And even if your infra is cheap, virtually every tech giant has shown that shaving 100ms off a request is a massive boost to customer engagement metrics, so maybe it _shouldn't_ be that cheap. And product teams are just as valuable, if not more so.
That explains the demand. On the supply side, people who can actually do the work are hard to find. There's a massive gulf between having a degree in CS and actually making good on improving complex software. I've watched like three teams fail to deliver on a GSLB[1] optimization tool. Two of the three iterations didn't recognize this as NP complete (bin-packing, essentially) and the third is learning the hard way that there's calculating an optimal response is only part of the problem -- you also have to change state without inducing outages on the receiving end, and a naive SAT solver won't produce that. Beyond that, bay area is expensive to live in, and is high tax. $634k becomes more like $300k, in a city where you might spend $5k a month in rent. So there's definitely a _floor_ to salaries.
Also: once all this is accounted for, retaining talent with equity grants has a side effect of accidentally pushing wages above target. Some places like Amazon seem to explicitly take this into account when issuing refreshers, others not so much. Which means to hire someone away from Google is really hard. But really easy to recruit from Meta at the moment, as their stock has fallen 60 percent so income has fallen as well. Beware of the double edged sword.
he could invest 50% or more of his salary in this work via donation and it would probably help the cause much more than his 40 hours/week. It sounds more like a middle life crisis to me.
ymmv: if "the cause" has technical or scientific elements and you are a skilled engineer or scientist your contribution of 1000h/y work on target is significantly larger than donating $1M/y.
I've been in a startup where the product was so cool that we'd get people working for nothing but options because they were too burned out by $MEGACORP developer culture. The money developers were leaving was so ridiculous I figure we could have charged people to work for us and we'd still have gotten more applications than we knew what to do with.
categorical imperative: if everyone did that nobody would do the actual work. there are problems in the world that must be solved with software engineering. software engineers need to work on them, and highly skilled ones, too.
disclaimer, i guess: i work at a sister project of the NAO
Because when you're a large monopolistic corporation receiving billions of dollars every quarter on the basis of work which was carried out decades ago, there are always going to exist many inefficiencies which unnecessarily cost you millions of dollars; many of these inefficiencies are created by your own employees and could have been avoided through a bit of additional foresight. Also, there always exists many other engineers on the market which you didn't hire and which could also have saved you millions and they would have done it for a lot less money. Google receives a huge number of job applications and the selection process involves a great deal of randomness/luck.
Please... They trash the vast majority of resumes on the basis of silly things like the candidate changed jobs too often, they didn't study at a fancy enough college or they can't recall a specific algorithm on a whiteboard. It's a joke. They're amateurs.
If you're too good, they will feel threatened and not hire you. It's all politics inside these megacorps. Engineers will never allow real talent to be hired on the same team as them... Why would they compromise their position within the company hierarchy?
They'd rather only hire moderate talent; just smart enough to get the job done but dumb enough to not get in the way of your next promotion.
While I think that's equitable, you could also see how an employer might try to keep a larger share. And most employees would probably agree to getting something substantially less.
> you could also see how an employer might try to keep a larger share
But trying to keep a larger share means you lose out on all of it, as you will get outbid.
If they can save other companies 1.2 million as well (which they will because few companies are so unique) then their price will naturally creep up towards that value as others will be willing to pay more because it's a good deal.
Basically that's what those companies did, and then some of those engineers started 1 trillion dollar corporations since they couldn't convince anyone to pay them 600k
Between real estate, and the equities market, a few million dollars can support your lifestyle indefinitely. But also factor in that this group of people can also be limited partners in Private Equity and Hedge Funds forever and get tiny pieces of a couple big bets (and I would seriously ignore articles that say the S&P beats them. YMMV, good luck!)
FWIW I don't have a few million dollars or other large investments, and I do still need to make some money from my work. But I can also live well on much less than I had been making!
Consider cost of living and taxes in the Bay Area as well. These salaries would be extreme in a place like Idaho but in the Bay Area your money can quickly disappear.
I'm in Boston, which is more expensive than Idaho, but significantly cheaper than the Bay Area.
For example, in 2015 I was able to buy a house that would have cost ~5x as much in a comparable location (25min commute to work, 10min from a subway station) in the Bay.
You should do it, man. People read a Google Zero blog post or something and think "Oh I'm not on their level", when the reality is far different. I think it's mostly hard work, infrastructure, and experience that lets people accomplish amazing stuff at these giant companies.
Sure, you need some baseline level of smarts, but it isn't some obscene 1/1000 genius. I'd be willing to bet that at least a quarter of all programmers are smart enough to work at FAANG and make 300-600k.
Interview/Leetcode problems are a lot like mystery novels or sudoku puzzles. Once you know the basic building blocks (data structures, algorithms, sneaky tricks) they're hard but not THAT hard.
Google's a bit of a different beast from the rest of the FAANG companies. They take it as a baseline assumption that you can easily crank through a super hard coding question, and throw a wrench into it while you're working on it. IMO it's still doable to pass the bar though.
After a couple of years in big tech and exposure to the tricks of the trade, you too will be able to do stuff that blows people's minds. Such as quit to take a 75% pay cut for a job that's personally meaningful
Not saying that publishing your salary isn't important, but for me the linked article sounds more like bragging and virtual signaling, like "I went from dishwasher to google developer, earning almost 700k/year but i gave up from everything to work with what I love.".. From $634k/year, to something like $34560/year? This makes 0 sense. If he would donate $400k/year to the cause that he wanted to help, would be much better for the cause and to his own familiy, than he investing 40 hours per month on that.
I think this a great idea, but how do you deal with people who are simply weird/jealous about money? For example, the responses here are a mix of 'cool, how can I do that' to 'you don't deserve that much'.
Every time I've seen people find out what others make there is a group that always first assumes they are getting hosed and are jealous. Even for numbers as small as .5% difference.
Personally, I'm not a jealous person so I don't understand the group I mentioned. But, the emotions/reactions I've seen are always in the back of my head when thinking about opening salaries.
I've never gotten negative feedback in person on this, and negative feedback online for it is both rare and not something that bothers me much?
In general how much I care about feedback is weighted by some combination of how much I care about the person giving me the feedback and how important it seems. When someone on HN or elsewhere gives me feedback the former is low, so I'm mostly thinking about the latter. If the feedback is "you're wrong to be working on detecting novel pandemics because of detailed reasons XYZ" I'll take that quite seriously, but if it's just "you're a bad person for trying to earn a lot of money", especially without any sort of argument, I just ignore it.
At this point I'm primarily evaluating jobs based on their altruistic impact, but if I went back to trying to optimize for compensation I think I would be able to get a few companies bidding against each other at which point my history isn't really relevant. That's what I did when I rejoined Google in 2017.
If a non-founder employee can do that the company is already at Google or FB scale and they're going to be paying accordingly.
And the SDE isn't the only person making the money come in, it's just (usually) very easy to draw a line between new products and revenue, or code changes and lower infra costs. There are a lot of other people - hundreds - contributing to that $60MM but everyone here likes to pretend if the SDE isn't getting 98% of it they're getting screwed by The Suits.
I never understood why people thought there was a giant leap in value between employee #1 and a founder, in terms of value-add. (And if someone can explain it to me, I would be appreciative. I understand how it makes a difference when getting seed money, but not after that.)
Meanwhile, sometimes it is dependent on lots of people. Sometimes it isn't. A programmer is the only person who has the possibility to rewrite some code and make a process take 1% the same amount of time.
Depending on the industry, this can be a 99% reduction in cost, a 1% reduction or a massive, massive increase in revenue (HFT).
Employers should be forced to be transparent as well. you know, things like a legally binding wage range on a job advertisement: Telling folks first thing in an interview what the pay range is as well as putting it in the advert (to cover anyone that was simply referred). The range should include all salaries at that position, if there are other people working it. If the 'starting pay' is less than current employees make, this should be justified (current employees have had raises, for example) This should be updated yearly and made public to your employees.
It is a lot harder to lowball folks if they have to be upfront about what they are paying.
Unfortunately the 2021 numbers were really juiced because of stock performance. It looks like OP took a different job, but if he didn't, he should expect his comp to drop to a measly 400k or so in 2022
That's about right: three things would have combined to decrease my 2022 comp:
* When I came back to Google my stock grant vested evenly over four years, creating a 'cliff' in year five. They don't do this anymore, I think because people tend to leave.
* My 2021 comp included several past years of stock grants, and the company's stock had been growing much faster than the market.
* The market overall is down since 2021.
I think I would have made about $470k in 2022 if I'd stayed the whole year.
2023 would have been higher, because it would have been my first year getting the full L6 comp.
(And I'm not sure if you're being sarcastic, but I definitely wouldn't consider $400k "measly" -- even after donating 50% I had much more to live on than most Americans, let alone most people globally)
Here in NZ $140,000NZD would be a good wage for a software developer. That is about $80,000USD. $400k US is about $700,600NZD. That is a massive amount of money for one years work.
Edit: My sarcasm meter is broken. In reading other comments I seem to have missed the joke. Sorry.
Keep in mind Google is a massive outlier inside massively successful startups which are outliers inside SV which is an outlier inside...
Lots of places in the US are as far from those numbers as NZ. Google numbers should not be an reference point to almost anyone, anywhere or they're likely to be disappointed.
Serious question, how many years? I ask because 1) I make really good money now, especially if you ignore the SV/FAANG outliers that everyone here pretends are the norm, but it still took me 7-8 years to break 100k USD, in the US. 2) Maybe because there are so many new devs now but I hear people say a lot "I've been doing this for years!" then when you dig into it "years" means 2 or 3. These are also the same people who don't consider themselves junior 6 months into their first job, or consider themselves senior after 3 years. A career is 30-40 years long.
The median income for a dev in the US is 100k. That's going to skew down due to lots of juniors but it also includes everyone making several hundred thousand dollars a year. I am taking a pay cut down to 160 for better WLB on a product I have used for years as a customer and really care about, and I think if you ignore the outliers I am very well compensated at 12 YOE and existing domain knowledge.
We can't (currently? yet?) hire people who are not working from Australia, for legal reasons. I'd love to change that, finding great people even across the whole of AU is extremely difficult.
There really aren't a lot of great candidates out there. The last hiring round I ran turned up a lot of candidates asking for 170k, but who couldn't even do elementary software engineering best practices. Not algorithms, but things like - reading code, writing comments, formatting their files.
Pretty incredible to see how tight the market is right now.
1. We have to use recruiters to find candidates, we barely get any hits on our job ad, even though we are a pretty innovative company with a modern tech stack and pay quite well. The recruiters field us the most woeful candidates, but at least it's someone rather than no one. The pool for qualified senior engineers is low, so we're all competing for a shrinking pool of candidates relative to the jobs on offer.
2. Hiring for fit is important to me, so it's not so much that they aren't stellar in their interview technically, but the fact that people don't realistically state what their strengths and weaknesses are, and sometimes outright lie to you, means that I don't want to work with them. Humility is the bedrock of real growth, how can you really grow if you're lying to people around you about how competent you are? I've hired weaker candidates technically purely because they had an on honest approach to their abilities, and demonstrated a keeness for learning.
If you're at the junior level, my advice is to job hop as mad as possible until you have a few years/companies under your belt. Get a breadth of experiences at a few different places, it will help you contextualise everything you learn/don't know Once you hit 5-10 years experience, that's the time to start slowing down and really honing in on your experience and stay at places for longer. Completing projects end to end, and crucially, learning how to plan, estimate and deal with change over time.
A$150k sounds fairly decent against USD but upon currency exchange, it is $94k. Accounting for the high cost of living in places like Sydney etc, it ain't that much
Better standard of living in Sydney or Melbourne than the Bay though. I really cherish the time I got to spend in Australia, despite the cost of living, and I’d live to return some day.
thank you for breaking it down between nominal and actual!
the data out there is so bad!
Even Levels.fyi takes both nominal offers as well as actual outcomes like W-2's, which can be wildly different in a volatile market. So nobody really knows anything.
I wish more tech founders would do the right thing - rather than trying to hide reality will only ends up unfairly hurting under represented groups and those who aren’t strong negotiators.
I feel I must ask where you live / what competitive salaries look like to you, because as far as I know, a software developer salary of $190,000 USD+ in Barcelona, Spain is eye-poppingly high
I think he's talking about runn where the compensation honestly looks terrible: $43k as a junior and under $80k as a senior. I wonder if the goal of transparency there isn't to avoid wasting time with the majority of people who won't put up with a salary that low.
I am sure it’s low in the Silicon Valley. Here in NZ - we are the highest paid tech juniors I know off. Most offer around 60k NZD.
Need to remove your US bias. However - the whole point of transparent is that everyone knows.
If the salary is low for you, you will never apply. But you know exactly what you’ll be paid, and know it’s the same as everyone else doing the same role/level.
That is the benefit to being transparent - it doesn’t have to be the highest paid, it’s simply fair. equal and transparent.
What are you even talking about? The median yearly take home pay (sorry, don't know the right word for it) in my middle-of-the-pack EU country is around $16k.
Let me say that again, this country is in 35th place out of 193 by GDP per capita and this is how much people make here.
Yeah, my bad. My comment is very US-centric. At the same time, cost of living is likely much higher in the US, so that also makes a difference in the comparison.
Is that double the median income of juniors in similar tech positions or the general median that contains part-time workers and jobs that require no education at all?
In the US at Big tech cos(FANG style), that would be the base salary for someone with 7-10 years experience. And then you add on generous compensation packages(stock grants, 20ish% bonus target, signing bonus).
I would say it is eyepopping for US techies who haven't made it into the "big leagues", but there are probably a million software devs in the US making that.
in norcal or new york, $190k is pretty standard for a senior role, with equity compensation on top. I get $185k with 7 years of professional engineering experience + rsus worth about $150k over 4 years, and really I could get more if I left for a bigger company, which I don't want to work at. Europe has lower salaries in general, but also a lower total cost of living and better gov't services.
6 figure salary for an executive assistant in Tennesse is quite nice. A lot of engineers I know dont make that much and the skillset gap required between both professions is quite large IMO.
Skillset gap is not what determines price. Supply and demand ratios do, which does not necessarily correlate with skillset gap.
For example, I might be able to be an executive assistant, but I imagine the quality of life of an executive assistant is worse than what I do now, so I would want even more money to be an executive assistant.
Salary transparency, like all levelling mechanisms, pushes salaries down. Your highest salaried team members are simply replaced by contractors as they realise that their remuneration is now tied to the impression it gives to their colleagues rather than the value of their own labor.
It seems to me, in my uninformed layman opinion, that it would do the opposite. Maybe it would force the outliers down but perhaps bring the average up.
These are two common scenarios I see:
- Two employees at the same level on the same team. One is paid $X higher than the other. Employee one asks for raise based on the fact they do the same job as employee two
- New hire is paid $X more than member of team who has been there receiving meager raises yearly. They can point to the new hire and request $Y more due to their experience
That said, this is conjecture and not backed by anything. Are there published works on salary transparency = lower pay for employees?
There is a 3rd scenario that I've occasionally seen: Two employees with the same title on the same team. Employee One is unhappy because they are paid 10% less than Employee Two, despite same experience and title. Employee Two ALSO unhappy because in practice they do 50% more work than Employee One for 10% more pay.
I still don't see the parent's connection of transparency to lower pay, but there is a rich scientific literature on the concept of "Comparison is the thief of joy" -- I hypothesize that turnover rates might positively correlate with transparency because they could promote intra-team competitive feelings.
The exception would be if there were a rigid structure that you know going in, similar to how e.g. government pay scales work. Since you know going in that the only input is seniority, you won't care that exceptional work is not rewarded because that was made clear from the get-go, and if that would have bothered you you wouldn't have accepted the offer in the first place.
The natural counterargument to that is that if the only input to compensation is seniority, then there is reduced incentivization for performing "above and beyond", possibly cultivating a culture of mediocrity.
It also would promote pay equity, however, since e.g. employees' implicit biases and social conditioning would not come into play under subjective evaluations.
While I support pay transparency on principle, I have never seen it work. In practise, no two employees are ever equal. Even those with the same years of experience, the same qualifications, and the same roles. One might be happy to work late. The other might be happy to pick up the phone on weekends. One might prefer working alone. The other might play better with colleagues. One might offer to take on more projects. The other might not, but they have better attention to detail. The differences go on ad infinitum. There is no "objective" way to determine the market value of each of these two employees. The best we can do is let each business make subjective judgments of each employee. We know this is far from perfect, but it could be more fair than paying two very different people the same wages just because they studied the same thing at university and worked in the industry for the same length of time. One of them will be contributing more to the business bottom line - sometimes significantly so - and they probably know it. They'll leave if they're paid the same as their lesser-performing colleague.
You can observe it by counting the contractors in any company that has salary bands, or transparency, or any other similar system. Very few high performing employees are prepared to accept that their remuneration is being constrained to prevent the lower performing employees from getting jealous. They are strongly incentivised to either leave or become contractors, increasing their remuneration even more. Only the average performing and under performing employees readily accept such an arrangement, because they are either unaffected by it, or benefit from it. You don’t need to do a study to figure out that people avoid things that are detrimental to their own interests.
This is only true if people are underpaid in their salary bands -- which certainly can happen.
However, it doesn't have to. We are still small with our experiment, but we pay 95% percentile in our market, plus provide additional benefits well above the norm.
We have no issues hiring and retaining high performing staff because we pay as much or more than they would get elsewhere in the local market.
We don't even need to speculate about it. In for example Sweden, everyone's tax return is public information. You just call the tax office and ask how much income someone declared last available year.
Do you have empirical evidence of this? I struggle to understand how salaries being in a black box helps your chances getting paid more as an employee.
It will be really difficult for all individuals to share their salaries if some of them are on low salaries and fear not being able to scale up if they publish those.
There's also an intrinsic bias in sharing salaries in that the well-paid folks are more likely to share theirs because they feel validated by the value itself.
We are also on this side and on the job boards we run [1], the companies are required to publish real salary data™ (and we also gather stats based on that).
What is real salary data™ - contrary to the flawed regulations in a few states, which basically allows putting something like 1$ - 100'000$, we require companies to be more specific and have a max range of 30-40k.
Interestingly, the majority (approx. 2/3) of companies are completely fine with publishing this information (if they are forced to) and out of the remaining 1/3, half can be convinced, and the other half is a lost cause (basically, management will not allow it)
With recent laws in California, NYC, soon nys, and the existing one in Colorado, only Washington needs to pass one for all the priciest tech hubs to have mandated transparency in job postings and internally. It's really promising.
Do you and buffer pay the same regardless of location? Honestly that always seemed more fair to me than "cost of living" adjustments which often fail to capture a lot of the nuances of actual differences in costs of living.
To answer your question as posed: to fix the power/information imbalance that is used to pay people less than they are worth.
To answer your question the way I wish to: thanks to Equifax's TWN, candidate resumes, reference checks, background checks etc - the candidate is already showing all their cards.
> the power/information imbalance that is used to pay people less than they are worth
Candidates often pad their resumes with skills they don't have. They'll pad their salary history. They'll hide things like stretches in jail. They'll list degrees they don't have. All to get a higher salary. The employer often doesn't realize for months that the employee wasn't as represented, and way overpaid.
It goes both ways.
I know you likely don't believe me, but I've been employer and employee, at min wage and professional wages. If you ever become an employer, you'll find out real fast how little power you have over employees. Anecdotally, I know employees with million dollar salaries. Is it credible that if corporations really had all this power, they'd be paid that much?
> The employer often doesn't realize for months that the employee wasn't as represented, and way overpaid.
that employee's coworkers and team members surely would realize how well the pay matches though. or at least, they could, wherever the employer makes that info public.
my own experience with internally-public compensation at a 70-engineer company: is that there's so much _error_ in setting salaries. i don't think my employer really cared if the salary they pay for equivalent work varies randomly by 20%: to them that's just the cost of doing business and they have enough margin to cover that. but when i see that my teammate, who's putting in literally 20-hr weeks and producing half the output as the rest of the team, is being paid 20% more than me? that's reason to feel that my employer isn't treating me fairly and to leave. that hurts my employer more than the 20% extra they're paying the other guy.
i felt like there was a catch-22 here: in theory erroneous salaries could be more quickly corrected if they were internally public. but it's risky to make salaries public before the employer is reasonably confident that they're accurate.
i made my case. i pushed for negotiations. i presented the ultimatum as tactfully as i could manage. and i exercised that ultimatum.
i believe the company truly just did not have the resources to expend on getting everyone's salary as accurate as would take to make me happy. it was a flat organization, in such a way that only a handful of people were responsible -- on top of their other duties -- for the determination of salaries for those 70 engineers. i think they are on track to fixing this broadly, but just not in time for me.
I've always hated the simplistic "Just negotiate, bro!" advice. I wish it came with more concrete tactics to use that work. I've never in my 20+ year career asked for more money from an employer and got it--no matter how many documents and facts I came in with.
Here's how it goes with existing companies:
[Me] Hi, I'd like a raise.
[Co] Nope.
[Me] OK, here are examples of the value I'm providing and how it's increased over time.
[Co] Your current salary accounts for this.
[Me] Other companies offer 20% more and I'm only asking for 10%.
[Co] ...
[Me] OK, I have an offer from the other company. Last chance.
[Co] Well... Bye?
Here's how it goes as a new hire:
[Co] Here is your offer letter with your salary, bonus, and equity. (it's 0.2% more than my current TC)
[Me] <gulp> I think the market rate should be much higher, based on my experience and skills.
[Co] We don't agree.
[Me] Can you be flexible with the equity?
[Co] No.
[Me] Can you offer a signing bonus?
[Co] No.
[Me] Can you be flexible with the base pay?
[Co] LOL No.
[Me] What about hours, time off flexibility, and so on...
[Co] Look, do you want the job or not? There's a line forming behind you, my dude.
I hate that a skill (negotiation) that is unrelated to my actual job has to be one of the primary drivers of my compensation.
Negotiation skills apply about everywhere in life. Not learning them can get very expensive.
> I have an offer from the other company
So take it!
> Can you be flexible with the base pay?
A better way is to make a counter-offer. May I recommend the book "Never Split The Difference" which has a lot of good information about negotiating. Remember your most important power is being able to walk away.
I sometimes ask people who claim a lot of C experience "could you give me an approximate value for 2^30?", which is vastly more difficult than 20% of $20K for an accountant.
I find it interesting the different approaches that people take. They've ranged from "I know 2^32 is a little over 4B, so 2^30 is a little over 1B", "I know max signed 32-bit int is a little over 2B, so...", "2^10 is a little over 1K, so 2^30 is a little over 1B", to "that's literally impossible and there's no way I could give you so much as an indication as to whether it's positive or negative, even or odd; I'm not even sure it's an integer..."
Doing that sort of mental arithmetic in a high pressure situation has very little to do with an accounting degree. Yes, it should be easy but I imagine I could make a lot of people flail at questions that they could answer easily sitting around a coffee table.
Yes. Give someone an hour, of course. I'd expect any minimally educated white collar professional to be able to that without a calculator.
As a verbal problem to answer in ten seconds? I'm more sympathetic with people freezing even if I certainly expect I'd be able to do it absent extreme pressure.
If someone regards an interview question as extreme pressure, I don't know what to say. Except advise the person to do more job interviews until they get used to it.
There's the elevated risk of re-offending, or being less trustworthy. For example, if they did a stretch for embezzling, they'd be placed in a position where trust is less of an issue, which would likely pay less. I wouldn't want to hire someone to operate heavy machinery if he did a stretch for drunk driving. Would you?
> I wouldn't want to hire someone to operate heavy machinery if he did a stretch for drunk driving. Would you?
Funny enough, that comes back on a background check...if it was within 7-10yrs depending on source, if you want to pay for it, iirc. JP Morgan will go back as far as they can to seek out any sort of theft or fraud charge for ANY position. Ostensibly this is about transparency for developers, so alcoholics are pretty common in corporate jobs the higher up you go in salary.
If you invent a 4-year stint at respected company XYZ to cover your resume gap, the company might pay you based on the value that faked experience brought.
It’s not that I’ll pay less because you were in jail a while, but rather that being in jail likely makes you less competitive skills and
experience wise compared to someone who worked straight through.
> Candidates often pad their resumes with skills they don't have. They'll pad their salary history. They'll hide things like stretches in jail. They'll list degrees they don't have. All to get a higher salary. The employer often doesn't realize for months that the employee wasn't as represented, and way overpaid. It goes both ways.
I'll explain why I disagree with you and downvoted you (since you are making an argument in bad faith).
1. Padding a resume is sometimes necessary to bypass automated systems. If the choice is between slight embellishment and never getting an offer, then I believe it is morally justifiable to pad the resume just enough to conform to requirements. It's really an open secret - recruiters will openly tell you to do this.
Also, to go further on this, job requirements are very often written by less technical people (HR) who will make mistakes in the number of required years in tech, or have ridiculous requirements that would limit the candidate pool to maybe...10 people on this entire planet.
2. Padding the salary history is almost impossible and easily verifiable through pay stubs. I very much doubt this happens often enough at desirable jobs, especially where people's reputation is on the line.
3. They'll hide things like stretches in jail - Again, almost impossible to hide, considering court records are public record. Even you or I could check this and not proceed with offering them a job. If the company doesn't do this diligence - that's on them, they certainly have the resources to do so.
> The employer often doesn't realize for months that the employee wasn't as represented, and way overpaid.
What about cases where the employee ends up being better than expected and brings way more value to the company than the originally agreed upon offer? How quickly is that reconciled? It goes both ways, after all.
> It goes both ways.
While it does go both ways, it's like saying a pedestrian is also causing damage to the car during a collision. The amount of resources a company/corp has is insurmountably higher than any individual could hope to achieve (barring billionaires). This is why we have multitude of protections for employees (that corporations are continuously trying to circumvent)
> Anecdotally, I know employees with million dollar salaries. Is it credible that if corporations really had all this power, they'd be paid that much?
The mere fact that they are able to pay a million dollar salary to a single employee signifies one of the following:
1. The employee is indeed a genius who brings this amount of money in or more, or contributes to the company growth in a way to justify this.
2. The company enjoys something like monopoly presence on the market and can afford to overpay for truly mediocre employees. If this is the case, then it's hard to feel sorry for the company.
You can disagree with me, but there's nothing "in bad faith" about what I wrote.
> Padding a resume is sometimes necessary to bypass automated systems
You're justifying lying. Not a good start for a relationship with your employer. Would you hire someone you knew was lying on their application?
> recruiters will openly tell you to do this
If they do, you know you're dealing with dishonest recruiters. Is that who you want to do business with?
> who will make mistakes
Just go to another company where you do qualify.
> Padding the salary history is almost impossible
Back before the internet, other people endlessly bragged to me how they got a better offer by padding their salary. When I interviewed for jobs, I'd bring a paystub to show the interviewer that my salary history was honest. They appreciated that. They were aware that such padding was routine.
> If the company doesn't do this diligence
A lot don't do that, especially smaller outfits.
> What about cases where the employee ends up being better than expected and brings way more value to the company than the originally agreed upon offer?
Simple. Document the value you brought to the company, go to the manager and start negotiating. If he won't budge, quit, and interview at the next company, being sure to present your evidence of the value you bring. P.S. if you really did bring the value, the company will be happy to raise your pay in order to keep you.
> The amount of resources a company/corp has
The only power a corp has over you is if you give it to them by being afraid to negotiate and afraid to walk away. They're not going to hire thugs to beat you and shoot your dog.
BTW, just for fun, I've been watching "Power", a miniseries about drug kingpins. I have to laugh at how they negotiate. It's always "do this for me or I'll kill you". Way to inspire loyalty! Or at least the silly Hollywood fantasy way.
> I'd bring a paystub to show the interviewer that my salary history was honest. They appreciated that. They were aware that such padding was routine.
While I agree with everything else you said, this strikes me as a poor strategy unless you have some highly assured leverage with which to negotiate your salary (e.g. you have lots of competing job offers, or you know that you're uniquely qualified for a job with few applicants).
Yes, but it is less than half of the states(though I'm not sure what percent of the population are covered), and even then, many of the bans are phrased such that pay history questions are only banned before an offer is made, or it is voluntary but employees may not know their rights.
It is still legal to rescind or modify an offer after you discover salary history in most states with a "pay history" ban in place.
I think you're right there - the transparency needed is from the companies, not the individuals. Otherwise it becomes a competition, and people stop sharing salary themselves because some doofus claims to be on 750k/year starting salary straight out of college.
Levels.fyi has some salary data too I think, and there's more and more being shared in Indeed and LinkedIn.
In my previous science career in academia someone would think you are insane and throw your resume in the trash if you kept working double digit days before quitting, being terminated, etc. Tech is weird.
You discover a lot when entering the job. It might be more true in tech than other jobs; god can the shock be awful, even after hours and hours of interviewing and asking questions.
Someone quitting within weeks usually has a discussion with HR the first few days and stay there only long enough to hire someone else. That's I think a sign that the person has decent communication and just wont let you down at a random time because they're too pissed to do their job anymore.
In this specific case, looking at the short job spree and the much longer tenure coming afterwards, I would not see it as a "throw the resume in the trash" kind of issue. Perhaps just bad interviewing skill (couldn't properly judge the company) and bad luck.
> You discover a lot when entering the job. It might be more true in tech than other jobs; god can the shock be awful, even after hours and hours of interviewing and asking questions.
The worst job I ever had was to be an excel administrator.
They had business critical spread sheets which only ran against certain version of excel and windows. A great way to learn the ins and outs of virtualization two years out of university. A sad day for humanity overall though.
I see the opposite: Someone who can be confident enough in their skills that they don't have to worry about finding another job if they are unhappy with the current one.
Of course, many companies would prefer desperate employees who are afraid to hit the bricks instead. But is that really who you want to be working for, given a choice?
I see it as they’re great at interviewing but their personality is not compatible with the teams they are on, and when multiplied over a dozen role changes in less than a decade.. then I’m less inclined to believe it’s the “company that was the problem” and they should probably be more introspective
I see. I can imagine that happening once or twice, but if it happens a lot, there are probably some behaviors you can change on your end to get a better idea of fit before jumping into the job. Either that, or the specificity of what you want would scare me as a potential employer. I wouldn't want to hire someone if there was an 80% chance they would decide the job was mentally unhealthy and leave within a few months.
I personally found that part very comforting. Very few people generally talk about getting fired or quitting early, which created this sort of impression to me that everyone just had a model career and never ran into any roadblocks and that I would be under pressure to do the same.
Seeing that someone who is quite succesful and to me admirable got terminated multiple times was very reassuring there.
I haven't worked with Xe but I've been in a lot of overlapping communities. That might be the impression you have but it wasn't mine. There's a lot of legitimate things that can cause that in tech, with the paragraph that leads this page being one.
Aside from the positive effect of potentially raising your peers expectations and their salaries, have you experienced any negative effects of having your public identity and salary published?
I imagine if someone on a very high SWE salary published this, people (family, friends, the public) would treat them differently. I also am curious if there would be safety concerns?
I have to ask: This says you've been terminated three different times within the first 90 days of employment. That's a lot of early terminations. What led to the terminations?
I wouldn't expect an answer. If I were in the author's shoes, I certainly wouldn't answer. What difference does it make? At best, it was simply a poor fit, perhaps mutually. Sometimes it's layoffs. Worst case? Use your imagination.
But it doesn't matter. If they didn't list the terminations, would you still be curious? If they lied and said they were laid off, when in reality they slept on the job and stole pens, would it matter?
Ultimately employers still rely on trust via interviews, and possibly reference checks, but most importantly by often having some sort of trial period (a year, six months) or simply being at-will. Isn't working? So long, no hard feelings.
Obviously it helps to weed out bad apples but don't read into it too much. If the person is fired because they performed poorly in a hostile environment, they could still thrive in the right environment. We've all had shitty jobs.
> If they didn't list the terminations, would you still be curious?
I’m curious specifically because they voluntarily chose to list the terminations on a public website, then left a comment inviting everyone to ask questions.
If I was a recruiter reviewing someone's application, I would not bother to interview someone based on the number of short term roles and being terminated. This is assuming there are a few applicants. I think this stuff does matter, probably less so in the last 10+ years.
You've listed terminations. I'm terrified of getting fired as I worry it would look really bad to future employers. How have you found employers react?
No employer has ever brought this page up during hiring discussions. If they did I would probably say something like "If you want your company to look good, then you should wow me with a very strong offer". I've been shitcanned a few times and it has made some things harder with career progression but really most of the time I was shitcanned it was a bad fit for me anyways.
> No employer has ever brought this page up during hiring discussions.
To be honest, it's an employer who found this page during the resume screening process would likely flag your resume as a pattern job hopper, at least in the pre-2017 years. The multiple terminations within the first 90 days would be a red flag to most employers.
So the fact that nobody brought it up is likely survivorship bias: Resume screeners who did find this page probably just quietly declined to proceed with the interview process.
I'm not sure of your frame of reference, but I heartily disagree. It doesn't matter at all. The only thing that might have any influence is salary and title.
I work with a boatload of extremely talented, top recruiters and, unless searching your name returns crimes, getting fired doesn't matter.
If you're the type of employer to hyperfocus on dumb details like this, then we're all better off not working for you.
Trying to pass 9 different jobs in 3 years as "hyperfocus on dumb details" and equivalent to being fired is not really a fair judgement.
I've been part of interview processes in some companies, and while I would not care about a couple of holes or being fired once or twice, I would definitely care about 9 jobs in 3 years.
It shows either that the person is hard to work with, and in this case I'd rather have someone else, or that the person prefers to jump ship very often, and in this case I'd rather not pay the price of onboarding.
> Trying to pass 9 different jobs in 3 years as "hyperfocus on dumb details"
I’m constantly baffled by HN assertions that nothing should matter in an interview.
If 3 early terminations and 9 jobs in 3 years are “dumb details” then I don’t even know what these people would consider relevant when it comes to work history.
Juxtapose this with the “Ask HN” posts from people asking how to deal with incompetent or difficult coworkers, where the response is usually a chorus of “GTFO”.
Like you said, there’s a reason hiring managers focus on these details: It’s because we have to protect the team, and bringing in someone who has a history of causing problems or failing to deliver puts everybody at risk.
Yes, people change in 6 years, and I would probably not consider it a strong bad signal anymore in 2022, given the following experiences.
But in 2017, if I actually need someone in because we're a small structure and recruiting errors are costly ? I'll definitely go for a less risky candidate.
> If you're the type of employer to hyperfocus on dumb details like this, then we're all better off not working for you.
I’m sorry, but evaluating candidates like this is the entire point of the interview process.
You’re also massively downplaying what’s going on here: I’m not referring to a single termination a long time ago after working somewhere for a long time, I’m referring to the pattern of firings within the first 3 months.
Firing someone within the first 3 months of a job is extremely rare. Two of these happened with a little more than one month on the job. I don’t know if I’ve ever worked at a company that fired anyone that early for anything other than flagrant workplace violations, which is why it’s a big deal to have one early firing on your resume, let alone 3.
I’m sorry, but these aren’t dumb details. I think you’re forgetting that the hiring process isn’t just about protecting the company, it’s about protecting the team. It’s also the hiring manager’s job to screen for someone who might have interpersonal issues or a failure to deliver results in a workplace environment that would negatively impact the team.
Do you perform background checks? What do you do when criminal charges show up? What if they're mundane like possession of marijuana?
Screening people is fine, but the signal here is incredibly weak -- so weak I wouldn't even look back that far. It's one thing if a person has never held a job for more than three months in ten years. Sure, lots of red flags. But the example here is not remotely noteworthy.
If I was the hiring manager skimming this resume I'd assume they were either in a bad place in life (I've lived in situations which made work incredibly difficult) or were perhaps going through something (illness, addiction (which is an illness)) or perhaps just ended up at a few consecutive shitty gigs, which statistically speaking is incredibly likely: most jobs are shitty. I wouldn't even give this a second thought.
The hiring process is all about gathering signal. Will this person be a good fit? Will they succeed? The things you are focusing on do not indicate in any way those things. If you disagree, then you are deeply misguided and I would run, very quickly, away from anything resembling employment at your company.
Figuring out the answers to "will this person do a good job?" and "are they still going to be here in a couple months?" aren't dumb details. It's literally the point of the interview process.
The hiring process has less direct incentives than you’re describing- at least at med-large firms.
The point for the recruiter is to close positions fast. The point for the interviewers is to get out of the interview and back to work. The hiring manager wants to increase the size of their team without having to deal with a fuckup.
But how much is the hiring manager even involved in the interview?
I've been fired once in 15+ years of writing software. Nobody has ever asked me why at any interview since then.
Additionally, as someone who has been on the hiring side, unless you're getting let go from multiple positions in a short (fiveish years) time span, I don't care. Most people get fired at some point in their career. It can be for so many reasons that it doesn't mean anything unless it forms a pattern.
The last thing I can say about it is make sure you have a very good explanation of what happened just in case someone does ask. Don't put all the blame on the employer/boss/team. Take some responsibility but make it clear that it was a one off situation that you have learned from and won't be repeating. The fact you understand why you were let go and what you learned from it so that I won't have to fire you for the same thing is a big plus when I'm considering if I want you on my team.
I've been terminated twice. Once was an actual "firing", complete with PIP, and the other was very odd in that it came out of nowhere (from my perspective) and they refused to give any reason.
My approach is just to be honest: "I was terminated from xxxx. Here's what I did wrong, here's what I would do differently today, and here's how I think they could have handled it to better."
For the second one... I mostly focus on how that experience motivates me to be as transparent as possible with my employer and seek solid metrics to judge my own performance.
I don't know if those events being on my history have negatively impacted me or not. I don't think I've ever been passed over during interviews because of them, but it's entirely possible that I was filtered out before getting to that point.
The bottom line is that I know where my strengths and weaknesses are. I know what value I bring to the table and more importantly I know how to communicate that. I'm not afraid to speak up and acknowledge when I'm wrong, and I do my best to use empathy in dealing with others in similar circumstances.
I've long told the story in interviews about the time I accidentally wiped out a production database, and how I was able to work under pressure to very quickly fix the problem. I say another company has already "paid for that part of my education" - I learned from the experience and am very confident I won't be making that mistake again. Those two terminations? Those were also part of my education. I learned from them, and won't be making those mistakes again either.
not trying to be rude but... this is a really really bad looking employment history. if i see people quit soon after joining once or twice i get that, if i see someone fired once or twice understandable, but anything where someone spends 4 years being employed for less than a month, lots of gaps, many of those just 1-2 months that looks bad. you might want to consider taking it down. (again i don't know what happened but just trying to be helpful)
Looking at it, I’m not so much concerned with the spate of short jobs at the start. What does worry me is the consistent yearly quittings. If you get 1 year of work out of them it’s a miracle.
It’s absolutely possible they were all just terrible companies, but…
But publishing it here doesn’t make a difference, presumably the same information is on their CV.
> It’s absolutely possible they were all just terrible companies, but…
Let me first say I think it's a terrible idea to publish this information publicly. The hiring company holds all the cards already, you don't need to give them additional power by showing yours. Companies understand this very well. But I get this has been done more for ideological reasons rather than practical ones.
Regarding the possibility that all companies were bad, that's actually important information that could point to the candidate's difficulty in evaluating opportunities. If that's an important part of the job which you're hiring for, you absolutely are going to take that into consideration.
There's probably a ton of employers that passed them up without even contacting them. I know I certainly would pass on this candidate if I saw the data from this page.
Also not trying to be rude but also being a little cheeky: This person is weeding out people (possibly like you? <- that's the cheeky part) who care about this type of thing.
I've been in the biz 13 years and only had 4 jobs but I felt varying degrees of "doing the job I wasn't hired to do" by two of them. This actually seems to have almost meme-status from others on the internet talking about their new jobs. Lots of these people stick around these jobs because, "Hey, I have a job!" but that's not for everyone. Some people, like the author of this post, have a bunch of cool personal shit under their belts (check the homepage) and afford to be picky.
The TL;DR here is that job interviews aren't always about an employer trying to impress a potential employee.
The raw data itself does record if it was remote or not. I could add that to the table I guess. I didn't at the time because I didn't want to clutter things more. I can re-evaluate this I guess.
I took the leap because it was easier than continuing to be in a long distance relationship. Everyone is different. It helped that I was trying to get away from my natal family anyways.
Things can cost less in other countries. I get a small fraction of the average US developer but have a pretty good life and we're raising our children on a single income.
I feel like a lot of the people who are into salary transparency stuff are not high earners. I would like to see some game-theoretic analysis of salary disclosure dynamics from someone who is on the right tail of the distribution; my suspicion is that salary disclosure is bad for the rightmost X% of the distribution, where X is somewhere in the 10-50 range, depending on things like:
* What is the scope of the distribution? Industry, company, friend group?
* What are the social dynamics of their company/industry like?
* Is there a partitioning mechanism that reduces the stress of having a wide range of salaries for the same conceptual job type?
People's pay and financial details is something I'm happy to not know. Once you know, you cannot "unknow". That knowledge would leak into my perception of neighbors and friends. It would also change their perception of me. Regardless of the number. It's human nature.
This information is easy to back into using public information like house purchase price and car price. Even occupation/employer is usually enough to get upper and lower bounds.
I'm happy for you to live in a culture with little envy. Personally, I'm yet to experience such a culture and am myself a long way from being free from this human emotion.
Note that my original comment didn't mention envy. I merely stated that peoples behavior changes in subtle ways around those with more or less means than them.
Anecdotally, I felt all SWE were happy to discuss details of offers during internships and within the first 3-4 years of industry. Now many years later, it seems only my closest friends talk about this freely
Can't speak for others but for me it's embarrassing how much money we make to twiddle around in a command line and text editor. In a lot of places it's rude to flaunt wealth among polite company.
Things I worry about, as someone who's (I think) very/moderately/somewhat far to the right for my industry/sub-industry/company:
* Coming across as bragging
* Having people who earn less than me be jealous/envious/resentful
* Making it harder for employers to justify my salary because people will be publicly envious about it and cause a stink. This could be anything from coworkers/candidates/random people saying "well why are you paying Knaek $X and not me?" (I have experienced people harassing my employers for lesser reasons) all the way to people seeing my industry as a political outlet for their envy
* It's leaking strategically valuable information, probably more valuable than the info I would get in return (plus no solution to free rider problem)
* It might help less aggressive people negotiate a larger slice of a finite salary budget, which has a negative impact on me
While I agree with most of your points, this one I can't get behind:
> It might help less aggressive people negotiate a larger slice of a finite salary budget, which has a negative impact on me
While it might indeed have a negative impact on you, if they deserve a higher salary, I'd personally feel bad for them too. I am fully aware that salary is highly related to negotiation skills (which is why job hobbing is so popular: you can at least always honestly say "my current salary is X, I'll only switch for more" — even if you are bad at negotiating), but that's the thing that's unfair.
So I like to consider those openly sharing their salaries as in service of those who do proper work and none of the shitty stuff you bring up, but simply can't negotiate their salaries properly.
Whether that's worth it is another matter altogether.
In my experience it's always coworkers on the lower end of the bell curve getting pissy. Nobody likes to be told he's just worth less.
And tbh I don't like salary transparency because it usually tightens the range of comp for a position. I've always been on the right side of the curve (getting promoted faster etc) so that would suck for me.
> And tbh I don't like salary transparency because it usually tightens the range of comp for a position.
Well yes, that's kind of the point. It's supposed to be a good thing, since the theory is that salary variance is caused by unseemly factors rather than simple skill variance.
I've had people sabotage me in a company I was working in as a contractor on $2,500 per day.
The most bizarre one was a very formal review where I was told I needed to stop taking long lunches and be at my desk. I asked where in my contract it said I had to work at a desk rather than a picnic table. They couldn't point it out. In the end they terminated me four weeks before the end of my year long contract and had to pay out 6 weeks of severance.
I've had to deal with very bizarre behavior like this a few times in my career. It's been shocking to me to learn how vindictive, petty, or simply mentally unstable some people are.
I once had a coworker concoct a story about me and report it to management because I interrupted him during a yoga session in the office gym...
Anyway, the less people like that know about the details of my employment, the better.
> The JSON format is not stable. Do not treat it as such. I reserve the right to change the formatting or semantics of the JSON format at any time without warning.
I find this snippet mildly hilarious. As though it's a realistic risk that someone is going to be building an app or API dependent on this guy's blog post, and then might take legal action.
Why is this considered a red flag? Honest question. Ignoring exchange rates, this person is making about double the median income of Massachusetts, which already is one of the higher paying states. Is it really a red flag if someone is still going to pay you $150,000/year?
I wonder what effect this would have if non-tech workers did the same. Going back to Massachusetts (guess where I live), a recent law prohibits employers from asking about your previous salary, presumably so they can't then low ball you based off that.
Hiring people takes a lot of work. You have to recruit and interview a large number of people, interview them until you've settled on the best candidate for the job, get them to accept an offer, and then send polite rejection letters to everyone else.
If the candidate you hire then quits within a few months, you have to start the process all over again. Even worse, you've also lost several months of progress that you were hoping to make on this project with the new hire, as well as another month while you try to re-fill the position. On top of that, you already rejected your 2nd and 3rd choice candidates, who probably have taken other jobs already or are otherwise not interested.
Beyond that, a pattern of short jobs with large gaps in between can be a warning sign of behavioral or personal issues that make the person difficult to work with. This shouldn't be assumed from a few short jobs on a resume, but if someone has 9 different back-to-back jobs of less than 12 months each, the interview process should do a very deep investigation into why those jobs didn't last very long so you can decide if your company will stand a better chance at retaining this employee than the last jobs.
> If the candidate you hire then quits within a few months, you have to start the process all over again.
That's a good callout for the positions with very short tenure. If you can tell in <30 days that it's not going to work out, there's a good chance that the company will be able to cut their losses and call back some of the other applicants, short-circuiting the hiring process and saving everyone involved both money and time. It could totally be positioned as considering the employer's interests.
It's a simple case of trend spotting - multiple terminations and the only common factor is the candidate. Either they've just happened to have picked a whole bunch of bad employers, or there is some complication/issue with the candidate themselves that is severe enough that it's caused multiple terminations. As a hiring manager you won't know until you hire them, and if they turn out to be unsuitable (as the data would suggest) then you're back to square one looking for a new candidate so you're taking a real gamble when you hire someone with a resume full of terminations and short stays.
In a busy job market like we've had the last couple of years (and arguably before that in a lot of places) you can get away with having a resume like this and use job hopping to boost your income. But IMO long term this gets harder and harder to explain especially if the trend continues especially outside of junior or non-senior/staff type roles.
Salary data is the least interesting part of this...
You have been fired 3 times, quit 4 times, demoted once, and twice had contract not renewed. At what point do you conclude that maybe your problem isn't "pay discrimination", but that you've personally had some negative impact in the outcome of your career salaries?
Maybe trusting OP's lived experience is the best path here. This is the kind of thing that someone is only going to conclude for themselves. So I don't think you're doing anyone any favors by saying/asking something like this.
Never trust anyone's lived experience, ever. Everybody lies, especially to themselves. Everyone's opinion of their own life is a lie they tell themselves to sleep at night. No one is the bad guy of their own experience.
This is great! A huge reason why we built Levels.fyi was because of how much this information is kept in the dark. We’re on a mission to bring these hidden pockets of data out into commons for everyone to benefit. For those of you who want to help, but don’t necessarily want to publish under your full identity for whatever reason, you can pseudonymously share your compensation here: https://levels.fyi/salaries/add
We recently released the anonymization toggle and it allows for your entry to automatically hide details such as the company, level, or exact years of experience until we have enough data points to make it safe to show.
First off, I love levels, have contributed my salary to it, and thank you for building such a useful site.
With that said, I'm very hesitant to share my compensation or financial information personally. Like many in technology I'm very well compensated but perhaps unlike many I grew up poor and many if not most of my social acquaintances have far less money, then I do.
It's not that my friends and family probably don't know this intellectually, like I'm sure if you asked them, they'd probably tell you that was the case, but I'd imagine if you quizzed them on how much I make per year they'd guess $90k, maybe $100k.
I worry that tying my actual compensation to my name publicly would lead to all sorts of awkward at best and relationship ending at worst interactions.
I've always felt fairly compensated for my work and I can't say I really have a desire to know what my peers make. Isn't there a quote about jealousy being the thief of joy?
With that said, I do think there's tremendous value in aggregated anonymous salary data like Levels provides. I think that it helps identify systemic biases and as a hiring manager frankly helps me calibrate to how the market overall is valuing talent. So again, thank you so much for the tool. I like it a lot better than the way OP shared their information.
> Oops, if you could make a quick PR to fix that it'd be great!
You might get some seemingly strange or flippant reactions to this, and since you wrote it, I figured you might benefit from some insight into why some people might react negatively.
GP pointed out a tiny bug in good faith. Your reply asking them to fix the bug they found in your code comes across (to me, I'm sure not everyone sees it this way!) as a little presumptuous or entitled, I think because there's no expectation in this context that GP was signing up to "do work" (check out the repo, make a change, submit a PR to you) for your project.
A less... feather-ruffling response might have thanked GP for the bug report and maybe also mentioned the repo link in case GP or anyone would like to contribute, vs. straight-up asking GP to do the work.
Maybe someone else can weigh in with more detail. Or disagree vehemently with the vibes I'm trying to illuminate :)
I think it's cool when websites are editable. If I found a typo on a site, I'd enjoy the overall experience of fixing it myself more than asking it to be fixed. I realize not everybody is the same.
Not sure how the original message was phrased, but if it was anything along the lines of: “If it bothers you, you can also submit a PR here” then I don’t see the issue.
I vouched for this comment because even though it's phrased kinda aggressively, it's also not wrong. Best case scenario it shows a profound lack of social awareness and competence in interpersonal dynamics. Probably something for him to work on.
I don't like non-standard titles. Some of them are cute, but I don't put them on the resume. I will map them to something else. I once had a company hire me into a Senior Software Engineer role but they gave me the title "Software Specialist". I have no idea what that is. It sounds like I'm working behind a counter at an Egghead Software.
I just used "Senior Software Engineer" on my resume for that role. I got nervous once when I got this total RotoRooter colonoscopy of a background check for an offer I accepted, but it didn't raise any flags.
I also legally can't call myself an "engineer" where I live unless I get a degree that says I'm an engineer. My official title is something boring like "Software Designer". I don't like that title, it makes me sound less capable than I actually am. I originally came up with "Archmage of Infrastructure" with the idea to change it every time I was asked but it stuck.
Code Butcher might be a nice title for a test engineer, think your codes bug free wait until the Code Butcher gets a hold of it, then you get an axe shaped keyboard, which no one sees because you’re remote
omg that is the new thing, custom keyboards have saturated market with keycap variations and standard body designs... but now they need to start engineering out novel body types like an axe cleaver haha
I can see why salary transparency might help even out the differences for employees of the same type. But I can also see potential downsides for permanent vs. contractors for instance.
As a freelancer I might gain something by knowing the going rate of others with the same experience. But I am not sure that me publishing my hourly rate would benefit my relationship with the permanent employees of the place I am working.
- Shows which companies really treat their employees well
- Might reduce discrimination (but only in salaries)
- You can brag about it
Cons:
- Salary is one of the only measurable element about a job, so you could be able to easily compare salaries, but not compare ethics, how relevant the job is to you, if the company is committed to protecting the environment, etc., so it might pile up on the unhealthy pursuit of more money that's already terrible for the environment and many other things
- Salaries depend on many things, skill is very hard to measure, so YMMV
- Salaries depend on company budget, not only on candidate skills
- Beyond a certain point, chasing even more money often indirectly leads to depression, and unethical company practices
- People online are extremely judgemental, if you have a high salary, they will bombard you with questions about your lifestyle and if you donate to charity. Even if you do, they'll continue because your choice of charities is not the same as them. Because you made a little commitment to be transparent, you'll feel that you have to answer because not doing so would not be transparent, and eventually they'll delve into personal stuff that's really unconfortable, and your lack of answer will tell them what they wished to know, and that you might have wanted them not to know
There may be all kinds of biases, but in my experience, when salary transparency is available, it's always in tech, and always top 10/20% salaries. The missing data points will paint unrealistic expectations for tech roles, and reinforce imposter syndrome, IMHO.
So it's fine if you do it, but I won't do the same, and I hope nobody pressures me to do it (peer pressure could happen if a significant portion of people did it).
Like with all things I'd keep the numbers you see from others in context.
A lot of companies do a thing I like to call "geopay". In its most cynical view, it subsidizes home prices in a given area, which adds to the employees net worth more than someone from an area where cost of living is low if both own homes. In its most optimistic view, it allows for income equalization in the short-term.
Most companies these days do less "geopay" and more "how much are my direct competitors for talent paying", which is even worse. That said, I don't use these numbers to job hop. Instead, I use them to remind my employer that geopay isn't ethical even if they refuse to listen.
I’m also based in Canada and my base salary at the last place I worked (medium-sized kinda-well-known cloud company) was 185k. I haven’t been in the industry nearly as long as you - I suggest you ask for a raise!
The company was a bad fit for me. I only really got that job so I could work with Foone. They said I would be doing product development but ended up maintaining Python 2 code. I left as soon as I could find an alternate employer. It being the year that the 45th president of the US was elected didn't help either. That whole year was a wash for me and I only list that stuff here because I use this data to help me write immigration forms.
>I only really got that job so I could work with Foone
That's very honest of you. I know you didn't ask but taking a job just to work with a microcelebrity seems a bit short-sighted, was it worth it in the end?
I wonder if learning from him/her was your plan, did you learn something?
I did learn from them (Foone prefers they/them pronouns). I kinda miss the chaotic energy Foone brought to the equation. Standups were fun. But I did also learn that it's okay to throw in the towel early if things aren't working out. It was a better work environment for me than I had at the prior job, but the job just wasn't for me.
This is a dressed up way of saying “buck up,” which is neither helpful nor polite. The GP is clearly intelligent; it’s safe to assume that they might have reasons other than mislaid priorities.
This is the dumbest idea ever. Putting it anonymous like glass door makes sense, everyone benefits knowing compensation levels for job levels.
But for personal?
"Never talk about how much money you make, you either make more or less than them. Either way it makes for a very awkward conversation".
Look at what happens to lottery winners, the ones who go public.
> But for personal? "Never talk about how much money you make, you either make more or less than them. Either way it makes for a very awkward conversation".
It's true, but also in large part cultural. Culture changes, though. We should discuss transparency's merits. What are the potential downsides versus benefits of having a more open salary approach?
I found that for freelancing, having an open-price policy is beneficial. For example, it filters out low-paying clients. And by providing this information to your competition, you also level up the entire field. Competition works better with a certain level of solidarity and fairness within a given field.
Not to be too cynical but: California passes a new law that prohibits employers from seeking salary history information about an applicant "personally or through an agent." ... and now there is a high profile HN thread urging people to publish it on their own.
Nice and thanks for sharing! I recently listened to the "SE Radio Podcast - Episode 531" where you talked about tailscale. I've subscribed to your blog and now I see you again on HN :D
This is not something that should be bold. This is something that everyone at every level should do unconditionally so that people can have fair discussions about pay.
No, I think there are solid reasons for not doing so. And regardless of that it’s private info that people should always feel free to not share. “Unconditionally” in your post is a big problem.
It sometimes comes up in these sorts of discussions that some places make people's tax returns "public" as in anyone can get them if they ask and have it made public that they asked. I don't know if I'd call that good or bad, but it's at least interesting.
My coworkers know it exists. I've previously had it on a blogpost that I updated, but after I had a discussion with someone (I forget who, may have been in a group?) I just decided to make it a more prominent thing. This page has had absolutely no impact on my career.
This observation seems unwarranted (and a little unkind). For a voluntary personal project - not to mention one that involves a bit of personal risk/discomfort - they can publish the data in whatever format they please and revise it at will.
Usefulness of the API aside, the tone of it is full of red flags. Combined with all the other red flags, I can't help but to read it like this:
"You should be grateful I ever bothered to make an API, if it changes that is your problem. I can't bother to make this API stable or version it, this data is so valuable I assume you will make changes on your end if you hope to integrate with it."
I only say that because I may change this schema in the future. If API stability is important to you then I can be persuaded to believe so if you pay me to maintain the stability. Not wanting to commit to a data model is not a sign of weakness, it is a sign that I am not omniscient and can and will make mistakes. This data model isn't as critical to me as things like the schema for RSS/JSON feeds. Not everything needs to be maintained to mission critical standpoints.
Frankly I'd vote to make the tax records of every single person public domain information. Would do a hell of a lot to combat fraud and discrimination.
Yeah ok, I wasn't complaining about that stuff. Literally he could have just ignored it or fixed it (the actions people normally take) and nobody would have cared either way.
Equifax selling your data: https://news.ycombinator.com/item?id=29834753
Here you can see the salary portion of compensation for H1B workers: https://h1bdata.info/
The less salary information we have, the more our ignorance can be abused.