HN Explorer

Ask HN: I am not able to find a job. Should I switch stacks?

12 points by need_a_work23 ↗ HN
I have 4 years of experience working with React, Next.js, and Node.js.

Other than that, I have also done some work with React Native and Three.js.

My last contract ended about 3 months ago, and I have been trying to find new work since then. I started with LinkedIn, then reached out through my network, HN threads, Wellfound, Reddit, and other platforms.

I also tried reaching out directly to startup founders building things in areas I like, such as worldbuilding and writing-related products. But many of them are also early-stage and do not seem to have much funding or hiring capacity right now.

At the moment, I can find around 6–8 jobs per week, but it is not moving forward. I am not based in the US, which is another hurdle.

I am open to learning new things. I have also done some work and courses around LLMs and RAG, so I would be open to working in that area too.

I’m wondering if I should continue with React/Next.js and keep applying, or if it makes sense to switch to another stack.

Has anyone been in a similar situation? What would you suggest? And how can I show experience in another stack?

17 comments

[ 4.8 ms ] story [ 36.9 ms ] thread
gk1
I highly recommend you read this classic post from Patrick McKenzie: https://www.kalzumeus.com/2011/10/28/dont-call-yourself-a-pr...

> You are not defined by your chosen software stack: I recently asked via Twitter what young engineers wanted to know about careers. Many asked how to know what programming language or stack to study. It doesn’t matter. There you go.

This is especially true now, since coding agents make it possible to work with any stack.

zerr
While this is true that the stack and domain does not matter for any capable software engineer, most jobs are for hiring particular narrow specialists, requiring the years of experience in a particular framework, and even experience working on an exact same product but in a different company.
bot41
Unfortunately, in the real world, if you try go for a c# job with java experience you'll run into roadblocks.
nitotm
I'm on a similar situation. When you say "switch stacks" what do you have in mind? It seems your experience is pretty demanded already. Do you have a strong Github profile?
rozenmd
The job has never been about "writing code". You're there to solve problems for the business.

I'd reach out to people you've worked with before and ask if they need help.

Froedlich
Managers might want solutions, but to get to them you have to go through HR, which wants checkboxes ticked.

That's two entirely different screening processes.

geldedus
nevermind, i was asked for "10 years of React experience" as a mandatory condition for a job, which was a no-pass in my case
sdevonoes
I started with js and php. Moved to Java. Then node. Then php again. Then Go. Then Kotlin. Then TS. Then Python. Then Go again. In between a bunch of sql, html, css, and many different tools, libraries and frameworks. The most important things Ive learned are around architecture/databases/distributed-systems, tho.

I don’t think i could have survived in this industry if I knew only 1 or 2 “stacks”.

aristofun
Serious employers don’t care what tools you used, they care what heights did you reach (what kind of projects did you deliver).
khurs
He said "my last contract"

In contract roles, they often seek a particular skillset

UK-Al05
That often means employers big budgets and training.
mixmastamyk
Don’t believe anyone is hiring “switchers” or people looking to learn new things these days. I only get interviews for things that done the last ten years.

Folks saying it doesn’t matter are correct in times of scarcity, but was always a hard sell to employers. Currently impossible without personal connections.

catzapd
Rather than switch stacks, better way to phrase it is that one should try to increase breadth and depth of knowledge.

By breadth I mean learning other programming language, frameworks, system design etc.

By depth I mean that - if you claim to know React - then get to know the deep detail of React, TS and the related ecosystem.

You can showcase the expertize by writing code, demoing it or sharing on github. Writing about it is another way

brudgers
Learning a new stack is easier than finding a job.

Because it is not finding a job.

And when you are done learning a new stack, your network is still the same and your on the job experience is just further in the past.

Finding a job sucks. Learning a new stack doesn’t change that.

austin-cheney
React jobs, even fullstack, pay well but are ultimately beginner jobs in a market swollen with other well experienced beginners. Stop worrying about the stack and stop competing with beginners for basic employment.

Instead focus on education: masters, certifications, and such. Secondly, write code in your spare time where you ship completed applications.

[deleted]
(comment deleted)