Skip to content(if available)orjump to list(if available)

The great displacement is already well underway?

shawnfrompdx

I am the author of this piece, and i didn't share it to HN, I don't hang out here. I just gotta say wow, tough crowd. i wrote this piece from an emotionally low point after another fruitless day of applying to jobs. I didn't have a particular agenda in mind. I was voicing what i've been through and some of what I was experiencing with no expectations.

you'll notice in the comments section that the population of substackistan is much less FUCKING CYNICAL AND NEGATIVE than you guys, with many commenters saying they are in the same position. I heard from writers, designers, engineers, going through similar times.

my portfolio site is https://shawnfromportland.com, you can find my resume there. if you have leads that you think I might match with you can definitely send them my way, I will even put a false last name on an updated resume for you guys.

for those who are wondering, I legally changed my name to K long ago because my dad's last name starts with K, but I didn't like identifying with his family name everywhere i went because he was not in my life and didnt contribute to shaping me. I thought hard about what other name I could choose but nothing resonated with me. I had already been using Shawn K for years before legally changing it and it was the only thing that felt right.

cjbohlman

I thought this piece really spoke to the landscape of software engineering in the present/future. Unfortunately discussions on this site are subject to a truly baffling mix of confirmation biases and messianic complexes.

Wishing you well and best of luck with your search.

jsbisviewtiful

> Unfortunately discussions on this site are subject to a truly baffling mix of confirmation biases and messianic complexes.

HN is about 2 years ahead of where reddit was before reddit really fell off - and at the current rate of HN's decay I wouldn't be super surprised if more posts start appearing here soon that are pro-fascism, pro-"masculinity" and anti-vaxx.

I was _really_ surprised to see my login has existed here for 15 years because coincidentally that's about the same timeline as when my first reddit username was created and when I started moving my surfing away from reddit due to the decay of my fav communities there.

Hoping HN can turn it around because it's a great grab bag of intriguing links.

bjclark

As someone with an 18 yr old account here, this site turned into engineering LARPing much farther back than 2 years ago.

dgfitz

Seems curious you only started commenting a few years ago. What changed?

hnthrow90348765

Any thread about hiring (here, reddit cscareerquestions, blind, whatever) is full of cunts waiting to put people down because they absolutely love telling people they aren't good enough for minor reasons despite proven records of competency.

They know that hiring is just as volatile as the rest of us. If any of their project requirements or job duties changed as much as hiring has, they'd think the company/PM were incompetent.

urbandw311er

Hey Shawn

Tough times. You’re doing everything right (except perhaps reading too many of the comments which is probably not great for your mental health) - your break will come. The night is darkest before the dawn and all that.

Peace & love.

mizzack

I thought most of these comments have actionable if not tough to hear advice.

Perhaps offering an opportunity for more humility and introspection. Instead you’re here doubling down on the victim mindset.

Wishing you the best.

shawnfrompdx

i have spent the last couple days responding to hundreds of comments on the substack piece. no new pieces of advice came up on this thread which were not already covered on the substack comments. advice which i have acknowledged. i was already about to do most of the pieces of advice anyways on my own as the next step, such as applying with a normie pseudonym. you don't know me. im not a victim and i don't have victim mindset. i am survivor.

dgfitz

I haven’t read most of the comments here and none on substack, but looking at your resume, I’d spend some time making it look slightly warmer, throw some color in there.

I’d also consider re-working your job history, it “looks like a lot of bouncing around” which shouldn’t be a bad thing, but it can be if framed poorly.

Finally, I’d spend a few weeks with c++/java and slap it on the resume as a competency. Can’t hurt, and you’re just learning some syntax at this point.

Best of luck to you. Market is tough, and there are a lot of sw folks looking around right now.

pseudosaid

ignore those addicted to negativity. for most people, their life is just reducing awareness to fit into their adlib structured arguments to assuage their insecurities. “Im so smart, i can ignore possibilities and unknowns and frame a thought construct that boosts my sense of ego and importance!”

Aurornis

> the population of substackistan is much less FUCKING CYNICAL AND NEGATIVE than you guys,

I took some time to offer some resume review tips here: https://news.ycombinator.com/item?id=43978225

This is a really difficult topic to address because it appears you're interesting in venting and commiseration, but it's mixed with pleas for job placement and opportunities. If you want some honest advice:

- Your resume still needs a lot of work. See my other comment with more details. After reading your Substack I see why you're keyword stuffing words like "Vibecoding" as your #1 skill, but I don't think you realize how much this is hurting you.

- I've read your resume and I clicked the link to go to your website. I still don't really understand what you specialize in or what kind of job you're trying to get. In a market like this one, you need to have a resume that tells a story of why you're a great fit for the job, not someone who has a couple years of experience 10 different times at 10 different things. There's a lot of vague claims about "award-winning state-of-the-art web experiences" but then you have everything from AI and Vibecoding to VR apps to teaching classes on your resume. Broad experience can be good, but I think you need to start writing different resumes tailored to different jobs because I can't make heads or tails of your career goals from the way it's all presented.

- I'd separate the Substack from your resume, personal website, and job search as much as possible. To be blunt, the tone is alarmingly cynical in ways that any hiring manager would want to keep away from their team. Phrases like "Generally, it’s the fresh-faced bay area 25 year old with a Steve Jobs complex" ooze a sort of anger with the world that people just do not want to bring into their company. Blaming everything on AI and "the great displacement" falls very flat for anyone who has just read your resume and seen "Vibecoding" as your top skill while trying to figure out what, exactly, you did at your past jobs.

