That's why people do it, no doubt. Keep in mind, a lot of these questions are asked by vastly less desirable companies that ape the hiring practices of FAANG, even though they pay much less. And these companies complain bitterly about a shortage of good developers to hire.

So... I'm all onboard with your statement, but I think you only said half of it. Nobody owes me a job, and if I don't like it, I'm free to not get hired. Nobody owes a company an employee either, and if candidates don't don't like it, the company is free to not hire. Zero sympathy for companies that do this and complain about a shortage of candidates.

> a lot of these questions are asked by vastly less desirable companies that ape the hiring practices of FAANG, even though they pay much less

I was asked to do a coding exercise for a tiny ($2500 if memory is correct) freelance project.

Do only those companies complain about a shortage of candidates? Because in the tech centers I know, the market is just empty. Lots of large companies are competing for talent, and if you can't pay bank salaries, you're going to have a hard time.

You make it sound like there's plenty of talent around but companies are being snobbish. That's not my experience at all in Germany.

In San Francisco, there's plenty of tech talent available at 500k a year. There's remarkably little available at minimum wage, though.

Complaining to congress that there is a shortage of IT talent is so common in American politics that it has become its own unique form of performance art. For instance, during the magic section of the act, companies make a labor shortage magically appear without any mention of wages, while also magically making the laws of supply and demand disappear.

“Shortage” is an economic term of art, so I won’t use it here. But it’s likely true that there is lot of valuable, economic-growth-producing work that could be profitable if a software engineer costs $100k/year instead of $500k/year. Businesses that lie on the margin of profitability are likely to feel that it’s hard to find good talent. Of course, it’s bad for us existing software engineers if the supply increases and the price goes down. It’s likely good for society overall though, if it enables a bunch of other businesses to exist. This is true in the same way that more trucks, more warehouses, and more conveyor belts would increase economic output, even if they were already available for the right price.

You just said that there's lots of valuable work that could be done, but your example of work that could be done is work isn't valuable enough to do unless software engineers get paid (in the SF Bay Area) notably less than a dental hygienist.

I like having clean teeth. If someone can make more as a dental hygienist, why on earth would it be valuable to society if they instead worked as a software engineer for less money?

If people won't work for 100k/yr as a software engineer, that means people capable of doing this work have found higher value things to do elsewhere. The higher salary elsewhere reflects the higher value produced doing something else.

This is one of many reasons why I'm so bewildered when people talk about a "shortage" of software engineers without considering the options available in other fields (fields that, perhaps, pay better and don't require taking bizarro whiteboard exams every time you change jobs).

I'd say there is a shortage of software engineers as long as most stem grads can easily raise their salary significantly by doing a few months at a coding bootcamp. That is still true, so there is a shortage of software engineers. I multiplied my salary that way, although I learned it on my own instead of a bootcamp but it is the same idea.

I didn’t say anything about the SF Bay Area.

That makes no sense. A voluntary pay reduction is like a subsidy leading to market distortion (more supply than the market can bear) and windfall gains (employers might just keep the extra profits) - only that this subsidy is coming from your and my paycheck lol.

The idea is an employer-side argument to counter the labour-side demand for higher wages: Don't have the wages to high, otherwise we go bankrupt and can't employ you any longer.

But programmers are already well employed, and software companies aren't really suffering. Cheaper programmers won't make website less bloated, won't make us figure out what to do with GPT-3, won't find a useful application for blockchains, won't make Windows 10 less moronic, won't make ad-tech less harmful, won't make the tech recruiters and the non-technical folk around software projects more competent...it would simply kill one of the few fields of employments that still pay well!

Look at construction. Did cheap immigrant labour make rents feel low in many areas? No, market forces drive up prices and owners keep the profit.

I didn’t say anything about a voluntary reduction in pay. Any reduction in pay would be a result of market forces in response to increased supply.

> Look at construction. Did cheap immigrant labour make rents feel low in many areas? No, market forces drive up prices and owners keep the profit.

