zuhayeer

Why'd this get removed from front page suddenly?

This is awesome! But I don't think you need to say never to all those display settings. You just need to go to Battery -> Options, and "Prevent automatic sleeping on power adapter when the display is off", and wake for network access when on power adapter.

Thanks for the feedback, would be nice to actually have aggregate stats right at the top perhaps too. So you can view a summary of the data.

It does seem off but it's directly from the Department of Labor data. The DOL LCA filings often have these misreportings where the hourly rate field is entered incorrectly, or an extra digit is added. Data cleanliness is still a huge issue, I'm realizing after working on this project.

Thinking about adding an outlier removal or flagging feature to get the obvious ones out.

Seems like this might be a data entry error in the DOL LCA filings. We are presenting the data as is, but can flag it to remove it. It does seem like a clear error, where it an extra digit was entered, or the hourly rate field was filled incorrectly.

And to clarify, this is a separate page, and separate data from the Levels.fyi total compensation data. I also doubt the US Department of Labor was reporting wages in Rupees lol, but it does seem like an error. Will take a look, and see if we can add some sort of outlier removal.

Thanks for pointing out the bug, will fix it to show the selected region once you get navigated to the docs.

For zip code, you can view the coverage we have via our explorer page here: https://borderly.dev/explorer

Curious about the customer, can you send some more info to me at zuhaz3@gmail.com

Great post! Sharing a similar sentiment, I built a fun tool to see how much meetings cost on Levels.fyi too: https://levels.fyi/cost/

Working on revamping our calculator page on Levels.fyi to make it more useful to see refreshers and stock growth over time. Check it out at https://levels.fyi/calculator/

This is how websites work

This is interesting since zip codes came up in consideration for how we built out our pay choropleth map in the US: https://levels.fyi/heatmap

Though ultimately it was far too granular (for example the Bay Area would be so many different zip codes). Instead we went with Nielsen's DMA (Designated Market Area) mappings within the US to abstract aggregated data a bit better. And of course this DMA dataset also had a different original use case. It was used for TV / media market surveys so it has some weird vestiges. Some regions are grouped very far and wide (you'll notice there's a bit of Denver within Nevada and its just a remnant of how it used to be categorized), but it still provides a bit of a broader level grouping than something acute like zip code.

I do like this map from the article though and the granularity you can get with zip code when zooming: https://clausa.app.carto.com/map/29fd0873-64cb-42a6-a90d-c83...

We've also been considering using Combined Statistical Areas using population instead. This is something that is under way, and in the interim we've considered charting styles that don't necessarily need borders (for example this bubble map: https://www.levels.fyi/bubble-plot/europe/). The benefit with DMAs is that it offers full border coverage of the entire US whereas some hubs can still be missing from CSAs if relying on a population threshold. But the plan is to create some of our own regional definitions and borders using our own submissions combined with population. Will be an interesting project.

GeoJSON data for the map borders: https://github.com/PublicaMundi/MappingAPI/blob/master/data/...

Nielsen DMA regions: https://blocks.roadtolarissa.com/simzou/6459889

Listen to it in podcast format here: https://notebooklm.google.com/notebook/3fba27cd-4baa-4343-9b...

View the PDF directly here: https://levels.fyi/assets/pdfs/research/w33383.pdf

We plan to work on city / region granularity and additional zoom levels. We just released this to gauge interest before going further.

The data is gross total compensation.

Love this, big fan of Glide. We've used Google Sheets for a long time to power Levels.fyi and allowed us to move fast without too much of a formal backend. Check out our post here: https://www.levels.fyi/blog/scaling-to-millions-with-google-...

Yeah that make sense, will work on adding for this heatmap

How do you think it should be treated? I think at the individual granular data point level adding a tag or note about the equity not being immediately liquid is a good start. But I don't think it'd be a good idea to weigh the stock differently since that can depend on so many things. For example SpaceX and some other private companies do offer regular liquidity and I would consider their equity close to liquid.

Appreciate the feedback though, and definitely agree we can work on how we display the data and make it more clear.

This is a great point, and something we plan to address. We currently use Nielsen's DMA (Designated Market Area) mappings within the US to separate out regional areas which was used for TV / media market surveys. We happen to use DMA categories for our regional pages on Levels.fyi which is why it was easiest to start with since we already had this data captured. The features can sometimes be a bit off and seem like they're grouped very far and wide (you'll notice there's a bit of Denver within Nevada and its just a vestige of how it used to be categorized), but it still provides a bit of a broader level grouping than something like zip code. We've also been considering using Combined Statistical Areas using population instead, but the benefit with DMAs is that it offers full coverage of the entire US whereas some major tech hubs are still missing from CSAs if relying solely on population.

