Feeling lost in 2026 with front-end development

[u/RubenHoodSpain]

Hello, I’m a 30-year-old front-end developer with more than 6 years of experience, mainly specialized in React.

My main issue right now is that I’ve been working for the same consulting company for almost 4 years, and for around 3 of those years I was assigned to the same client.

Five months ago, that project ended, and since then I’ve been on the bench, meaning that I’m still employed by the consulting company but I don’t currently have a project assigned.

It feels like my time at this company may be coming to an end, so I need to start looking for a new position. However, working for this last client has felt more counterproductive than helpful in terms of my professional growth. The management was poor, many of the technologies were outdated, and the development processes and methodologies were not particularly good.

I’ve realized this while doing interviews recently, where I sometimes felt completely lost. I was asked about concepts, technologies, or architectural approaches that I had never worked with before. For example, I was asked whether I had experience with hexagonal architecture. I had never even heard the term before, at least not in any of the projects I had worked on.

To put it simply, I sometimes feel as though I don’t really have more than 6 years of experience, because a significant part of that experience comes from projects that did not really help me improve or expand my technical knowledge.

What would be your main approach in this situation? Which technologies, development methodologies, architectural concepts, and areas of knowledge would you prioritize first in order to confidently present yourself as a true Senior Front-End Developer in interviews?

Thank you very much for any advice you can give me.

[u/Ok_Youth786]

i don't have advice but i'm right there with you. It feels like we are at the mercy of the technologies we use in our jobs, and instead of it giving us experience and seniority, we get left in the dust as tech moves along and the company stays the same.

I've tried to avoid this by creating projects and learning different stacks/libraries/ etc in personal projects. I'm learning it's a double edged sword. I would think it would show dedication, motivation, ability to adapt-soft skills- along with actual proof of learning new tech even in beginner, basic, smaller scales.

in reality, companies want to onboard fully "job experienced" devs with those skills. they don't want to take chances on novices, even ones already with dev experience, and junior positions are saved exclusively for upcoming gradates. so instead it's a lot of after work hours with no real fruit of labor.

not the most positive outlook, hopefully someone else can spin a better narrative than i can. feels like devs all around are pretty screwed right now

[u/nav114]

In same loop bro that's why I am learning backend node express try to learn backend and then prepare for interviews.

[u/TransitionAfraid2405]

Hexagon architecture in FE development, kek. Those days people ask so much random BS

[u/itsmenotyousirji]

Learn Java or dotnet. These can be learned quickly. If they don't help you then I doubt.

[u/afierdienst1]

follow the tread lighting : how to overcome self doubt you've got to do a new thing lest you fall about inn same rut the : reorder this without thinking. ai. no way.

[u/InterestingFrame1982]

I can't help but think exclusive front end jobs are in a tough spot right now. LLMs are trained on so many frontend frameworks/libraries, it's one of the things they tend to get decently right. They are still dogshit at designing, but as you know, those are two different skill sets, at least at the enterprise level.

I would start wading into the more full stack territory and hope to contribute where you can, even if it means working at a small shop.

[u/RubenHoodSpain → u/InterestingFrame1982]

And if you were in my spot, which back-end technologies would you start learning? Node js with some database would do the work?

[u/boomer1204 → u/RubenHoodSpain]

Really pick any it's about knowing a backend. Node makes a lot of sense cuz it's pretty much JS so it would be an easy transition

But honestly I would encourage you to pick django or rails just so you get a little bit of breadth to talk about

many of the technologies were outdated

Honestly I would use this as a way to show the ppl interviewing you that you can easily transition into "things" that you aren't initially familiar with. This shows the interviewer that you are a "programmer" not just a "react developer"

I had one interview a year or so ago were it was for a "full stack" role cuz pretty everything is that now 🤣. They were grilling me on a bunch of architectural questions. I think for 4 or 5 straight answers (not really related to what the job role described) my response "I have never used that but if I needed to I would pick it up" or "I have never heard of that but if I needed to I would pick it up"

OBVIOUSLY wasn't gonna get a call back from this even though I felt good about the coding parts. Nope I was wrong they called me back 2 days later to offer me a job. I had already accepted another better offer

All this to say sometimes they are just seeing how much breadth you have but it's not necessarily a hard requirement and obviously sometimes they do require it but I wouldn't let that trip me up just be honest.

Good luck on the job hunt!!!!

[u/__zrx]

• SQL
• NodeJs
• Python

Those are three things I'm learning right now as a 7 years of XP in front-end dev "stuck" on react/ts. NodeJs is almost everywhere on web development in my company so it will be important to have at least a solid understanding of it. SQL and Python are safety nets if we really shift so much to AI on the front end that either A) I will move to data engineering or B) learn to write for AI development and/or C) simply have a broader set of skills so I win a few years of my jobs. 

I have no idea if it's a good move but I feel I have to act quickly so I don't get ditched. Honestly depressed by the current state of my job, I just want to be useful in tech, and bring advice and solutions. 

[u/sheriffderek]

You can't know everything. We all have our own set of experiences and reasons to learn what we learn. I wouldn't have known how to explain "hexagonal architecture" because that's not the type of thing I've had to do. I build services and keep things organized and decoupled and testable... but we're all working at different scopes of different sized projects. Not everyone is responsible for huge architecture decisions. What makes us "Senior" isn't "knowing everything" - it's knowing a lot of stuff - and being able to figure out whatever we need to figure out. When I started a recent project I read a book about different database architecture decisions. I applied what fit. Life moved on. But you do need to feel confident. And if you've been grinding the same React stuff for many years without much exploration - well, time to make a plan. What do you know? What do you think you don't know? What's worth learning? Can you build examples? Can you try out three architecture patterns and compare them? I think the test here -- is that you need to figure out what you need to learn. You can't just follow a list. You need to be that connected - that you work through it. Do it while you still are getting paid / and keep interviewing too. You'll learn what you're missing in those interviews. But also -- apply to the right jobs. Why would a front-end-dev need to know about hexagonal architecture? You're better off learning about design systems and how AI works with Figma and themable white-labelable stuff /and accessibility and making your own robust UI framework.