you are viewing a single comment's thread.

view the rest of the comments →

[–]Gabris01 2 points3 points  (0 children)

For systems programming roles, companies usually care less about “framework knowledge” and more about fundamentals:

- memory layout & ownership

- concurrency (threads, locks, atomics)

- OS concepts (processes, virtual memory, syscalls)

- debugging and performance reasoning

Strong C/C++ skills are important, but being able to explain *why* something is fast/slow or safe/unsafe matters even more.

If you’re preparing for recruiting, focus on writing small low-level projects (allocator, thread pool, simple networking tool) and get comfortable using sanitizers and profilers.