I just spent 2 hours looking for a dataset on county-level median household income in the US. I want to compare it to the software engineer salary dataset I already have.
While that’s brewing, here are some facts I found, complete with sources and in no particular order. Not all facts agree with each other, and I don’t know why. ?
The median household income tells you what is considered “middle class” in a certain area. 67% of median to 200% of median falls into middle class. You can use this as a rough proxy for cost of living in an area.
“Cost of living” is not a defined thing. Most researchers build a composite index based on tens, sometimes hundreds, of indicators that feel right. Things like cost of groceries, rent, transportation, and stuff like that.
In this data set, the Composite Index is a measurement of the relative price of goods and services within an area. These prices include things like rent, healthcare, groceries, transportation, and more. Collectively, they are considered the “cost of living.”
All percentages are comparisons to the national average. The national average is represented by “100%,” so a city that has a 132% composite index is a city where goods and services (or the cost of living) are about 32% more than the national average.
Median household income does not follow a uniform random distribution. This implies network effects play a large role in how much you can earn.
Social class in the US has an interesting definition:
While many people in the US believe in a three-class system, sociologists disagree on their precise definition and acknowledge that class structure (particularly in the the “middle class") does not always match income distribution.
Why so much focus on those oh so very evil people at the top? The ones we hate vicariously through episodes of Mr. Robot?
Because the average software engineer makes $90,000/year, according to my dataset.
If you’re an average software engineer in the United States, and you have a salaried job, you are an upper middle class household. You, personally, as an individual.
I don’t know exactly what I’m making yet, but it smells like there’s a good story in here somewhere.
I write articles with real insight into the career and skills of a modern software engineer. "Raw and honest from the heart!" as one reader described them. Fueled by lessons learned over 20 years of building production code for side-projects, small businesses, and hyper growth startups. Both successful and not.
Subscribe below 👇
Join Swizec's Newsletter and get insightful emails 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.
"Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"
Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.
Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.
Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.
Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev
Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization
Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️