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?
> 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.
That is why I would be hesitant to review complex Rust or some other code I have no experience in, sure the language has ways to handle things like async, garbage collection, etc. but I would just be assuming the AI is doing it right or even worse trying to steer it to handle it in a Javascript or Go manner.
Instead focus on education: masters, certifications, and such. Secondly, write code in your spare time where you ship completed applications.
I'd reach out to people you've worked with before and ask if they need help.
That's two entirely different screening processes.
if you think you can do the job, track down the hiring manager and convince them.
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.
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
I don’t think i could have survived in this industry if I knew only 1 or 2 “stacks”.
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.
In contract roles, they often seek a particular skillset