This is actually a non-issue (or at least a minor issue for extremely long pages) on a Mac, because macOS has system-wide kinetic scrolling and all Apple input devices use touch sensitive surfaces for scrolling.
Not saying you're wrong, it's certainly annoying on mobile devices (compounded by the narrow screens and responsive content).
You can always click on the scroll bars -- invisible doesn't mean they don't exist, they simply go out of the way when they're not needed (i.e. most of the time / when not scrolling). You can do that on iOS and Android as well, tap and hold on the scroll bar to quickly scroll through an entire document.
It's trivially easy. Just put your mouse at the edge and move the scroll wheel. You can then click it. There is also an option in System Preferences to change this behavior and always show the scroll bars. Since this motion is more intuitive on a trackpad than on a mouse, scrollbars always show when using a mouse by default.
I really hate it too, I don't understand why they do this... Even using Chrome on mac I can't scroll properly if I'm not fast enough to catch the scrollbar after a light scroll.
My latest system design interview was: design this app. Dude was like "I'm expecting you to lead the conversation". I was like, bitch there's a million things to talk about, at some point you have to tell me where you want the convo to go. Needless to say I failed, when I'm probably overqualified for the job, but heh...
I don't think you're overqualified. I'm not a systems designer by any means but here's how I'd lead this conversation:
"Ok cool. Before we get started, let me understand some non functional requirements. How many concurrent users do we expect? Is brief downtime acceptable?"
Then you listen to the answer.
Then you say "ok cool. So given what we just estsblished, it's making me lean towards X type of architecture. Here are trade-offs A,B, and C that are involved. Does this make sense to you so far?"
You listen to their answer. They will 100% of the time indicate to you if you are on the right track or missing something.
Then you go "ok cool. So on the high level we are going to have (for example) a client, a server, a proxy, a database, etc . Given what we discussed, I think the most complex part of the system will be X so let me begin by thinking through that and then we can pop back up to other parts. Does that sound good to you?"
Etc.
I am not looking to make you feel bad but being able to have this conversation in this way is a baseline skill of a senior engineer. Compare that to what you actually did and ask yourself if it's you or the "bitch" that has room to improve here.
I had this for my current job. I was asked to design Facebook and it just ended up being nearly entirely about how to design a notification microservice. Got the job so it evidently worked, but I was just going on in a direction until told to stop.
If you specifically mean files you can try https://www.sharedrop.io to share files in the browser (I'm not affiliated in any way, just an occasional user.)
I think we should create some rules:
- if there's an animation/wait time to get to a UI, it's crap
- if users have to be fast to get to a UI, it's crap