Don’t you brainstorm your ideas, communicate them, and discuss tradeoffs *before* writing any code in your interview? I hope you do; if not, you probably won’t pass, which is why they always call for ‘thinking out aloud’.
Researching is tricky to evaluate in a 45 min interview though.
Look, none of the existing interviewing systems is perfect (you can probably find a bunch of Hacker News/Reddit posts whining about this). Tons of great engineers (e.g., homebrew author) fail in Google/FaceBook interviews. But my point is the system exists for a reason: it’s probably the most efficient and fairest one you can come up with.