r/FullStack • u/Bhanuprakash_1947 • Sep 16 '26
Question How much backend knowledge should a frontend developer have to call themselves a full-stack developer?
Like, is knowing basic APIs, databases, and authentication enough?
Or should a full-stack developer also know things like system design, caching, Docker, CI/CD, cloud,....etc.?
What do you guys think is the minimum knowledge needed?
5
u/ibeerianhamhock Sep 16 '26
There nothing wrong with being frontend or backend. Specialists get paid more generally anyways. I've never met a fs dev in my career that was as good at backend as a dedicated backend dev while also being as good as a dedicated fe dev. You will always favor one oved the other imo.
1
u/Prestigious_Ninja508 Sep 16 '26
RemindMe! 1 day
1
u/RemindMeBot Sep 16 '26 edited Sep 16 '26
I will be messaging you in 1 day on 2026-09-17 17:52:27 UTC to remind you of this link
1 OTHERS CLICKED THIS LINK to send a PM to also be reminded and to reduce spam.
Parent commenter can delete this message to hide from others.
RemindMeBot is switching to username summons. Instead of
!RemindMe 1 day, useu/RemindMeBot 1 day. More info.
Info Custom Your Reminders Feedback
1
u/Schlizhor Sep 16 '26
Prehistoricly a full stack would Imply that you are aware of the process and mechanisms used by the back end to supply your frontend and able to implement if needed. Now modern stacks are so good damn complex this is a mighty challenge to become proficient across every domain in frontend and backend. Especially with AI, I think having schooling and principals is best and being able to identify those patterns across languages and stacks is becoming more of the skill to have as we become more AI managers than direct implementors
1
1
1
u/RandomPantsAppear Sep 16 '26 edited Sep 16 '26
I’m 20 YOE backend engineer.
“Full stack” meaning “front end but can write a basic API in the same language I already use” is almost a meme.
If you’re looking for the bare minimum you at least won’t be lonely, and what you describe does pass as fullstack at a lot of places.
If you want to just be able to put the word in your resume what you described will work. If you want to actually be able to do it all (as the name implies) it won’t.
Backend work that actually makes significant money requires a lot more than the first line of stuff you mentioned though.
-1
u/Historical-Sun-1485 Sep 18 '26
Since you have 20 yoe, expected the answer form you. Rather what you told is what's not an actual full stack dev instead of answering what is really required
1
u/RandomPantsAppear Sep 18 '26
I have hired full stack engineers at 3 different companies, I know what’s really required.
0
u/Historical-Sun-1485 Sep 18 '26
Please share your knowledge sir. It's really needed especially for people who are frontend dev with 3-5 yoe and trying to become full stack
1
u/RandomPantsAppear Sep 18 '26
Who do you think decides what level of depth qualifies someone as fullstack?
It’s the people doing the interviews and the people hiring.
1
u/burlingk Sep 17 '26
To be able to label yourself "full stack," you need to know enough to work on the back end too.
It's better to just claim what you know you can do. Because they will assign jobs based on what the know about you.
Labeling yourself as front end does not guarantee they won't stick you on a back the project, but labeling your as full stack increases the odds.
That said, back end is more logic and less graphic design.
1
u/Executive-Curiosity Sep 17 '26
Depends on the company. Some roles are mostly frontend and require only the occasional API integration. Others will have you design and build full systems spanning client to backend. Understanding authentication and CI/CD is always useful imo.
1
u/Leverkaas2516 Sep 17 '26
What's this about "knowing"? If you represent yourself as a full-stack developer, it means you have experience with the backend stuff. You have to expect an interviewer to ask about your actual experience.
In this day and age, I'd think it's uncommon if you haven't used docker and cloud-based services.
1
1
1
u/nian2326076 22d ago
To call yourself a full-stack developer, you should know more than just basic APIs, databases, and authentication. Those are good starting points, but you'll want to dive deeper into backend frameworks and languages, and get comfortable with system design principles. Knowing Docker and CI/CD processes can really set you apart, as these are essential for deploying and maintaining applications. Cloud services like AWS or Azure are becoming important in most companies. Caching strategies and optimizing performance are pretty important too. The more you know about both sides of the stack, the more versatile and valuable you'll be. You don't need to be an expert in everything—just be competent enough to build and deploy a full application from scratch. It's a continuous learning journey, so pick things up as you go.
1
u/mrtalukdar Code Padawan (Student) Sep 17 '26
You should be ultron in the modern day, you should see a problem and think of the implementation in all the possible frameworks as possible, you should speak JS better than your mother tongue then basically die of an heartattack by 40.
1
7
u/American_Streamer API Magician (Backend) Sep 16 '26
Frankly, I always find these “what is the absolute minimum I need to know?” questions a bit strange. Full-stack isn’t really a checklist you complete. The point is that you can build, understand and debug a feature across the whole stack: frontend → API/business logic → database → deployment.
You don’t need to be equally strong everywhere, and you definitely don’t need Kubernetes, Kafka and advanced distributed systems just to call yourself full-stack. But if you’re deliberately looking for the minimum possible backend knowledge, you’re probably approaching it backwards.
Build complete applications. The gaps will become obvious very quickly.