In areas that aren’t constrained by density limits, homes are actually very cheap. In terms of square footage of home per population, the US is doing great. Problems are with inequality, in terms of geography and wealth.

Market forces should have already brought in more people into software if they really are that high, bringing down the salaries. What other measure would you suggest? Importing supply from abroad? Whatever it is, it would lead to a reduction in pay, which you suprisingly support - that amounts to walking into your boss' office and asking for a pay reduction.

> In areas that aren’t constrained by density limits, homes are actually very cheap.

That's the point. The effect of cheap construction labor only affects the rent prices in some areas, in other areas owners pocket the extra profit - while making construction jobs largely untenable except for immigrants coming from poverty.

I suspect something similar could play out in the software field.

> Whatever it is, it would lead to a reduction in pay, which you suprisingly support - that amounts to walking into your boss' office and asking for a pay reduction.

I just think it’s useful to try to understand the effects of policies not just on me, but on society at large. For example, I might observe that a tax increase hurts me personally but helps others. Are you saying that instead I ought to come up with reasons why the policies that are bad for me are also bad for everyone else, to better lobby for myself, or perhaps so I feel less cognitive dissonance?

> That's the point. The effect of cheap construction labor only affects the rent prices in some areas, in other areas owners pocket the extra profit - while making construction jobs largely untenable except for immigrants coming from poverty. > I suspect something similar could play out in the software field.

So in a region where home supply is constrained by density restrictions, there’s surplus extracted via high rents, and some of that surplus could go to construction workers (and they ought to fight to get a good wage so the developers don’t get all the surplus). Great for the construction workers, but bad for renters. In the analogy, software engineers are the construction workers and everyone else is the renters. Given the high market value of my wages, I will negotiate hard to get my share. At the same time, I can acknowledge that there would be benefits to society if there were more people qualified to write software, even though it would lower my personal wealth.

Currently there seems to be no mechanism increasing construction workers' wages or lowering rent. The extra profits are kept, and society isn't better for it (if it were, I'd be all for it like you). The reasons for this are fundamental, partly explained in an economics class, partly the result of imperfect markets and practicalities (a rich landlord might not immediately go out and build new real estate that would lower rents overall, he'd just sit on his boat).

My final point therefore is, let's keep IT salaries high for now.

In areas absent density restrictions, the US is indeed great at building tons of housing, developers don’t make huge profit margins, and rents are low. Is your argument that society would be better off if there were less construction workers, so housing costs would go up, allowing each remaining worker to be paid more and less total homes to be built? My opinion is that the higher wages for construction workers are nice, but they don’t nearly make up for the undersupply housing (we see both of these phenomenon in the Bay Area - higher wages for construction workers, who still can’t afford a home themselves).

You argued that software isn’t good for the world, so society wouldn’t benefit from more of it. This is a perspective I don’t usually get (especially here on HN) and I’m interested in hearing more. My belief is that software is part of a centuries-long trend of technology/productivity advances that have brought billions of people out of poverty, the continuance of which is necessary (although not sufficient) for a post-scarcity utopian future. I don’t know if we will ever invent a replicator, but I think more software engineers increase the odds!

Currently in NY making 150k with 10yoe at a non-tech company. Would jump ship in a heartbeat to SF for 300k, or 250k, or even 200k.

This legendary meme that everyone in SF is making 300k and drives a Ferrari has taken on a life of its own, and now we even have people outside of the Bay Area believing and repeating it. This is an outlier compensation for senior people at outlier companies. Anyone would jump ship for it, but it's not like hundreds of companies are handing out these salaries at the airport when you land.

Is it? Not sure about 300k, but 200k seems within the realm of realism. I've interviewed at a few Bay Area companies (I'd say they are "mid tier", not FAANG or top tier) and expected comp ranged around 200-250k.

That said, I was actually surprised at the lack of expensive cars driven by SFBA techies. I interviewed at Netflix, which I know pays astoundingly well, and the parking lot had a distinct lack of luxury brand cars. The exception seemed to be Teslas - I did see a bunch of Model S's and X's (Model 3 had not come out yet at the time).

