The data is digital, it's 1s and 0s, that's digital. And most software types never worry about data storage, that's under the hood stuff for hardware driver developers. In the world of software if you don't learn anything about under the hood until you take classes that are on under the hood stuff, it's a black box until then, something you don't have to worry about how it works just understand the API calls to put stuff there and get it back. And there's nothing wrong with black boxing stuff too complicated for the level of the student.
The stored data is NOT 1's and 0's. You must have the proper circuits to analyse the voltage patters and extract the data from the disk.
This is unrelated to the discussion, but back about 1982 I has a Trash-80 computer that used cassette tape for storage. It was incredibly slow, and several people wrote alternate storage routines. I typed in one such assembly language routine from a magazine and wound up debugging it, due to a typo.
This was an interesting process. The tape signal was noisy, and the program had to filter the raw signal.
AS a result of this I have enormous respect for the folks who have packed hundreds of gigabytes into cheap disk drives.