Need advice: Back end engineer → infrastructure: how do you make the transition?

I’ve been a backend-heavy engineer for about 4 to 5 years, mostly in startups. For about 3 months I’ve been reading and building small things, but I’m not sure if I’m progressing or just spinning. I also don’t really have people around me in these areas, so I’ve mostly been trying to figure this out on my own, including using tools like GPT and Claude, but I still feel unclear.

My work includes APIs, some real-time systems like WebRTC and streaming, and debugging production issues such as latency, buffering, and reliability. I’ve used AWS, Docker, Redis, and similar tools.

I’m trying to move toward more systems-oriented work, such as infrastructure, distributed systems, or AI infrastructure like inference pipelines and data flow.

The problem is I feel stuck and scattered. I keep jumping between directions such as infrastructure, SRE or platform work, and AI infrastructure, and I don’t have a clear sense of what the actual path looks like from where I am.

Some questions:

How do people actually move from backend or product work into infrastructure or systems roles?

Is it better to pick one direction early, or explore broadly first?

How do you pick a theme or direction that actually compounds over time instead of second-guessing constantly?

What kinds of projects really signal readiness?

And practically, how do you start getting interviews without already having an infrastructure title?

Would really appreciate advice from people who’ve made this transition.

Thanks

6 points | by gokuljs 18 hours ago

4 comments

  • tacostakohashi 15 hours ago
    Find some detailed job ads, and work backwards from there to see what skills are in demand.

    What exactly do you mean by "infrastructure" or "systems"? At my organization, that basically means stuff like grafana, open telemetry, kubernetes, aws/azure, etc.

    Your "AI infrastructure" is perhaps what other people call "MLOps" - data pipelines, airflow, that kind of stuff.

    Both of those are different from each other, and also different from being a developer/SWE etc.

    Its a bit annoying to me how these things have become segmented, I kind of preferred when it was all just "programming" or "computers" and most people did most things, but unfortunately these days the market is quite segmented / specialized, and the key to getting any particular job is to already be familiar with the popular tools in that space.

  • yol 14 hours ago
    I'm curious, what's the reason for you to move toward more system-oriented work? Is it because you're looking for a way of career progression?

    If so, I'd suggest you have some in-depth conversation with your manager and your mentor (if you have one), to identify area of skill developments for you, and opportunities for "learning on the job". And if your current situation/management won't afford you that opportunity, you should focus on finding a new job, which should be fitting for your current skill set, but with clear space for doing something more.

  • gokuljs 17 hours ago
    And this is what I am doing right now, like I am just reading the DDIA book and writing the raft consensus algorithm in Go just for learning purposes
  • gokuljs 17 hours ago
    [dead]