- Consider sprucing up your portfolio a bit. It's a little jarring to read a resume about "award winning state of the art web experiences" and then encounter some centered yellow text on a black background in a quirky font that slowly fades into view. I would also recommend that you include screenshots of your specific work on each site and a short description of what you did for each. Random links and screenshots aren't helpful. Hiring managers aren't going to watch YouTube videos at this point of scanning your resume, either. Try to view your website like a hiring manager who wants to know what they're getting into. Seeing "21 years of experience" and then having the first large link on your website being a link to University of Oregon because that's where you got your degree doesn't make sense.

- To be more blunt: There are some major red flags that you need to clean up. Your portfolio links to the live nike.com/running website, but your resume says you last worked on a Nike website over a decade ago. This is the kind of thing I expect to see from fake applicants, not a real person. I would go so far as to suggest leaving your portfolio off of your resume until it can be cleaned up and modernized with specific information about your work. Use a template if you have to, but the site clashes with your headline claim of being an award winning web developer.

- Finally: Try to create a cohesive narrative in your resume and application process. If you're applying for full-stack web-dev jobs, your resume should show a career trajectory of starting with small websites and working up to more and more complex projects. Right now the top job entry lists "tens of thousands of MRR" as an achievement but a decade ago you were working on Nike.com. You need to find a way to tell the opposite story, that you've been working your way up. Unfortunately the substack article makes this even worse with talk of being a Doordasher now. It's okay to vent on Substack, but don't cross the streams with your application process.

shawnfrompdx

thank you for taking the time. If i was petty i could share the past 5 versions of my website and resume i created in the last year which precisely followed most of what you recommended here. I had a completely vanilla narrative resume by version 3, and was getting nowhere. analytics and my own vibe check was making me think that all of that was too verbose and it wasn't being read. I was feeling unseen and began retargeting things to create an impression in 2 seconds, enough to hopefully hook someone to want to talk to me to learn more. the latest strategy was to try to emphasize within 2 seconds the point that im all about ai coding, while having a conventional cs/agency background at the same time.

Because you have taken the time to review this stuff and make these same recommendations that everyone else has here, i am going to refactor the site and resume yet again according to these recommendations.

I would love it if my career arc had one through-line narrative that made sense, but I'm afraid it doesnt necessarily. I started as a data architect and backend developer for the first many years, never touching front-end. I had to expand to tackle front-end to meet the changing market demands. in later years, the distinction of what were primarily front end vs back end tasks or roles has become a lot more fuzzy, as things have turned into "all-js-all-ts-everything-everywhere!" I've adapted, and been working full stack ts roles.

I often feel my data architecture / problem-solving skills are overlooked when my last few roles show that i've been developing with a vue ecosystem, pigeonholing me as a front-end dev, something i have never identified with.

aembleton

It might be good to expand on your data architecture work more in your CV. Write a paragraph about the data architecture work you did at your last company. You could remove some of the older jobs to free up space.

muskyFelon

Not to be rude, but unless your portfolio site is nothing short of spectacular you shouldn't include one. In all likelihood, its doing you more harm than good.

Keep your head up. These are interesting times. Things will get back to normal at some point.

codr7

Well, for what it's worth, I recognize a lot of what you're going through.

I barely thought I was going to make it through this time, but finally somehow managed to at least land another SW job; we'll see how far that goes.

HN is to large extents a bunch of spoiled, transhumanist AI fanatics, don't let them get to you.

Initiated a connect on LN, but wasn't allowed to send a note since I'm not a premium member.

JohnMakin

I’m not trying to be unsympathetic in this comment so please do not read it that way, and I’m aware having spent most of my career in cloud infrastructure that I am usually in high demand regardless of market forces - but this just does not make sense to me. If I ever got to the point where i was even in high dozens of applications without any hits, I’d take a serious look at my approach. Trying the same thing hundreds of times without any movement feels insane to me. I believe accounts like this, because why make it up? as other commenters have noted there may be other factors at play.

I just wholly disagree with the conclusion that this is a common situation brought by AI. AI coding simply isnt there to start replacing people with 20 years of experience unless your experience is obsolete or irrelevant in today’s market.

I’m about 10 years into my career and I constantly have to learn new technology to stay relevant. I’d be really curious what this person has spent the majority of their career working on, because something tells me it’d provide insight to whatever is going on here.

again not trying to be dismissive, but even with my fairly unimpressive resume I can get at least 1st round calls fairly easily, and my colleagues that write actual software all report similar. companies definitely are being more picky, but if your issue is that you’re not even being contacted, I’d seriously question your approach. They kind of get at the problem a little by stating they “wont use a ton of AI buzzwords.” Like, ok? But you can also be smart about knowing how these screeners work and play the game a little. Or you can do doordash. personally I’d prefer the former to the latter.

Also find it odd that 20 years of experience hasnt led to a bunch of connections that would assist in a job search - my meager network has been where I’ve found most of my work so far.

bradgessler

It feels like we're in a phase where hiring is slow for a lot of reasons:

1. Lot's of great talent on the market. It's a great time to be owning a company right now in terms of hiring.

2. The reality and perception of AI making it possible to do "more with less". I can imagine conversations playing out today, "we need to hire more developers" with the rebuttal, "ok, what about AI? Let's see how far it will go without hiring more people"

3. Even without AI, software teams can do more with less because there's simply much better tooling and less investment is required to get software off the ground.

4. Interest rates and money is simply more expensive than it was 3-5 years ago, so projects need to show greater return for less money.

It does feel like the reality and perception of AI hasn't converged yet. There's a general sense of optimism that AI will solve a lot of huge problems, but we don't really know until it plays out. If you believe history rhymes, humans will figure out what AI does well and doesn't do so well. Once that's worked out, the gap between perception and reality will close and labor markets will tighten up around the new norm.

