u/Ok_Pin_9155

I'm a software engineer with 10+ years of experience (mostly backend, with a few years on infrastructure teams) and I'm trying to transition into GPU infrastructure or GPU performance engineering.

The problem is I can't figure out what role I should realistically target.

It feels like a chicken-and-egg problem. Many jobs want years of GPU/HPC experience or a master's degree, but I don't see many master's programs that actually prepare someone for these roles. Are employers asking for master's because it demonstrates a candidate's ability to handle rigorous workloads? Or are there actual master's programs that prepare you for this career path.

I moved into infrastructure because I wanted to be closer to systems, but much of that work eventually became operational (provisioning access, keeping services running, etc.). I'd rather be building the infrastructure than operating it.

I'm in the NY/NJ area and struggling to identify a realistic goal Should I be aiming for GPU infrastructure, HPC, performance engineering, or something else that serves as a bridge?

I'm also overwhelmed by the number of topics to learn. CUDA, Linux internals, computer architecture, kernels, networking, distributed systems, profiling tools... I learn best with structured paths, but right now I don't know what to double down on.

For those already in these roles:

• What job title or companies would you target if you were in my position?
• What projects actually helped you break into the field?
• Is a master's degree worth it, or is project experience enough?
• If you had six months to prepare, what would you focus on?

I have 10+ years of software engineering experience, mostly backend and infra development.

Lately I’ve become interested in GPU infrastructure, HPC, performance engineering, and eventually GPU programming. I’ve been reading books like AI Systems Performance Engineering, Programming Massively Parallel Processors, and Computer Architecture: A Quantitative Approach.

The problem is that every time I look at job descriptions, I end up with a completely different list of skills.

Some roles want:

• CUDA and GPU kernel optimization
• Computer architecture knowledge
• NCCL, RDMA, InfiniBand
• Kubernetes and Slurm
• Distributed training
• Performance profiling and benchmarking
• Linux kernel knowledge
• Cloud infrastructure

Other roles seem much more focused on operating GPU clusters and supporting AI workloads at scale.

I’m considering doing a master’s degree, but even when I look at programs like OMSCS, Computer Engineering, or Systems-focused master’s degrees, it feels like they teach foundational concepts but not necessarily the practical skills companies are hiring for.

As someone coming from a traditional software engineering background, I’m struggling to identify:

1. What skills are truly foundational versus “nice to have”?
2. If you had 6–12 months to prepare for GPU infrastructure or GPU performance engineering roles, what would you focus on first?
3. Did a master’s degree help you break into this field, or was self-study and project work more valuable?
4. For those already working in GPU infrastructure, ML infrastructure, HPC, or GPU programming, what did your path actually look like?

Right now it feels like there are five different careers hiding behind the phrase “GPU engineer,” and I’m trying to figure out which path is the most realistic transition from a backend/infrastructure background.

I’d appreciate hearing from people who made a similar transition.

I have 10+ years of software engineering experience, mostly backend development, with a few years working on infrastructure/platform teams.

Lately I’ve become interested in GPU infrastructure, HPC, performance engineering, and eventually GPU programming. I’ve been reading books like AI Systems Performance Engineering, Programming Massively Parallel Processors, and Computer Architecture: A Quantitative Approach.

The problem is that every time I look at job descriptions, I end up with a completely different list of skills.

Some roles want:

• CUDA and GPU kernel optimization
• Computer architecture knowledge
• NCCL, RDMA, InfiniBand
• Kubernetes and Slurm
• Distributed training
• Performance profiling and benchmarking
• Linux kernel knowledge
• Cloud infrastructure

Other roles seem much more focused on operating GPU clusters and supporting AI workloads at scale.

I’m considering doing a master’s degree, but even when I look at programs like OMSCS, Computer Engineering, or Systems-focused master’s degrees, it feels like they teach foundational concepts but not necessarily the practical skills companies are hiring for.

As someone coming from a traditional software engineering background, I’m struggling to identify:

1. What skills are truly foundational versus “nice to have”?
2. If you had 6–12 months to prepare for GPU infrastructure or GPU performance engineering roles, what would you focus on first?
3. Did a master’s degree help you break into this field, or was self-study and project work more valuable?
4. For those already working in GPU infrastructure, ML infrastructure, HPC, or GPU programming, what did your path actually look like?

Right now it feels like there are five different careers hiding behind the phrase “GPU engineer,” and I’m trying to figure out which path is the most realistic transition from a backend/infrastructure background.

I’d appreciate hearing from people who made a similar transition.

I have 10+ years of software engineering experience, mostly backend development and infrastructure.

Lately I’ve become interested in GPU infrastructure, HPC, performance engineering, and eventually GPU programming. I’ve been reading books like AI Systems Performance Engineering, Programming Massively Parallel Processors, and Computer Architecture: A Quantitative Approach.

The problem is that every time I look at job descriptions, I end up with a completely different list of skills.

Some roles want:

• CUDA and GPU kernel optimization
• Computer architecture knowledge
• NCCL, RDMA, InfiniBand
• Kubernetes and Slurm
• Distributed training
• Performance profiling and benchmarking
• Linux kernel knowledge
• Cloud infrastructure

Other roles seem much more focused on operating GPU clusters and supporting AI workloads at scale.

I’m considering doing a master’s degree, but even when I look at programs like OMSCS, Computer Engineering, or Systems-focused master’s degrees, it feels like they teach foundational concepts but not necessarily the practical skills companies are hiring for.

As someone coming from a traditional software engineering background, I’m struggling to identify:

1. What skills are truly foundational versus “nice to have”?
2. If you had 6–12 months to prepare for GPU infrastructure or GPU performance engineering roles, what would you focus on first?
3. Did a master’s degree help you break into this field, or was self-study and project work more valuable?
4. For those already working in GPU infrastructure, ML infrastructure, HPC, or GPU programming, what did your path actually look like?

Right now it feels like there are five different careers hiding behind the phrase “GPU engineer,” and I’m trying to figure out which path is the most realistic transition from a backend/infrastructure background.

I’d appreciate hearing from people who made a similar transition.

I have a bachelor’s degree in computer science and about 10 years of software engineering experience, mostly in application/backend development with a few years on infrastructure teams.

I’ve always enjoyed computer architecture, operating systems, and lower-level systems topics, so I’m considering using OMSCS to revisit that part of the stack in a more structured way. I’m especially interested in whether the Computing Systems specialization could help me move toward roles such as:

• GPU infrastructure engineer
• GPU performance/optimization engineer
• HPC software engineer
• Systems/performance engineer
• Infrastructure roles closer to hardware, compilers, or distributed systems

I’m still early in exploring the exact path, and I’m trying to decide whether a formal CS master’s program would be more effective than self-study for building depth in systems, architecture, and GPU computing.

For those who completed or are pursuing the Computing Systems specialization:

1. What career paths did it realistically open up for you?
2. Did it help you become better prepared for systems-oriented interviews or roles?
3. Which courses were most useful for moving into lower-level systems, performance, GPU, or HPC-related work?
4. Were employers receptive to OMSCS as evidence of systems depth, or did projects/work experience matter much more?
5. Looking back, would you choose this specialization again for a systems career pivot?

I currently have the time to dedicate seriously to learning, so I’m trying to understand whether this specialization is a strong path for leveling up or whether I should focus on a targeted self-study/project route instead.