Compare that to many East Coast suburban office campuses of non-tech companies that pay pretty poorly - you still see tons of mid to high end BMWs, Benzes, etc.

> Lots of large companies are competing for talent, and if you can't pay bank salaries, you're going to have a hard time.

Sounds like Economics 101. The curves of supply and demand meet at some point. Some customers can't buy (enough of) the thing because the price at the intersection of the curves is too high for them. Yes, that's how free market works.

There are things I can't buy, because they are too expensive for me. Or I could buy them, but I would have to sacrifice something else I need more. This is considered normal. When some company can't afford (people like) me, it's the same thing.

They would like to have cheaper developers. Sure, who wouldn't? There are also things I would like to have cheaper. Same problem. Why am I not entitled to get things as cheaply as I want, but my potential employer would be?

In my experience many companies prefer to whine about the shortage of talent, even if they could easily hire another person by increasing the offered salary by 50%. But they won't. Then they make millions of profit, which shows that the money was there, it was just their decision not to spend it on salaries. Okay, fair, it's their money, their decision. But if it's your decision, own it, don't pretend there wasn't an alternative.

Make it known that you offer double of the market salary, and you will be surprised how many people are out there in the "empty market". At least I never heard about a company that offered lots of money and couldn't find a person for the job.

That's all well and good, but that's not the point I was trying to make. Companies aren't having a hard time finding talent because developers are so annoyed by coding interviews, they're having a hard time finding talent because they can't/don't want to pay high salaries.

So developers go to work on finance and ad-tech, and not on normal, boring, only-making-three-times-the-national-average-salary stuff. And those companies then complain that they can't find developers. Because whether they have a coding challenge or not, they can't find developers because money.

I disagree with this, somewhat. Adam Smith, in Wealth of Nations, reminds us that there are a lot of factors that go into determining the desirability of a certain job, and that wages reflect this. The butcher earns more than the baker, Smith reasons, in part because most people would prefer the work of the baker. You have to pay someone enough more to convince them to be a butcher.

There are a lot of jobs that pay less than software engineer, but would be more desirable provided the pay isn't too much less. For example, someone might prefer to be a dental hygienist, figuring that the work is flexible, steady, and there's less of a possibility of age discrimination later in life. This person would become a software engineer for twice the dental hygienist salary, but not for 10% more.

In a free market society, it's not up to us to make that decision. If you want to get software engineers for in San Francisco for 10% more than a dental hygienist's salary, and you can't get any, that's the market's answer.

Corporate capitalists have discovered that if you don't like the market's answer, have the government ask for you.

> The butcher earns more than the baker, Smith reasons, in part because most people would prefer the work of the baker. You have to pay someone enough more to convince them to be a butcher.

And the surveillance capitalism developer earns more than the entire village. Ergo the market commands us to all develop surveillance stuff so Saudi Arabia can spy on dissidents and then chop them up in their embassies.

But again, that's not the point I was making, it's weird that multiple people understand my comments as "we should remove the free market". Me saying that it's the market that is making it hard for normal companies to find talent is only the background for what I'm actually trying to get across: It's not the coding challenge that is making it hard to find developers.

A company that isn't in a hyper-profitable space like ad-tech or surveillance (watching employees during WFH is booming) or fintech (figuring out new ways to make people part with their money) won't be able to attract talent by removing a coding challenge. It's just not an important factor in the equation.

I will engage with your claim that coding tests aren't making it hard to find developers. I think it is a more important factor than you do.

On a personal level, coding tests are a deterrent for me in applying for new jobs. I have my old copy of data structures and algorithms, and I've gone through "Cracking the Coding Interview." I actually enjoyed it at first. They're interesting and challenging problems. If there were an exam - maybe something similar to the actuarial calculus or probability exams - I'd probably be interested in studying hard for it and passing it.