araes

> It does feel like the reality and perception of AI hasn't converged yet

I learned a word cruising Reddit the other day that summarizes that issue quite well - "liminal". At the time, it was in the context of malls, and the collapse of American storefront consumerism, yet the issues are similar:

  "relating to the transitional stage of a process", or "the quality of ambiguity or disorientation that occurs in the middle stage"
> general sense ..., but we don't really know ... the gap between perception and reality will close and labor markets will tighten up

We're stuck in that in-between land where your 2) seems like it's often the response to most suggestions. We'll, we don't really want to take a risk ... cause tomorrow AI may make that choice irrelevant. We don't really want to invest ... cause tomorrow AI may make our investment worthless. We don't really want to hire more people ... cause tomorrow AI may do their jobs easily. And there's always that number 3) sensation somewhere "your team can do more, you're just not leveraging tools enough".

noduerme

The impact of AI already goes further than just delaying hiring - at least in fields adjacent to engineering, such as technical writing. Anecdotally:

For the past 10 years, one of my best friends has been the senior copy editor for [Fortune 500 company's] sprawling website, managing more than a dozen writers. It's a great job, full time, mostly remote, with fantastic benefits (including unlimited PTO, a concept that I can't even fathom as a freelancer). The website comprises thousands of pages of product descriptions, use cases, and impenetrable technical jargon aimed at selling "solutions" to whatever Fortune 500 executives make those kinds of mammoth IT decisions.

Recently, he was telling me how AI was impacting his job. He said he and his writers started using GPT a couple years ago to speed things up.

"But now I have to use it. I wouldn't be able to work without it," he said, "because in the last year they laid off all but two of the writers. The workload's the same, but they put it all on me and the two who are left. Mostly just to clean up GPT's output."

I said, "I don't know who ever read that crap anyway. The companies you're selling to probably use GPT to summarize those pages for them, too." He agreed and said it was mostly now about getting AIs to write things for other AIs to read, and this required paying fewer and fewer employees.

So while AI may be a nice productivity booster, it's not like there's unlimited demand for more productivity. Companies only need so much work done. If your employees are made 4x more productive by a new tool, you can lay off 75% of them. And forget about hiring, because the tools are just getting better.

Coders like me don't want to believe this is coming for us, but I think it is. I'm lucky to have carved out a niche for myself where I actually own a lot of proprietary code and manage a lot of data-keeping that companies rely on, which effectively constitutes technical debt for them and which would be extremely onerous to transition away from even if they could get an AI to reverse engineer my software perfectly (which I think is still at least a few years off). But humans are going to be an ever-shrinking slice of the information workforce going forward, and staying ahead of those layoffs is not just a matter of knowing a lot about the latest AI tech or having a better resume. I think the smart play at this point is to prepare for more layoffs, consider what it would take to be the last person doing your entire team's job, and then wedge yourself into that position. Make sure you have the only knowledge of how the pipeline works, so it would be too expensive to get rid of you.

teeray

> I can imagine conversations playing out today, "we need to hire more developers" with the rebuttal, "ok, what about AI? Let's see how far it will go without hiring more people"

That is almost certainly happening. What needs to play out for the pendulum to swing the other way is all of these companies realizing that their codebase has become a bunch of AI-generated slop that nobody can work on effectively (including the AIs). Whether that plays out or not is an open question: how much slop can the AI generate before it falls over?

kagakuninja

I am 61, and have been working for almost 40 years. I don't really have a lot of personal connections, because I am on the autistic spectrum. Yes, I have many former co-workers linked on LinkedIn, but to most of those people, I'm just an old acquaintance, not someone they are going to phone up with a hot new job opportunity.

The exception is one college friend who did help me get multiple jobs at startups, but he retired several years ago.

Establishing and maintaining relationships is hard, and many of us are simply not good at it.

Now I did make sure to stay in touch with a couple ex-managers who I knew would be good references. One of them even helped me get an interview. But even when I had a connection on the inside of a company, all that really does is move me to the head of the line, past the HR screen. I still have to interview, something I still suck at despite decades of practice.

harmmonica

Pure speculation, but I wonder if it's not so much AI as tech companies realizing they actually can do more with less. And, again, I have no evidence to back this up other than "feels," but I swear when Elon bought Twitter and cut so much of the workforce that's when sentiment seemed to shift materially. I wonder if that wasn't a bit of an "aha" moment for mega tech and tech in general. It's like all the major companies said maybe we don't need as many people as we have. Of course people are going to debate whether the changes at Twitter had a monumentally-negative impact (they may very well have in terms of revenue, but I'm not so sure in terms of absolute or even relative profit).

Of course, as a sibling comment, I think, said it could be the end of ZIRP. But maybe the truth is it's end of ZIRP, seeing a "peer" shed employees en masse and not fail outright, and AI.

Twitter deal in 2022. Headcount by year for a few (not suggesting this data supports my theory; just sharing to reality check)...

https://www.macrotrends.net/stocks/charts/META/meta-platform... https://www.macrotrends.net/stocks/charts/GOOG/alphabet/numb... https://www.macrotrends.net/stocks/charts/AAPL/apple/number-... https://www.macrotrends.net/stocks/charts/MSFT/microsoft/num...

Edit: grammar

rurp

A huge amount of staffing cuts were to teams working on things like moderation or combating bots, which are areas Elon doesn't care about continuing development on. He's not so much doing more with less but rather doing less with less. We can debate about whether or not the projects he cut were worthwhile, but given the company's disastrous finances I wouldn't give him the benefit of the doubt.

The bull case is that he sacrificed Twitter capital in exchange for political capital, which I think is pretty sound. But that doesn't really apply to most CEOs running most businesses.

harmmonica

Good point. I shouldn't have said more with less. I should've said Twitter lost 80% of its employees and somehow still exists (I thought it was "only" 50%). 80% is nuts. That said, if 100% of those reductions were outside of engineering (they weren't, I realize) then I'd mostly agree with your point. But I do think that even in that case it would cause every other company to ask some hard questions about staffing that could lead to layoffs and/or have implications for hiring.

All feels on my part just to hopefully add to the dialogue. Nothing scientific here.

Aurornis

I'm sure some CEOs followed the Twitter lead, but I also think the entire industry was already shifting with regards to headcount. A lot of companies were hiring excessively going into that period and middle management bloat was a well-known phenomenon.

The overstaffing problem was painfully obvious at many of the companies I spoke too as a consultant during that time. They'd have bizarre situations where they'd have dozens of product managers, project managers, program managers, UX designers, and every other title but barely a handful of engineers. It was just a big gridlock of managers holding meetings all day.

One friend resigned from Twitter prior to anything Elon related, specifically citing the fact that it paid well but it was impossible to get anything done. Not all of Twitter was like this, but he was outside of engineering where he was one of scores of people with his same title all competing to work on tiny features for the site or app.

The pendulum seems to be swinging to the other direction, where companies are trying to do too much with too few people. I still see a lot of growing (or shrinking) pains where companies are cutting in the wrong places, like laying off engineers to the point of having more people with {product,project,program}-manager titles combined than engineers. I hope we settle out somewhere more reasonable soon.

harmmonica

This all rings true to me. I would take it a step further and say that during normal times throughout the history of corporate America, and especially in boom times, management will let fiefdoms grow fairly unchecked. Then an external trigger causes them to re-evaluate and that's when they're like "holy shit we don't need nearly this many people."

For those of us who have been around the block (i.e., are old), the only times I've personally seen companies aggressively cut personnel is during economic shocks (dotcom bubble and housing crisis as two examples) and only then were the companies running lean (I wouldn't even say they were running bare bones; it's the only time I've seen headcount actually optimized for the work being produced).

I think the Twitter purge was actually an example of a major trigger. Not on par with the previous two I mentioned (obviously), but it was so high profile that anyone in tech took note of it, which is why I made the original comment. I've never seen so much discussion around a layoff for a company that was not imminently imploding (some may say Twitter was about to implode, but if you said that at the time I think you were wrong regardless of the state of its financials).

keeda

Yes, that was the turning point. You have to remember, in addition to the end of ZIRP this also happened after a few years of an extremely strong employee's market. Jobseekers were asking for and getting some pretty wild packages.

Elon's actions were a clear signal to the industry and investors that it's time to "fight back" and show the labor market who's really in charge.

mattgreenrocks

It goes beyond Elon. PE was (are?) pressuring Google to lay off more employees because their pay was so high. And the Fed said that worker pay was "too high," in the context of inflation.

Basically, the ownership class was pissy that some people were able to actually get away from exchanging time for money.

sapphicsnail

Do people see Elon's takeover of Twitter as a success? I think he leveraged Twitter as a social media platform to make himself wealthy, but as far as I can tell, the actual company has been losing a ton of money.

harmmonica

I was trying to stay away from the debate about the success of it by making that comment about it not failing even with a fraction of the former employees. My sarcastic reply to your question, though, is it depends on which side of the aisle you sit on. More seriously, there is something extremely telling about a tech company cutting half or more of its workforce and still living. I can guarantee you every major tech company took note of that reality and so I have to believe it begged some questions about headcounts.

It brings you back to that old HN saw "why do these companies need so many people to do that?" Maybe the answer actually was they didn't/don't.

giobox

Ignoring the financial aspects, I agree to some extent with OPs opinion this trend of doing more with less engineers really took off following Elon reducing Twitters headcount.

It's worth remembering Twitter was a buggy mess before Elon bought it. Sure it's still a buggy mess today, but the staffing costs are dramatically lower.

Losing a ton of money was something Twitter was also pretty good at even before Elon too - only profitable 2 years out of the 8 leading up to the acquisition while it was still a public company etc.

pclmulqdq

For every engineer who sees things not working on the site and going unfixed, there's a manager who sees how many people still use it.

voidspark

We don't know if it is losing money. It's a private company.

He reduced the headcount to roughly what it was in 2017. At the time of the acquisition, many of the employees were in non technical roles, contributing nothing of value, posting videos about their empty work day on TikTok. Jack Dorsey admitted that he made a mistake by over hiring - more than doubled the headcount from 2017 to 2021.

https://www.statista.com/statistics/272140/employees-of-twit...

JohnMakin

I'm sure companies are realizing this - and tech unemployment is still on the rise - but if this trend was as pervasive as people seem to suggest, it doesn't really explain why tech unemployment is still significantly lower than the national unemployment rate. Maybe it going from 1.5% to 3.4% or whatever is what people are feeling, but it doesn't seem like that should result in massive amounts of people spamming resumes with no response. I'm sure some jobs/careers are gone forever now, but it can't seriously be that many.

jmye

Meta is probably the better example, here - dropped 20% of it's headcount (11% in Nov-22 and another ~9% subsequently, plus whatever's happened since Jan-24) and then 7x'd it's stock price. You can probably argue about decommitting from the "metaverse" fever dream idiocy, but a lot of companies looked at the deep cuts to headcount and certainly thought "AI or no AI, a lot of these people aren't adding value and Meta (and possibly Twitter, depending on what you believe) prove(s) it."

