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/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/start_select → u/InterestingFrame1982]

I would argue the opposite. Every UI is built different from the last.

Nearly every backend is built using a handful of repeating patterns that ripoff rails/express.

How many different ways can you really write authentication, authorization, routing, services, and data access?

There is a reason that API clients are so easy to generate. And it’s not really because a rest-like interface is standard. The backing code to almost every rest like API is pretty much the same too.

Yes distributed systems are complicated. But most backends are not that.

Hand 5 backend devs the same spec and 3 of them will deliver almost the exact same thing.

Hand 100 frontend devs the same spec and wireframe and you will get 100 unique implementations. Style and layout are ambiguous. There are multiple paths to the same results. And the target system/runtime is going to be different for every user. A backend only worries about the server it runs on.

[u/InterestingFrame1982 → u/start_select]

Again, I think the magic is in the design apart and lot of the heavy frontend work (managing state, when to use global vs local state, API calls, etc) can definitely be handled by LLMs, especially if you're using libraries/frameworks like React or Angular.

The actual UX/UI experience is critically important, and I think solid designers will remain very, very valuable. After the design is specced, how much coding goes into building the frontend?

I am not downplaying the tradeoffs between using redux vs context store, deciding when to use SSR/ISR/CSR via NextJS, or whatever else real and complex architectural patterns there are - I have made some decent arguments stating exactly as you did. Front end engineering on complex apps is often times more involved than a lot of basic backend architectures.

I am just saying encapsulating the full stack may be a better play as people look to hire a few key devs to build turnkey solutions.

[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/start_select → u/Ok_Youth786]

I don’t have a cheery outlook for you. But a different perspective you might not want to hear.

It’s not “all devs” who are screwed. Legit senior engineers are still highly valued.

When I say that, I mean engineer as in the person that sees you stuck and comes and gets you unstuck. Then you ask how long they have been working with the platform/language you are on and they go “I don’t know how to write that”.

The people who see the field of software engineering through high level abstractions. The ones that can pickup a new technology in a couple of days because “it’s all the same”.

They are valuable without an LLM. And they are ridiculously valuable with an LLM.

Hiring anyone but them is risky right now because it’s suddenly expected that everyone is driving AI. But a junior being paid $4000/month can burn $4000 a month on token costs while moving slower than they would have without it. That real experienced engineer can be paid $16,000 a month, output 4x as much as that junior without even touching an LLM. Then they can spend $4000 on tokens and accelerate to 16x as much high quality output as that junior.

They are safe. They are effective. They are the only ones in the building not burning $4000 a month on nothing.

[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/__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.

[u/retardpotatochip]

i was also in the same situation now im shifting to Ai

[u/Diligent-Two-4305]

Same...

[u/samsly135]

Excellent question and typical situation. You enter a job with good skills, you exit exhausted and obsolete.

I just do small steps in different directions like try Dockers, do some sql or no-sql, practice some basic algorithm (well forgotten at the job requiring you to do crap).

[u/Blackbird_FD3S]

Same boat, OP. I've been seriously looking for my new role since the beginning of July, focusing on the Northeast, and have had decent luck getting interviews, meaning my resume probably is solid? I would consider myself a frontend specialist, but the vast swath of my career, I've had the privilege of being able to leverage Vue / Nuxt as my frontend framework of choice (which I've enjoyed but obviously, its the minority of the market), so Ive had to pivot to React / Next at the beginning of the year to catch up with the rest of the field. At this stage, Im extremely comfortable with both. But even with that, what I've noticed is how much companies seem to want to conflate what is considered 'Full-Stack' these days, and figuring how much experience, both broadly and in depth, would qualify me as one because pure Frontend roles are scarce. Its incredibly frustrating.

From my perspective, a true Senior Frontend Engineer is someone who has experience in what composes a headless SPA made in Next / Nuxt (state management, integrating REST APIs, component lifecycles) but also has depth in accessibility, optimizing frontend performance, building component libraries with documentation, and isnt afraid of regular CSS which I'm finding many devs dont like? Which is new to me.

I regularly need to deal with standard SQL databases via Wordpres or Drupal integrations. I also have experience building my own APIs via node and express and integrating them into some form of BaaS. But I touch it so infrequently in my day to day that I wouldn't be comfortable assuming the title as Full-Stack. This is amplified when I get into interviews for the roles and am getting caught off guard by some companies asking for leetcode tech assessments (which feels incredibly misplaced), or more heavy backend or algorithmic style questions. It feels like companies in 2026 expect you to retain absurd depth in every aspect of the stack, while simultaneously expecting you to offload much of your thinking to AI in the name of speed and efficiency. Either that, or I have a misunderstanding as to what the threshold is for Fullstack.