However, I'm no longer interested in re-loading this information into short term memory in order to take a whiteboard exam. This may be a facet of how my own brain works vs others. I just don't walk around prepared to figure out which elements of a set, when combined after permutation, are equal to an existing member of the set. Or how to find all square sub-matrices with a positive determinant in a larger matrix. I can do these things - I've enjoyed doing them - but for me, it takes a lot of training and prep to re-load it in a way that I'm ready for the 45 minute whiteboard exercise. If it were a proper, lasting exam, I'd be happy to do it, but it's just too random, uncertain, and capriciously scored for me to want to do it anymore. I will note that some people don't have thae same trouble I have with this, and - I really mean this - this may actually indicate that they are better candidates than I am. In short, I need to acknowledge that I may certainly not be the "talent" that anyone is missing out on.

Money makes a difference too, but the reason I brought up Wealth of Nations is to draw your attention to the section "Of Wages and Profit in the different Employments of Labour and Stock" http://geolib.com/smith.adam/won1-10.html

I would recommend the entire article, as Smith breaks down the various factors that can lead to higher or lower wages, but you don't really need to read the whole thing, here's smith's summary:

"THE five following are the principal circumstances which, so far as I have been able to observe, make up for a small pecuniary gain in some employments, and counterbalance a great one in others: first, the agreeableness or disagreeableness of the employments themselves; secondly, the easiness and cheapness, or the difficulty and expense of learning them; thirdly, the constancy or inconstancy of employment in them; fourthly, the small or great trust which must be reposed in those who exercise them; and, fifthly, the probability or improbability of success in them."

Within this matrix, software engineering does have a lot to recommend it. For example, Law requires a very expensive and lengthy graduate degree, whereas software engineering doesn't, even though most successful SE's generally do have some kind of undergraduate, and often graduate, degree in rigorous fields that require a lot more math than law. How people will respond to this (along with other aspects of these two fields) depends a lot on their own personal wiring as well.

Within this matrix, yes, I do think that many people find in person, oral exams, at a whiteboard or at a computer under scrutiny and time pressure, on topics that they often don't know well in advance, evaluated by people whose credentials and skill they don't know in advance... yes, I think many people find that a deterrent, either for applying for new jobs, or entering the field in the first place. Many people consider these on-the-spot exams extremely stressful, especially when they are in person, at a whiteboard. And we go through days of it, and a new round of study, every time we apply for a jbo. Tech interview exams are not the only factor making it harder to attract candidates, but neither are any of the multiple factors identified and elaborated on by Smith. But I absolutely believe they are a factor.

And those small companies would be able to compensate the difference in pay with "partner" status, i.e. making an employee an unfireable stakeholder that can live off profits by the time he or she turns say 45, but owners of said small companies are too greedy for that. I'd argue that opportunistic at-employement with 500k/year at Big4 is worse than guaranteed 250k/year that nobody, not even the company's owners can take from you.

In my experience the talent shortage is a giant myth - there are two thing going on: companies that can't hire or won't pay, and companies that can, but wish it were cheaper.

Evey job I've applied or hired for either a) had lots of candidates with a very selective process, or b) telegraphed that you should avoid the company or didn't pay well enough (and often still got plenty of applicants who wanted their foot in the tech door despite not being capable).

My current company would claim there's a shortage, but they actually don't know how to hire and telegraph that you probably don't want to work there in a variety of ways.

What you describe isn't a shortage. It's an unwillingness to pay the going rate for the talent they want to hire.

All the more reason for candidates to not do the coding challenges. If you can't find candidates, don't add stupid ways to reject candidates.

As someone who had administered dozens of "objective" coding challenges to non-native english speakers... I can guarantee you your language skills will negatively impact your performance. So those tests aren't as objective as you think.

It comes up with questions that are as simple as "Create a function that deduplicates an array of integers"

> I can guarantee you your language skills will negatively impact your performance.

As it should.

If someone is a poor English speaker, at an English-speaking company, they absolutely should be penalized.

