Bridging DevOps and Research - Why Both Worlds Matter

People often ask me: “You’re a DevOps engineer AND a researcher? How do those connect?” It’s a fair question. On the surface, managing Kubernetes clusters and studying depression screening seem worlds apart. But the overlap runs deeper than you’d think.

Systems Thinking

DevOps taught me to think in systems. When I design a CI/CD pipeline, I consider: How do components interact? Where are the failure points? How does a change in one part cascade through the whole?

HCI research requires the same thinking. When I study how a USSD-based service (NavConnect) impacts boatmen’s livelihoods, I’m mapping a system: technology, users, socioeconomic context, cultural norms, infrastructure constraints. Change one variable, and everything shifts.

Automation Mindset → Reproducible Research

In DevOps, we automate everything. Infrastructure as code. Automated testing. Reproducible deployments. This mindset directly translates to research:

  • Reproducible data analysis - scripted pipelines, not manual Excel work
  • Version-controlled experiments - tracking every change to your study design
  • Documentation - if it’s not documented, it doesn’t exist (true for both servers and research)

Working Under Pressure

Production outages at 2 AM taught me to stay calm, diagnose systematically, and communicate clearly under pressure. These same skills are invaluable during:

  • Thesis defense presentations
  • Conference Q&A sessions
  • Tight paper submission deadlines

Infrastructure for Vulnerable Populations

My DevOps work at RedDot Digital (a subsidiary of Robi Axiata) gave me firsthand experience with the digital infrastructure that serves millions. I saw how platform decisions - uptime, accessibility, latency - directly impact users, especially those in rural or underserved areas.

This experience informs my HCI research: I don’t just study user interfaces in isolation. I think about the infrastructure those interfaces run on, and whether that infrastructure is equitable.

The Unique Perspective

When I apply for PhD positions, I don’t hide my industry experience - I lean into it. I bring:

  • Technical depth (Docker, Kubernetes, CI/CD, cloud infrastructure)
  • Production-scale thinking (real systems, real users, real constraints)
  • Research rigor (published papers, thesis work, grant-funded projects)

This combination is rare, and I believe it positions me to tackle research problems that require both technical skill and human understanding.

For anyone navigating a similar path between industry and academia - embrace the duality. It’s a strength, not a contradiction.