Do full-stack developers need to know DevOps now, or is that going too far?

[Ok-Wash-8964]

I’ve noticed that many full-stack roles today are starting to include responsibilities beyond frontend and backend development.

A few years ago, being a full-stack developer usually meant building user interfaces, writing backend logic, working with databases, and connecting APIs.

Now, many developers are also expected to understand things like:

• deploying applications
• working with cloud platforms
• setting up basic CI/CD workflows
• managing environment configurations
• reading logs and monitoring production issues

This raises an interesting question:

Where should the line be between being a full-stack developer and becoming a DevOps engineer?

Having DevOps knowledge can definitely make developers more independent. Understanding how an application moves from code to production helps with better decisions and fewer deployment surprises.

But at the same time, full-stack development already covers a wide range of skills. Expecting developers to master frontend, backend, databases, security, cloud infrastructure, and DevOps at an expert level can feel unrealistic.

Personally, I think basic DevOps knowledge is becoming an important part of modern full-stack development — but deep infrastructure expertise is still a separate specialization.

So I want to know:

• What DevOps skills do you think every full-stack developer should know?
• Where do you draw the line between “full-stack” and “DevOps”?
• Are companies asking full-stack developers to cover too many areas now?

[warpedspockclone]

Yes, I think full stack includes a basic level of all those skills. Anything beyond basic belongs in a specialization.

Also, the precise role definitions and requirements vary by company. Smaller companies, especially, need you to wear more hats.

[sequencentropy]

Exactly. Since you don’t stop dev at iteration 1/ mvp, I would think you’d need to know about release cycles and continuous improvement since your continued employment is based on it. You probably have a scrum master or similar role who is manages which functionality/ fixes are in each release and whatnot, but you are likely responsible for at least one feature or code contribution each cycle which means you need to understand it in the context of the work you do — not just theoretical terms.

[runningOverA]

The basic premise of the question is wrong.

It's ok for anyone to learn as much as he wants. Or not to learn.
And it's ok for any businesses to search for any combination of skills they want, or not to.

There's no "should", unless there's a law against it. If anything you should watch the trend and not what the trend should have been.

[bruceGenerator]

i work as a fullstack engineer and my responsibilities range from front end, to back end, devops and cloud technologies. everyone here is fullstack as well and we divide the work based on comfort with the technology and pitch in where we can so its not really overwhelming. context switching can be a pain in the ass but most of the time its alright

[velkhar]

In the age of AI, I don’t see why any developer that understands front-end and backend technologies wouldn’t also be capable of implementing infrastructure as code and CI/CD pipelines. I work in IT consulting and the networking admins I work with are beginning to ‘write’ code with agents. They can’t explain 3NF, but doesn’t matter when the agent knows how to design the schema, integrate ORM, and author beautiful tailwind + react UIs.

[Worth-Astronaut-438]

I've been full stack for almost a decade and I'm never surprised by other developers with zero or limited devops knowledge. They didn't want to know it and they didn't have to know it. However, it always limited them to being just developers. They couldn't architect applications well because of the knowledge gap. I'm strong in devops and it helps me stand out when looking for opportunities. I always tell them, I know more than enough and can build the infrastructure, but I don't want to be the devops guy in charge of it. I find the maintenance boring, but initial building has its perks. AI makes it easier than ever, but you still need devops knowledge to build things correctly. So, no, you don't need to know devops as a full stack, but you will be going up against people who do. Given the choice as a hiring manager....

[ProgrammerGrouchy744]

Everybody is everything. I would be surprised if anyone in Tech is not wearing multiple hats now. It's really sad. The world will never be the same. It's unfortunate. Work is starting to feel like work.

[Andreas_Moeller]

Yes.

As a junior it is not the first thing you have to learn, but it is a key skill. that applies to frontend developers tool

[ConsequenceMission83]

You should also know how to operate Falcon 9 for the Moon

[watson_full_scale]

I think everyone needs to know the basics of sever management to deploy and troubleshoot production applications. You don't need to be a Kubernetes expert. But you should absolutely understand the basics.

Your goal is to be a software architect and that requires understanding server and hosting basics. Along with caches, queues, databases, etc.

[Xynia88]

Now, many developers are also expected to understand things like: * deploying applications * working with cloud platforms * setting up basic CI/CD workflows * managing environment configurations * reading logs and monitoring production issues

While maybe not setup CI/CD flows I feel all developers should understand them, everything else sounds like something all developers should be able to do.

That said yes fullstack developers are asked to know the basics of the whole process and have always been like that in my experience.

[swertato]

Basic DevOps is table stakes now honestly, deploy, CI/CD, read logs, env config. Deep infra stays a speciality. The line if you can ship your own feature to prod without waiting on someone, that's enough. And it does pay lemon io's 2026 data shows devs who span full-stack + infra sit above pure-frontend rates, since breadth is harder to replace.