You basically can't refactor reliably without static types, you can't navigate the codebase quickly without static types, and it makes it more difficult to understand other people's code without static types.
What a great interview test. I’d absolutely not hire someone that can’t do that. It also doesn’t make any sense. That’s like saying entire codebases without types can’t be worked on. Huh? Those are basic things you can do in any language.
This Typescript anointing has got to die. It’s lame, and most of you overuse it even when it’s appropriate.
I said reliably. Without static types in large codebases you are likely to miss things. E.g. you rename a variable but don't catch everywhere you should have updated it.
Don't say "but tests".
If your data model is open and not closed you only need to change the location you are changing. This is how the internet works. Types that don't support this model actively hinder refactoring.
Ifv you include the artificial restriction of not "use the correct tool/tests", then maybe you are right.