This article draws on ideas originally published on TechTarget and a Tech Talks podcast interview with Ranjdar Abass, interim head of development at Settled.
The Changing Role of the DevOps Developer
DevOps developers have traditionally been deeply focused on technology — and for good reason. On-premises infrastructure was expensive, risk-averse organisations demanded that shipped products be correct from day one, and a significant portion of engineering time was consumed by low-level concerns: availability incidents, scaling constraints, and security hardening. These were necessary tasks, but they kept developers firmly in the trenches, far removed from end users.
That picture is changing rapidly. The spread of cloud-native platforms, serverless computing, SaaS tooling, and Agile delivery practices has shifted much of that operational burden to vendors and managed services. The result is a fundamental change in what a DevOps developer is expected to do — and how they are expected to think.
Start With Users and Expand Your Thinking
A useful illustration of this shift comes from Ranjdar Abass, interim head of development at Settled, a PropTech startup working to simplify the residential property market. Because most people buy and sell homes multiple times across their lives, Settled serves a diverse, ever-changing customer base with evolving needs. Technology limitations cannot be allowed to dictate business decisions — UX must sit at the heart of every product choice.
As Abass explained in a Tech Talks podcast interview, the goal is not to build one perfectly engineered product. Instead, the aim is to build something good enough to use and good enough to love, then iterate rapidly based on real feedback. DevOps practices, Agile delivery cycles, and SaaS infrastructure make that approach viable by enabling tighter feedback loops and faster, more confident decision-making.
The practical effect on the developer’s day-to-day work is significant. When a vendor manages availability, scalability, and security at the infrastructure layer, the development team recovers time and mental bandwidth that was previously consumed by operational firefighting. That freed capacity can be redirected toward understanding users, experimenting with ideas, and iterating on product experiences.
Closing the Gap Between Developers and Users
One persistent criticism of traditional development organisations was that engineers were too far removed from the people using their software. Decisions were made based on technical constraints and internal assumptions rather than real user behaviour. Modern DevOps workflows — continuous delivery, feature flags, A/B testing, real-time monitoring — actively close that gap by surfacing user signals directly into the development process.
This is genuinely good news for end users, who receive software that adapts to their needs rather than forcing them to adapt to technical limitations. It is also an opportunity for developers: those who engage with user feedback and take ownership of outcomes — not just code — become significantly more valuable to their organisations.
The Industry Is Changing — So Must Your Mindset
If you work in DevOps today, technical skill remains essential — but it is no longer sufficient on its own. The specific hard skills that are in demand shift with each technology cycle, meaning that knowledge can become dated within a few years. What endures is the ability to learn, adapt, and contribute ideas.
Organisations building on modern DevOps stacks actively look for developers who bring more than implementation capability to the table. They want people who can:
- Think from the user’s perspective — asking why a feature matters before asking how to build it.
- Embrace iterative delivery — treating a release as a hypothesis to be validated, not a finished artefact to be defended.
- Stay curious about tooling — evaluating new platforms and practices critically rather than defaulting to familiar approaches.
- Communicate across disciplines — engaging meaningfully with product, design, and business stakeholders rather than working in isolation.
- Adapt when the landscape changes — recognising that today’s best practice may be replaced by something better within a few years.
Practical Takeaways for DevOps Engineers
Embracing adaptability and creativity is not about abandoning technical rigour — it is about applying that rigour in a broader context. A few concrete habits help DevOps engineers develop this orientation:
- Spend time with user research and analytics. Review session data, support tickets, and usability findings regularly. Understanding where users struggle is as important as understanding how the system works.
- Participate in product discovery. Join conversations about what to build before the technical approach is decided. Early involvement leads to better solutions and fewer late-stage surprises.
- Treat automation as a creativity enabler. Automate repetitive operational tasks not just to save time, but to protect the mental bandwidth needed for higher-order thinking.
- Build learning time into your workflow. Set aside regular time to evaluate emerging tools, read about industry trends, and experiment in a low-stakes environment.
- Seek feedback on your assumptions. Ship small, measure the result, and adjust. This applies to features, infrastructure changes, and developer experience improvements alike.
Summary
The DevOps developer role is evolving from a primarily technology-focused position into one that demands user empathy, creative thinking, and genuine adaptability. As cloud and SaaS platforms absorb the operational concerns that once dominated engineering backlogs, developers who invest in soft skills alongside technical depth will be better positioned to deliver lasting value — and to navigate the continuous change that defines the DevOps discipline.