Ask HN: What is your best type of technical interview?

I encountered several types of interview through companies of different values (small startup to big tech). First kind is Leetcode-style interview where your task is to write algorithm/data structure to solve given problems. Second kind discards algorithmic problems treating them as "uneffective" method to choose developers who can produce maintainable, well scalable code. They prefer problems focusing on knowing execution environment like "make autocomplete work for this React template", spaghetti-mess of setTimeout/promises in JS etc. Third kind don't ask coding problems from mature developers at all, they only talk about architecture/internal mechanics of programs from previous jobs or pet-projects of applicant. And asking theoretical questions for basic knowledge of developed systems like "what happens if I type a link in browser's address input and then press "Enter"?". They think that you can't detect good developer by how much of execution environment internals or algorithms they know/they can design, but by their high-level ability to build business programs and systems. It is biasly assumed that interviewee already knows some basics of execution environment and algorithms. Etc.

What style of technical interview do you prefer and what are objectives for that?