georgeecollins

>> Also find it odd that 20 years of experience hasnt led to a bunch of connections that would assist in a job search - my meager network has been where I’ve found most of my work so far.

I had the same impression. Anyone reading this who is younger: at some point in your life your employment will probably mostly depend on the connections you make to your successful peers, the companies you start, or the products/ technologies you are associated with. When you are starting, strangers will hire you off of your resume. At some point this effectively stops and if people aren't familiar with you or your work they will not consider you. This has been true long before LLMs existed.

sabellito

Overall I'd agree with your sentiment, but it depends on the market.

I only know personally of one counter example to your message. In my career, I've reviewed, interviewed, and hired a few hundred people for somewhat known companies and startups. I also helped many friends find jobs in the past, before the market became what it is today, without any issues. So I like to think I understand what recruiters and hiring managers are looking for.

End of last year, a friend with 12 years of relevant experience started looking for a job. I reviewed his CV (which he tweaked for some of the applications) and cover letters (he wrote one for each company). Everything was as good as it can be for the position he was applying for.

Out of ~20 applications he got a total of 4 replies: 3 generic rejections and one screening that led him to being hired. He killed it during the interviews, but just getting his foot in the door was so hard. Maybe in some parts of the world we're back to 2015-2020 levels of recruiter "harassment", but in others it's super dry, even for senior positions.

