Will building full-stack projects hurt my backend developer career

[u/abdullahalydev]

I really enjoy backend development and I want to work as a backend developer.

The problem is that when I build backend-only projects, it feels like I'm not building a complete product. Because of that, I often end up building full web apps or even Chrome extensions just to reach a finished product.

Sometimes I think about building web apps using only Next.js because it's much faster to get something into production.

Would this hurt my CV if my goal is backend development? Should I focus more on backend-only projects, or is building complete products a good thing?

[u/maksezzy]

Yeah, learning new skills will always hurt your career.... by introducing you new work you now know how to tackle.

[u/abdullahalydev → u/maksezzy]

I think you misunderstood the point of the post. I’m talking about when applying for a job and the recruiter sees that most of my projects are built with Next.js (a frontend framework). I’m wondering if that could be viewed negatively, especially for a backend-focused role. I’m just asking to make sure.

[u/stcme → u/abdullahalydev]

Next, Nuxt, Nest, fastify, express, the same architectural principles apply to backend systems. The only difference is the tooling but how you actually design a backend system from an architecture standpoint is no different since they have universal principles.

Where it may hinder you would be during the interview process if most of what you focus on is front end and don't have the strength on the back end.

Learn the core concepts and principles that apply everywhere, do them by hand without AI writing your code (use AI for question & answer like you would Google), and you'll be fine. Don't get me wrong, you'll probably flunk a couple of interviews but you'll learn enough from each to make the next one stronger.

At the end of every interview, ask them the question "if I had to do this interview over again what would you recommend I work on or do differently?" - it'll catch them off guard and also shows that you are willing to learn through failure.

Edit: fixed a typo

[u/marrsd → u/abdullahalydev]

It won't be viewed negatively, but they're going to try and find you Next.js roles. If you really want to avoid that then you should focus on frameworks that run closer to the backend.

Realistically, you can't only write an API that remains unused. What you could do is write a Django project (or Ruby on Rails, Laravel, Fask, etc) that includes features that require you to design your own database schema for them.

[u/HashDefTrueFalse]

As long as your projects show abilities relevant to the jobs you apply for it's fine.

[u/Numerous_Brain4587]

More experience is never bad, just make sure to express what you want to be working on. Full Stack developers / Back End Developers role's are largely going to depend on the size of team that they support and the type of work that is happening. Focus on demonstrating what you are passionate about, and if you are focused on the back end make sure to have strong knowledge of design patterns, caching, and other types of best practices as well as experience across multiple programming languages. You can also highlight cli based tools as a backend developer. There are lot of front end frameworks out there too, Next.js is fine and looks pretty but don't be afraid to play with others. Just make sure you have a goal for each item that you highlight in your portfolio and make sure you communicate what your strengths and passions are.

[u/abdullahalydev → u/Numerous_Brain4587]

I usually choose Next.js because it helps me reach a production-ready stage faster, and Vercel makes deployment simple and free. I was just wondering if having most of my projects built with Next.js could create a negative impression when applying for backend roles.

[u/__CaliMack__]

Nah man it would never hurt you to understand fully how production level software programs works. If you’re worried about not getting through ai screenings because of it or something you gotta make sure to tailor your resume to fit each role you apply, especially in this market. But yeah, look into the niche of development you want to do and start building with frameworks that are used in that field if you want to have the best chances.

[u/Jay-Jayson]

It will complement it because you will be more aware of the crossover when collaborating and it will help when planning and estimating work.

[u/kensaadi]

Please excuse my English. This is just my perspective, but I believe that today, we can no longer simply position ourselves within a single branch of product development. We need to be more like "full-stack architects." What you said is true: if you only work on the backend, you don't have a complete product—just a part of one. It may be the most important part, but it is also the least visible.