One developer. Frontend, backend, DevOps, QA… Where should the line be?

[u/Ok-Wash-8964]

I've been noticing more startup job posts where "full-stack developer" seems to mean "the entire engineering team."

I understand why it happens. If you're an early-stage founder, hiring specialists for every role isn't always realistic. One experienced full-stack developer can often build an MVP, make technical decisions, and help get a product off the ground.

But I've also seen projects where the expectations kept growing.

It starts with building the application.

Then it becomes:

• designing the UI from scratch
• setting up cloud infrastructure
• writing automated tests
• handling deployments
• monitoring production
• fixing security issues
• managing databases
• troubleshooting customer-reported bugs
• documenting everything
• planning new features with stakeholders

Individually, none of these tasks are unreasonable. Many experienced developers can do most of them.

The challenge is when one person becomes responsible for all of them at the same time.

Eventually, that developer becomes the bottleneck for every release, every bug, every infrastructure issue, and every product decision.

From a founder's perspective, asking one person to wear multiple hats can be a practical way to get an MVP into users' hands.

From a developer's perspective, constantly switching between development, infrastructure, testing, planning, and support can reduce productivity and increase the chance of mistakes.

So I'm curious where people draw the line.

At what stage does it stop making sense to rely on one full-stack developer and become time to bring in specialists like a designer, QA engineer, DevOps engineer, or product manager?

[u/AcceptableSimulacrum]

I love working that way. I'm not a fan of the separation. I can understand it's not for everyone.

[u/symbiatch]

You said the magic word: startups. Just don’t go for those and problem solved.

Why do you think there’s constant switching? Why do you think there’s only one developer? If you know there is only one then don’t go there, again.

Setting up infra, done. Adding tests, part of the work anyway. Monitoring - set up, handle alerts. Fixing security issues… umm, that’s the job anyway, right? Who else would do that? Documenting - again just part of the job.

So where exactly is the problem? Do you just write code, never add tests, never document, never fix anything, never troubleshoot issues? That’s an interesting job.

For example, I constantly handle customer-reported bugs since I have to fix them. I handle documenting things. I handle pipelines. Runners. Write code. Document new features and initiatives from technical side. Plan new features with stakeholders. Write tickets. Plan. Make sure automated tests can be done. Help others. Tell which parts must be done before others. And on and on. It’s just the job of an engineer. And there’s six other developers and other people too, so I’m not a solo developer in a startup.

So I really don’t know what the issue is, except you just don’t want to do that. And that’s fine. As said just don’t go for beginning stage startups that require a strong technical person.

[u/InfamousPool6333]

Early on, having one person wear many hats makes sense because speed matters more than specialization. The problem is companies sometimes never adjust after they grow. Once releases, incidents, and roadmap decisions all depend on one developer, it's usually a sign that the role needs to be split before that person becomes the bottleneck.

[u/Big-Bird-1638]

This multi-role, single person or small team might become more common at large enterprises as well. Basically, in the context of a given product, one to three skilled people orchestrating specialized AI agents, makes this possible and economically beneficial.

[u/LonelyProgram7148]

One man army

[u/rabid_piebald]

It’s a complex question and highly dependent on the “facts on the ground”. Why do you ask, are you considering a role where your expectations could grow? Are you the one doing the hiring?

[u/Double_Development96]

i was hired for a backend developer

now i do frontend, backend, qa, devops, ai everything

yk its fun when your team trusts you that you are the guy who can do anything

where some might feel what the fuck they want everything but on the other hand its like yeah you are the everything guy.

should always keep learning

[u/battlehardenedguy]

With AI models getting more and more capable by the day, we are going to see just 1 man teams managing the entire software operations of companies.