JohnMakin

That ratio you mentioned vis a vis applications to hire is about normal for me and something I would consider tolerable

strken

Absolute numbers are probably less interesting than the % change. If you're getting a 5% hit rate but you used to get 20%, that implies that someone who used to get a 5% hit rate is going to have a much harder time.

I'm not sure the relationship is strict enough that the formerly 5% hit rate engineer is now going to see 1.25%, but my guess would be that they'll at least find things a lot more difficult.

sabellito

I'm sure it varies quite a bit depending on role.

Before the market change, for senior engineering and eng management positions, the ratio was 1:1 if the person so wished. My whole career was exactly that: 1 application, 1 offer, always.

karaterobot

It's hard to say for sure without knowing his whole situation, but I will agree with you that when I hear someone say they've submitted 750 applications, my first thought is that they're taking a machine gun approach, applying to a lot of jobs in a short time. I was always taught that you tailor your resume to the position you're applying for, and apply only after doing a lot of research on the company to know whether you are suitable for their position. I'm older than the author of this post, and applied for my most recent job at about his age—though it was a few years ago, before AI was really a consideration. In my entire life, I've probably applied to ~25 positions, made it to the final round 8 times, and been hired 6 times.

Knock on wood that he's wrong about the cause of his current frustration, because that means it's fixable.

JohnMakin

That is my approach as well. It ends up being a lot less work than the machine gun approach.

didibus

> I come from poverty. my father was a drug addict who is dead. my mother is disabled and i’m helping support her. my grandparents are dead. my friends are on the west coast, dealing with similar financial hardships and they are already living with their parents and on couches. I’m not above asking for help, but there is no one to ask.

I wonder how much this factors in. We know from statistic this situation tends to lead to worse outcomes.

Basically those connections you are talking about, are some form of nepotism and a kind of privilege. Should it be this way?

bobsomers

I don't think nepotism is what we're talking about here.

I don't come from poverty, I come from a firmly middle class background. We were a single income household where my dad was a public attorney. Nobody in my immediate or extended family worked in tech. Over the course of my ~15 year career, I've built up a fairly extensive network of former coworkers, many of who I'm sure would try to hire me or get me referrals at their companies if they found out I was on the market. None of this was built through nepotism, as I literally had no connections in tech when I started out.

So, that's the question. The author claims they have had a 20 year career. What happened to all those connections? Do they have a bunch of connections, but no prior coworkers would want to work with them again?

squigz

I don't think GP was talking about TFA - and thus not a professional network - with regards to nepotism, but rather being able to depend on family.

In any case, networks can be hard to build and maintain, and they can easily fall apart if you fall into a rut.

ChrisMarshallNY

I suspect it's not AI.

> dismissing me when they find out my dinosaur age of 42

I gave up, after encountering this (at 55). It's been a thing for quite some time (more than the 2.5 years he mentions).

What's annoying, is that the very people doing the dismissing, are ones that will soon be in those shoes.

I believe ol' Bill Shakey called it "Hoist by your own petard."

pclmulqdq

I have heard from doctors and lawyers that there comes a time in your career when people are no longer interested in people who are older and unremarkable. In many ways it is worse to be a mediocre senior engineer at 45 than a naive junior at 20. You are expensive and you have shown that you have a ceiling.

It sucks that this perception attaches to people at this point in their career. Many become managers at this point because that's an easy way to have broader impact and show career growth when you don't _really_ care about engineering.

If you have spent 20 years as a software engineer amassing wealth (3 houses) and not making significant contributions to your peers or the field, everyone knows where your priorities are. It's okay that you aren't that interested in engineering. It does mean that it's harder to get a job than someone who really is, especially in tight markets. You're also not going to find employment below your level because they know you're going to jump ship when the market shifts. It does mean lowering your standards on certain things, like the "100% remote" requirement.

For the last 20 years, there has been tremendous demand for software engineers that has allowed people to coast. That demand is cooling down for a variety of reasons, AI being one of them (but IMO not anywhere near the most significant). That cool-down really started in ~2021-2022 and really hasn't picked back up. When the market cools down, the unremarkable old-timers are sadly the first ones to be shown the door.

Aurornis

> when people are no longer interested in people who are older and unremarkable. In many ways it is worse to be a mediocre senior engineer at 45 than a naive junior at 20. You are expensive and you have shown that you have a ceiling.

I have to emphasize this a lot to mid-career developers that I've mentored. In the past decade it was really easy to find a comfy job and coast, or to job-hop every year to get incrementally higher salary.

