The market is still extremely tight for good talent in-between Senior and Junior.
So the Senior market is saturated? this is an early sign companies are getting nervous about bloat. After the '08 recession many companies rushed to ditch Architect titles as they found that the role did not serve the interests of their productive engineers or the companies higher ups. Companies that had gone heavy on such talent might find themselves stuck. I recall seeing talks on "Staff Engineer" and thinking that…
How much have tech layoffs affected engineers vs. other departments?
31–40 of 359 posts
Re: How much have tech layoffs affected engineers vs. other departments?
#32> At some point in the last 2.5 years, you’ve probably visited layoffs.fyi. I have?
Re: How much have tech layoffs affected engineers vs. other departments?
#33Earlier quoted context omitted.
Staff engineer is just title inflation for what used to be senior engineer. Senior engineers at most companies just means this isn’t your first job right out of college.
I have 15 yoe and have senior software engineer title so do people with 2 yrs experience. I might be doing same thing over and over. Time to make a radical change :/.
Re: How much have tech layoffs affected engineers vs. other departments?
#34Earlier quoted context omitted.
> So the Senior market is saturated? I am not sure I would say saturated, but yeah, the Sr. SWE market is definitely not as tight as it was a year ago for most role types. However, it does depend on qualifications and company type. Seniors for R&D positions (so, PhD with 5+ years in product-focused R&D) are still basically impossible to hire. Friends tell me that hiring seniors at mid-pay or low-pay companies is stil…
CS programs are overproducing but they are overproducing the wrong skills. Most don’t have the cloud skillset or experience with IaC, they are never thought how to solve problems within distributed systems. And their idea of systems design is a Flask app talking to a MySQL database on a laptop. It’s not the students fault, but the education system is constantly behind the times, and sometimes even teach bad engineeri…
Yes/no/maybe. The schools got pressured by the bootcamps that were teaching the "flask app talking to a mysql db" .. they simplified their classes and stop teaching some things. It sucks, the people who come out of that don't have the theory/flexiblity/skills coming out that you would expect before.
Re: How much have tech layoffs affected engineers vs. other departments?
#35Re: How much have tech layoffs affected engineers vs. other departments?
#36Re: How much have tech layoffs affected engineers vs. other departments?
#37Earlier quoted context omitted.
> I recall seeing talks on "Staff Engineer" and thinking that this was going to be the next version of "Architect". Engineers who's primary job is to write code often dislike working with people in such roles. That depends. If they are actively involved and the architectural decisions are sound, it's fine. If they are "drive-by architects", showing up, dropping a bunch of useless boxes they read on some book, and the…
Drive by architects don't read books. They read AWS's latest product brochure and think "yes".
The bad ones took what they read as gospel and the good ones took what they read in context.
Re: How much have tech layoffs affected engineers vs. other departments?
#38We (large FANGish) are more or less in a hiring freeze but still grabbing a few new hires here and there. A friend just interviewed for SSE at AAPL and seemed to have the job only to be told they closed the req. I'm still getting lots of recruiter spam though so I think we're still fairly early in any sort of layoff cycle. The economy is still trucking. Despite many people trying to be first to declare it, we're not…
Re: How much have tech layoffs affected engineers vs. other departments?
#39The market is still extremely tight for good talent in-between Senior and Junior.
So the Senior market is saturated? this is an early sign companies are getting nervous about bloat. After the '08 recession many companies rushed to ditch Architect titles as they found that the role did not serve the interests of their productive engineers or the companies higher ups. Companies that had gone heavy on such talent might find themselves stuck. I recall seeing talks on "Staff Engineer" and thinking that…
I've found those roles to be:
* Technical Leadership (driving major technical initiatives)
* Technical Contributor (shipping stuff, with technical mastery beyond what would normally be expected from senior engineer)
* Architect (planning stuff)
* Team Management (mentorship + taking load off an engineering manager's plate if the team is big)
Biggest mistake I see orgs make when hiring staff engineers is hiring someone whose strength is in mentorship and technical contributors and decide their new role is architecture and driving major technical initiatives at a high level. Some are best "in the weeds" and others are better planners. Know their strengths!