This is probably why you are getting downvoted. Squabling about semantics / gatekeeping what counts as systems-programming isn't useful. It probably doesn't answer OPs question, and it is rather rude to assume that what OP meant by "systems programming" is wrong just because it is different from what you mean by "systems programming".
edit: maybe it was your dead comment that caused the downvotes.
There are a lot of neat, and not-too-intimidating things that will give you a good appreciation of the techniques used in systems programming you don't see in other areas. Eg reading technical documentation (datasheets, Reference Manuals etc), reading and writing registers, familiarizing yourself with memory layout, and communications protocols. Writing a HAL to see how you can abstract over register writes to make high-level code.
In other words, I agree, and don't think this post's parent was gatekeeping; it's the definition I had assumed as well.
The OP asked about System Programming not System software.
Driver is an interface and you can write application software on top of it.
I don't think this is system programming rather network programming.
You should try embedded or try to write drivers
Better yet write a mini OS your own that interface with hardware
Edit: Wow, I'm getting down voted. I guess political correctness