Juniors are mostly a blank slate. Once someone has 10-20 years you should be able to see a trajectory in their career and skills. I've seen so many resumes from people who either did junior-level work for a decade, or who job hopped so excessively that they have 1 year of experience 10 times, almost resetting at every new company.

It's hard to communicate this to juniors who are getting advice from Reddit and peers to job hop everywhere and do dumb things like burn bridges on their way out (via being overemployed by not quitting the old job until they're fired, or by quitting with 0 days notice, or just telling them off as you leave). A lot of people are having a sudden realization about the importance of leaving a good impression and building healthy relationships in your network now that organic job offers are hard to find.

jere

> If you have spent 20 years as a software engineer amassing wealth (3 houses) and not making significant contributions to your peers or the field, everyone knows where your priorities are. It's okay that you aren't that interested in engineering.

Lots of unfounded assumptions and snobbery in this.

gscott

The first thing I thought of was he would benefit from joining an open source project.

gwbas1c

> That cool-down really started in ~2021-2022 and really hasn't picked back up. When the market cools down, the unremarkable old-timers are sadly the first ones to be shown the door.

It makes me wonder if we're in a the early stages of some kind of economic depression or recession.

> In many ways it is worse to be a mediocre senior engineer at 45 than a naive junior at 20. You are expensive and you have shown that you have a ceiling.