Not everyone is equal, was equal, nor will be. Some people are born blind too. Shouldn't we adjust our hiring practices for them too?

> Some people are born blind too. Shouldn't we adjust our hiring practices for them too?

Not only should we adjust our hiring practices for blind applicants, there's a legal obligation to make "reasonable adjustments" for these candidates under the Equality Act! *

* Laws may vary in less developed jurisdictions.

Well, it's more objective than asking a subjective question.

> 20k USD per month

As someone who's been in a FAANG for nearly 8 years and is making 2/5 of that...where the hell did you find that position!?

EDIT: oh wait. I was comparing my take-home salary. You're probably describing gross total comp? In which case - yeah, that makes sense. Good luck!

20k/month is only 240k a year. It's a take home TC for an average senior engineer in Bay Area.

Dude - you're not even making $180k/yr (gross) at FAANG and you've been there for 8 years?

What is your position...? I earn about $9k/month (net) at $170k/yr (gross) in CA as a software engineer. So, I'm already past the 2/5 mark and I'm just at a startup that doesn't even pay well! On top of that - you should be getting stock that translates directly into a good chunk of cash - not just a salary component. (Unless Netflix I guess)

Check out https://www.levels.fyi/

Check my edit! I was talking about my actual takehome salary (post-tax, not counting RSUs). Total gross comp is just north of $300k, which is pretty much in line with levels.fyi's average for that position (a little below - which tracks. I've only been promoted into that position just under a year ago, so I'm probably under-average across the whole population, despite being in the Bay Area so I'd hope to accelerate past that average soon).

I don't know of any software company that would hire an introverted person who can't articulate themselves for 20k a month. This is how micro-service architected fully optimized solutions that solve the wrong problem happen. Do you really think the high value of a developer just comes from being able to pass coding challenges when there's millions of them out there?

Eh, each of FAANG will do exactly that (as will other tech companies!). To be charitable to the parent commenter's point, they probably mean articulate in two senses:

1. Speaking perfect English, both fluently and without a heavy accent.

2. Talking about technical topics or other shibboleths with the same cultural affect an American would, as opposed to a foreigner. For example, many Indians will call a phone screen a "telephonic interview", and I've personally seen Americans react poorly to that.

I know lots of developers who are very well paid and very effective in their jobs, but they don't speak English as well as an American and would stumble at certain cultural nuances.

Thank you for being charitable. I speak English well enough to fare in FAANG as senior engineer.

But I always notice how a native English speaker almost always speak perfect English. They pick the right word to use and many other small things that make their English superb.

You seem to be confusing english speaking ability with the ability to communicate and articulate well. Communication is not about being able to speak english perfectly, it's firstly about listening and understanding the context of requirements. It's about being approachable enough so that the clients/stakeholders want to work with you, and clarify things with you, which in turn leads to a product which is close enough to something that they needed.

I don't think they're confusing anything; I thought their use of the word, "articulate" was pretty apt.

No worries :) You speak English well enough that I agree you shouldn't have any problems communicating in a technical discussion. Personally I find thick accents to be a bigger obstacle to communication than stumbles in grammar. But realistically most engineers will be professional and charitable enough to work around either issue as long as you're earnest.

That's only 240k probably not for a base salary but total comp sure.

It's a total comp. I'm not sure why we don't talk about TC especially when it's a public company.

Well, I have a bridge to sell you if you believe it's total comp.

That's perfectly in line with expectations for a new inexperienced hire at a FAANG. If anything, it's a little high for entry-level even at these companies. Obviously much higher numbers are attainable via career progression or already having such a job to negotiate from as leverage.

I've seen messy devs who absolutely can't articulate themselves, to the extent that when they tried, everybody else would keep awkward silence, and yet they made 60k/month.

What do those devs do to make 60k/month?

720k TC is hard to attain but possible.

Any decent engineer joining Facebook in 2012 and sticking there until now would earn 60k a month.

Isn't that because of the stock which just happened to appreciate that much, not because Facebook wants to pay them 60k / month?

Yes, that's correct.