Should I focus on full-stack development?
My team maintains microservices that were built three years ago using Spring Boot. These services are in maintenance mode, and my contribution at the time was writing REST APIs as a junior engineer. Since last year, we've been working on an internal product that includes both frontend and backend development, using React and Node.js. The work involves solving various problems, participating in design discussions, prioritizing tasks, strategizing, and providing support.
I’ve realized that I’ve forgotten much of Spring Boot and don’t recall many details of what I implemented back then. At the same time, I’m not well-versed in JavaScript either, despite working with Node.js. This leaves me feeling like I can’t confidently call myself a backend engineer because I’m not actively using those technologies, and my JavaScript skills are still not strong enough.
Would it make sense to learn React to build a full-stack profile, considering I already have team members who specialize in UI engineering? Or should I focus on something else? I feel like I’m working on different things but not becoming an expert in any particular area.
![Senior Software Engineer [E5] at Meta company logo](/_next/image/?url=https%3A%2F%2Ffirebasestorage.googleapis.com%2Fv0%2Fb%2Ftech-career-growth.appspot.com%2Fo%2Fcompany_logos%252Fmeta.jpeg%3Falt%3Dmedia%26token%3Da7a5bcc0-e178-4b5b-b71e-09bf6c6aefae&w=48&q=75){kind=small}
![Entry-Level Software Engineer [L3] at Google company logo](/_next/image/?url=https%3A%2F%2Ffirebasestorage.googleapis.com%2Fv0%2Fb%2Ftech-career-growth.appspot.com%2Fo%2Fcompany_logos%252Fgoogle.jpeg%3Falt%3Dmedia%26token%3D780356ef-3efc-4728-9eb4-d909b75bb4a6&w=48&q=75){kind=small}
Discussion
(3 comments)- 0
a month agoTech Lead @ Robinhood, Meta, Course HeroGood question! My general advice goes as follows:
- Do what gets the most impact for your team - This is always the highest priority as it's best for earning trust, making your team more respected (and less likely to get laid off), and building up general skills (product intuition, communication, etc). If front-end adds the most impact, do front-end. If back-end adds the most impact, do that. If the team really needs a full-stack person who can do both, do that (I've seen this scenario many times, including among my mentees who needed to do this to get to senior at Meta).
- Try to specialize - I'm a huge believer in going deep, not wide, but this still comes after #1. What you can do though is try to sway your path - Ask your manager if you can work out a niche that's specialized in just one or the other. If you do end up as a full-stack developer but want to specialize, you can reinforce the side you want via side projects and open-source.
- 0a month agoMid-Level Software Engineer [OP]Taro Community
Thank you Alex! What would you suggest if I had to switch and not stay at the same company?
- 0a month agoTech Lead @ Robinhood, Meta, Course Hero
Switching jobs/interviews is a big reason why specializing is a lot better - It's generally easier to get opportunities if you can effectively brand yourself as a high-quality specialist, especially for engineers with <5 years of experience.
In your scenario, I suggest figuring out what path you want to take. I think it's worth it for you to dabble in front-end just to see if you like it. If you do, you can invest more into it by taking on more front-end tasks at your current job. Eventually you'll have enough experience there that you can brand yourself as a front-end engineer on your resume/LinkedIn and apply to front-end roles.
Conversely, if it turns out that you hate front-end, invest yourself more into back-end and brand yourself as that.
Your resume and LinkedIn are artifacts that you completely own, so you can use that to control the narrative surrounding yourself.