Yes, this is something that is poorly understood. (And something that I fear, given that I'm middle-aged.) It's easier to take a risk on someone who charges less, than to take a risk on someone who charges more. Often budgets just won't allow for an expensive software engineer, especially when an overseas engineer is cheaper.

georgeecollins

It's not even that you necessarily have a ceiling, some people work for twenty years and are lucky with success, some are unlucky. You can be 45 and not have reached your ceiling. But the perception is there and you have to think about ways to re-invent yourself. It's really hard when you have family obligations and can't take a lot of risks.

I have a friend in a similar situation to the poster and tbh I don't have great advice.

shawnfrompdx

just for reference about my amassed 'wealth', the combined cost of my mortgages is less than a studio apartment's rent in the bay area. i left the west coast for precisely this reason

s1artibartfast

property values are wealth. mortgage payments are costs. one doesn't imply anything about the other.

Are the properties underwater on the mortgage?

Can you rent out the vacant units?

shawnfrompdx

if you read the original article i talked about how i got into this position. I originally had renters at both properties covering almost all the costs. they left shortly before losing my job.

mattgreenrocks

> If you have spent 20 years as a software engineer amassing wealth (3 houses) and not making significant contributions to your peers or the field

Unpack this for me: what constitutes significant contributions to peers or the field?

riehwvfbk

For the HN crowd it's coming up with the umpteenth JavaScript framework, I think.

hackingonempty

I think your name is unduly handicapping you. Since it is only a single letter people reading your resume think you are being coy and trashing it.

On you resume, change your name to "Shawn Kay." Wait until you're doing HR paperwork to use your legal name.

trenchgun

Yep.

Some context from the blog post: > I turned to service apps this winter: doordash, instacart, uber eats. Their signup systems were incompatible with my full, legal, one-letter last name, and it took about 50 hours on the phone with doordash support in Malaysia and the background check provider in India to eventually get cleared to drive them. I was not able to get through on the other apps.

For sure the impact is not just limited to service apps.

shawnfrompdx

I will probably begin doing this but i will say-- in the past it was not a hurdle at all, and i got many interviews and a few jobs with this name. I have had about 10 interviews in the last year, going to 4th rounds, and nobody suggested it was a problem. my ratio of landing interviews per applications i put in parallels what I am hearing/reading from all other developers on the job market now. I don't strongly suspect my one-letter last name is a huge culprit here, but after a year on the job search and willing to try anything, i may begin applying with a pseudonym

WalterBright

Long ago I knew a person named Gregg. He constantly had to correct peoples' spelling of his name.

Why would parents burden their kid like this?

cellis

More importantly, why don't adults give up names that clearly put them at an economic disadvantage? The same reason people don't sell houses when they are almost always a bad investment; pride, sunk-costs, sentimentalism or other reasons for their subjectivity.

https://www.reddit.com/r/namenerds/comments/10hssp8/why_do_p...

collinvandyck76

I'm a Collin with two l's. Not as uncommon as Gregg but it's never been a burden. I also don't bother correcting people unless it's happening a lot with the same person and someone I expect to interact with a lot.

mserdarsanli

Why would any parent name their child water with an extra L?

s1artibartfast

It really shouldnt be a problem, and in the case of simple corrections, it isnt.

I think it does become a problem where formal systems are inflexible and unable to accommodate or be corrected.

gscott

Change name to an Indian one, problem solved!

m0llusk

This is completely insane. Anyone filtering out qualified applicants based on their names is messing up.

hackingonempty

Ideally the process is blind to avoid bias but that isn't how most people operate. In this case rejection is based upon his perceived behavior, because abbreviating a last name to a single letter to avoid identification is a lot more common than single letter last names.

leksak

I took a look at your resume to see if I would have relevant work for you but doesn't seem like it.

Maybe having vibecoding listed as a skill on your resume is a problem?

Alarm bells also go off when I see "Github (advanced)"

While you are powerless to change it I would also be concerned reviewing this resume as with the sole exception of your consultancy your longest tenure anywhere is just two years.

shawnfrompdx

thanks. this is the fifth iteration of my resume in this last year's search. im clearly trying to push for ai-coding, as i think i was often overlooked for being too 'trad'. in reality im all-in on ai.

leksak

I understand that and from the rest of your writing on your site that very much shows. I use AI professionally to great avail. Personally, I wouldn't put something similar in tone on my resume and when I review resumes this language is not something I'm looking for either.

I'll point out that what is your reality in your job market might be far different from mine. I'm in Europe.

I try to screen out people who come across as zealots or dogmatic about just about anything. Everything could have it's time and place - PHP included ;)

I look for people who are pragmatic and doubt I represent the "people who are hiring pool" to a great extent. But I am hiring and I can just tell you what I see here and how I see it.

why-el

I am not sure if this will help you, but have an extended, deep conversation with ChatGPT about your resume. Tell it who you are, what you excel at, and list projects and technologies. Then, paste a couple of the job postings that did not work for you.

This might sound silly to you, but it absolutely works, because it will distill your experience better, ask you to re-arrange and generalize, and more importantly, it is far superior to us in finding unique key word combinations that work.

shawnfrompdx

ive done this with chatgpt and claude

steve_adams_86

This is an interesting perspective. I've sort of intentionally pushed towards working where AI isn't so useful (physical workflows that are heavily dependent on inputs from humans—scientists in particular) but my experience nonetheless has been discovering how useless AI is in so many ways I envisioned it replacing people by now. It's extremely useful in very narrow bands of application, and outside of that, it's often more of a distraction than an advantage.

I have a hard time believing it's making people that much more productive. It certainly helps me here and there with very specific low-level implementations, but the really important, higher-level work I do? The way I decide which low-level work to do in the first place? Not really, no. I have to interface with very non-technical people who need bespoke solutions to their problems. I need to tie implementations for them together with existing systems that are not standardized, not well-known, and often poorly documented. I need to consider how the life cycle of these solutions can integrate with that of others, how it fits into the workflow and capacity of myself and people I work with, etc.

AI can't do any of that properly right now, and I don't expect that it will any time soon. If I tried to get it to work, I'd likely spend as much time fighting Claude as I'd save. I don't know... What are people doing that they can actually be replaced? Or that companies could decide they actually need fewer people?

My suspicion is that with money being more expensive to borrow, teams are staying lean because we were absurdly inefficient as an industry for the better part of a decade. That's not an AI thing, but a staying closer to actual means thing.

flerchin

> I even hit rock bottom: opening myself up to the thought of on-site dev work

This to me is likely the issue. I suspect if he was willing to move and work on-site, he'd have been back in the saddle quite quickly. My forced career moves also all involved a nationwide job search, and corresponding move.

Still, I believe the struggle, and worry that we'll all be there in the next few years.

starkparker

I'm sure if he wasn't also a caretaker, losing control of his ability to schedule around being a caretaker wouldn't be "rock bottom".

His life would be much "easier" if he didn't have to be his mother's caretaker. But this is America, so he has to, so he's fucked.

shawnfrompdx

for sure it would be much easier if it was just me to consider in the picture

awkward

Yup. The trust issues around overemployment or straight up fraudulent candidates have made remote work rare and have lead to companies offering a premium for hybrid or fully in person roles. I don't think WFH only is line you can afford to draw anymore if you're on the ropes and leveraged.

shawnfrompdx

ive had tons of in-office dev jobs, but have primarily been working online since like 2012. not only has it been way better for my health and sanity but my productivity is way way higher. the thought of going back to an office is PTSD inducing, a big step back

mplanchard

I worry about this, having moved away from a tech center for a better QoL. My current fallback plan if I can't find remote work on the next search is to look for hybrid jobs in NYC, which is a long-but-less-than-a-day's train ride from here, and to try to negotiate being in the office for either just a couple days a week or doing like a week on and a week off or whatever. It'd eat into salary to have to pay for somewhere to stay in the city for sure, but it'd be better than nothing.

aorloff

I stumbled upon this line as well.

And then I realized that he started with just getting home after driving 6 hours of uber to make $200, which didn't really square with on-site work being rock bottom.

On site work is exhilarating at the right place

awkward

Exhilarating on site work often doesn't line up with needing to be a full time caretaker for family, unfortunately.

parliament32

Employment, in general, doesn't line up with needing to be a full time caretaker for whoever. SWE is a curious exception, sometimes, in some companies, but the vast, vast majority of the workforce goes to a place to work, then hires a nurse/nanny/caretaker to fit their other obligations.

shawnfrompdx

I said what I said. it still beats going into in an office

squigz

You think doing gig work for pennies and slowly losing your dignity is better than just going into an office?

I'm sorry but the absolute privilege of the author here, goodness...

Havoc

Tough reading this sort of thing. :(

I don’t quite see the link to AI though?

The CV bot hellhole yes, but not how it replaced him? Is he saying nobody is hiring php devs anymore because of cursor & co? Presumably with 20 years experience he isn’t coding simple stuff so that doesn’t seem super likely

> something has shifted in society in the last 2.5 years.

End of ZIRP. For a lot of companies, especially in the early stage world the math stopped mathing without free money

Regardless overall the message does seem directionally correct - society is going to need a solution pretty soon for people struggling to compete, AI or otherwise

perrygeo

Opinion: the end of ZIRP has a much greater influence on the job market than AI. No more free money means an entirely different incentive structure. There's a fair bit of "oops we overbuilt in the past assuming we'd have free money to hire more engineers". The interest rate thus mediates how and what we build (Conway's Law strikes again!).

Generative AI is a novelty that makes us crazy productive at certain tasks. But it doesn't yet seem to fundamentally change what we build or why. We just do it faster and sloppier with AI. It's a tactical tool to help you win, whereas interest rates define the rules of the game.

alabastervlog

> Generative AI is a novelty that makes us crazy productive at certain tasks. But it doesn't yet seem to fundamentally change what we build or why. We just do it faster and sloppier with AI. It's a tactical tool to help you win, whereas interest rates define the rules of the game.

We're building some stuff that actively uses it—not (just) using it to write code, but integrating it into business processes.

This is both:

1) A far, far more valuable use of it than as a replacement for e.g. macros in your editor, assuming it worked as one might hope it would.

2) In practice so incredibly brittle, tightly-coupled, expensive, and slow to develop (not to mention some of the most boring work I've ever done in my 25 year career) relative to other options that the business could have embraced at any time in the last 15 years (but didn't because it took the hype of "AI" to gain activation energy for the project) all with no evident path toward any of that meaningfully improving, that I'm looking for an exit to another project that's ideally non-AI-related for when this one turns into a nightmare before eventually imploding and staining everyone involved's reputation, if not getting them fired. I reckon the nightmare phase is about six months out, for this one, and the implosion 12-18 out.

