Breaking into Kernel Engineering from a backend application background

I’ve spent ~10+ years working primarily in backend application development, with a few years doing infrastructure at both small and large companies.

I’ve always been interested in computer architecture and operating systems, but never pursued that path deeply. Lately, I’ve been considering a shift toward lower-level, systems-oriented work.

I’m trying to better understand what this transition actually looks like in practice, specifically:

  • What career paths exist under “systems engineering” (e.g., kernel, performance, distributed systems, HPC, etc.)
  • How people coming from a backend/infrastructure background make themselves competitive
  • What the most effective way is to ramp up (projects, courses, specific topics, etc.)

Some roles that caught my attention:

  • Kernel engineering
  • AI / ML performance engineering
  • Low-latency / high-performance systems

Concerns:

  • Many of these roles seem to prefer candidates with an EE or deeply specialized background
  • Unclear how realistic this transition is without going back to school
  • Availability of roles that are remote or NYC-based

Posted Apr 3, 2026, 4:51 PM UTC

30
Loading comments…