- Boot camp graduates flooded the frontend job market
- These roles turned into full stack positions
- Many jobs have moved overseas
I don’t know what’s happening. I haven’t been able to get a job in this field for 18 months. I feel like I’m blacklisted. I’m 35 and don’t have a computer science degree. Applicant tracking systems also seem to work against me. I have 8 years of experience from frontend to full stack. I know what I’m doing and can learn anything. It’s frustrating.
In my circle, a couple of Java developers are now coding in TypeScript/Node. Switching from Java to TypeScript seems easier now.
I also lost my last frontend role to someone who calls themselves a Full Stack Engineer aka ChatGPT engineer. Their code was messy but there was a lot of it. Only companies that value cohesive and maintainable code probably won’t want that, I guess.
This usually cycles through phases, and right now companies think they can find one person to be an expert in everything.
Soon they will realize their frontend work has turned into a chaotic mess and they will need to start hiring frontend specialists again.
I believe this shift is due to JavaScript/TypeScript being used in backend roles. Frontend developers are generally expected to know JavaScript well, so when they need to write some backend code, it makes sense for them to use the language they’re comfortable with. This means they pick up some backend knowledge along the way.
As long as ‘Full Stack’ positions focus on JS/TS, there will be many developers available for those roles. Even those who advance to senior level in full stack JS/TS can quickly learn other languages used in backend roles. Most of the fundamental principles are relatively similar.
For these reasons, it seems that anyone who has worked in frontend for a long time will eventually transition to full stack roles, though many backend developers prefer to avoid frontend work and styling.
@Reese
I’m one of those backend developers who understands how frontend works but I prefer to stay away from styling and layouts. Thankfully, I rarely have to deal with that.
However, I think JavaScript is mostly a poor choice for backend development, and I have received messages asking to fix poorly written JavaScript code. I enjoy collaborating with good frontend specialists, so I find it disappointing that companies reject hiring them, though it’s not surprising.
@Dana
I mostly agree that JavaScript isn’t the best option for backend work. But I think that for frontend developers, JS has become a common path to full stack roles.
Some will move on to better tools, while others may stick with JavaScript in backend roles because there are plenty of job offers available. Companies know that frontend developers can handle some backend work if it’s JavaScript-related—it’s a self-fulfilling situation.
@Reese
Exactly! I think there will be a reaction against this trend, as companies will end up spending more on fixing poorly written backend code, and I expect that to worsen over time.
Many jobs have gone overseas. I’ve been doing freelance work for poorly skilled frontend developers who can’t grasp Figma designs or are just too lazy to follow design guidelines. But I doubt anyone would hire me for a steady salaried position. I come in, handle a contract, and then they go back to their in-house full stack developers.
I’m also capable of full stack work, but I’m very skilled in frontend, which helps me integrate both when needed.
At the end of Q4, check in again after Q2. This pattern happens every year.
I do mainly frontend work while handling some updates on the backend alongside our actual backend developer. I mostly work with JavaScript in React.
-
Slow hiring processes. Check back after the end of the fiscal year for most companies.
-
The era of developers that only focus on HTML, CSS, and a touch of jQuery is mostly over unless you’re crafting marketing pages or working in an agency. Those roles still exist, but they’re rare and often don’t pay well.
Frontend is dead, backend is dead, fullstack is what companies are looking for now
I think frontend developers hurt their own market when they created frameworks that act like pre-made templates. Most websites look similar now and neither users nor managers mind. So they stopped hiring designers and instructed full stack developers to make everything look like Bootstrap.
As someone who has hired plenty of engineers, I’ve started preferring full stack developers since there are more of them available now. This lets teams operate more independently by tackling all needs to build a feature or product without depending on other teams or creating bottlenecks between frontend and backend roles. Moreover, with the trend of backend development switching to JavaScript and TypeScript, it’s easier for traditional frontend or backend focused engineers to learn the other side.
I still hire for specific roles, but they are usually senior positions where I need someone to lead frontend or backend development.
It’s not about cheap prices. I’m willing to pay a bit more for good full stack developers, and that’s what the market typically reflects.
This is part of the streamlining that companies discuss when justifying layoffs. I’m seeing more of these roles being offered remotely, with a focus on hiring from places like Brazil, Russia, and other popular outsourcing areas.
I’ve gone through several ‘full-stack’ interviews only to find they were heavily focused on frontend work. Being a frontend expert isn’t very valued right now. My recommendation? Lie and learn.
I think the rise of Remix (now React Router 7) and NextJS has had an impact. As some have pointed out, server-side rendering in React has blurred the lines between frontend and backend work. Companies now seem eager to hire developers who can do both.
Your issue is just one step behind mine. I’m trying to get a full stack role, but so many want me to also be a devops engineer.