I expect similar stories are playing out all over the place.

awkward

The end of ZIRP coincided with some reorganizing of the tax code that wasn't favorable to developers, as well. Both hit after a year or two of windfall profits and massive hiring due to covid.

AI is a very convenient way to tell that story as being about an ascendant new technology, rather than a post covid decline for the tech sector.

pclmulqdq

The increased interest in using generative AI to replace high-paid workers may well have been caused by the end of ZIRP.

cellis

Not just end of ZIRP, not just Agentic AI / Vibe Coding being effective [1], but also:

"Software development is now considered a Section 174 R&D expenditure. This means it must be capitalized and amortized over 5 years (15 years for foreign software development)."

If any one of these were the case you'd have tens of thousands of previously gainfully employed swes out of work. But ALL of them became the case and pretty much in the last 3 years.

[1] - Let's just say I'm a believer

shawnfrompdx

my parent corp let go many, maybe 20% of each of their various dev teams in early 2024, right after everyones productivity was starting to go 3-10x. instead of keeping everyone and dreaming way way bigger, it was more like 'get the same amount of stuff done with way less people.' now i have more experience and skills than ever before, but the ratio of applications to even getting a response much less an interview is lower than ever in the past. anecdotally, in my job searches in 2018 and 2020, roles that would say they had ~20 applicants within the first day of posting, now have like 1000+

ecshafer

I live in syracuse, I found a job this year after being laid off in 2 months. It was a stressful time. Instead or 5-6 hours a week hed be better off studying C,C++ and Java and applying to places locally. Syracuse does not have a ton of web work, but there is a big defense industry here (Saab, SRC, Lockheed, AFRL) so there are things. Cornell, SU, UofR, I imagine are hiring fewer software engineers now though with the potus changes.

shawnfrompdx

i applied at a web dev role at SU, in-office, making less than what i made in like 2009, with skills that are frankly below me. custom written cover letter. job been posted for months. they just hit me with the 'no thanks'

ecshafer

Your resume might need to be rewritten then. Schools do pay very poorly, thats an undisputable fact, but their benefit of free tuition for you and your kids is pretty good.

I would reiterate that most jobs in syracuse are basically C, C++ or Java. The only real web shop is TCG Player, I think theyre C# and god sold to ebay so its the same high competititon. Equitable might have some stuff, not sure how things are going there but they are a java shop. Out to rochester you get a few more web places. But most of the web jobs even are corpro enterprise jobs, they probably dont have a ton of need for php or javascript front end really. Theres plenty of cloud out in Rome. Rochester has more than syracuse, from syracuse its doable, I know people that did that commute.

GuinansEyebrows

> but there is a big defense industry here (Saab, SRC, Lockheed, AFRL)

i hope things don't get so bad that my options are destitution or the defense industry, but i'm used to eating ramen.

ourguile

There are also quite a number of medical device and pharmaceutical companies on the east coast (based in upstate NY here), along with defense industry contractors. So, there are some more options.

GuinansEyebrows

medical devices i am slightly more sympathetic to, as a user of a DMD. pharmaceutical companies, only slightly higher than "defense" companies. they exist in practice so that few may benefit from the misery of many.

cebert

Lockheed can be an excellent place to work. While I’m not particularly fond of building war machines either, I had the opportunity to work on Space Situational Awareness. My role involved developing software to track the movements of space debris and alert operators to potential collisions. This project has been one of the most fulfilling aspects of my entire career.

nottorp

Hey nice - the substack cookie dialog went into an infinite loop when i clicked 'only necessary' cookies.

alborzb

Are you in Firefox? I just had the same loop of click allow all cookies over and over again until only necessary made it disappear!

jspash

I’m on safari mobile and ended up in an endless loop. I had to use reader mode to get out of it.

nottorp

Firefox and ublock origin.

Are there any other browsers left? :)

srdjanr

Well it does the same for "accept all"

didibus

I think it's interesting to ask ourselves if there are still jobs for everyone that pay well, and where people can get the training to do.

Like the article mentions, the cornerstone of US based society is that everyone needs to do something that provides value to others. Yet we constantly seek to scale and automate, to lower our dependence on others.

There must come a day where, you don't need others, but they need you. Then what?

kubb

You'll become a servant for the people who have some wealth, and they'll feel thrilled to be able to order you around.

dexterlagan

I feel for all who feel obsolete and unneeded. The only solution I found for myself was to switch from implementing other people’s ideas to implementing mine. It’s a luxury some cannot afford, but I honestly think it’ll be necessary for many to think long and hard about an idea they can monetize. I wrote about it here: https://www.cleverthinkingsoftware.com/programmers-will-be-r...

jihadjihad

TBH I much prefer your linked post to the OP for its positive tone and outlook. Thanks for sharing.