Senior interviews add design pressure: an injected clock so the code can be tested, a priority queue instead of a sort, a structure that does O(1) work per item, or async code that must respect a concurrency limit and keep results in order. State the cost before you write, and keep the code testable; these problems come with hidden tests on timing edges and ties.
Work the way you would in the room: say what the input looks like, pick the edge cases first (empty input, one item, duplicates, large values), state the time and space your solution needs, then code. Each problem has hidden tests on exactly those edge cases.