We're planning to create some of our own regional definitions and borders using our own submissions and that should offer some more tighter bounds. This was just a v1, and I think its already resonating with folks.

GeoJSON data for the map borders: https://github.com/PublicaMundi/MappingAPI/blob/master/data/...

Nielsen DMA regions: https://blocks.roadtolarissa.com/simzou/6459889

I think that part is still a bit ambiguous, it's almost how people and companies self-identify the role. But that said, we collect a bit of a taxonomy for our role structure, and we specifically look at Software Engineers focused on AI. The responsibilities can still differ from company to company, but that's what we used for our dataset.

Congrats on the launch! Awesome to see this release as an early user who was able to check it out. The shared workspaces and shared browser windows with context in place has been incredible for collaborating with folks. We have our Figma design, Notion doc, and Gitlab MR all in the same space so we don't have to go searching for each one independently or have them cross-linked to each other.

The soundtrack actually goes so hard. Love it.

Another framing of this is whether companies treat their engineering organizations as a cost center or a profit center. Cost centers suppress salaries as much as possible optimizing the budget. There's little growth within these companies which is why the zero-sum philosophy is passed down to their compensation strategy. Whereas profit centers encourage more and more investment as compounding profits come in from previous dividends. Growth is what powers everything, higher pay has a positive-sum gravitational pull on talent sustaining a flywheel for more profits to come in (hopefully).

All the companies that pay very well such as on https://levels.fyi/2023/ are profit centers encouraging investment in talent, competing for the best across companies because they know its worth it. Each hire even at extremely competitive wages will make back their salary manyfold if they're successful.

Work email isn't required to sign up, you can skip it

Incredible to see Sam Altman in the acknowledgments for this article.

That’s fair, but 0 guardrails just entirely minimizes the incentive to create a custom GPT.

I was also thinking about when there’s paid access to certain GPTs. Someone can just download the files and spin up their own? Doesn’t seem valuable for devs. If that’s how the incentives were intended then sure. I just don’t expect many people to be enabling use cases with it.

Most companies still don’t necessarily list total compensation. For base salary though, these ranges are quite helpful and has definitely caused some “good” trouble increasing baseline wages among competing companies.

At higher levels it’s still ambiguous what ranges truly are since job postings can span multiple job levels (which is why some ranges can feel dubiously wide). Ended up writing a bit about this phenomenon here and what contributes to it: https://www.levels.fyi/blog/notes-on-california-transparency...

That's actually intentional, and one of the reasons why our site exists. Every company has different nomenclature for their leveling that doesn't necessarily align with other companies. So we developed a standard as a normalization for all the leveling which you can view here: https://levels.fyi/standard

As a part of this standard, ICB 6 falls under the 'Staff Engineer' standard level (you'll also notice it maps closer to Google and Facebook's Staff levels as well: https://www.levels.fyi/t/software-engineer?compare=Broadcom%...)

We had similar findings via our 2023 Mid-Year report on Levels.fyi: https://www.levels.fyi/blog/2023-mid-year-report.html

In particular, the median for software engineer compensation stayed the same (which is a slight decrease when adjusted for inflation), while roles such as software engineering management saw a 5% increase in overall pay. Specific areas such as Augmented Reality saw larger hikes in compensation. AI engineers have also seen elevated compensation compared to their other engineer counterparts, which we analyze on our post here: https://www.levels.fyi/blog/ai-engineer-compensation.html

We have quite comprehensive Google compensation information available on https://www.levels.fyi/companies/google/salaries/software-en...

You can even see the recency of each individual data point, and filter for specific levels. (Disclosure: I'm one the founders)

Knowledge is compression, and thus it can be infinite

We published the Levels.fyi 2023 mid-year compensation report earlier: https://www.levels.fyi/blog/2023-mid-year-report.html

While volume of hiring may have been lower overall so far this year, median compensation has generally remained steady or increased in the first half of 2023 relative to the last half of 2022 for most roles. In particular, the median for software engineer compensation stayed the same, while roles such as software engineering management saw a 5% increase in overall pay.

Augmented reality was quite in-demand so far in 2023. AI engineers have also seen elevated compensation compared to their engineer counterparts, which we analyze on our post here: https://www.levels.fyi/blog/ai-engineer-compensation.html